The word "SOP" sounds like something a 500-person business uses. It is not.
Standard operating procedures are the single highest-leverage thing a growing business can build, and the single most common thing the business postpones. The cost of not having them never shows up as a line item. It shows up as a hundred small failures across the year that look like personality problems or bad luck.
This is the honest case for SOPs, what happens without them, and the five you should write first.
What an SOP Actually Is
An SOP is a written description of how a recurring task or process is done in your business. It includes:
- ·The trigger (what causes this process to start)
- ·The owner (who runs it)
- ·The steps in order
- ·The decision points and who decides
- ·The output (what "done" looks like)
- ·Who is informed when it is complete
It is not a policy document. It is not a vision statement. It is the answer to "if I had to hand this off to someone new, what would I tell them?"
A good SOP is one page if the process is simple, three pages if complex. Anything longer than three pages usually means the process itself needs simplifying before documenting.
What Happens Without SOPs
The cost of missing SOPs is invisible until it is not. The pattern across the businesses we work with is consistent.
Onboarding takes three times longer than it should. A new hire spends weeks asking "how do we do X?" because nobody wrote it down. Existing team members spend hours per week answering. By month three, the new hire is finally productive. That is two months of salary and half a senior team member's attention spent on knowledge transfer that an SOP would have done in 30 minutes.
The same problems recur. Every quarter, the same issue surfaces. The team solves it the same way each time. Nobody writes down the solution. The next new hire hits the same problem and the team solves it again. The third new hire hits it and the team is annoyed by the third time.
The business runs on three people's memories. The founder. The longest-serving operations person. One senior delivery lead. If any of them leaves, takes leave, or burns out, parts of the business stop working. We covered this in the business that runs on the founder's memory.
Quality is uneven across the team. Two people doing the same task produce different results. Customers experience the business differently depending on who handles them. The founder steps in to "fix" specific cases that the team should have handled consistently.
Critical processes break under pressure. When the team is busy, the parts that have no written process are the parts that get dropped. Billing slips. Onboarding gets skipped. Customer escalations sit unanswered. The team blames volume. The real cause is that without SOPs, what is in the head gets forgotten when the head is overloaded.
The founder cannot take a real holiday. Two weeks off without checking email is impossible if a third of the business runs on the founder's instinct and tribal knowledge. SOPs are the price of a holiday.
The Resistance Is Real and Wrong
Founders push back on SOPs for predictable reasons. The reasons all sound reasonable. None of them hold up.
"We are too small for SOPs." You are not. The right time to write SOPs is when a process has been done three or four times. Past that point, every additional run reinforces unwritten habits that are harder to change later.
"SOPs are bureaucratic." Only when written badly. A one-page SOP that the team actually uses is the opposite of bureaucracy. The bureaucracy is the founder being interrupted 12 times a day with questions that an SOP would have answered.
"Our work is too creative for SOPs." Some of the most creative businesses run on the strongest SOPs. The SOPs free the team from having to remember the mechanics so they can spend their attention on the creative work.
"The team will resist." The team usually resists writing SOPs. They almost never resist using them once written. The friction is one-off. The benefit is permanent.
"I will write them when we have time." You will not. The businesses that write SOPs are the ones that schedule SOP writing as scheduled work, with a named owner. The ones that wait for free time never write them.
The Five SOPs to Write First
If you are starting from zero, do not try to write everything. Write these five. They unlock 80% of the value.
1. Hiring
From the moment a role opens to the moment a new hire is productive. Job description owner. Sourcing approach. Screening criteria. Interview stages and who runs them. Reference check process. Offer process. Day one onboarding. Week one milestones.
This SOP saves more founder time than any other. It also produces better hires by making the process consistent across roles.
2. Customer Onboarding
What happens between "contract signed" and "customer producing value". Welcome sequence. Information collection. Kickoff call structure. First deliverable timeline. Check-in cadence. Handover to ongoing account management.
A clear onboarding SOP cuts customer time-to-value and reduces the percentage of customers who churn in the first 90 days.
3. Customer Escalation
When something goes wrong, what happens. Who picks up. What authority they have. When the founder gets involved. How the issue is documented. How resolution is communicated. What we change after to prevent recurrence.
Without this SOP, every escalation lands on the founder. With it, the team handles 80% of escalations cleanly and the founder only sees the genuinely strategic ones.
4. Monthly Financial Close
What happens at the end of each month to get from "month done" to "books closed and reviewed". Who runs it. What inputs are needed by what date. What outputs are produced. Who reviews. What decisions come from the review.
This SOP transforms financial management from quarterly chaos to monthly rhythm. It is also the foundation for any future fundraising or due diligence process.
5. Decision Documentation
Where decisions get written down. What template. What gets recorded (decision, context, options considered, why this option, who decided, when). Who reads it. When it gets reviewed.
This SOP is the cheapest one to write and the highest leverage. It prevents the same decisions being re-litigated quarterly. It speeds up new hire onboarding. It is the single best protection against organisational amnesia.
How to Write SOPs People Actually Use
Most SOPs sit in a folder nobody opens. The ones that get used share traits.
They are written by the person who does the work, not the founder describing what they wish the person did. The first draft is messy. The first draft is also accurate. Edit for clarity, never for aspiration.
They live where the work happens. If the team works in ClickUp, the SOP is in ClickUp. If the team works in Notion, the SOP is in Notion. SOPs hidden in a shared drive nobody opens are SOPs that do not exist. Choose the right tool for your team - we wrote a comparison of Notion, ClickUp, and Asana for the operations-led businesses we work with.
They have a review date. Every SOP has a "review by" date. Six months for stable processes. Three months for evolving ones. Without review dates, SOPs drift out of accuracy and get ignored.
They are short. The longer the SOP, the less it gets used. If a process needs more than three pages of description, the process probably needs simplifying before documenting.
They have a named owner. Every SOP has one person responsible for it being current. Not a team. One person. When the SOP drifts, that person fixes it.
The Compounding Value
The honest case for SOPs is compounding.
Year one with SOPs: onboarding faster, escalations handled cleaner, the founder less interrupted.
Year two: the team grows without the founder becoming a bigger bottleneck. New hires are productive faster. The same quality of customer experience scales.
Year three: the business becomes acquirable. Or expandable. Or franchisable. SOPs are what makes a business an asset rather than a job.
The cost is one to two hours per SOP, plus disciplined review. The return is years of avoided friction. We covered the practical writing process in how to create SOPs for a growing team.
Where to Start This Week
Pick one process. Write it down in 30 minutes. Have the person who does the work review it. Edit. Publish.
Then the next one.
The businesses that have SOPs are the ones that started. The ones that do not are the ones that planned to start.
Related Reading
- ·How to Create SOPs for a Growing Team - the practical writing process
- ·The Business That Runs on the Founder's Memory - what happens when too much is undocumented
- ·SOPs Service - how we design and document SOPs with growing businesses