Sword's Filing Says 579 Headspace Staff. Only 345 Are in Cut Range

If you want Headspace's engineers, product leads and senior clinical-ops people, the headline figure of 579 employees will mislead you about how many are actually in play. A little over two weeks after Sword Health's deal for Headspace officially closed, Behavioral Health Business reported that post-transaction layoffs had started, and the reporting gave no count of who was cut.

The deal filings give you a better count than the news coverage does, provided you read past the headline figure to the line underneath it.

Why 579 is the wrong number to count against

Only 345 of Headspace's 579 US employees work for Headspace, Inc., the corporate entity where the cuts were planned. The other 234 belong to Headspace Medical Group, and the deal documents say patient care is not expected to be touched.

Behavioral Health Business reported that Sword employed 624 people in the US before the deal and Headspace added 579, for a combined 1,203 before layoffs. Healthcare Dealflow first spotted the Massachusetts HPC filing on the deal. The entity-level split is in a different document, Oregon Health Authority HCMO Transaction 090, which was approved on September 28, 2026.

Two details in that table do most of the work:

• The medical group is mostly part-time. It has 234 people but only 80 full-time equivalents, a 34% ratio. An FTE (full-time equivalent) is total hours worked expressed as a number of full-time staff. This is mostly part-time staff, not a corporate team.
• The filing walls off the clinic. Cuts are "expected to be limited to corporate functions and are not expected to affect patient care, customer or payer relationships," per the filing as reported by Healthcare Dive.

That makes Headspace, Inc. 59.6% of the 579, and it is the realistic upper limit on who can be cut.

The counts don't fully reconcile

Treat every number here as a range. Earlier Behavioral Health Business reporting said Headspace employed about 598 people, 418 of them full-time. On Sword's side, the Oregon notice lists Sword Health, Inc. at 203 and Sword Health Care Providers, P.A. at 372, and the listed entities add up to 614, not the 624 in the deal coverage. None of that changes the shape of the problem. You have a corporate layer of roughly 345 people, and that layer is where Sword is looking for redundancy.

Where Sword's "duplicative corporate functions" overlap

The overlap is between Headspace, Inc.'s 345 corporate staff and Sword Health, Inc.'s 203 US corporate staff. Engineering is probably the biggest duplicate because Sword builds its product in Porto. That second point is my inference. The filing doesn't say it.

The plan was in the documents from the start: "Sword anticipates reducing its corporate staff to create efficiencies where redundancies exist." The question is which functions count as redundant, and the answer depends on where the buyer already has the work covered.

Revelio Labs estimates Sword has about 1,575 employees worldwide, with 409 in engineering (26.0%), and lists the headquarters as Porto, Portugal. Glassdoor puts pay for a Senior Software Engineer at Sword in Porto at €35K to €44K a year. When the buyer runs a centralized engineering org at that cost, the target's San Francisco engineering and product teams are the obvious place to look for savings.

Here is roughly how exposure ranks by function:

1. US engineering, product and design. Highest exposure. Sword's Porto org already does this work, and Headspace's teams would be a parallel cost.
2. G&A (finance, marketing, communications, people ops). High exposure. Sword's 203-person US corporate entity already exists, and Headspace, Inc. is 1.7x its size, so there are more seats to consolidate than to keep.
3. Clinical operations and payer-facing roles. Lower exposure, because the filing's own language protects patient care and payer relationships.

The leadership list fits this reading. CEO Tom Pickett, COO Karan Singh, chief clinical officer Dr. Jenna Glover and chief people officer Lisa Mulrooney Gross all kept their roles. Sword founder and CEO Virgílio Bento kept a full Headspace executive team, so the layer being thinned is the one below it.

Why a HIPAA keyword filter finds the wrong people

Engineers rarely list compliance frameworks as skills, so filtering on "HIPAA" misses most of the people you want. In Refolk's index, only 260 US software, senior and staff software engineers list HIPAA as a skill. That is fewer than the 345 people at Headspace, Inc. alone.

1.33x

Product managers tag it more often. Refolk's index has 304 US product managers, senior PMs and directors of product who list HIPAA, or 1.17 PMs for every engineer. Listing a compliance skill is a PM and compliance habit. Engineers list their tech stack, so an engineer who spent years handling regulated health data at Headspace may never write the word "HIPAA" on a profile.

The keyword also skews toward a particular kind of employer. The top employers among HIPAA-tagged engineers in Refolk's index are UnitedHealth Group, Google and CVS Health. Among PMs, Oracle leads (5 of 25 in the sample), followed by Cognizant and athenahealth. If you're trying to hire digital health engineers who have shipped a consumer mental health product, the keyword pushes you toward payers and enterprise vendors and away from the Headspace people you actually want.

So HIPAA software engineer recruiting done by keyword returns a thin list from the wrong kind of company. The fix is to search by where people worked.

Source by employer history, not compliance keywords

Build the list from where people worked and what data they handled, then confirm regulated-data experience in the first conversation. Employer history at Headspace is a better signal than a skill tag, because the tag depends on whether someone bothered to write it down.

A practical sequence:

1. Pull US profiles with Headspace in their employment history, plus the older names that appear on earlier profiles: Ginger and OrangeDot.
2. Strip the false positives. In Refolk's index, 856 US profiles have "Headspace" in their headline, but only 8 of a top-25 sample list Headspace as their current employer. The rest include Leadspace and Headspace Real Estate.
3. Split by function. Put engineering, product, design and G&A in the first wave. Keep clinical ops separate, because its exposure is different.
4. Split current from former. People who left during the 2023 or 2024 rounds are reachable now and know who is still there.
5. Confirm regulated-data exposure on the call. Ask what data they touched and which controls they built. A single answer tells you more than any profile tag.

Steps 1 and 2 take the most manual time, because the "Headspace" string catches every company with a similar name. That is the gap Refolk closes. You describe the person in plain English and get back a ranked shortlist with the lookalike companies already removed.

How to read the director-level leaver posts

Treat each director's leaver post as a map to a team, not as a single candidate. Social posts suggest the cuts landed at director and senior levels while the C-suite stayed, so the people posting are the ones who ran teams and know which of their reports are good.

The titles in Refolk's top-25 Headspace headline sample show which layer is affected: Senior Director of Product Management, Head of Support, SVP Marketing & Communications. These people hire. Each one you place is a referral route into a team that may get cut in a later round.

Signals worth reading in a leaver post:

• Past tense or "ex-Headspace" in the headline. Headlines are self-reported and lag reality, so a recent edit tells you something.
• Tagged former reports. Directors often name the people they want placed. That is a warm list handed to you.
• Scope language. "Led mobile platform" or "owned payer integrations" tells you which side of the overlap they were on.
• Silence from the team. If a director posts and their reports don't, the reports are probably still employed, and still exposed.

Hire the director in week one and you have a referral line into the team Sword cuts next.

Why this pool is stronger than a typical layoff list

The people at Headspace in October 2026 had already survived three rounds of cuts: 4% in December 2022, 15% in July 2023 and 13% in November 2024. That is a filtered group, and they have been working on thin teams since.

A typical layoff list mixes strong and weak performers because cuts follow org charts, not ratings. Someone who kept their seat through three rounds, then lost it because Sword has a Porto team doing the same job, is a stronger candidate than a random name on a layoff list.

Clinical ops has its own angle. In March 2025, Headspace moved clinical delivery to a flexible contractor network. Senior clinical-ops people there know how to run a contractor clinician network. Sword runs a full-time-clinician model and doesn't use that skill, so it is worth more to a company that runs on contractor clinicians than it is to Sword.

Compensation may also work in your favor. Headspace has fallen far from its $3 billion 2021 valuation, so equity granted near the peak is unlikely to be what keeps anyone in their seat. A competitive cash offer has less to compete against.

Timing: get there before the next integration round

Contact the directors now and plan a second wave for their reports, because Sword did not comment on whether more layoffs would follow. The people still inside are the ones you can reach before a competitor does.

A workable cadence:

• This week: directors and senior ICs who have posted publicly. They are available and they control referrals.
• Next two to four weeks: their former reports in engineering and product, introduced through the director you just engaged.
• Ongoing: re-run your Headspace employment-history search every week to catch people who update their profiles after a later round.

For healthtech product manager sourcing in particular, use the 304 HIPAA-tagged PMs in Refolk's index only as a calibration set. Then widen to everyone who held a product title at Headspace, Ginger or OrangeDot. In Refolk, the weekly re-run is the same plain-English sentence, run again.

FAQ

How many people were cut in the Headspace layoffs?

The reporting so far gives no number. The filings put Headspace at 579 US employees, but the Oregon HCMO notice shows only 345 of them work for Headspace, Inc., the corporate entity where cuts were planned. That 345 is the realistic ceiling, and the actual number is probably well below it.

Are Headspace clinicians affected by the Sword Health Headspace layoffs?

The filing says cuts are "not expected to affect patient care, customer or payer relationships." Headspace Medical Group has 234 people but only 80 FTEs, so it is mostly part-time staff, and it falls outside the planned corporate reductions. Senior clinical-ops managers on the corporate side are a separate group and could still be exposed.

Do I need HIPAA on a profile to hire digital health engineers?

No. In Refolk's index only 260 US software engineers list HIPAA as a skill, fewer than Headspace, Inc.'s corporate headcount, because engineers list their tech stack instead of compliance frameworks. Source by employer history at regulated companies and confirm regulated-data experience in the first conversation.

Will Sword cut more Headspace staff later?

Sword did not comment on whether more layoffs would follow. The filings say corporate reductions were planned from the start, and the overlap with Sword's Porto engineering org suggests US engineering and product remain the most exposed. Treat the people still at Headspace as a second-wave pipeline.