Ask the question out loud. Most founders answer in under five seconds, and the answer is usually right.
Why this one question works
“If sales doubled next month, or you took a week off, what would break first?” forces two tests at once. Doubling sales tests capacity: can the business take twice the work without you doing twice the work? A week off tests dependence: does the business run to a standard, or does it run on you? The thing that fails both tests is the operation behind the sale, and it is the thing to fix first.
The question also keeps you honest about growth. Founders often say they want to grow or they want their time back. In practice the same fix does both: when work has an owner, a standard and a check, more of it can happen without more of it coming back to you.
The five places it usually breaks
- The handoff. The sale closes and the project starts when someone finds time to start it. Scope, approver and inputs live in your head. Breaks when sales double.
- The owner. Capable people, nobody accountable for the result, so decisions climb back to you. Breaks when you are away.
- The standard. “Done” means whatever you would accept. Work comes up to you instead of out to the customer. Breaks both ways.
- The check. Mistakes are caught by the customer: the wrong price on the page, the follow-up that never went out. Breaks when you are away.
- The numbers. You find out about problems late, from a complaint or a bank balance, because nothing is reviewed weekly. Breaks when sales double.
A twenty-minute diagnostic
Take the path a customer travels after they say yes, and write down the stages. For an agency that is usually sale → kickoff → delivery → review → invoice. For an online business it is purchase → access → onboarding → support → renewal. Then, for each stage, answer four questions:
For each stage
- Who owns it? One name, not a team. If the honest answer is “me” or “whoever notices”, mark it.
- What is the standard? Could a new hire tell what “done” looks like from what is written down? If not, mark it.
- Where is the check? Is there a step that catches mistakes before a customer sees them? If the check is “the customer tells us”, mark it.
- What number tells you weekly that it is working? If nothing is looked at weekly, mark it.
Count the marks. A stage with three or four marks is what breaks first. If every stage is marked, start with the handoff: it is the one that makes every later stage worse.
What to do with the result
Pick the stage with the most marks and fix it in this order, because each step makes the next one possible:
- Name the owner and give them the authority to hold others to the standard. Owner without authority is a messenger.
- Write the standard where the work happens: in the task template, the checklist, the brief. Not in a separate document nobody opens.
- Add one check before the customer sees the result. Two lines are enough: what to look at and what to do if it is wrong.
- Pick one number and look at it every week for a month. Late items, rework, tickets, refunds: whatever the stage produces when it fails.
- Then step back. Do not review the work for two weeks. If the stage holds, move to the next one. If it does not, the owner, the standard or the check is wrong, and the number will tell you which.
Two traps
Writing SOPs first. Documents do not run a business; owners, checks and a weekly rhythm do. Write the standard into the work, not into a manual.
Buying a tool first. A new platform does not fix a missing owner. Set up the tools you already have around the way the work actually flows, then decide what to add.
When to get help
If you can name the stage and the tool, a Workflow Sprint fixes it in ten business days at a fixed price. If several stages are marked and you want them fixed with your team one at a time, that is what Operating Partner is for. If the honest answer to “who owns operations?” is “nobody senior”, read about Fractional COO. And if you are not sure, book 30 minutes and bring your marked-up list.