For RevOps and business systems
Do the job once. Get the SOP your team follows and your AI can read.
Your runbook is a Slack thread and your memory, so every ‘how do I’ routes to you.
Handle the request once with Steptree recording, in whichever system it happens. Steptree writes the runbook, with your note on why a field exists and where each exception routes.
Approve it and connect Claude or Cursor over MCP. The next rep asks Claude and gets your runbook back, instead of sending you a DM.
Free plan: 300 AI credits a month and two recordings, no card. Claude can connect on any plan.
Three steps
One handled request becomes a runbook your reps can ask about
Handle the next request while Steptree records
The CRM, the billing system, the spreadsheet the board deck reads from. The Steptree App or the Recording App records any app on Windows or Mac, the browser included.
Password fields are never recorded, and emails and card numbers are stripped from typed text.
Say why at the odd field
Press Decision where the request goes an unusual way, and give the reason. Press Info for the context a rep would otherwise message you about.
Approve the runbook, then connect Claude
Steptree writes the goal, the steps with screenshots under them, and your reasons. Edit it like a doc, approve it, and connect Claude, Cursor or GitHub Copilot in VS Code over MCP.
The runbook itself
One recorded request comes back as a runbook you can edit
Reps ask Claude, and Claude reads your runbook
Where to start
The requests worth a runbook first
- Lead routing QA
- Somebody edits an assignment rule, and checking that records still land with the right owner comes back to you. Record the check once.
- The deal desk exception
- A non-standard term, a discount that needs a second approval. The runbook keeps where each one goes, and why.
- CRM hygiene before the board deck
- Duplicates, stage dates that cannot be right, the fields the deck reads from. It comes round every quarter, so write it down once.
- The rule that changed last week
- When a rule, a system or a policy moves, record the request again. A fresh draft runbook is ready in minutes.
Questions
What RevOps teams ask before connecting Claude
- Does this replace the automation platform we already run?
- No. Steptree writes down how a request is handled, which is what anybody building an automation needs first. Your platform stays exactly where it is.
- How do reps get answers from the runbooks?
- Each rep connects Claude, Cursor, Codex or GitHub Copilot in VS Code over MCP. They mint their own key, it expires, and it is read-only unless they allow edits.
- If we stop paying, what happens to the runbooks?
- Any runbook can become a SKILL.md skill file, which is plain text you download and keep. Until then, your own AI reads the whole library over MCP.
- How is this different from pointing a chatbot at our wiki?
- A wiki page is written from memory, usually a week later. This runbook is written from a request you really handled, including the exception you made halfway through.
- Does it record the CRM and the finance system?
- Yes. The Steptree App and the Recording App record any application on Windows or Mac, the browser included. There is no Linux recorder.
- What will our security team want to know?
- Password fields are never recorded, each workspace is separated inside the database, and every AI connection uses a personal key that expires. SSO and SCIM are on Enterprise, and we say plainly they have not yet been run against a live identity provider.
- Where does this fall over?
- The draft only knows the run it recorded, so it misses a branch you did not hit. Record that exception when it next arrives, and add it to the runbook.
Next
Where to go from here
The two apps that record
The Steptree App and the Recording App.
What a runbook holds
The goal, the steps, the reasons.
What it costs to try
Free, no card, no demo gate.
Record the request you answered twice this week
Handle the next repeat the way you always do, and read the runbook Steptree writes from it. Free gives you 300 AI credits a month and two recordings, no card, which is enough to see whether reps should ask Claude next time.
