How to ask who the client contract is before you take a remote job (2026)

Here is the easy idea first: your job can be remote and still end when someone else’s hospital contract ends. Before you accept, ask who the client (or main customer) is, and what happens if that contract ends.

This is a job-seeker piece. For country and authorized-to-work language, use How to tell if a remote job will hire you from your country (2026). For the five card filters, use How to filter remote jobs before you apply (2026). For how to read a board itself, use How to pick a remote job board in 2026. For cameras and keystroke scores, use How to ask about monitoring before you apply to a remote job (2026).

A public example of client-contract risk

In mid-September 2026, Healthcare Dive and Becker’s Hospital Review reported on a Texas WARN notice for Conifer Health Solutions, Tenet Healthcare’s revenue-cycle arm. Hoodline covered the same Dallas-linked cuts.

As those outlets report the notice, Conifer will lay off 1,037 primarily remote employees, effective November 2, 2026. The cuts are expected to be permanent, with no bumping rights. People report to Conifer’s Dallas office organizationally, but the roles are mostly remote across the United States.

The timing is the seeker lesson. CommonSpirit Health’s service contract ends October 30, 2026. That follows a February 2026 deal in which CommonSpirit exited early, left its stake in Conifer, and moved to bring revenue-cycle work in-house. Treat the headcount and dates as reported from WARN and press, not numbers we audited.

You do not need to work in hospital billing for the tip to matter. A role can be fully remote and still sit on one client’s contract. When that client walks, the remote seat can vanish with it.

What to look for before you accept

On the job description and in recruiter chat, scan for:

• Vendor or staffing language: you work for Employer A, but day-to-day work is for Client B (a hospital system, bank, or big brand).
• Single-client revenue risk: the posting or chat leans hard on one named account, or the team exists mainly to serve that account.
• “Our client is…” talk: write the name down. If they will not name a main customer book, that is also a signal.

None of these lines prove the job is bad. They do prove you should ask what happens if that contract ends before you resign from something safer.

Three questions to ask early

Ask in the first recruiter chat, or in email if there is no chat, before you treat the offer as solid:

1. Who: Who is the main client or customer book for this role (or this team)?
2. Share: Roughly what share of the role (or the team’s work) ties to one contract or one customer?
3. If it ends: What happens to people in this role if that contract ends or is not renewed?

Write down the answers. A company that cannot say who the work is for is asking you to guess. Guessing is how people learn about a client exit on a WARN notice instead of in an interview.

How this fits the other remote filters

Client and contract risk sits next to the filters you already run:

1. Card eligibility (country / region).
2. Actually remote (not hybrid dressed as remote).
3. Salary you can see.
4. Overlap you can live with.
5. Employment type that works where you live.
6. Monitoring you can live with.
7. Client / contract risk you can live with.

A role can clear “100% remote” and still fail you on single-client exposure. That is a valid reason to pass, or to negotiate a clearer runway. Remote removes the commute. It does not remove the contract behind the seat.

What Remote Army shows today

Remote Army is a curated 100% remote board. Seekers are free forever. Browse live roles on the homepage and jobs by location.

We store location and region. Who-can-apply is not on every card yet. Client contracts and “what happens if the account ends” are almost never on the card. You still have to ask in the job description and the interview. That is the honest row.

Start with the card. Ask who the client is. Then apply on Remote Army.