Is Motions a separate product?

Motions is the harness inside Thread. It runs on the same platform, reads the same connected systems, and drives the same guides, you don't choose between them.

How is a Motion different from workflow automation?

Workflow rules are if-this-then-that. A Motion holds a goal and lets guides pick the next step from the account's actual state. Stages exit on reads of your systems, a fresh record, not a completed send.

Does a Motion run on my own data?

Yes. A Motion reads the systems you connect, CRM, warehouse, product telemetry, to ground the guides and to check exit criteria. It stays within the permissions you set, and every read is logged.

What does Motions cost?

A platform fee plus $1.25 per verified outcome. The 30-day pilot is priced per verified outcome only.

How do I get access to Motions?

Motions is in private preview, running with a small set of design partners. Book a 30-day pilot and we'll run your first Motion on a real cohort.

Workflows

Every account down the right path.

A workflow is the routing layer inside a Motion. It reads each account's actual state, plan, segment, stall point, warehouse facts, and sends it down the right branch, so the right guide engages at the right moment with the right play. Described in plain language, compiled into a graph you can read. Branch on facts, not guesses.

Workflow builder · described, then compiled

Builder

promptDesign the motion: enterprise onboarding

compiling…

9 steps5 automated1 human approval

if enterprise

if self-serve

Startclosed-won in CRM

Assign playbookenterprise template

Create portalcustomer workspace

Compliance reviewhuman approval

Create portalself-serve setup

Request documentspacket + reminders

Guide goes livefirst text, with consent

✓ playbook compiled, every account after this runs it

Describe the motion in a sentence; the builder compiles the branches, the human gates, and the verified exit. Every account after this runs the same playbook.

An automation tool moves data between apps. A workflow moves an account toward live, and proves it arrived.

Routing

Reads state. Routes accounts. Gates the risky steps.

Branch on what's true. Enterprise or self-serve, stalled at KYB or stalled at setup, the branch condition is a read of your CRM and warehouse, not a static list uploaded last quarter.

Human gates where they belong. Compliance review, pricing exceptions, every outbound dial: any step can require a named human's approval before the workflow proceeds. No batch overrides.

Waits, retries, and patience. Workflows hold state for weeks. No reply Tuesday means a different touch Friday, on the recipient's clock, inside quiet hours.

Exits are verified. A branch completes when the system read confirms its outcome, the record landed, the module is live, the unit is open. Never when the messages ran out.

Change once, everywhere. Edit the workflow and every account behind it follows the new playbook, with the change logged for the audit trail.

Measured

Every branch reports against the baseline.

Each path in the workflow rolls up to the same outcomes view: enrolled, engaged, verifying, done, reported against your pre-Thread baseline. Done turns green only when a fresh read of the warehouse confirms it. The routing is inspectable, and so are its results.

thread · outcomes

8.2median days to value

−30%vs your baseline

183verified done

illustrative cohort · the report and the verification are the same read

One system

Workflows route. Guides work. Motions hold it together.

The agent

Guides

Long-lived resident agents, one per account, grounded in your knowledge base, speaking text, email, and voice.

Meet the guides The harness

Motions

Holds the goal, the context, and the exit criteria at every stage, and closes outcomes on a fresh system read.

Explore Motions The router

Workflows

Reads each account's state and routes it down the right path, so the right guide engages at the right moment.

See the builder

See all features →

Start here

Your first workflow compiles in the pilot.

In the 30-day Verified Activation Pilot we describe your motion together, compile the workflow, and run it on 50–100 real accounts against a holdout, priced per verified outcome. Start by building your agent, it takes about a minute.