Where your SOPs get written,approved, and kept current.
Click through it once in your browser, talk it through, upload the doc, paste the meeting transcript, or write it by hand. Whichever way you start, you end up with a numbered SOP with steps, roles, and decision branches, behind an approval gate and a review schedule so it doesn't quietly go stale.
No account neededNo credit cardSee the whole SOP before you sign up
$49/month flat, for the whole team. The same price at 5 people and at 80. Sign up yourself, in about a minute. 5 SOPs free without a card.
Handling a refund request
Trigger
A customer asks for a refund in the support inbox
Steps (4)
- Open the Refunds queue and check the order dateThe queue is shared with Finance, so claim the ticket first.
- Is the order inside the 30-day window?Yes3Issue the refund and paste the receipt ID in the ticketNo4Close the ticket
- Issue the refund and paste the receipt ID in the ticket
- Close the ticket · End
Roles
Start from whatever you already have
Process knowledge turns up in whatever shape it happens to be in: a call that already happened, a half-accurate doc, a click path, or something only one person knows. Sendabrief takes all five shapes and returns the same structured SOP.
Nobody writes SOPs because there's time. They write them because something already went wrong.
“It's all in Priya's head, and Friday is her last day.”
Book 30 minutes, record it, upload the file. You get a structured SOP out of the conversation instead of a recording nobody will ever rewatch.
“We're onboarding six people next month with nothing to hand them.”
Turn the walkthroughs you're already doing into SOPs as you do them, then assign each new hire the ones they need and see who has actually read them.
“A process broke and it hit a customer.”
Write the fix down once, put it behind an approval gate so it can't be quietly changed, and set it to re-verify every quarter.
“The next round wants to see documented operations.”
Export any SOP to PDF or Word under your own branding, or share the whole library through a read-only portal link.
You spend the two minutes. Sendabrief spends the afternoon.
Hand it over, however it exists
Record, upload, paste, or talk. Two minutes of explaining beats an afternoon of writing, and you can start from a file you already have.
The AI writes the draft
Steps get numbered, roles get assigned, if/then decisions become real branches, and screenshots land next to the step they belong to. Nothing gets invented that wasn't in your source.
You approve it, then it's live
Read the draft, fix what's off, approve. It lands in a searchable library your team can filter by folder, tag, or team, and every later edit runs through the same gate.
No account neededNo credit cardSee the whole SOP before you sign up
Every SOP has an owner, a cadence, and a date it was last verified
Writing it down is the easy half. Steps change, nobody updates the doc, and months later someone follows the old version. A SOP that is quietly wrong does more damage than one that was never written, so here re-confirmation is part of the document rather than something a person has to remember: give a SOP a cadence and an owner, and when it comes due that person gets an email to check it. One click if nothing changed, and the clock resets.
People see only their SOPs
Group SOPs into teams, or grant one person access to a single sensitive procedure. Owner, Manager, Editor, Member, plus a separate role per team.
Re-confirmed on a schedule, by email
Weekly through yearly, set per SOP with a named owner. When it comes due they get an email listing what needs checking. Confirming is one click; the SOP is stamped with the date it was last verified, so anyone reading it can see how current it is. Included on the free plan.
See what's missing
Every library search is logged, including the ones that return nothing, so you find out what your team needed documented before they ask you twice.
Assign it to someone with no account
Send a contractor or new hire a magic link to one SOP. They read it, mark it complete, and the link expires. No seat, no login.
Ten languages, still governed
Translate a SOP and it stays hidden until an approver publishes it, and it goes stale automatically when the source changes.
Wired into everything else
REST API, signed webhooks on create/update/view/acknowledge, share links, iframe embeds, and a branded client portal.
No account neededNo credit cardSee the whole SOP before you sign up
“Will it actually be usable, or will I spend longer fixing it than writing it myself?”
Fair question, and the one we get most. The answer isn't that the AI is perfect. It's that the product is built so an imperfect draft can't become a bad SOP:
- Nothing publishes on its own. Every generated SOP lands as a draft you read and approve. Editors and team members can propose changes, but only an approver can make them live.
- It won't invent steps. The model only writes what was in your recording, document, or description. If it wasn't said, it isn't in the SOP.
- Duplicates get caught. Before a new SOP saves, it's compared against your existing library. You get a side-by-side and choose whether to update, keep both, or discard.
- Nobody approves their own work. Self-approval is blocked on the server, not just hidden in the UI.
- Sensitive data never leaves the browser. During screen recording, emails, phone numbers, card numbers, and SSNs are detected and blacked out on the screenshot before it's uploaded.
- It can't quietly go stale. Set a review cadence and the SOP resurfaces to its assigned verifier when it's due. Edit one and everyone who confirmed the old version is marked out of date.
What we think a SOP library owes you
Six things decide whether a library is worth keeping: where the SOP can come from, whether the parts of the job that aren't on a screen get captured, whether anything is checked before it goes live, whether it stays true, whether you find out what isn't written down, and what it costs once the team grows. This is our answer to each, with the usual approaches alongside for context.
| Sendabrief | Manual SOP tools | Screen recorders | A wiki | |
|---|---|---|---|---|
| Where the SOP comes from | A screen walkthrough, description, doc, recording, or by hand | You write it | A screen walkthrough only | You write it |
| Process that isn't on a screen | Captured from the conversation or the doc | You write it | Can't capture it | You write it |
| Approval before it goes live | Built in, and you can't approve your own | Sometimes | No | Comments, not a gate |
| Staying accurate over time | Re-confirmed on a schedule: the owner gets an email, one click to verify | Nothing catches it | Nothing catches it | Nothing catches it |
| Tells you what's undocumented | Logs searches that return nothing | No | No | No |
| Cost as the team grows | $49/mo flat, unlimited members | Usually per seat | Usually per seat | Per seat |
Weighing us against a specific tool? There is an honest side-by-side for each of the six we get asked about most, including what they cost at 30 people and when to buy them instead of us. See the comparisons.
Two plans. The free one isn't a demo.
Five real SOPs, built any of the five ways, using the same model paying customers use. Keep them whether or not you upgrade.
Free
$0
For seeing whether the output is any good before you commit.
- 5 SOPs, yours forever
- All five ways to create one, including the Chrome extension
- Review cycles: put any SOP on a schedule so it can't quietly go stale
- Share any SOP by link and export it to PDF or Word
- No credit card, no trial clock
Try it with no account, then sign up to keep it.
Sendabrief Pro
$49/month
For the whole team. One flat price, no per-seat fees, ever.
- Unlimited SOPs and unlimited members
- Approval workflow, teams, roles, and per-SOP access
- Version history, duplicate detection, and guest task assignments
- Embeds, a branded client portal, and export under your own brand
- Translations, analytics, API, and webhooks
Card required to start. Nothing charged until day 14.
The specific promise: cancel before day 14 and you are not charged a cent. No form, no email, one button in your billing settings. Your SOPs stay yours either way, and you can keep reading them on the free plan. See the full plan comparison →
The questions we get asked
What actually counts as an SOP here?
A numbered procedure with a trigger that starts it, steps written as instructions, the role responsible for each one, and if/then decision branches where the process forks. Not a transcript, and not a wall of prose.
How accurate is the AI?
It only writes what was in your source, and it never publishes on its own. Every draft goes to a human to read and approve first. Expect to fix wording, not to rewrite from scratch. On the free plan you can test that on five real SOPs before deciding.
Do I need to record my screen?
No. Screen recording is one of five options. Uploading a document, pasting a meeting transcript, describing the process out loud, or writing it by hand all work the same way.
Can I write an SOP myself, without AI?
Yes, and it's a first-class path rather than a fallback: a zero-AI editor with rich text, callout boxes, inline screenshots, and if/then decision steps. A hand-written SOP gets the same approval gate, version history, duplicate detection, and review schedule as a generated one.
What stops the library going out of date?
Give a SOP a review cadence (weekly, monthly, quarterly, or yearly) and a named verifier, and it comes back to that person to confirm it's still how things work. Edit one and everyone who confirmed the old version is marked out of date, translations of it go stale automatically, and every library search that returns nothing is logged so you can see what people needed and didn't find.
Will my team actually use it?
That's the honest risk with any new tool, so Sendabrief is built to meet people where they are: assign a single SOP by magic link to someone with no account, track who has confirmed they've read the current version, and see which SOPs people search for and don't find.
Is my data safe?
During screen recording, emails, phone numbers, card numbers, and Social Security numbers are detected and blacked out in the browser before a screenshot is ever uploaded. Nothing you create is used to train models, and every workspace's data is isolated at the database level.
Is the free plan 5 SOPs per month?
No. It's 5 in total, and they don't reset. It's meant to be enough to judge the output honestly, not a metered trial: you can share those SOPs by link, export them to PDF or Word, and put them on a review schedule, all on the free plan. No card is required and there's no clock on it.
Is pricing per seat?
Never. Sendabrief Pro is $49/month flat with unlimited members and unlimited SOPs. Adding your tenth teammate costs the same as your second.
What if I want to leave?
Export any SOP to PDF or Word on either plan (Pro drops the Sendabrief footer and lets you use your own branding), and cancel from your billing settings in one click. See the full details on the pricing page.
Pick the process you keep re-explaining. Document it in the next ten minutes.
Record it, upload it, or just talk it through. No account, no card. If the draft isn't good enough to work from, you've lost ten minutes and nothing else.
No account neededNo credit cardSee the whole SOP before you sign up