Not a philosophy. These are the four things Sendabrief will not let you get wrong, and the specific mechanism behind each one. You can check every claim on this page inside a free account.
1
Five ways in, one pipeline out
Process knowledge arrives in whatever shape it happens to be in, so there are five doors into the library and they all open onto the same room. Whichever one you use, what comes out is a numbered procedure with a trigger, steps, the role responsible for each one, and if/then branches where the process forks.
Click through it once and the Chrome extension turns every click into a numbered step with an annotated screenshot. No video is recorded.
Talk it through or type it, upload a PDF, Word file or deck, or paste a meeting transcript and upload the recording if you only have the file.
Or write it by hand, with no AI involved at all, in an editor with rich text, callouts, inline screenshots and decision steps.
All five hit the same draft editor, the same duplicate check, the same approval gate, and one searchable library.
2
Nothing goes live until a person says so
A draft is not an SOP. Every draft, generated or hand-written, is read and approved by a human before anyone can follow it, and the rules that make that meaningful are enforced on the server rather than hidden in the interface.
Self-approval is blocked server side. Whoever wrote it is not who signs it off.
Before a new SOP saves it is checked against your existing library. You get a side by side and choose to update, keep both, or discard.
Later edits run through the same gate, so a live procedure cannot be quietly changed.
The model writes only what was in your source. If it was not said, recorded, or uploaded, it is not in the SOP.
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.
3
Every SOP has an owner, a cadence, and a last-verified date
Writing it down is the easy half. A procedure that stopped being true six months ago does more damage than one that was never written, so re-confirmation is part of the document here rather than something a person has to remember to do.
Give an SOP a cadence, from weekly to yearly, and a named owner. When it comes due that person is emailed a list of what needs checking.
Confirming takes one click, and the SOP is stamped with the date it was last verified so anyone reading it can see how current it is.
Edit an SOP and everyone who confirmed the old version is marked out of date. Translations of it go stale automatically.
Every library search is logged, including the ones that return nothing, so you find out what people needed documented before they ask you twice.
Review cycles are on the free plan, because a claim about staying current is worth nothing if you cannot try it.
4
The workspace is priced, not the people in it
A library only works if everyone can open it, including the people who need it twice a year. So the price is attached to the workspace: $49 a month whether you are five people or eighty, and the number on the pricing page is the number you pay.
Unlimited members and unlimited SOPs on Pro. Your tenth teammate costs the same as your second.
No setup fee, no implementation fee, no annual commitment, and no call with anyone required to see a price.
Free is 5 SOPs that are yours for life, not for a month, with no card and no trial clock.
Pro is a 14 day trial. Cancel before day 14 in one click and nothing is charged.
What this does not do
Worth knowing before you spend an afternoon on it. If one of these is a dealbreaker, better to find out now than on day thirteen of the trial.
It is a browser extension, so a process that runs in desktop software is not captured by clicking through it. Describe that one out loud or upload the document instead.
There is no connected import from Zoom, Google Meet or Microsoft Teams. You paste the transcript or upload the recording file yourself, up to 24 MB.
You still edit. Every draft is a first draft, and the honest expectation is that you fix wording rather than rewrite from scratch.
A source that never actually described the steps produces a thin SOP. There is no procedure to extract from a document that only lists outcomes.
If your team is under fifteen people and nothing has broken yet, you probably do not need this. The problem it solves is handoff at scale.
