Every freelancer who has tried to hire without documentation hits the same wall at week two. The new person asks a question you’ve never had to articulate before, “how do you decide which revision requests to push back on?”, and you realize the answer lives entirely in your muscle memory, not anywhere transferable. You spend the next hour explaining something that should have taken five minutes to read. Then you repeat it the following week.
The problem isn’t hiring. The problem is that your business is still running on undocumented institutional knowledge. Every system, judgment call, and quality standard exists only in your head, which means you can’t delegate anything meaningful without essentially teaching a course first.
The solution isn’t complex. It’s disciplined. Record yourself doing the work. Transcribe the key steps. Refine them into a one-page SOP. Repeat until you have 15-20 documents. That’s your hiring foundation. Without it, every hire you make will cost you more in training time than they’ll save in the first 90 days.
Why Written SOPs Fail (and What to Do Instead)
Most freelancers who try to document their processes sit down with a blank document and freeze. They either write something so generic it’s useless (“send the client the deliverable”) or get so detailed they never finish. Neither creates a workable reference document.
The Loom-first method solves both problems by separating capture from refinement.
Step one: Open Loom and start a recording while you actually do the task. Don’t stage it. Do real work. Talk through your reasoning out loud, not just your actions, but why you’re making each choice. “I’m going to check the brief one more time before I start the mockup because the client changed their brand colors last week and I don’t want to redo this.” That reasoning is the gold. It’s what a new hire can’t get from a checklist.
Step two: Watch the recording once, pausing to write down the 5-12 key steps. Don’t transcribe every word, extract the skeleton.
Step three: Turn those steps into a one-page SOP document using the five-section template below. Link the Loom recording at the top so anyone can watch the full context.
The SOP template:
- Task name and owner, Who does this, and for which clients or project types?
- Trigger, What causes this task to start? (New project kickoff, client sends X, weekly on Mondays?)
- Steps, Numbered, with decision points called out explicitly (“If the client hasn’t sent the brief by Day 2, send the nudge template”)
- Tools, Which tools, which accounts, where to find credentials
- Done criteria, How do you know this task is finished?
One page. If it spills to two, split it into two separate SOPs.
The 60-Day Documentation Sprint
This is not a background project. It requires blocked time, 30-45 minutes per day for 60 days. Most people fail documentation projects because they treat them as optional. They aren’t. If you want to hire, this is the prerequisite.
Days 1-30: The Recording Phase
Your goal is 15-20 Loom recordings covering every repeatable task in your business. Aim for one per day, with some days doubling up on shorter tasks. Recording protocol:
- Record in real time, not staged. If you’re recording yourself writing a proposal, use an actual client project, anonymize the client name afterward.
- Talk through your reasoning, not just your actions. The reasoning is what differentiates your process from a generic how-to video.
- Keep recordings under 10 minutes per task. If a task takes longer than 10 minutes to demo, it needs to be broken into sub-processes.
- Name recordings with the task name, not the date. “Client Proposal Writing Process” beats “Loom Recording May 4 2026.”
Days 31-60: The SOP Writing Phase
Watch each recording once. Write the SOP using the five-section template. Timebox yourself to 30 minutes per SOP, if you’re spending more than that, you’re over-engineering it. The goal is a usable reference document, not a manual.
By Day 60, you’ll have a folder of 15-20 Loom recordings linked to 15-20 one-page SOPs. That’s your hiring foundation.
The recordings you make before hiring are more valuable than the SOPs themselves. New hires who watch you think out loud during real work develop judgment faster than new hires who only read steps. Documentation isn’t just instructions, it’s a way of transmitting how you think.
The 10 Processes to Document First
Not all processes are equally important to document before your first hire. Start with the ones that:
- Happen at least twice per month
- Have quality standards that aren’t obvious
- Involve client interaction (where a mistake has real consequences)
Here are the 10 to document first, in order of priority:
1. Client onboarding, From signed contract to project kickoff. Every step, every email, every document you send.
2. Proposal writing, How you scope a project, how you calculate your rate, how you structure the document.
3. Revision handling, What counts as an in-scope revision, what triggers a change order conversation, how you phrase the pushback.
4. Weekly client update, What you send, when, how much detail, what to do if the project is behind.
5. Invoice and payment follow-up, When you send invoices, what tool you use, the exact sequence if payment is late.
6. Project kickoff call, What you cover, in what order, what you’re listening for, what gets documented afterward.
7. File organization, Where files go, how they’re named, what gets archived and what stays active.
8. Quality review checklist, What you check before sending any deliverable. Every item, in order.
9. Subcontractor briefing, How you explain a project to someone helping you deliver it. What they need to know, in what format.
10. Project close and offboarding, Final deliverable handoff, invoice, testimonial request, referral ask.
Document these 10 and you’ve covered 80% of your business’s operational surface area.
The Judgment Calls Are the Most Important Things to Capture
Written checklists capture actions. What they miss are judgment calls, the moments where you make a decision that isn’t explicit in any process but shapes your quality and client relationships.
“I usually send the first draft on Thursday so the client has the weekend to review it.” That’s a judgment call. Document it.
“If a client’s brief is vague, I send a three-question clarification email before I start rather than making assumptions.” That’s a judgment call. Document it.
“I always check a client’s LinkedIn and recent news before a kickoff call.” Document it.
The way to surface these is the Loom recording. When you’re recording yourself doing real work, the judgment calls are visible, you pause, you consider, you choose. A new hire watching that recording sees the deliberation, not just the outcome.
This is why staging recordings doesn’t work. A staged recording produces polished narration. A real recording captures actual decision-making.
How to Keep Your Documentation Current
Documentation decays. A process you recorded six months ago may not reflect how you work today. Build in a quarterly review: one day per quarter, watch 5-6 recordings, update the corresponding SOPs where the process has changed, and re-record any that are significantly outdated.
The discipline is: every time you notice yourself doing a task differently than the SOP describes, flag it immediately. Add a note at the top: “OUTDATED, review on [quarterly date].” That prevents a new hire from following an old process while you’re using a new one.
The review day doubles as a hiring readiness check. If you can hand any of your SOPs to a capable adult and they can execute the task with one question or fewer, the SOP is ready. If they come back with five questions, the SOP needs work.
Most freelancers overestimate how long documentation takes and underestimate how long bad onboarding costs them. A 60-day sprint produces 15-20 SOPs. One bad hire onboarded without SOPs can cost you 40-60 hours of re-training and cleanup. The math favors the sprint.
Starting Today
You don’t need to wait for the 60-day sprint. Open Loom right now and record the next task you do, whatever it is. Name it correctly, talk through your reasoning, and save it to a folder called “Process Library.”
That’s one recording down. Fourteen more to go before you’re ready to hire.
Ready to send stronger proposals?
Build, send, and track proposals in one place so follow-up is easier.
Start your free trial →
