# Small Business SOP Starter Pack

## Stop Running Your Business From Memory

Turn a recurring task into a clear, reusable system your team can follow without chasing you for the next step.

**Built for:** solopreneurs, consultants, agencies, coaches, and small service businesses.

---

## What a Useful SOP Covers

Use this checklist before you call a process ready to hand off.

- [ ] **Name the result.** Write the finished outcome, not just the activity. Example: “A new client has confirmed their kickoff time and knows what to prepare.”
- [ ] **Choose one trigger.** State exactly what starts the process: a signed agreement, a paid invoice, a booked call, or another observable event.
- [ ] **Assign one owner.** One person owns moving the process forward, even if others contribute.
- [ ] **List inputs.** Capture what must be available before work begins: form responses, access, payment confirmation, files, or approvals.
- [ ] **Write the steps in order.** Use short action verbs. One step should create one clear action or decision.
- [ ] **Set a standard and deadline.** Define what “done well” looks like and when each critical action happens.
- [ ] **Plan for exceptions.** Note what to do when information is missing, a client does not respond, or the normal path breaks.
- [ ] **Link the working tools.** Point to the exact folder, form, CRM record, tracker, or template used in the process.
- [ ] **Define the handoff.** Name who receives the completed work and how they know it is ready.
- [ ] **Review after real use.** Improve the SOP after the next three runs; remove steps that do not help and clarify the ones people miss.

---

## Fill-In Process Template

Copy this page into your workspace and complete it for one recurring task.

### [Process Name]

**Outcome**  
When this process is complete, ________________________________________________.

**Trigger**  
Start this process when ________________________________________________.

**Owner**  
The person accountable for moving it forward is ________________________________________________.

**Inputs required**  
Before starting, confirm you have:

1. ________________________________________________
2. ________________________________________________
3. ________________________________________________

**Steps**

1. ________________________________________________
2. ________________________________________________
3. ________________________________________________
4. ________________________________________________
5. ________________________________________________

**Standard and timing**  
This is complete when ________________________________________________.  
Critical deadline or response time: ________________________________________________.

**Exceptions**  
If ________________________________________________, then ________________________________________________.

**Tools and links**  
Use: ________________________________________________.

**Handoff**  
Send the completed work to ________________________________________________ via ________________________________________________.

**Last reviewed**  
Date: ____________________  |  Next review: ____________________

---

## 30-Minute Implementation Guide

### 1. Pick the process that creates the most repeat questions (5 minutes)

Choose a task you perform at least twice a month and explain repeatedly: client onboarding, discovery-call follow-up, project kickoff, proposal delivery, or weekly reporting. Start small; a useful one-page SOP beats an unfinished operations manual.

### 2. Document the current way, not the ideal way (10 minutes)

Walk through the last time you completed the task. Write the actual trigger, decisions, tools, and handoffs. Do not optimize yet—make the existing work visible first.

### 3. Make ownership and standards explicit (10 minutes)

For every critical step, answer: who does this, by when, and what tells us it is complete? Add one exception path for the most common delay or missing input.

### 4. Test once and improve (5 minutes)

Use the SOP on the next live task, or ask someone else to follow it. Record the first point where they need to ask a question. That question is the next line your SOP needs.

---

## Keep Building From Here

One dependable process reduces chaos. A small library of dependable processes gives your business room to grow.

Build your next operating system with Nexonym.

*Nexonym — Digital products. Instant impact.*

---

## Design Direction for Downloadable Layout

Keep the future PDF or hosted version premium and minimal: near-black background (`#0F1320` / `#111827`), high-contrast off-white type (`#E5E7EB`), restrained purple/indigo highlights (`#7C5CFF`, `#A788FA`), and Space Grotesk. Use generous space, fine divider rules, a small purple accent line, and simple document/checklist icons. Avoid generic stock imagery and dense visual decoration.