Skip to content

For whoever owns the SOPs

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

The SOPs your business wrote down have drifted from the screens people actually use, so nobody trusts them.

Do the task once with Steptree recording, in any app on Windows or Mac. Steptree writes the step-by-step SOP from the real screens, with screenshots under the steps and the notes you added.

You check it, approve it and share a link. Connect Claude so it reads the same page. Every SOP sits in one library instead of a copy on every shared drive, and when a screen changes, you re-record it in minutes.

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

One pass, recorded

One real pass, judgement included

Not a walkthrough performed for a camera, and not an interview a week afterwards.
  1. Do the task, in whatever app it lives

    The spreadsheet, the ERP, the vendor portal, the browser. Steptree records the window you work in, on Windows or Mac, with a screenshot for every click.

    Password fields are never recorded, and emails and card numbers are stripped from typed text.

  2. Say why at the moment you decide

    Two buttons sit on the recorder bar. One records the call you just made and why, the other takes a note a newcomer would miss.

  3. Read the draft, fix it, approve it

    Steptree writes the SOP, then waits. You edit it like a doc and approve it, and nothing is published until you do.

The document itself

A step list runs out exactly where the judgement starts

Record one job on the free plan and read what comes back.
The goal, in one sentence
What the job is for, stated at the top, so a reader knows when they have finished.
The steps, with screenshots under them
Numbered and written from what was really clicked, with the screenshot a new starter needs to find the button.
The judgement calls, where you made them
The exception, the threshold, the reason you took the second option, each placed at the step it belongs to.
Things to know
The caveats you noted while recording, kept apart from the steps so nobody mistakes one for the other.

Flag the exception while you are still in it

What a new starter needs is the sentence an experienced colleague would have said out loud. A button on the recorder bar takes it down during the job. Claude, Codex or GitHub Copilot can read the finished SOP over MCP, and any SOP can become a SKILL.md skill file.

After it is signed off

The folder nobody opened becomes one library people trust

  • A drifted SOP is one re-record away

    When a screen moves, record the task again. A fresh draft is ready in minutes, so the yearly rewrite stops being a project.

  • One library, not a copy on every drive

    Folders, tags and comments in one place. Share any SOP by link, and nobody has to sign in to read it.

  • The hard cases are written in

    The exceptions your best person handles sit in the step they belong to, so the SOP covers the awkward case as well as the easy one.

  • The induction pack is written once

    A new starter follows the approved SOPs, and can ask Steptree AI in the Steptree App how a job is done here.

Questions

A second attempt at this starts with harder questions

We already have a tool that records steps and makes a document. Why change?
If your team reads those documents and trusts them, stay where you are. A Steptree SOP carries the goal and the judgement calls as well as the clicks, and the AI your team uses can read it.
Does it record software that is not a web page?
Yes. The Steptree App and the Recording App record any application on Windows or Mac, from desktop software and spreadsheets to the ERP and the browser. There is no Linux recorder.
How does our AI read the SOPs?
Connect Claude, Codex, Cursor or GitHub Copilot in VS Code over MCP, the standard AI tools use to connect. Each person uses their own key, and it comes with every plan, free included.
What happens to our SOPs if we leave?
Any SOP can become a SKILL.md skill file, which is plain text you download and keep. Until then, your own AI can read the whole library over MCP.
How is a recorded SOP better than one a person writes?
It is not better. It is written from what happened rather than from what somebody remembered a week later, and you still review the draft.
Who can publish an SOP?
Its owner, a team manager or an admin. Until one of them does, it stays a draft, and an AI reading it is told that it is one.

Next

Where to go from here

Start with the job that has the most exceptions

Record it once. You get back the SOP with the judgement calls written in, ready to check, approve and share. Free: 300 AI credits a month and two recordings, no card.

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