For PE-owned B2B SaaS & operating teams
If the onboarding team is the req you keep approving, the motion doesn't scale. Thread puts a guide on every new account, activation chased to done and verified in product telemetry, while your CSMs judge instead of chase.
bookable to EBITDA, proved on your own data
Illustrative portfolio. Each lane is one company's motion; green is verified activation read from that company's own telemetry. One playbook, run and proved N times.
The gap
CSMs are judged on NRR and staffed for chasing. Most of an onboarding team's week is follow-ups, checklist nudges, and "did you connect it yet", work that scales with accounts, not with skill.
Activation is a telemetry event, not a meeting. The product already knows which accounts hit first value. Most onboarding motions never read it, they close on a call instead.
Stalls are silent until renewal. An account that never activated shows up in the NRR number four quarters later, when the save is expensive.
How the motion runs
Every closed-won account gets a guide at kickoff, loaded with the deal context and the activation checklist. Consent attested before the first touch.
Setup steps chased, data collected, integrations walked through, by text, email, and phone. The CSM is pulled in for judgment calls, not for follow-up number nine.
Activation is read from product telemetry, first value event, usage threshold, never taken from a kickoff-call promise. "They said they're live" is a lead, not a close.
The account flips activated on the record, counted apart from hand-confirmed closes. The NRR math changes at the top of the funnel, where it's cheap.
One playbook, N companies. A 30-day pilot per portco, metered per verified outcome, AI you can book to EBITDA, proved on the portco's own data, not a vendor deck.
The sponsor's seat
Legacy software companies live on installed bases, and installed bases live on attach and adoption. Pick the portco with the most obvious stuck number, entitled-but-inactive, signed-but-not-onboarded, and run the pilot there. The day-30 readout is lift vs. holdout and cost per verified outcome: numbers an IC memo can carry. Then hand the playbook to the next portco.
Native to your world
The value-creation plan dies in portco inboxes. Guides carry it into every company the same way, and the board pack reads adoption from the systems, not from management’s slides.
More of your world
Guides carry the value-creation plan from day one, and the reporting writes itself, because every number in the pack is a read from the portco’s own systems.
What you're buying
Guides, long-lived resident agents, one per account, each with its own memory and a single goal it pursues across text, email, and voice.
Motions, the harness over the lifecycle: it holds the goal, the context, and the exit criteria at every stage, and reads your systems to close outcomes.
Voice Studio, design the voice agent beside the guide: persona, guardrails, knowledge, a phone number that answers as your brand.
Workflow builder, routing and segmentation: reads each account's state and engages the right guide at the right moment.
See it in detail, Motions, the full feature set, or call the live guide: the product answers the phone.
The floor
Every touch consent-first, quiet-hours-aware, logged, and auditable, enforced in the runtime, not a policy PDF. The same log that runs the motion answers the diligence questionnaire.
Add your own rules on top. The floor never comes off.
Proof
Customer.io cut onboarding cycles 30% and approved ~$1.4M in expansion value with this motion.
a named B2B SaaS logo, verified on their own systems
A national point-of-sale platform runs this motion on merchant activation today.
anonymized · installed-base activation at long-tail scale
Start here