Skip to content

For automation agencies

Do the job once. Get the SOP your team follows and your AI can read.

Discovery costs you margin, because the process doc the client gave you is wrong by week two.

Send the client the Recording App. Their operator does the job once, and Steptree writes the SOP with the decision points an interview never surfaces.

The client signs it, and that SOP is your spec. Your build reads it over MCP, or loads it in Claude Code as a skill file.

Free plan: 300 AI credits a month and two recordings, no card. Claude can connect on any plan.

The commercial case

The week you never billed becomes the deliverable

Discovery stops being unbilled research and becomes an SOP the client signs and keeps.
  1. Send the client the Recording App

    Their operator does the job once, on their own screen, in their own systems, at normal speed. No script, no whiteboard session.

    Whoever records needs a seat in the workspace they record into, the client's or yours.

  2. You correct the wording, they sign it

    The steps and decision points are already there, so you are editing rather than writing from a transcript. The client approves the same SOP you read.

  3. Build from it in your own stack

    Read it over MCP from Claude Code, Cursor or Codex, or load it as a SKILL.md skill file. It is the spec for a build on whatever platform you already run.

What you get

A spec you can version control, not a slide deck

Any approved SOP becomes one plain-text skill file: no lock-in, readable in a diff.
Decision points are the exception handling
Where the operator does something other than the obvious next click, they flag it and say why. That is the branch logic an interview never surfaces.
Readable when a screen changes
When the client's software moves, record the job again. A fresh draft SOP is ready in minutes, for them to approve.
Plain text you keep
Any SOP can become a SKILL.md skill file you download. Take it to whatever platform you already run.

Your build reads the SOP the client signed

Connect Claude Code, Cursor or Codex over MCP, and it searches the client's SOPs with their decision points. A draft arrives labelled as a draft, so nobody builds from an unsigned spec by accident.

For RPA teams

Maintenance stops being the whole budget

  • The client's approval is already there

    Nothing is published until a person approves the SOP.

  • A document, not a black box

    When a bot breaks, the SOP it was built from is the page a person opens and corrects.

  • A redesign is a re-record

    When a vendor moves a screen, record the job again and rebuild from the new SOP, not from memory.

Questions

What agencies and RPA teams ask first

We've already scoped our current clients. Why keep paying between projects?
Because discovery is the cost you eat on every new client, not just one. Every recording adds an SOP you can build from, so the subscription keeps buying back the afternoon it saved on the first.
Do we own the output, or is it locked to Steptree?
You own it. Any SOP can become a SKILL.md skill file in an open, plain-text format, and your own AI reads the library over MCP on every plan.
Can we resell this to clients?
Yes. Record inside the client's own workspace so they hold the SOP, or inside yours if you are the one maintaining it.
How is this different from the workflow builders we already use?
They run a workflow someone specified. Steptree writes the specification from a recording of the real process, including the decisions an interview misses.
Does the client need to install anything?
Their operator needs the Recording App on Windows or Mac and a seat in the workspace. Anybody who only reads a public link installs nothing and signs in to nothing.
Does this replace our RPA bots?
No. It replaces the discovery interview and the handover doc. A recorded SOP with its decision points is what stays readable when a screen changes.
What does a client's security team ask?
Whether their process is separated from every other workspace's, and it is, inside the database. Password fields are never recorded, and nothing is published until a person approves it.

Next

Where to go from here

Record the next client process instead of interviewing for it

See the SOP your next proposal could be built on, from a process the client runs anyway. Free plan: 300 AI credits a month and two recordings, no card.

Someone at a wall of sticky notes talking a seated team through a process.