10 min read

Sample Standard Operating Procedures: 10 Workflow SOPs

Sample Standard Operating Procedures: 10 Workflow SOPs

Sample standard operating procedures show you what a finished SOP looks like, so you can copy the shape instead of starting from a blank page. Below are ten filled-in SOP examples for a small service business, written in the same format I used to document my agency in a numbered library.

A good sample SOP has a numbered title, a one-line purpose, who, what, when, where and why, short steps with one action each, and a "done when" line. The ten below cover sales, onboarding, content, finance, support and hiring. Copy one, swap in your tools, and have Claude draft the rest from recordings.

The blank format is in my SOP template. This page is the filled-in version.

How to use these SOP examples

These are samples for a typical small service business, not copies of my clients' documents. Policies like the refund window are placeholders for your own. Each one follows the template: number, purpose, who, what, when, where, why, steps, done when. Add your own recording link.

SOP library

numbered P001 to P010, one file per procedure

  • Sales

    P001 lead follow-up, P002 proposals

  • Onboarding

    P003 new client onboarding

  • Content

    P004 publishing, P005 social scheduling

  • Finance

    P006 invoicing, P007 month-end close

  • Support

    P008 support tickets, P009 refunds

  • Hiring

    P010 hiring a virtual assistant

Ten sample SOPs across one small business

Each SOP ends with a note on why it works and a one-line prompt. Use it with this base prompt and a transcript of you doing the task:

> Here is a transcript of me doing a task, and my SOP template. Fill the template from the transcript. One action per step, plain words, no steps I did not do. Put anything unclear under "Questions for the owner".

If you need the task-level clicks under each step, see step-by-step instructions examples. For the decisions drawn out, see the matching process flowchart examples.

Sales SOP examples

P001: New lead follow-up

P001 - New lead follow-up
Purpose: Every new lead gets a fast, personal reply so fewer go cold.
Who: Sales assistant. For the owner's calendar.
What: Reply to new leads and book a discovery call.
When: Every new lead form, during business hours.
Where: Shared inbox, CRM, calendar booking link.
Why: Leads that wait go to whoever replies first.

Step 1: Add the lead to the CRM with the tag "new-lead".
Step 2: Call the lead. If no answer, leave a short voicemail.
Step 3: Send the "First reply" email with the booking link.
Step 4: Set Stage to "Contacted".
Step 5: If no reply, start the follow-up sequence.
Done when: the lead books a call or is marked "Cold".

Why it works: the "why" line explains the speed, so nobody leaves leads until the afternoon. Prompt: base prompt, plus "include the exact follow-up timing I mention."

P002: Proposal and follow-up

P002 - Proposal and follow-up
Purpose: Qualified leads get a clear proposal the same day as the call.
Who: Account manager. Owner approves price.
What: Draft, approve and send the proposal, then follow up.
When: After every discovery call marked "Qualified".
Where: Call notes, proposal template, CRM, e-sign tool.
Why: Proposals sent days later close less often and get forgotten.

Step 1: Open the call notes and the proposal template.
Step 2: Fill in the client's goals, scope and timeline.
Step 3: Send the draft to the owner to approve the price.
Step 4: Send the approved proposal through the e-sign tool.
Step 5: Follow up two days later if it is not signed.
Done when: signed and moved to onboarding, or marked "Lost" with a reason.

Why it works: the owner approval step sits inside the SOP, so pricing never goes out unchecked. Prompt: base prompt, plus "mark the step where the owner approves."

Onboarding SOP example

P003: New client onboarding

P003 - New client onboarding
Purpose: New clients get set up so their work starts on time.
Who: Account manager, campaign manager, copywriter, client success.
What: Onboard every new client from signed proposal to kickoff.
When: Every time a client signs a proposal.
Where: Google Drive, the client database, the project tool.
Why: A slow start is a common reason a new client feels let down.

Step 1: Send the first invoice.
Step 2: When paid, send the welcome email and the onboarding form.
Step 3: Create the client folder from the template in Drive.
Step 4: Create the onboarding tasks in the project tool.
Step 5: Chase any logins or assets not received in 3 days.
Step 6: Book and run the kickoff call.
Done when: the kickoff is done and first-week tasks are assigned.

Why it works: the who line names every role, which is how my agency's onboarding SOP read. Prompt: base prompt, plus "list who owns each step."

Content SOP examples

P004: Content publishing

P004 - Content publishing
Purpose: Approved content goes live correctly and on schedule.
Who: Content assistant. Owner gives final approval.
What: Take a draft from "Ready" to published.
When: Every draft marked "Ready" on the content board.
Where: Content board, website editor, image folder.
Why: Typos, broken links and missed dates cost trust.

Step 1: Open the draft and check it against the brief.
Step 2: Send it to the owner for approval.
Step 3: Paste it into the website editor and add the meta description.
Step 4: Upload the image and write its alt text.
Step 5: Preview on desktop and mobile, then publish.
Step 6: Paste the live link on the board card.
Done when: the link works and the card shows "Published".

Why it works: the approval loop is written down, so drafts stop waiting in chat threads. Prompt: base prompt, plus "add a pre-publish check list at the end."

P005: Weekly social scheduling

P005 - Weekly social scheduling
Purpose: The week's posts are scheduled before the week starts.
Who: Social media assistant.
What: Schedule every approved post for the coming week.
When: Every Friday.
Where: Content board, scheduling tool.
Why: Posting in the moment leads to gaps and rushed captions.

Step 1: Filter the board to "Approved" posts for next week.
Step 2: Upload each file and caption to the scheduler.
Step 3: Set accounts, dates and times from each card.
Step 4: Move each card to "Scheduled".
Done when: next week's calendar matches the board.

Why it works: it is tied to a day of the week. Prompt: base prompt only.

Finance SOP examples

P006: Invoicing and collections

P006 - Invoicing and collections
Purpose: Every client is billed on time and late payments are chased.
Who: Finance assistant. Owner decides on accounts over 30 days late.
What: Send invoices and follow up on unpaid ones.
When: The 1st of each month, and every Monday for chasers.
Where: Billing tool, client contracts in Drive.
Why: Money that slips here is pure loss.

Step 1: Duplicate last month's invoice for each client.
Step 2: Check each amount against the contract.
Step 3: Send the invoices.
Step 4: Every Monday, send a reminder on any unpaid invoice.
Step 5: Send accounts over 30 days late to the owner.
Done when: every invoice is sent and late accounts are flagged.

Why it works: the limit of what the assistant decides is written in. Prompt: base prompt, plus "state who decides at each lateness stage."

P007: Month-end close

P007 - Month-end close
Purpose: The owner sees an accurate month in one page.
Who: Finance assistant. For the owner and bookkeeper.
What: Match transactions, chase gaps, write the summary.
When: The last working day of each month.
Where: Bank and card exports, receipts folder, finance folder.
Why: Errors found months later are harder to fix.

Step 1: Export bank and card transactions.
Step 2: Match each one to an invoice or receipt.
Step 3: List anything unmatched and ask the owner.
Step 4: List unpaid invoices.
Step 5: Write a one-page summary and save it.
Done when: the summary is sent to the owner and bookkeeper.

Why it works: it ends in a document someone reads. Prompt: base prompt, plus "add the summary's headings."

Support SOP examples

P008: Support tickets

P008 - Support tickets
Purpose: Every customer question gets a correct answer within one business day.
Who: Support assistant.
What: Answer, route or escalate incoming questions.
When: Twice a day, morning and afternoon.
Where: Support inbox, saved replies, CRM.
Why: Slow or wrong answers turn small problems into refunds.

Step 1: Sort new messages into question, problem or complaint.
Step 2: Answer questions with the matching saved reply.
Step 3: Send problems to the person who owns that area.
Step 4: Send complaints to the owner the same day.
Step 5: Log each ticket in the CRM.
Done when: the inbox has no unanswered message older than a day.

Why it works: three categories, three routes, no guessing. Prompt: base prompt, plus "turn my answers into saved replies."

P009: Refund request

P009 - Refund request
Purpose: Refunds are handled the same way every time.
Who: Support assistant. Owner for anything outside policy.
What: Check, issue or escalate refund requests.
When: Every refund request.
Where: Support inbox, payment tool, CRM.
Why: Inconsistent refunds create unfair outcomes and disputes.

Step 1: Find the order and its date.
Step 2: If inside the refund window, issue the refund.
Step 3: If outside, send it to the owner with the order details.
Step 4: Email the customer the outcome.
Step 5: Log the reason in the CRM.
Done when: the customer has an answer and the reason is logged.

Why it works: the decision is one question. Prompt: base prompt, plus "write my refund policy as one yes or no question."

Hiring SOP example

P010: Hiring a virtual assistant

P010 - Hiring a virtual assistant
Purpose: Hire assistants who can follow the SOP library from week one.
Who: Owner, with an operations lead.
What: Post, test, interview and set up a new assistant.
When: When a role is approved.
Where: Job board, test task doc, interview calendar, the SOP library.
Why: A bad hire costs weeks of training and redone work.

Step 1: Write the job post and a short paid test task.
Step 2: Post the listing.
Step 3: Shortlist applicants who meet the must-haves.
Step 4: Send the test task to the shortlist.
Step 5: Interview those who pass.
Step 6: Set up tools and assign the first week's SOPs.
Done when: the new hire has finished their first assigned SOP.

Why it works: the done line is the first finished task, not the signed contract. I hired and managed assistant teams for years, including a team of ten in the Philippines, and the point of a library is that the next hire learns from it, not from you. Prompt: base prompt, plus "list the SOPs a new hire should learn first." Weighing a hire against AI? Read hire a virtual assistant vs AI.

From SOPs to automation

Once written, each step gets a label: person, workflow tool or AI agent. "Duplicate last month's invoice" is a rule. "Sort new messages into question, problem or complaint" is an agent job. I explain the split in AI business process automation, and how to save the drafting prompt as a reusable skill in Claude skills for business. For running a VA team with the same library, see Claude Code for virtual assistants.

Sample standard operating procedures: FAQ

What is an example of a standard operating procedure?

A new client onboarding SOP is a common example: it names the purpose, the roles involved, the trigger (a signed proposal), the tools, then steps from the first invoice to the kickoff call, and ends when first-week tasks are assigned.

What should an SOP for a small business include?

An SOP for a small business should include a number and title, a one-line purpose, who, what, when, where and why, short steps with one action each, and a done-when line. Add a screen recording link and a last-updated date.

How many SOPs does a small business need?

Start with five to ten SOPs for weekly work that costs money when it slips: lead follow-up, onboarding, invoicing, content and support. Add more as you hand off tasks.

Can I use these SOP examples as templates?

Yes. Copy any sample, change the tools, names and policies to your own, and record yourself doing the task to check the steps.

Can Claude write SOPs for me?

Yes. Give Claude a transcript of you doing the task and your SOP template, and it fills in the format. Have the person who does the task follow it once and fix any step where they get stuck.

Get the jobs, not just the format

The AI Operator Kit gives you five ready systems for content, leads, outreach, sales and building, a daily operator plan and 107 prompts sorted by job, so the procedures your business runs every week are already written for Claude.

More on automation

View all