kilnbyte.online

Your First 3 SOPs as a One- or Two-Person Business | Kilnbyte
Operations 15 min read

Your First 3 SOPs as a One- or Two-Person Business

You don't need a big team to deserve proper systems. These three SOPs will make your business feel stable, calm, and ready to grow.

You don't need a big team to feel overloaded. If you run a one- or two-person business, your job is not just "doing the work". You are the sales team, the delivery team, the finance department, the customer support, and sometimes the IT person as well.

On a good day, this feels exciting and flexible. On a bad day, it feels like you're spinning plates and hoping none of them hit the floor.

A lot of that chaos doesn't come from how much work you have. It comes from how your work moves.

  • You send a proposal, but forget to log it anywhere.
  • You onboard a new client, then realise two weeks later that you never clarified how feedback will work.
  • You complete a project, but the invoice sits in a draft because you get pulled into something else.

Nothing is wrong with your intelligence or your discipline. What's missing are simple, repeatable paths for the things you do over and over again.

That's what Standard Operating Procedures (SOPs) are for.

Not the stiff corporate documents you might imagine. Not a 100-page manual that lives in a drawer.

In a one- or two-person business, SOPs can be light, human, and extremely practical: they are written directions for how you want key parts of your business to run, every single time. When you create just a handful of them, your workday starts to feel less like improvisation and more like following a clear rhythm.

In this guide, you'll walk through:

  • What an SOP really is (in non-corporate language)
  • Why SOPs matter even if it's "just you"
  • The first three SOPs that create the biggest shift in small businesses
  • How to draft them step-by-step, without getting lost in complexity
  • A simple week-long plan to make them real

You will not need any fancy platforms. A folder in Google Drive, Notion, or even a small "Operations" notebook is enough to start.

What an SOP Actually Is (Without the Corporate Jargon)

When people hear "Standard Operating Procedure", they often imagine something heavy and bureaucratic. That picture is unhelpful, especially when you're small and fast.

At its core, an SOP is much simpler than it sounds.

An SOP is a repeatable path, written down

Think of an SOP as the agreed way you will handle a particular type of work. It's written once, and then followed many times.

A good SOP:

  • Describes when you should use it (the trigger)
  • Defines what "done" means for that process
  • Breaks the work into clear, logical steps
  • Lives in a place where you can actually find it

It doesn't have to be fancy. It might be:

  • A one-page Google Doc with headings and bullet points
  • A page in Notion with sections and checkboxes
  • A Word or Pages document in a shared "Operations" folder
  • Even a laminated printed checklist for something you do physically

The format is less important than the clarity.

SOP vs checklist vs "how-to" document

It helps to see how an SOP relates to other types of documentation:

A checklist is a simple list of actions to tick off.

A how-to guide explains the steps in more detail, often with screenshots or examples.

An SOP often combines both: a clear sequence of steps, plus short explanations where needed, plus the "when" and "why" around them.

In a tiny business, you can be flexible. Some of your SOPs may basically be structured checklists; others may read more like short guides. The key is: they describe one process from start to finish.

SOPs are living documents

The first version of any SOP is not "the law forever". It is simply:

"This is the current best way I know to do this."

As your business grows, your tools change, or you see better ways to do things, you update the SOP. It evolves with you. That's why it's important to keep them lightweight and editable, not frozen in a PDF you're scared to touch.

Why SOPs Matter Even When It's Just You

It's completely natural to think, "I'm one person, I don't need this level of structure." But there are three big reasons small businesses get a lot from SOPs.

1. Your brain is already overbooked

As a solo operator, your mind holds: Current projects and deadlines, promises you've made to clients, ideas for marketing and new offers, admin tasks, tax dates, invoices, and renewals.

On top of that, you're dealing with life: family, health, home, messages.

Every time you rely on memory for a multi-step task, you spend energy that could be used for creative or high-value work. SOPs let you move that burden out of your head and onto paper. You stop thinking "What was the next step again?" and start thinking "Let me open the checklist and follow it".

2. Consistency builds trust and makes improvement possible

Clients rarely complain about your talent. They complain about inconsistency:

  • One client gets a beautifully structured onboarding, another gets a quick "Hi, let's start" message.
  • One project ends with a clear summary and next steps; another ends with a file attached and silence.

When you handle the same type of work differently every time, it becomes hard to know what's actually working. With SOPs, you deliver the same type of experience across clients. That:

  • Makes you look more professional
  • Makes it easier to spot weak points and improve them
  • Gives you real confidence to raise your prices because your process feels solid, not improvised

3. SOPs make delegation and growth less scary

You might be "just you" today. But at some point you may want:

  • A virtual assistant to help with admin
  • A contractor to support delivery
  • Someone to handle invoices or scheduling

Without SOPs, bringing someone in means training them verbally every time and hoping they remember. With SOPs, you already have a starting point:

"This is how I currently handle onboarding / delivery / monthly admin. Let's walk through it and refine it together."

Even if you never hire anyone, your future self will be grateful that past-you took the time to write down how important work should run.

The 3 High-Impact SOPs for One- and Two-Person Businesses

You could, over time, document dozens of processes: content creation, launches, tech setup, customer support scripts, and more. That would be lovely, but you don't need all of that to feel a big difference.

If you want to feel a real shift without drowning in documentation, start with these three SOPs:

The 3 Essential SOPs:

  • Client Onboarding SOP
  • Core Service Delivery & Quality SOP
  • Monthly Money & Admin SOP

These three touch your revenue, your reputation, and your stress levels directly. Let's go through them one by one and see what they can look like in practice.

SOP #1: Client Onboarding – How You Start Every Engagement

Picture this: a client says "Yes, let's do it."

This moment can lead to two very different experiences.

Without an onboarding SOP:

• You send a quick "Great, let's start!" email.
• You remember later that you never confirmed timelines.
• The client isn't sure what happens next or when they'll hear from you.
• You find yourself digging through old messages for basic details.

With an onboarding SOP:

• You have a standard welcome email ready to adapt.
• You know exactly what information to collect and how.
• You have a consistent internal setup you run through each time.
• The client feels held, informed, and confident from day one.

What your Client Onboarding SOP should cover

A good onboarding SOP for a tiny business doesn't need to be long. It should answer five basic questions:

Five questions your onboarding SOP answers:

  • Trigger – When is onboarding officially "on"?
  • Internal setup – What do you set up behind the scenes before you speak to the client again?
  • Client communication – What do you send, in what order, and what do you say?
  • Information collection – How do you gather the details you need to do your best work?
  • Definition of "onboarded" – What must be true for you to consider the client fully onboarded?

Building your Client Onboarding SOP step by step

You can structure it like this.

1. Define the trigger

Write one clear line at the top:

Use this SOP when: a client has agreed to work with me (verbally or via email) and we have confirmed the basic scope or package.

This tells you exactly when to open the document and follow it.

2. Internal setup – organise your side first

Before you send anything, you prepare your own systems smoothly. Your SOP can describe actions such as:

  • Create a folder in your file storage with a simple naming convention, for example:
    Clients → [Client Name] → [Project Name]
  • Add the client to your contact system or CRM sheet with key details:
    Name, email, phone, business name
    Time zone, preferred communication channel
  • Create a project or task list in your task manager:
    Add a few starter tasks: "Onboard [Client]", "Schedule kickoff", "Draft phase 1 plan"
  • Create a short "client snapshot" note summarising:
    What they do
    Why they reached out
    Key outcomes they want from working with you

When you follow this internal setup every time, new projects don't feel like they're "floating". They land in a system.

3. Welcome email – one template, many uses

Next, your SOP should reference a welcome message template. This is not just a polite hello; it's a structured message that:

  • Confirms what you've agreed
  • Explains what happens next
  • Shows the client you know what you're doing

Your SOP can include an outline like:

  • Thank the client for choosing to work with you
  • Restate the purpose of the engagement in your own words
  • Mention the main phases or milestones ahead
  • Share how you'll communicate (e.g., "I primarily use email, with WhatsApp for urgent messages")
  • Share how to book the first call or the next step
  • Attach or link any documents they need (agreement, questionnaire, prep guide)

You don't need to write the full email in the SOP; you can link to a "Templates" document. But your SOP should clearly say:

"Open 'New Client – Welcome Email' template, personalise, and send within 24 hours of agreement."

That sentence alone can stop days of delay after a "yes".

4. Information collection – don't chase details later

Many onboarding problems come from not asking key questions early. Your SOP can define:

  • Do you send a short intake form?
  • What are the exact questions?
  • At what point do you ask for access to any documents or tools?

For example, your SOP might say:

"Within 24 hours of sending the welcome email, send intake form with these sections: current situation, goals, past attempts, success criteria, constraints."

You might then specify:

"If no form is used, prepare these questions to cover in the kickoff call instead."

This way you never start work based on half the information.

5. Kickoff and confirmation – start clearly, not vaguely

Finally, your SOP should describe how you:

  • Run the first structured conversation
  • Confirm everything in writing afterwards

Your SOP might include bullets like:

"During kickoff, confirm scope, boundaries, and communication norms: what's included, what isn't, how feedback will work."

"After call, send a brief summary email with: what we're doing, what you'll deliver by which dates, and what you need from the client."

At the end, add a "Done when…" statement:

The client is considered onboarded when:
– Folder, project, and contact are set up
– Welcome email has been sent
– Intake info is collected or kickoff call is completed
– Next date is in the calendar with clear purpose

From that point, you and the client are on the same page. You're not operating from a vague feeling; you're operating from a shared plan.

SOP #2: Core Service Delivery & Quality – How You Deliver Great Work Every Time

If onboarding is how you say hello, delivery is how you keep your promises.

Your core service might be:

  • Designing websites
  • Writing content
  • Coaching or consulting
  • Managing ads or campaigns
  • Providing a structured digital service

Whatever it is, you have a cycle: you gather information, you do the work, and you hand it over. When that cycle is undocumented, you tend to rely on adrenaline and memory. That's when quality drops—especially when you're tired or juggling multiple clients.

A Core Service Delivery & Quality SOP ensures that:

  • You follow a consistent structure each time
  • You know what "ready to send" actually means
  • You catch errors before your client does
  • You finish projects feeling complete instead of "I hope it's okay"

What your Delivery & Quality SOP should cover

This SOP can be built around four questions:

  • What are the stages of your typical project or service?
  • What happens inside each stage?
  • What checks do you perform before you show work to a client?
  • How do you package and communicate the delivery?

Turning your delivery into a clear SOP

Here's one way to structure it.

1. Define the stages of your service

Take your main offer and break it down into 3–6 stages. For example, if you provide strategy documents:

  • Discovery and understanding
  • Outline and agreement on direction
  • Deep work and drafting
  • Review and refinement
  • Final packaging and delivery

In your SOP, write a short paragraph about each stage in plain language:

"In the discovery stage, I gather everything I need to understand the client's situation. That includes reading their intake, reviewing any materials they shared, and asking clarifying questions."

This gives you and future collaborators a map of the experience, not just the tasks.

2. Detail the actions that belong to each stage

Under each stage, list the actions you take. This is where you move from vague phases to clear steps.

For "Deep work and drafting", your SOP might say:

  • Block at least two focus sessions in the calendar for this client's work.
  • Re-read discovery notes before starting.
  • Build a rough structure (sections or slides) before filling in content.
  • Draft content in your writing tool; don't worry about perfection yet.
  • Keep a small note open for ideas that belong to later phases.

These are still simple actions, but now they sit inside a clearly defined phase.

3. Create a "ready to share" checklist

This is one of the most valuable parts of a Delivery & Quality SOP. For each important deliverable type, define what must be true before you share it.

For example, for a written strategy document:

  • The file name follows your convention and doesn't include "v9_final_FINAL".
  • Spelling and grammar checks are complete.
  • All headings use consistent formatting.
  • You have removed internal notes or comments.
  • Every promise in the original agreement or proposal is clearly addressed.
  • You have added a short summary at the beginning so the client knows what they're looking at.

Instead of hoping you remember all of this at the end, you simply tick through the list. This makes your work predictably high-quality, even on days when you have low energy.

4. Define how you package and send work

Delivery isn't just the content; it's the container.

Your SOP can specify:

  • Whether you send a PDF, editable file, link, or combination
  • Where you store the final version in your folder structure
  • Which template you use for the delivery email or message

For example:

"Export the final document as a PDF and keep the editable version in the client folder. In the email, include: a short friendly opening, 2–3 bullet points summarising what's inside, any instructions on how to review, and a reminder of when you'll follow up."

You can even include a script like:

"You don't need to read this all at once. If you only have time for one thing, read the one-page summary on page 2 first."

Those little touches come from having thought through the experience once, instead of improvising every time.

5. Close the loop internally

Finally, your Delivery & Quality SOP should describe how you mark work as delivered in your own systems:

  • Update the project status ("Phase 1 delivered", "Awaiting client feedback").
  • Note the date of delivery.
  • Set a reminder to follow up if you haven't heard back by a certain date.

This means projects move through your system in a traceable way. When you look at your list of clients, you know exactly where each one stands.

SOP #3: Monthly Money & Admin – How You Stay on Top of the "Unsexy" Work

Most small business owners don't avoid money and admin because they don't care. They avoid them because they feel messy and emotionally loaded.

Without a simple routine, it's very easy for things to slide:

  • Invoices go unsent because "I'll do them later".
  • Payments go unchecked because logging into accounts feels heavy.
  • Subscriptions renew that you forgot you had.
  • You reach tax season with a pile of unorganised information.

A Monthly Money & Admin SOP turns all of that into a short, predictable ritual. It doesn't have to be perfect to be powerful.

What your Monthly Money & Admin SOP should cover

This SOP usually includes:

  • When and how often you run it
  • Which accounts and tools you check
  • How you log income and expenses
  • How you handle unpaid invoices
  • Which small admin tasks you tidy up regularly

Designing your Monthly Money & Admin SOP

You might structure it like this.

1. Choose your "money & admin" slot and write it into the SOP

Start by deciding when you're going to do this every month:

"Use this SOP on the first Friday of every month at 3 p.m. (block 60–90 minutes in the calendar)."

Writing this into the SOP turns it from a good intention into an actual appointment with yourself.

2. Prepare your tools and views

Before dealing with numbers, you prepare your workspace. The SOP can specify:

  • Open banking and payment accounts in separate tabs.
  • Open your income and expenses spreadsheet or money-tracking tool.
  • Have your calendar or client list open for the month you're reviewing.

This keeps you from bouncing back and forth later.

3. Log and review income

Next, you look at what came in:

  • List all clients or income sources for the month.
  • For each, confirm:
    • Did I send an invoice?
    • Has it been paid?
  • Update your income log with:
    • Client/source, project, amount
    • Invoice date, payment date (or "unpaid")

You're not building a full accounting system here; you're making sure you know who paid, who didn't, and roughly how much came in.

This alone often reduces a lot of anxiety because you're no longer guessing.

4. Identify and handle unpaid invoices

Then you focus on money that should have come in but hasn't:

  • Filter your log for invoices marked "unpaid" and older than their due date.
  • For each invoice, decide whether it needs:
    • A first reminder
    • A second reminder
    • A different kind of conversation

Your SOP can link to or include short reminder templates that sound polite but clear. For example:

"Hi [Name], just a quick note that invoice [number] for [project] was due on [date]. These things are easy to miss – could you let me know when you expect to send it through?"

Handled on a schedule, this feels neutral and normal, not emotionally loaded.

5. Log and scan expenses

Then you flip to the "Money Out" view:

  • Check your bank and card statements for the month.
  • Log any new expenses in your expenses sheet:
    • Vendor, purpose, amount, monthly vs one-off.
  • Highlight anything that looks unfamiliar or surprisingly high.

Your SOP can prompt you to ask simple questions:

  • "Is this subscription still useful?"
  • "Am I paying for similar tools that overlap?"
  • "Is there a free or cheaper option that would be enough for now?"

You don't need to optimise everything every month. The goal is to stay aware and make one or two small improvements.

6. Do a mini admin tidy

While you're already in "maintenance mode", your SOP can guide you through quick admin actions that often get ignored:

  • Archive finished project folders or emails.
  • Move loose files into the right client or project folders.
  • Check that key documents (contracts, receipts, agreements) are in your "important" space.
  • Review your list of active projects and check if any can be formally closed.

You're not trying to reorganise your whole digital life every month. You're just preventing build-up.

7. Capture a simple monthly snapshot

To finish, your SOP can ask you to answer a few reflective questions in a log:

  • Roughly how much did I earn this month?
  • What percentage came from my main offer(s)?
  • Did anything feel especially easy or especially heavy about money this month?
  • What is one decision or small change I want to make for next month?

This keeps you connected to the direction your business is moving, rather than just reacting to daily fires.

How to Write These SOPs Without Overwhelm

Knowing what should be in these three SOPs is one thing. Getting them out of your head and into a usable format is another.

Here's a practical way to create them without feeling like you're writing a textbook.

1. Start from reality, not from imagination

Instead of trying to design the "perfect process" from a blank page, start with what you already do.

For each SOP:

  • Run the process once (or mentally replay the last time you did it).
  • Write down every step you actually took, in rough order.
  • Include messy moments like "search for last version of this email" or "check WhatsApp to remember what the client said".

Only after you capture reality should you start organising and improving.

2. Keep the language human and direct

Write your SOP as if you're talking to yourself on a tired day when you don't want to think:

"Open [folder] and duplicate last month's invoice."

"Send welcome email template and personalise the first paragraph."

"Check that all links in the document work by clicking each one."

Avoid legal or overly formal language. You don't need "hereby" or "shall". You need verbs and clarity.

3. Add context where it actually helps

Some steps will make sense on their own. Others might benefit from a quick note.

For example:

"Check client name spelling in subject line and greeting. (This is one of the top places where mistakes slip through.)"

Those small bits of context remind you why a step matters and make it more likely you'll follow it even when you're in a rush.

4. Decide where these SOPs will live

Before you finish drafting, pick a home:

  • A folder called "Operations" in Google Drive
  • A Notion page called "How We Work" with sub-pages
  • A set of Word documents in a clearly labelled folder

Create a simple index at the top level:

Client Onboarding SOP – link

Core Delivery & Quality SOP – link

Monthly Money & Admin SOP – link

You want to reach any of them within a few seconds when you need them.

5. Let Version 1 be imperfect—and use it anyway

The only bad SOP is the one that lives in your head and not on paper. Your first versions will be rough. That's fine.

What matters more than polish is using them while you work:

  • Open your onboarding SOP when someone says yes.
  • Open your delivery SOP when you're preparing something to send.
  • Open your money SOP at the start of your monthly slot.

Each time you follow one, you'll see things you want to tweak. That's a sign it's working, not failing.

Keeping Your SOPs Alive and Useful

SOPs lose value when they become outdated or ignored. To keep them alive, build small habits around them instead of big promises.

Review them lightly during your weekly or monthly check-in

You don't need a formal review meeting. Just:

  • When you use an SOP and something feels off, edit it right afterwards.
  • Once a month, skim your three core SOPs and ask:
    • "Is there anything here that no longer matches how I work?"
    • "Have I learned a better way to do this step?"

Small, frequent edits are easier than occasional big rewrites.

Mark versions and dates simply

You can add a tiny footer:

"Last updated: 7 October 2025"

This helps you trust the document. If you know it was touched recently, you're less likely to think "this is probably outdated".

Treat SOPs as support, not rules

Your SOPs are there to help you, not to punish you. If you occasionally need to deviate because a situation is unusual, that's okay. You can even add:

"Exception: For X type of client, skip steps 3 and 4 and follow [link] special process."

The goal is not rigidity. The goal is reliable support in the background of your work.

A 7-Day Action Plan to Create Your First 3 SOPs

Here's a realistic plan you can follow without pausing your business.

Your 7-Day SOP Creation Plan

Day 1: Choose your order and create your "Operations" home

  • Decide which SOP to start with: onboarding, delivery, or monthly money.
  • Create an "Operations" folder or page and add three empty documents:
    • "Client Onboarding SOP (Draft)"
    • "Core Delivery & Quality SOP (Draft)"
    • "Monthly Money & Admin SOP (Draft)"

Day 2: Draft Client Onboarding SOP (Version 1)

  • Think about your last 1–2 clients.
  • Write down what actually happened from "yes" to "we started".
  • Turn that into rough sections: trigger, internal setup, welcome email, info collection, kickoff, "done when".
  • Don't worry about perfect wording yet.

Day 3: Update Client Onboarding SOP while using it

  • The next time a lead looks close to saying yes, keep the SOP open.
  • As you follow it, update unclear lines and add missing steps.
  • At the end, add "Last updated [date]" at the bottom.

Day 4: Draft Core Delivery & Quality SOP (Version 1)

  • Choose your main service.
  • Describe its stages and list the actions you currently take in each one.
  • Write a "ready to send" checklist for your most common deliverable.
  • Add a short section about how you package and send work.

Day 5: Use the Delivery SOP on a real piece of work

  • While you prep a client deliverable, follow your SOP.
  • Notice where you're tempted to skip steps or where something feels out of order.
  • Adjust the document so that it matches what actually works.

Day 6: Draft Monthly Money & Admin SOP (Version 1)

  • Decide your monthly money slot and write it into the SOP.
  • Define steps: prepare tools, log income, check unpaid invoices, log expenses, mini tidy, capture snapshot.
  • Keep it to one or two pages maximum so it feels doable.

Day 7: Run a mini Money & Admin session

  • Even if it's not your usual date, run a shortened version using the SOP.
  • Notice whether the steps feel too detailed or too vague and adjust.
  • Add the "Last updated" line.

At this point, you won't have a "perfect" operations manual. You will have something better: three living SOPs that match how you actually work and make your day noticeably lighter.

You don't need a huge team to deserve proper systems. Even as a one- or two-person business, these three SOPs can make the difference between constantly re-inventing your week and quietly running a business that feels stable, calm, and ready to grow.

Ready to build systems that scale?

Let's create SOPs and workflows that make your business run smoothly—without the overwhelm.

Work with Kilnbyte