SOP examples for a small service business, with the templates

By Mariam Raouf. Published 2026-07-06. 8 min read.

Most SOP examples for a small service business are written to look impressive rather than to be used. Twelve pages, a purpose statement, a scope statement, a revision history table, and no sentence saying what actually starts the thing.

A useful SOP is short and boring. It says what triggers it, who owns it, what the steps are in order, how you know it is finished, and what to do when it goes wrong. If a document has those five parts it works. If it is missing the trigger or the definition of done, it will sit unread in a shared drive forever.

Below are four SOPs written out in full, not described. Copy them, change the names, delete what does not apply.

What makes a useful SOP in a small service business

A trigger. The observable event that starts it. "A form is submitted." "A deal moves to Won." Not "when a new client joins", which is a state, not an event.

An owner. One named role. Not a team. If two people own it, nobody does.

Numbered steps. In order, each one an action a person can do without asking a question. Say which tool, which field, which template.

A definition of done. The condition that says it is finished. Everyone leaves this out, which is why work sits at ninety percent forever.

An escalation path. What to do when reality does not match the steps.

Write in the imperative. "Send the welcome email", not "the welcome email should be sent".

SOP 1: New client onboarding

Trigger: Deal moves to Won in the CRM. Owner: Account lead. Done when: The kickoff call has happened, the client has access to everything, and the project record shows a start date.

1. Within 4 business hours, send the signed proposal and the welcome email.
2. Create the client folder from the folder template, named for the client and start month.
3. Create the project record. Set the start date and the named client contact.
4. Send the intake form: billing contact, billing address, purchase order number if they use one,

brand assets, and any access you need.

1. Send the calendar link for the kickoff call. Offer three slots inside 10 business days.
2. Two business days before the call, confirm the intake form is complete. If not, phone the

client contact.

1. Run the kickoff call. Confirm scope, dates, the single point of contact on each side, and how

you will communicate.

1. Within 1 business day, send written notes with dates and owners.
2. Raise the deposit invoice per SOP 3.

Escalate if: the intake form is still incomplete 5 business days after kickoff, or the client asks for anything outside the signed scope. Escalate to the business owner, same day.

SOP 2: Responding to an inbound enquiry

Trigger: A website form submission, an email to the general inbox, or a voicemail. Owner: Whoever holds the enquiry inbox. Done when: The enquiry has a reply, a CRM record and a next action with a date, or a logged reason for declining it.

1. Log it in the CRM within 1 business hour: name, company, email, phone, source, and what they

asked for.

1. Reply within 4 business hours on business days. Acknowledge what they asked for specifically,

not with a generic hello.

1. Decide: qualified, not qualified, or more information needed.
2. If qualified, send the calendar link and set a CRM task for a call.
3. If not qualified, reply with a short honest no and a referral if you have one. Mark the record

Closed Lost with a reason.

1. If it needs more information, ask a maximum of three questions in one message.
2. If there is no reply after 3 business days, follow up once. After a second silence, mark it

Closed Lost and stop.

Escalate if: the enquiry mentions a deadline inside 2 weeks, a budget above your normal range, or a legal or compliance requirement. Escalate to the business owner immediately.

SOP 3: Invoicing and chasing payment

One number first, because it changes how you write this one. Among US firms surveyed in three industrial sectors, Atradius found 43% of the value of B2B invoices was overdue.

Source: Atradius Payment Practices Barometer, US 2025. Hold onto the caveat: 240 online interviews across three industrial sectors, agri food, energy and fuel, and electronics and ICT. That is not a survey of US small businesses generally and I will not present it as one. It is still good evidence that late payment is normal, so build chasing into the process rather than treating it as a surprise.

Trigger: A milestone completes, or the invoicing date arrives for a retainer. Owner: Whoever runs the books. Done when: Payment has cleared and the invoice is marked paid in the accounting system.

1. Raise the invoice within 1 business day. Include the purchase order number if the client uses

one, because a missing reference is the most common reason an invoice sits.

1. Send it to the billing contact captured at onboarding, not your day to day contact. Copy the

day to day contact.

1. Offer bank transfer or ACH as the default, card on request. Stripe charges

0.8% capped at $5.00 for ACH against 2.9% plus $0.30 for cards, which on a $4,000 invoice is the difference between $5 and $116.30.

1. Three business days before the due date, send a short reminder. Friendly, no apology.
2. On day 1 overdue, email the billing contact and copy the day to day contact.
3. On day 7 overdue, phone. Email alone stops working around here.
4. On day 14 overdue, pause new work and say so in writing, referencing your contract.
5. On day 30 overdue, send a formal demand and decide whether to escalate.

Escalate if: an invoice passes 30 days, or a client goes silent for 10 days after a chase. Tell the business owner, with the invoice number, amount and chase history.

SOP 4: Offboarding a client

The one everybody skips, and the one that costs most in security risk and lost referrals.

Trigger: Final deliverable accepted, or notice given by either side. Owner: Account lead. Done when: Access is revoked, files are handed over, the final invoice is paid, and the CRM record is closed with an outcome.

1. Confirm the end date in writing and what is included before it.
2. Deliver everything outstanding. Send one handover document listing what was delivered and where.
3. Transfer ownership of assets held in your accounts: domains, ad accounts, analytics,

repositories.

1. Revoke your access to their systems and theirs to yours, within 5 business days.
2. Remove the client from internal automations and shared inboxes so nothing keeps firing.
3. Raise the final invoice per SOP 3.
4. Ask for a testimonial or referral 2 weeks after final delivery, not on the last day.
5. Set a CRM reminder to check in at 6 months.
6. Archive the folder and close the CRM record with an outcome note.

Escalate if: the relationship ended badly, anything is disputed, or credentials cannot be recovered. Escalate to the business owner before sending anything further.

How to write SOP examples for your own business

Do not write SOPs for everything. Write them for what repeats and for what somebody else will eventually run.

The fastest method is to do the job once with a document open and narrate it. Write what you actually did, including the bit where you checked something in another tab. Then have someone else follow it and note every place they had to ask a question. Those are your missing steps.

Review each one when it fails, not on a schedule. A quarterly reminder gets ignored. A rule that says fix the document before you fix anything else does not.

Where this leads

An SOP is not a filing exercise. It is what lets you hand work to somebody else without two weeks of shadowing, and it is the prerequisite for automating anything. You cannot connect a set of tools to run a process nobody has written down.

That is the honest order of operations. Write it, run it manually until it stops surprising you, then look at what could run itself. Our guide to what to automate first covers the choosing, and n8n vs Make vs Zapier covers the building.

At Calpir a lot of the work starts exactly here, with somebody's process written down properly for the first time. Our operations and HR page explains that side of it, and there is nothing stopping you writing these yourself this afternoon.

Frequently asked questions

What should a small business SOP include?

Five things: a trigger saying what starts it, one named owner, numbered steps in order, a definition of done, and an escalation path. Purpose statements, scope sections and revision tables are optional and mostly ignored. If it does not fit on one page, it is probably two SOPs pretending to be one.

How long should an SOP be?

One page. If a process needs more, split it, the way onboarding and invoicing are split above. Long documents get skimmed, and a skimmed SOP is worse than none because people believe they followed it. Screenshots help more than paragraphs when a step involves finding something in a tool.

Who should write the SOPs in a small business?

The person who currently does the job, not the owner writing down how they imagine it is done. The owner's version is always idealised. Have the person doing the work narrate it as they do it, then have a second person follow it and mark every point where they had to ask something.

Do I need SOPs before I automate anything?

Yes, and this is the practical reason to bother. Automation encodes a process exactly as written. If the process is not written, you will encode three people's different versions of it and find the conflict in production. Write the SOP, run it manually for a month, then automate the parts that never vary.

Sources

• Atradius, Payment Practices Barometer, US 2025
• Stripe US pricing