Standard Operating Procedures for Small Business: What to Write First

"SOP" is a corporate phrase for a simple idea: the way we do this thing, written down so it's done the same way every time. Big companies have thousands. A small business needs about five, and the order you write them matters.

Why order matters

If you write the SOP for something that rarely goes wrong, you've spent an afternoon and changed nothing. The first SOPs should be for the steps that cost the most when they're done inconsistently, which, in our experience, are the same five for almost every small business.

SOP 1: Inquiry intake

The first thing to standardize is what happens when a new customer contacts you. Because right now, it depends on who answers. One person captures everything, another writes a name on a napkin, and some inquiries never get written down at all.

The SOP is short: where the inquiry gets recorded, what details are required (name, contact, address, what they want, how they heard about you), what the customer receives back and how fast, and who owns the follow-up.

Why first: every inquiry that isn't captured properly is revenue that never existed. This is the most expensive inconsistency in most businesses, and it's invisible because you never see the customers you lost.

SOP 2: Quoting

How a price gets produced and sent. The rate sheet or pricing method, the template, who can send a quote, how long it should take from inquiry, and how it's recorded.

Why second: inconsistent quoting loses jobs (too slow), loses money (too low), and loses trust (two customers get different prices for the same work). A quoting SOP with a standard rate sheet is usually the single fastest revenue improvement a small business can make.

SOP 3: Job completion

What "done" means. What gets recorded when a job is finished: photos, notes, materials used, time, anything the customer signed. Who marks it complete and where.

Why third: everything downstream depends on this. If completion isn't recorded consistently, invoicing is late, job costing is impossible, and disputes are your word against the customer's.

SOP 4: Invoicing and collection

When the invoice goes out (the answer should be "on completion, automatically"), what it includes, when the first reminder goes out if it's unpaid, when the second, and who makes the call after that.

Why fourth: the gap between finishing work and getting paid is where cash flow dies. Most small businesses can shorten it by a week or more with nothing but a consistent procedure.

SOP 5: Problems and complaints

What happens when a customer is unhappy or something went wrong. Who they talk to, what that person can offer without asking (a redo, a discount up to a limit), when it escalates to the owner, and how it's recorded.

Why fifth: without this, every problem lands on the owner, and every response is improvised. A simple procedure lets your team handle most issues and makes the ones that reach you the ones that should.

How to write each one

Use the one-page format from our post on documenting processes without a manual: trigger, owner, steps, done-when, and rules. Twenty minutes each. Write it by doing the process once and recording each step. Put it where the work happens.

What comes after the first five

Once these five are running, the next SOPs come from wherever things still break: material ordering, scheduling changes, onboarding a new customer, handling a cancellation. Write them when the problem shows up, not before. Five good SOPs that get used beat thirty that sit in a folder.