Standard Procedure
Book a demo
Menu

Built for the people you can’t replace.

Describe the job. Agents turn it into a procedure and learn automatically from your corrections.

We’ll email you when we can set your business up.

Book a demo Send us a checklist or description of one job. We’ll draft the procedure before the demo.

Illustration of Josh’s Now screen in Standard Procedure. One review is stopped for him: the QA agent passed 30 of 31 checks, the export button is cut off on phones, and he can send the filter back to the coding agent.

One thing is stopped for you

You’re running QA on one thing

Nothing is stopped for you

6 running on their own · 14 finished since yesterday · Tuesday 10:48

Warehouse filter Kestrel Logistics

1234567 · yours8910 1234567 · yours8910 12345 · agent678910 12345678 · agent910 40 min

Nina reviews Wednesday · Step 7, Review

One QA check failed on phones. Send the filter back to the coding agent?

QA agent’s run

30 of 31 passed

31 screenshots, desktop and phone

Check 4 · phone, 390 px

Export button cut off

Screenshot 27 of 31

Nina approved 5 points on MondayEvery desktop check passed

Nina sees nothing until you decide.

Sent back to the coding agent at 10:48 with screenshot 27. QA runs again when the fix lands.

You’re running QA. The agent’s 31 screenshots stay beside your run.

Sent on at 10:48. The write-up tells Nina about the phone issue.

Running

  • Driver sign-in fix Kestrel Logistics 12345 · agent678910 25 min
  • Invoice export Oakline Physio 123456789 · Oakline10 1 d
  • An agent
  • A teammate
  • Someone outside, like a client
  • You, at the steps you mark

Greenfield’s delivery procedure. The client and request are examples.

What you tell the agents on one job, they do on every job after.

Three examples, about a minute long. In each one, someone describes a job out loud. Agents run it on the next real job and wait for that person at the step they marked.

Watch on YouTube Example businesses. The voices are AI-generated.

Procedures for dispatch, billing, delivery and more.

Choose a team to see the work agents can prepare and the decisions you can keep for a person.

A procedure that learns as your team works.

How it works, step by step

  1. Describe the job

    Write how the job gets done or upload your checklist. An agent drafts the procedure. Review the steps, assign them to people or agents, and choose where work needs approval before publishing.

  2. Run it on a job

    Start the procedure by hand, from an email or on a schedule. People and agents take their assigned steps. Work that needs your decision appears in Now, along with questions agents ask when they need help.

  3. Learn from corrections

    Edit or correct the work as you review it. The procedure automatically keeps the lesson and agents use it on future jobs. Learning happens as part of normal work, with no separate training task.

Ten steps from a client’s request to the next deployment.

Greenfield runs its client work on this procedure. Pick a step to see who has it and what happens there.

The client In their portal

Step 1 · Request

The client requests a new feature in their portal.

  • What they want, in their own words
  • Any files or examples they attach

Hand an agent the docs, and it builds the connection.

Attach the API docs for the systems your team uses, whether that’s field-service software, an accounting platform or your own supplier portal. An agent drafts the connection with every call switched off. You check where it sends data and enter the key before anything runs.

Illustration of connecting a new system. You describe Pellham Supply, a parts supplier, and attach its API documentation. The integration agent drafts the connection with four calls, all switched off. It then waits for you: you type the domain you expect it to use, from memory, and it confirms the connection goes where you expected before you approve it. Next, you enter the key in a sealed panel, and the agent never sees it.

Integrations New connection

  1. You

    Pellham Supply, where we order parts. It’s at pellhamsupply.com, and they gave us an API key. Their docs are attached.

    pellham-api.pdf

  2. Integration agent

    Drafted Pellham Supply from the docs. It signs in with an API key, and all four calls are off.

    • Search partsOff
    • Check stockOff
    • Order statusOff
    • Place an orderOff

  3. Waiting for you

    What domain do you expect Pellham Supply to use?

    pellhamsupply.comFrom memory

    Goes where you expected. Uses pellhamsupply.com.

    Approve Pellham Supply Show every address

  4. Next, you enter the key in a sealed panel. The agent never sees it.

An illustration. Pellham Supply is an example.

Built in
Gmail and Google Calendar, Drive, Docs and Sheets; Outlook and Outlook Calendar, Teams, OneDrive, SharePoint, Excel, OneNote and To Do; Slack, Notion, Airtable, Stripe, Jira, GitHub and DocuSeal. What each one does
What can start a procedure
Someone starting it by hand, an email arriving in a connected inbox, a schedule, a signed webhook from another system, or something that happens in Standard Procedure, like a piece of work finishing or a client signing a proposal.

Agents never see your keys, and they can’t give themselves more room.

An agent knows a connection only by its name. The key is encrypted and added on the server as each call goes out. You choose which calls an agent makes on its own and which wait for you, and only a person can change that.

Security in full

Illustration of what the parts agent may do. On its own, it searches parts, checks stock and looks up an order’s status. It asks you first before it places an order, emails a supplier through Gmail or makes any call you haven’t decided on. It never sees the Pellham Supply key, moves a call out of Asks first, switches on a connection, publishes a procedure, uses a tool its step doesn’t list or reaches the internet from code it writes.

What the parts agent may do

On its own

  • Search parts
  • Check stock
  • Look up an order’s status

Asks first

  • Place an order
  • Email a supplier through Gmail
  • Any call you haven’t decided on

Never

  • See the Pellham Supply key
  • Move a call out of Asks first
  • Switch on a connection
  • Publish a procedure
  • Use a tool its step doesn’t list
  • Reach the internet from code it writes
Policies
Changing the rules for every agent at once takes a second person’s approval.
Stopping
Pause one run, or hit the emergency stop and every agent halts before its next outside action.
Record
Every call is kept with its run, in a tamper-evident record.
Changes
Try a new version on past jobs first, and go back to any earlier one.
Sign-in
Single sign-on through your identity provider, and two-step sign-in.
Your deployment and data
Your own deployment, on Google Cloud in the US. Your data, procedures and the knowledge learned from corrections remain yours.

How we compare with Zapier, n8n, Make and Power Automate.

Standard Procedure learns automatically from edits and corrections during a job. Compare how each product improves future runs, handles approvals and connects your tools. Each page links its sources.

We’re setting up the first businesses now.

Send us a checklist or description of one job. We’ll draft it as a procedure for you to review at the demo.

We’ll email you when we can set your business up.

Or Book a demo