Would your business survive three months without you?
Let's start with a morbid but necessary question: If you were hit by a bus tomorrow and couldn't work for 3 months, would your business survive?
For many Indian MSME founders, the honest answer is a terrifying "No."
Your sales team doesn't know how to approve a discount without asking you. Your accountant doesn't know which vendors to prioritize. Your operations manager doesn't know how to handle that one specific client who needs special packaging.
Your business isn't a system; it's a series of fires that only you know how to extinguish. And every question that only you can answer costs your team time: McKinsey Global Institute estimates that the average interaction worker spends nearly 20 percent of the workweek looking for internal information or tracking down colleagues who can help with specific tasks.
The only way to escape this "Founder's Trap" is through Standard Operating Procedures (SOPs). But wait - before you scroll away thinking this is boring corporate paperwork, let me stop you.
SOPs are not 100-page manuals that gather dust in a cupboard. In 2026, an SOP is a 3-minute Loom video. It is a 5-point checklist on WhatsApp. It is the "source code" of your company.
Short checklists work even for highly trained experts. When eight hospitals in eight cities, including New Delhi, introduced a 19-item surgical safety checklist under a World Health Organization programme, the death rate fell from 1.5% to 0.8% and inpatient complications fell from 11.0% to 7.0% (Haynes et al., New England Journal of Medicine, 2009). Your invoicing process is less dramatic, but the principle is the same: a checklist catches what memory misses.
This guide provides a comprehensive SOP checklist for small business owners, specifically designed for the fast-paced, chaotic reality of the Indian market.
How to Run the Hit By A Bus Test in Five Days
You do not need a consultant to find out how exposed your business is. You need one working week and a notebook.
- Day 1, log every interruption: write down every question, approval and decision that comes to you, with the name of the person who asked. Do not filter. The "small" ones matter most.
- Day 2, map each item: for every entry, note who else could handle it tomorrow and where the instructions live today: a document, a video, someone else's memory, or only yours.
- Day 3, score the critical processes: use the scorecard below for each process that touches cash, customers or delivery.
- Day 4, run a short absence drill: stay off calls and WhatsApp for a full working day, or two if you can. Ask a deputy to keep a list of everything the team could not resolve without you.
- Day 5, build the backlog: combine the Day 1 log and the drill list. Every item on it is an SOP, a decision rule or a training gap. Rank the items by how often they occur and how much damage they do when they go wrong.
| Score | What it means | What to do next |
|---|---|---|
| Red | Only you know how to do it, and nothing is written or recorded | Record it this month and train one backup person |
| Amber | Someone else can do it, but they still call you for exceptions or approvals | Write down the decision rules and approval limits, not just the steps |
| Green | It is documented, a trained backup has done it without you, and the SOP has a named owner | Review it every quarter |
Your business passes the test when every process on the critical path scores green. Many owners find their reds in finance and in the relationships with their biggest clients.
Part 1: The "Video-First" Methodology (Stop Writing Manuals)
The biggest mistake founders make is trying to write SOPs. You sit down to write a "Procurement Policy," stare at a blank Word doc for 20 minutes, get bored, and quit.
The Solution: Record, Don't Write.
- Identify the Task: e.g., "Creating a GST Invoice."
- Hit Record: Use a tool like Loom or Vidyard.
- Do the Task: Perform the task on your screen while talking through what you are doing. "Okay, first I log into Zoho Books, then I click 'New Invoice'. Make sure you select the correct 'Place of Supply' or the IGST calculation will be wrong..."
- Save & Share: Save this video in a Google Drive folder named "Finance SOPs."
Done. You have just created an SOP in the exact time it took to do the task.
Part 2: Which SOPs Should a Small Business Write First?
You cannot document everything at once. Use this checklist to prioritize the "Critical Path" processes - the ones that, if broken, stop the cash flow.
A. Finance & Accounts (Priority: High)
If this breaks, you run out of cash.
- [ ] Invoicing Process: How to generate a bill, what tax codes (HSN/SAC) to use, and who approves it.
- [ ] Collections Follow-up: A script for the accounts team to call clients who are 30+ days overdue. (e.g., "Monday morning calls script").
- [ ] Vendor Payments: Who gets paid first during a cash crunch? What is the approval limit for the accountant (e.g., up to ₹10,000)?
- [ ] Petty Cash Handling: How is cash dispensed, and how are receipts digitized?
B. Sales & Marketing (Priority: High)
If this breaks, growth stops.
- [ ] The "First Call" Script: How should a salesperson answer the phone? What are the qualifying questions?
- [ ] Proposal Template: A standard format for quotes so your team doesn't send ugly, unformatted Word docs to clients.
- [ ] Lead Entry: How to enter a new lead into the CRM (Zoho/Salesforce). Required fields (Name, Number, Source).
- [ ] Objection Handling: A "Cheat Sheet" for common objections like "Your price is too high" or "We are happy with our current vendor."
C. Operations & Delivery (Priority: Medium)
If this breaks, you lose customers.
- [ ] Client Onboarding: What happens immediately after a deal is signed? (Welcome email, WhatsApp group creation, Project kickoff).
- [ ] Quality Control (QC) Checklist: The final 5 things to check before a product is shipped or a service is delivered.
- [ ] Inventory Reordering: At what stock level do we reorder? (The "Reorder Point").
- [ ] Complaint Escalation: If a customer is angry, who handles it? What is the "Make Good" offer we are allowed to give?
D. HR & Admin (Priority: Low - but essential for peace of mind)
- [ ] Hiring Process: Standard job descriptions, interview questions, and the offer letter template.
- [ ] Onboarding New Hires: A checklist for Day 1 (Laptop setup, Email creation, Introduction to team).
- [ ] Leave Policy: How to apply for leave and who approves it.
Part 3: The "SOP Template" You Can Steal
Don't overcomplicate the format. If you must write it down, use this simple structure.
[Process Name]: Handling Customer Returns
[Owner]: Warehouse Manager
[Goal]: To process returns within 48 hours and update inventory.
Prerequisites:
- Customer Return Authorization (RA) number.
- Access to Inventory Management System.
The Steps:
1. Receive Package: Check the package for physical damage before opening.
2. Verify Contents: Match the item received with the RA slip.
- If mismatch: Take a photo and WhatsApp the Sales Rep immediately.
3. Quality Check:
- Grade A: Unopened, resellable → Put back in Main Stock.
- Grade B: Opened, functional → Put in "Refurbished" bin.
- Grade C: Damaged → Move to "Scrap" pile.
4. System Entry: Log into the ERP, go to "Returns," and mark the status.
5. Credit Note: Trigger the finance team to issue the credit note.
Video Walkthrough: [Link to Loom Video]
Part 4: How Do You Get Your Team to Actually Use SOPs?
Writing the SOP is the small part of the work. Getting your staff to use it is the big part. The Indian workforce often resists documentation ("Sethji, I know how to do it, why write it down?").
The "Train the Trainer" Strategy:
- Don't write it yourself: Ask your best employee in that department to create the draft. They know the reality better than you.
- The "No SOP, No Answer" Rule: When an employee asks you a question that is already documented, do not answer them. Send them the link to the SOP. If you keep answering, they will never look at the document.
- Review Quarterly: Processes change. Set a calendar reminder every 90 days to "Audit SOPs."
Part 5: A Worked Example, the Discount Approval
Take one of the most common founder interruptions: a salesperson wants to offer a discount to close a deal.
Before the SOP, every discount request goes to the founder. Deals wait while the founder is travelling or in meetings, and each salesperson learns a slightly different version of what is "allowed".
After the SOP, the rule is written down once. For example, a salesperson may approve a discount up to a set percentage on standard products, the sales head may approve up to a higher limit, and anything beyond that, or any change to payment terms, goes to the founder with a one-line reason. The exact limits are your call. What matters is that they exist in writing. The SOP also lists what to check first, such as the customer's payment history and the margin on the order, and where to log the approval in the CRM.
The result is that the founder sees only the exceptions that genuinely need judgement. This is why the best SOPs contain decision rules as well as steps. Steps tell people how to do the task. Decision rules tell them when they may act without asking you.
Part 6: Common Mistakes That Kill SOP Projects
- Trying to document everything at once. Start with the critical path, and finish ten processes before you start the next ten.
- The founder writing every SOP. The person who does the work should record the first draft; you review it.
- Storing SOPs in personal drives and WhatsApp chats. Use one shared folder or tool, with a clear naming convention by department.
- Documenting the ideal instead of the reality. Record how the task is actually done today, then improve it.
- Leaving out the limits. Without approval limits and decision rules, people follow the steps and still call you.
- No owner and no review date. Every SOP needs a named owner and a next-review date, or it quietly goes out of date.
- Never testing it. Hand the SOP to someone who has not done the task before. Wherever they get stuck, the SOP needs work.
Part 7: Your 90-Day SOP Plan
| Window | Focus | Output |
|---|---|---|
| Days 1-30 | Run the five-day test, then record the finance processes | Invoicing, collections, vendor payment and petty cash SOPs, each with a named owner |
| Days 31-60 | Sales, operations and delivery | First-call script, proposal template, CRM lead entry, client onboarding and the QC checklist |
| Days 61-90 | HR, admin and the first review | Hiring and onboarding checklists and the leave policy, then a repeat of the absence drill and a fresh score |
At day 90, compare the list of questions your team could not answer during the second absence drill with the list from the first. If it is shorter, the system is working. If it is not, look at which SOPs were written but never used, and apply the "No SOP, No Answer" rule more firmly.
Conclusion
Great businesses are boring. They are boring because they are predictable. McDonald's is boring. The burger tastes the same in Mumbai as it does in Delhi. That "boring" predictability is what lets a business grow without the founder in every decision.
Use this SOP checklist for small business to build your own boring, predictable, and highly profitable machine.
Need Help Building Your Business Operating System?
Start with the Stratisian Operating System, a free framework of SOP templates you can read with no sign-up. If you want help building the system with your team, see how the diagnostic and execution work are priced on our pricing page, then book a strategy call.
This guide is part of the Stratisian Vault - execution playbooks for scaling businesses across the India-Gulf (GCC) corridor.