SOPs your team actually follows — written with them, measured weekly, enforced.
Most SOP documents die in a folder. I write operating procedures with the people who do the work, attach a KPI to each one, and install the weekly rhythm that keeps them alive — so the business runs the same way whether or not you are in the room. 24 years of running sales, operations and e-commerce teams, not writing about them.
Purpose: every complaint logged, answered and closed within SLA
- Log complaint with tracking ID within 15 minutes of receipt (WhatsApp, call or email)
- Acknowledge to customer with ID and expected response time
- Assign to engineer by zone; manager escalation if unassigned after 4 working hours
- Close only after customer confirmation; log root cause
The document is not the problem. The follow-through is.
Businesses hire an SOP writer, receive a 90-page manual, and nothing changes. The procedures were written about the team instead of with them, nobody owns them, and nothing measures whether they are followed.
- Written with the person who does the job, in their words, at the length they will read
- One owner and one KPI per procedure — if it cannot be measured, it is not finished
- Installed into the tools you use: WhatsApp groups, Google Sheets, your CRM, a checklist app
- A weekly operations meeting with a fixed agenda that reviews the numbers
- Automated where it makes sense — the complaint SOP above runs as a WhatsApp bot at my own company
An operating manual and the system that keeps it alive.
Process map
Every repeatable process in the business, who owns it today, and which ones leak money or depend on one person.
The SOPs that matter
Usually 8–15, not 90. Sales follow-up, quoting, order handling, delivery, complaints, onboarding, cash collection, reporting.
KPI framework
One measurable per SOP, a dashboard your managers update themselves, and targets agreed with the team.
Operating cadence
Weekly ops meeting, monthly review, quarterly reset — with agendas, so it survives without me.
Training and roll-out
Each SOP trained with the team that runs it, with a 30-day check that it is being followed.
Automation where it pays
Steps that can be automated get built — n8n workflows, WhatsApp bots, Google Sheets reporting — instead of asking humans to remember.
Six weeks from chaos to cadence.
Week 1–2 · Map
I sit with each role, watch the work, and map every process with its owner, tools and failure points. You get the process map and the shortlist.
Week 3–5 · Write and install
SOPs drafted with the team, KPIs attached, dashboards set up, procedures installed into the tools people already use.
Week 6 and after · Run
First weekly ops meetings run with me in the room. 30-day follow-up on adherence. Optional monthly retainer or move to a fractional COO arrangement.
On-site in Pakistan and the Gulf. Remote everywhere else.
Before you reach out.
What does an SOP consultant do?
Maps how your business actually runs, writes the standard operating procedures that matter with the people who do the work, attaches a KPI to each, and installs the routine that keeps them followed. The writing is the smallest part of the job.
How do you write SOPs for a small business without slowing it down?
Short, in the team’s own words, one page where one page will do, and installed as checklists in the tools people already open every day. A procedure nobody reads is worse than none, because it creates false confidence.
How much does SOP writing cost?
A fixed fee for the six-week programme, quoted after the free call once I know how many roles and processes are involved. Single-process SOPs (for example complaints or quoting) are quoted separately and are quick.
Can SOPs be automated?
Often, partly. If a step is “check, log, notify, remind”, software should do it. I build those with n8n, WhatsApp bots and Google Sheets or your CRM — the complaint-handling SOP at my own company runs as a bot that logs, acknowledges, assigns and escalates.
Do you work with teams in Urdu or Arabic?
Yes. I have run teams in Pakistan and across the GCC; procedures are written in the language the team actually uses, with English versions for management where needed.
What is the difference between this and a fractional COO?
This is a fixed six-week project that builds the operating system. A fractional COO is ongoing: I run that system with you two or three days a week. Many clients start here and continue there.
Which process keeps breaking?
Name it in a line or two. You will get a personal reply within one business day and a free 30-minute call.