If every decision waits for you, your business can only grow as fast as you can answer the phone. Making your business run without you is not about working less. It is about moving decisions, routines and reporting out of your head and into rules your team can follow. This guide covers the five pieces I put in place for owner-run businesses, in the order that works, and a simple test to know when you're done.
Sach batau? Most owners don't have a staff problem. They have a "sab kuch mujhse poochho" problem.
Step 0: Measure how dependent the business is on you
For one week, keep a notebook or a note on your phone. Every time someone calls, messages or walks in to ask you something, write one line: who asked, what about, and whether you were the only person who could answer.
At the end of the week, sort the list into three groups:
- Information: "Where is the file?" "What rate did we give them?" The answer exists. It just lives in your head.
- Approval: "Can I give 5% off?" "Can we buy this?" A rule and a limit would handle these.
- Judgement: real decisions only you should make.
In most businesses I see, the first two groups are the large majority. That's good news. They can be fixed with documents and rules, not with new people.
Step 1: Draw a delegation map
A delegation map is one page that lists every recurring area of the business and names one owner for each. Not "sales team". A person.
| Area | Owner | Backup | Reports to you |
|---|---|---|---|
| New enquiries and first reply | Sales executive | Sales head | Daily, in the 6 PM report |
| Quotations up to standard price | Sales head | Accounts | Weekly |
| Purchase of regular materials | Purchase in-charge | Production head | Weekly |
| Dispatch and delivery | Dispatch in-charge | Store keeper | Daily |
| Collections follow-up | Accounts | Sales head | Weekly |
Illustration: roles will differ in your business. The point is one named owner and one backup for each area.
Two rules make the map work. Every area has a backup, so leave and resignations don't stop work. And the map is shared with the team, so they know whom to ask instead of you. Later, turn each line into a one-page role card: what that person owns, the numbers they report and the decisions they can take.
Step 2: Set decision rights and approval limits
Most calls to the owner are approvals. Replace them with written limits.
- Sales head can give up to 5% discount on standard price. Above that, the owner.
- Purchase in-charge can order regular materials up to ₹50,000 per order from approved vendors. New vendors or bigger orders need the owner.
- Accounts can release vendor payments as per the agreed terms. Advance payments need the owner.
- Any staff member can spend up to ₹2,000 to fix a customer problem the same day, with a note in the report.
Illustration: these limits are examples. Set yours by looking at your last three months of approvals.
Start with lower limits and raise them every quarter as trust builds. A limit that is a little too low is far better than no limit at all. Write each one as "who can decide, up to what amount, and who to ask above that".
When someone still calls for something inside their limit, don't answer the question. Ask, "What does the rule say?" It feels slow for two weeks, and then the calls drop.
Step 3: Write SOPs for the tasks that break when you're away
You don't need a 200-page manual. You need one-page SOPs for the 10 to 15 tasks that go wrong when you're not watching: preparing a quotation, checking incoming material, packing and dispatch, raising an invoice, handling a complaint.
A good SOP fits on one page. It names the trigger (when this task starts), the steps in order, the standard (what "done properly" looks like), and who checks. Ask the person who does the task best to explain it while someone writes it down, then test it with a newer team member. If they can follow it without calling anyone, it works.
Use the one-page SOP template for the format, and my post on reducing dependency on one key employee for the same idea applied to your team, not just to you.
Step 4: Install the 6 PM daily report
Most owners stay close to the business by walking around and asking questions. That's why they can't leave. Replace the walk with a report.
Every team lead sends a short message by 6 PM, in the same format every day:
- Sales: new enquiries, quotations sent, orders won, value.
- Operations: orders dispatched, pending orders, any delay and why.
- Accounts: collections received, payments made, overdue amount.
- Problems: anything that needs a decision tomorrow.
Keep it to numbers and one line of problems. If a lead misses the report, that is the conversation, not the content. The 6 PM report and daily huddle template includes the format and a 15-minute morning huddle to act on it.
Step 5: Build a 2-minute dashboard
The daily report tells you what happened today. The dashboard tells you whether the business is healthy. It should take two minutes to read and fit on one screen of your phone.
Start with eight numbers or fewer: enquiries this month, conversion rate, orders booked, sales value, gross margin, cash in bank, receivables over 45 days, and one operations number such as on-time dispatch. Each has a target and a colour (green, amber, red). You look at the reds and ask the owner of that number what they're doing about it.
The format is in the one-page dashboard template. It can start as a spreadsheet updated every Monday. Automate it later, once you know which numbers you actually use.
The 2-week-break test
Here is how you know it's working. Plan a two-week break: a family trip, a trade fair, anything. Before you go, tell the team three things: the delegation map is the rule, the 6 PM report continues, and you'll take one 20-minute call every two days for real emergencies.
While you're away, keep a list of every call or message you get. When you're back, sort them as you did in Step 0.
- Information calls mean a document or SOP is missing.
- Approval calls mean a limit is missing or too low.
- Problems nobody reported mean the 6 PM report needs a better question.
Fix each gap and run the test again in three months. When the business runs for two weeks with fewer than five calls to you, you've moved from owner-dependent to owner-led.
Where automation fits
Notice that automation comes last. Once the rules are clear, software can enforce them: a CRM that routes enquiries and starts follow-ups, approval flows that send anything over the limit to you, a dashboard that fills itself from your accounting software and CRM. Automating before the rules exist only makes the confusion faster. Clear rules first, then the software.
"But my team is not ready"
This is the objection I hear most. Three answers.
They are not ready because they have never been allowed to decide. A sales head who has had to ask for every discount for five years has never built the judgement. Limits let them build it in small, safe steps.
Mistakes will happen, and they are cheaper than you think. Say a wrong call inside a ₹10,000 limit costs you ₹10,000 once. Being the only person who can approve anything costs you every week, in orders that waited and in time you could have spent on customers, pricing or new markets.
Some people won't step up. That is useful to know. The delegation map shows you, within a month, who owns their area and who keeps passing it back. Hire or reshuffle from what you see, not from what you assume.
Ek aur baat: don't take back a delegated decision the first time it goes wrong. Ask what the rule should say next time, update it, and leave the decision with the person.
This is the Operate layer of the Self-Running Business System, and the whole of it is in my book, Jugaad Is Not a System. If you want an outside view of where your business depends on you most, start with the Automation Scorecard or book a Growth Diagnostic.
