Write an SOP before you hire anyone, human or AI, because nobody can do a job that only exists in your head. A short written process turns "let me show you" into a handoff you make once, check easily and repeat with the next person.
Most solopreneurs look for help when they are already stretched, then spend the first weeks explaining, correcting and quietly redoing the work. The problem is rarely the person. It is that the job was never written down. This post covers why SOPs come before help, a five line format you can use today, which jobs to write up first, and how the same SOP becomes the brief for an AI employee.
Why SOPs come before help
An SOP, or standard operating procedure, is a written description of how a recurring job gets done. In a one person business it does three things:
- It moves the knowledge out of your head. While a process lives only in your memory, you are the only person who can do it, and you redo the thinking every time.
- It sets the standard. Whoever picks up the job knows what finished looks like, so you review against something clear instead of a feeling.
- It makes the handoff repeatable. If a freelancer moves on or you add a second helper, the job does not leave with them.
Hiring without SOPs means paying someone to learn your business by trial and error. Writing them first means the first week is spent doing the work, not decoding it.
What an SOP for one person looks like
You do not need a binder or a twenty page manual. For a solopreneur, five lines are enough to start:
- Trigger: what starts the job, for example "a new client signs the proposal" or "every Monday at 9:00".
- Steps: the actions in order, one line each, written so someone new could follow them.
- Tools: the apps and templates the job needs, and where to find them.
- Done looks like: how anyone can tell the job is finished, and finished well.
- Who checks: who reviews the result, and when.
Here is the format filled in for a job almost every service business has, new client onboarding:
- Trigger: proposal signed and deposit paid.
- Steps: send the welcome email; create the client folder from the template; add the client to the project board; book the kickoff call; send the intake questionnaire.
- Tools: email templates, shared drive, project board, scheduling link.
- Done looks like: within one working day the client has the welcome email, the kickoff is booked and the questionnaire is sent.
- Who checks: you, on the kickoff call.
If a step needs judgement, say so inside the step: "if the client asks for a discount, stop and flag it to me". One line like that prevents more mistakes than pages of detail.
Which jobs to write up first
Start with work that is repetitive, easy to check and already eating your week. Three good candidates for most service businesses:
- Client onboarding. The steps between "yes" and the first session. It happens every time you sign someone, and a smooth start sets the tone.
- Enquiry handling. How new enquiries are sorted, answered and followed up, so no lead waits for days.
- Weekly admin. Invoicing, receipts and the end of week review that keeps your numbers tidy.
Write the SOP the next time you do the job, not from memory. Do the task with a note open, jot each step as you go, then tidy the notes into the five lines. Writing while you work captures the small steps you would otherwise forget to mention.
How an SOP becomes the brief for an AI employee
The same five lines work whether the job goes to a freelancer, a virtual assistant or an AI employee. An AI employee depends on them even more, because it cannot read between the lines or ask you a quick question over coffee.
When we build an AI employee at The Founder's Flow, the SOP is where we start. The trigger becomes its schedule, the steps become its instructions, the tools become the apps it is allowed to use, "done looks like" becomes its quality check, and "who checks" becomes the approval step: it drafts, you approve.
SOPs are also the foundation of the wider operating system behind your business. Processes, client journey, tools, automations and the people or AI employees doing the work all depend on the job being written down first. If you have one job you want off your plate soon, tell us about it here.
Common questions
How long should an SOP be?
As short as it can be while someone new could still follow it. For most solo jobs that is the five lines above and a handful of steps. Add detail only where people actually get stuck.
Where should I keep my SOPs?
Somewhere you and your helpers already work: a shared folder, a page in your project tool or your notes app. One place, clearly named, beats a perfect system nobody opens.
Do I need SOPs if I am not hiring yet?
Yes. Written processes stop you redoing the thinking each time, and when you are ready to hand something off, the brief is already written.
Can AI write my SOPs for me?
It can help you turn rough notes into the five line format, but the knowledge has to come from you. Do the job once, describe what you did, and let AI help with the wording.
About the author: Maryam is the founder of The Founder's Flow, which builds AI-powered operating systems for service-based solopreneurs. Based in Barcelona, working worldwide.
