Map your client's AI workflows. Then hand them over.
Build the runbooks in your own workspace with your AI, walk your client's team through them, and transfer the runbooks to your client's workspace when the work is done. The client owns them, and you keep a free seat there.
You build it. Your client owns it.
Stepflow is built for the way advisory work happens: you do the mapping, the client's people review and sign off, and the client keeps the result.
Map in your workspace
Your AI drafts each runbook over MCP. You place every step in its lane and set what it can access and where a person approves.
Review with the client
Invite the client's people as free viewers. They sign in, use the lenses to find their part, and views and exports are logged.
Hand it over
Transfer the runbooks to your client's workspace. The client owns them, and your AI loses access to the runbooks you transferred.
Stay on
You remain a guest editor until the client removes you. The seat is free and never bills your client.
One move, nothing to rebuild.
The runbooks move with their versions and history, so the record of who built and approved each step stays intact.
A deliverable they can check, not a slide.
A process map in a deck goes stale the day it is presented. A Stepflow runbook stays in the client's workspace with its versions, its checks and its history.
- Versioned runbooks. Numbered versions, each with the name of the person who published it.
- The access register. Every system, access level and human gate, exportable as PDF and CSV.
- Checks and overrides. Any error that was published anyway, with the reason recorded.
- The change log. Which edits your AI made and which you made, hash-chained.
- The run audit trail. Events from any runs so far, labeled by source and hash-chained.
Pay for your own editors. Your seat in client workspaces is free.
Full pricing is on the pricing page.
Editor seats for your team.
You pay the standard editor price for the people who build. Viewers are free.
A free guest editor seat.
After you transfer runbooks, you keep editing access in the client's workspace at no cost, and it never appears on the client's bill.
Consultant questions
Does my client need their own AI?
No. Viewers read runbooks in the browser. Anyone who already uses an MCP client can connect it read-only to ask about published runbooks.
What happens to my AI's access at handover?
Your AI loses access to the runbooks you transferred. They now sit in the client's workspace, under the client's control.
Can my client remove me?
Yes. You stay on as a guest editor until the client removes you.
Who pays for my seat in the client's workspace?
Nobody. The guest editor seat is free and does not bill the client.