Pricing
Every day an account sits between sold and live costs you real money. Thread cuts those days, measures the savings against your own baseline, and takes 10% of the savings your systems verify. You keep 90%. Start in beta: $1.25 per verified outcome, no platform fee, no setup fee.
Two ways in, always in this order
30 days on a live slice of your base, at the beta rate. No platform fee, no setup fee, and the pilot measures the baseline the savings share is later priced against.
We measure the days Thread cuts from time-to-live against your own baseline, price your cost of a stalled day together, and bill 10% of the savings your systems verify. If it churns inside 30 days, it's clawed back.
The math
Tell it how long going live takes today, the rest is defaults you can edit. The 30% cut is what Customer.io measured on their onboarding cycle; $16 a day stands in for your real cost of a stalled account until the pilot measures it. Whatever the savings turn out to be, you keep 90% of them.
The 30% cut is the default because it's what a customer measured; your pilot earns your own number. Savings verify the way outcomes do: a fresh read of your systems, on your baseline, audited line by line.
How billing works
Savings are measured, not asserted. The baseline days-to-live comes from your own history and the pilot's holdout. The days Thread cuts, and the dollars they're worth, are computed from your systems, and the fee is 10% of that number, nothing else.
An outcome is a read, not a claim. A guide never bills on "the customer said it's done." The outcome closes when a fresh read of your warehouse or CRM shows the record flipped, usage rows, config flags, the state you defined up front.
Hand-confirmed closes are counted apart. Some outcomes can only be confirmed by a person. When a human closes one instead of a system read, it's marked separately in the count, you always know which is which.
The audit log is the invoice's backup. Every line item traces to the read that closed it: what was checked, when, and what it returned. Finance can audit the bill the same way you audit the motion.
Questions
Three numbers, all yours: your baseline days-to-live (from your history, checked against the pilot's holdout), the days Thread cut, and your cost of a stalled account per day, priced together before the first invoice. Savings = days cut × cost per day × accounts. Thread's fee is 10% of that; you keep 90%. Anything that churns inside 30 days is clawed back.
That's the beta rate, and it's what the 30-day pilot runs on: $1.25 per verified outcome, no platform fee, no setup fee. It's time-boxed beta pricing, not the long-run model; the pilot's job is to measure the baseline the savings share is priced against.
Whatever state change you define before the motion starts, module live, first transaction, install kept, milestone hit, confirmed by a fresh read of your system of record. A customer saying "I set it up" is a lead, not a close. The guide reads your warehouse or CRM, and only a confirmed flip counts.
Then the pilot cost you very little, because you only paid for outcomes your systems confirmed. You keep the day-30 readout and the full audit log, and there's nothing to unwind, no platform fee, no setup fee, no annual commitment hiding behind the trial.
No. The holdout gets no outreach, so it generates no verified outcomes and nothing to bill. It exists for one reason: so the lift you see is measured against a matched group, not against last quarter's memory.
Your system of record for the outcome in question, a warehouse like Snowflake, a CRM like Salesforce or HubSpot, product telemetry, billing, OSS. If a system your team already trusts holds the truth, the guide can read it. The verification read is defined with you before the first touch goes out.
The pilot is 30 days, priced per verified outcome, and you can walk away clean at the end. If the readout earns it, we move to the standard model: 10% of the savings your systems verify, with the baseline and the cost-per-stalled-day agreed in writing first. The terms are set before the pilot starts, so the day-30 conversation is about the numbers, not the paperwork.
The numbers are registered to your brand, and the guide texts and calls as you, under your consent posture. Consent is attested before the first touch, quiet hours run on the customer's local time, and STOP ends it instantly, the floor is enforced in the runtime, not in a settings page.
Start here