SOPs Your Team Actually Uses. Not Documents That Sit in a Folder.
Most SOPs fail because they are written in the wrong format, for the wrong audience, in a tool nobody opens. We build SOPs in a one-page format that takes 30 minutes per process and gets used.
SOP audit from $2K - full SOP library engagement from $5K
Knowledge Lives in People's Heads. Then People Leave.
Every business that grows past 5 people accumulates operational knowledge that lives in someone's head. It works fine until that person is on leave, leaves the company, or simply forgets a step. Then everything that depended on that knowledge breaks.
The founder answers the same questions every week because nothing is documented for new hires.
Two team members do the same task and produce different results because there is no documented standard.
Onboarding takes 6-8 weeks because new hires have to be taught everything verbally.
Quality drops when key people are out because the team improvises instead of following a process.
The business has tried writing SOPs before but they are 20-page documents nobody reads.
There is an SOP folder somewhere but nobody can find the document they need when they need it.
What an SOP Engagement Actually Delivers.
The Right Format
One page per process. Numbered steps. Tool links. Owner and trigger clearly defined. Plain language. Written to be followed, not to look impressive in a meeting.
The Right Processes First
We do not document everything at once. We start with the 10-15 processes that cause the most pain - same question repeated, inconsistent execution, key-person risk. The rest can come later.
The Right Tool Setup
Notion, ClickUp, Google Drive, or whatever your team uses. We set up the structure - master index, ownership tags, review cadence - so the library is findable. Not just written.
The Habit That Keeps Them Current
We coach the team on updating SOPs in the moment - when someone discovers a step is wrong, they fix it then, not in a quarterly review. This is the only way documentation stays current without dedicated maintenance.
When SOPs Are the Right Engagement.
Growing teams past 10 employees
Onboarding new hires has become a bottleneck. The same questions get answered weekly. Knowledge lives in 2-3 people's heads.
Services businesses
Consultancies, agencies, IT services firms where delivery consistency matters. SOPs are what make client work predictable.
Post-funding startups
Hiring fast and need new team members productive in days, not weeks. SOPs accelerate ramp-up and reduce founder-as-trainer time.
How We Build Your SOP Library.
SOP Audit (Week 1)
We map every operational process in the business. We identify which ones are documented, which are partial, and which exist only in someone's head. We prioritise by leverage.
Format Design (Week 1-2)
We define the SOP format your team will use - one page, numbered steps, tool links, ownership. We set up the tool (Notion, ClickUp, Drive) with the master index structure.
Writing and Review (Weeks 2-5)
We write each SOP with the person who actually does the work. They contribute the steps, we shape the format. We test each SOP by having someone else follow it.
Implementation and Habits (Week 6+)
We launch the library to the team, run an onboarding session, and coach the update habit. After 30 days we check in to verify SOPs are being used and updated.