How to Work on Your Business Instead of in It: Operator's Guide
Quick answer: You work on your business instead of in it by turning recurring work into a defined process: a clear standard, one accountable owner, and a weekly view of results. Delegate with structure, let systems handle the repeatable steps, and keep your own judgment for the decisions only you should make.
I am Martin Perdomo. I operate businesses, and I have learned that being involved in everything is not the same as being responsible for everything. Here is how I think about the difference.
What does working on your business actually mean?
Working in your business means you are the process. Work moves because you remember it, approve it or chase it. Working on your business means the work moves because a standard, an owner and a system make it move, and you check the results.
If it only works when you touch it, it is not a system. It is a dependency.
The book makes the same point from the achievement side. "Achievement isn't about lucky breaks; it's about developing systems that produce consistent results." (From Survival to Mastery, Chapter 8)
Where does everything in your business come back to you?
Start with a typical week. Write down every repeated question, every approval, every scheduling task, every follow-up, and every problem that depends on your memory. Do not fix anything yet. Just list it.
The pattern shows up fast. A handful of recurring jobs account for most of the interruptions. Those are your first candidates.
What should a business owner delegate first?
Delegate the recurring work that follows a pattern, not the decisions that need your judgment. Before you hand anything off, define the standard:
- The result you expect
- The steps that matter
- The deadline
- Who has decision authority
- When an issue must be escalated to you
Then name one accountable owner. A task assigned to "the team" has no owner, and a process with no owner drifts. One person owns completion and reporting, even when several people do the work.
Delegation without a standard is just hope.
What should you automate first?
Start with the front of the process: inquiry capture, scheduling, reminders, routing and follow-up. These steps repeat, they are easy to describe, and they are where people fall through the cracks when someone forgets.
Use AI and your CRM where they support a clear workflow. Keep a human reviewing anything that needs judgment. Automation carries the process. It does not carry the accountability.
What does this look like in a real operation?
This week I built additional calendar infrastructure in GoHighLevel so people can book to appear as a guest on the Wealthy AF Podcast. [NEEDS MARTIN TO CONFIRM, DO NOT PUBLISH UNTIL FILLED IN: (1) What does a guest do from the first click to a confirmed booking? (2) What did you or your team coordinate manually before, such as emails back and forth, calendar checks or reminders? (3) Which steps does the calendar now handle: confirmation, reminders, rescheduling, intake questions, routing? (4) Who owns this process and who checks it? I will describe only what you confirm and will not claim time savings.]
Building it was not the finish line, and a lesson I wrote down last week shows why. A person booked a strategy call with us. I received the internal alert, and the contact entered our follow-up list. Then that person told us they had received no text reminders and no emails. On our side, the automation looked complete. From their side, it had not worked. [NEEDS MARTIN TO CONFIRM: you are comfortable sharing this story in general terms. The vault says the cause and fix are still unverified, so I state no cause and no fix.]
The lesson is that built does not mean verified. A system is finished when the outcome is confirmed, not when the workflow is switched on.
Martin's Rule
You can delegate the work, but you cannot delegate the verification to the person doing the work. A system is finished when the intended outcome is confirmed, not when it is built.
How do you delegate without losing control?
You keep control through visibility. Review one small dashboard every week. It should answer four questions: what moved, what is overdue, who owns it, and where a decision is needed from you.
Test the process the way a customer would experience it. Use a controlled contact, run it end to end, and confirm the outcome actually arrived. Ask for evidence, not reassurance.
How do you protect the owner's highest-value work?
Every hour you spend on routine coordination is an hour you do not spend on capital, relationships, strategy, teaching and the decisions that require you. That is the real reason to build the system.
It also takes a shift in identity. Many owners treat personal involvement in every task as proof of responsibility. It is not. Responsibility includes building a business that executes reliably when you are not in the room.
Do this week: one recurring task, five steps
- Choose one recurring task that keeps coming back to you.
- Document it in plain steps, with the result you expect.
- Assign one owner who is accountable for completion and reporting.
- Set the escalation rule: what the owner can decide and what comes to you.
- Define how completion will be verified, and who checks it besides the person doing the work.
Frequently asked questions about working on your business
What does it mean to work on your business instead of in it?
It means building the standards, owners and systems that move work forward, so the business does not depend on you to remember, approve or chase every task.
What should a business owner delegate first?
Recurring, patterned work with a clear definition of done, such as scheduling, follow-up and routine reporting. Keep the decisions that require your judgment.
How do you delegate without losing control?
Define the standard, assign one accountable owner, set an escalation rule, and review a short weekly dashboard of what moved, what is overdue, who owns it and where a decision is needed.
What should you automate first?
Inquiry capture, scheduling, reminders, routing and follow-up. Keep a person reviewing anything that needs judgment.
How do you know whether the system is working?
You confirm the outcome, not the setup. Test end to end with a controlled contact, check that the result actually arrived, and have someone other than the process owner verify it.
Bring this to your team. I speak and train teams on moving from owner dependence to disciplined operations. Book Martin to speak or train your team.
