Skip to content
Steptree

In practice

Three jobs only one person knew how to do

Not features. What changed once the job was written down, and what their colleagues can now do without asking them.
Start freeStart with your own

Told end to end

Somebody records it once. Now anyone on the team can follow it.

Three SOPs, three teams, and one of them on a system nobody had written a manual for.
  • Tax forms and statements spread across a white desk beside a calculator app on a phone.

    Finance

    Month-end reconciliation

    Recorded once by the person who does it, including her rule for any gap over $500 that is not just a timing difference. Steptree wrote the SOP with that rule as a decision point. Her colleague now runs the close from it while she is on leave.

    Followed by the finance team · Steptree AI answers from it

  • A shop assistant taking a card payment at a counter tablet.

    Customer support

    Refunds and first-line triage

    The refund policy lived in a document almost nobody had read. The senior support lead recorded a refund, flagging each call she makes. The SOP now sits in the support team's library, and the team asks Claude about it instead of asking her.

    Shared with the support team · Claude reads it over MCP

  • A tidy desk by a window with a laptop open in front of a larger monitor.

    Back office

    A legacy Windows program

    A Windows program from twenty years ago that the whole business depends on, with no manual and no vendor left to ask. Steptree records it like any other app. A new starter follows the SOP on their first day instead of sitting beside the one person who knows it.

    Recorded in the Steptree App · followed by new starters

What actually changes

Before and after, in the terms you would measure it

The same three jobs, said the way the person doing them would say it.
Before: two days a month, and only Jane can do it
Month-end starts with a download and ends with a spreadsheet nobody else understands. It cannot happen while Jane is on leave. Every unexplained difference is chased by hand, and the small ones get written off because there is no time.
After: it is written down, rules included
The steps are in an SOP with screenshots under them, and the judgement calls Jane used to make in her head are decision points her colleague can follow. When she is on leave, the close still happens.
Before: the same forty questions every week
First-line support answers what has already been answered, slowly and inconsistently. The policy lives in a document almost nobody has read, and the people who have read it disagree about it.
After: answered from your own policy
The refund process is an SOP the team approved, with the judgement calls in it. Staff ask Claude or Steptree AI, and the answer comes from that SOP rather than from somebody's memory.
Before: only one person knows that system
The program the whole business runs on has no manual, no vendor left to ask, and a screen layout from 2004. Everyone who needs it sits beside the one person who knows it.
After: a new starter can follow it
Recorded once by the person who knows it, like any other app on the computer. A new starter follows the SOP on day one, and asks Steptree AI when a screen does not match.

Questions

Asked before you pick one

How long before we see something like this?
Your first SOP takes as long as the job itself takes, plus a few minutes to read it through. Most people have one approved the same afternoon. You can do that on the free plan without a card.
Which job should we start with?
The one that only one person can do. It costs you most when they are away, and the person doing it usually understands it well. It also produces the clearest before-and-after, which is what you need in order to decide whether to do the next twenty.
Do we have to change how we work?
No. You do the job the way you already do it, once, with the recorder on. The point is to capture what already happens rather than to redesign it — if the process needs improving, you will see it far more clearly written down.
What if our process is messier than these examples?
Most are. That is what the decision points are for. When you hit the bit that depends on judgement, you say so as you go, and it lands in the procedure as a rule. You still end up with one procedure anyone on the team can follow.

Next

Where to go from here

  • Do this with your own process

    What the first hour looks like, from pressing record to an approved procedure.

  • What it costs

    Free to start with no card, and you pay for the people who write procedures — not the ones who read them.

  • Why not another way?

    The three alternatives you are weighing, and exactly where each one stops.

Get your own before-and-after

Record the job that is costing you most and read the SOP Steptree writes from it, free. Paying is for when every job like it is written down, not just the one you tested.

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