How much time should I spend on the business versus in the business, and how do I even tell the difference?
The short answer
In the business is you doing the operational work: sales calls, support tickets, writing code, fixing today's problem. On the business is you making the machine better: pricing, positioning, hiring plan, which bets to kill. If you spend zero hours a week on the business you will stay busy forever and grow slowly. Book one recurring block a week where you are forbidden from touching the operational queue and only think about the next level up.
Go deeper, your way
3 hand-picked resources, 3 link-checked. Pick how you want to dig in.
📄 Article
✓ Link checkedFreeIntermediate
Why we picked it
This is the E-Myth idea made measurable: Levels CEO Sam Corcos logged 7,922 hours across two years into ten categories and shares the exact spreadsheet so you can copy it. The gut-punch is the actual-vs-perceived gap: he expected to spend big chunks on recruiting and strategy and found recruiting was 3 percent and strategy just 5 percent, while email quietly ate 30 to 35 percent every week. That is precisely how you tell 'in the business' from 'on the business': you count.
From
First Round Reviewby Sam Corcos (as told to First Round Review)18 min read
Build ten or fewer time categories, log every hour in your calendar, then export to a sheet and review it, because the work that feels light (email, easy meetings) is usually the work eating your week
Founders systematically overestimate time on strategy and underestimate time on information processing, so trust the log over your memory
A CEO's real job is to be an information router unblocking the team, not the top individual contributor, so protect the hours that only you can do
Why we picked it
The cleanest founder-written explainer of the E-Myth distinction, from a repeat founder (Pardot, exited to ExactTarget) rather than a consultant. It names the trap directly, cites Paul Graham's Maker vs Manager schedule as the reason the switch is so hard, and lands on a concrete number: once the business is stable, spend at least 10 percent of your time on the business. Short enough to read in one sitting and set your weekly block against.
Early on almost all your time is correctly 'in the business'; the failure is never making the deliberate shift as you grow
In vs on maps to Paul Graham's maker vs manager schedules, which is why context-switching between the two in one day is so draining
Once you have a working business, hold at least 10 percent of your week for on-the-business work: pricing, hiring plan, positioning, which bets to kill
Why we picked it
Trenchard has watched a lot of founders run their calendars, and his core move is the one that makes buffer-based planning survive contact with reality: block one or two hours against your top three priorities when you are sharpest, then batch the reactive stuff (email, ad-hoc meetings) into defined windows instead of letting it bleed across the day. The practical lever for a founder who cannot escape fires is his insistence on saying no and ending every meeting with a decided outcome, so the reactive load that does hit you is compressed rather than open-ended. Read it as the how of protecting your 60%: guard the priority blocks, fence the firefighting into batches.
