How Many Hours a Week Does Getting Out Take?
Fewer than most owners fear: about three protected hours a week at first, easing toward one once the team has rules to work from. Those hours only count when they sit in fixed blocks on the calendar, and most owners have to delete a couple of standing meetings to make room for them.
Monday at 7:40am, an owner at 58 hours a week opened his calendar with me on a shared screen and said he had nothing to cut. The grid was solid color. Monday status. Wednesday "quick sync." Friday vendor call that had become social. Client fires. His own deep work blocks that got eaten by 9:15.
He wanted a business that ran without him. He also wanted the grid to stay full of everyone else's needs. Both wishes cannot win at once.
If you cannot spare two to three focused hours a week for about twelve weeks, you will not get a business that runs without you. That sentence makes people angry, which is useful. "I don't have time" is the most common objection I hear from owners already at 55 hours a week. It is also true. No time is both the symptom and a hard constraint. You either pay with hours now, in a bounded window, or you pay forever in a calendar that never opens. This is not a pep talk about waking up earlier. It is time math.
How do you build an hours budget?
Block three 45-minute decision windows a week. Put them on the calendar like payroll. Name them. "Systems decisions" is fine. Protect them the way you protect a customer install.
In each window, work from a single list of questions that need a yes, a no, or a rule. Answer by voice or screen recording when typing stalls you. Batch the questions so your team is not pinging you at 7am and 9pm for the same class of problem.
A simple filter helps: "What should I do?" does not enter the window. "I recommend X because Y; approve or redirect" does. That single filter cuts the volume and trains judgment at the same time.
Pay for the blocks by deleting two standing meetings. Not "shorten." Delete. Most owners I work with can find 90 minutes of recurring meetings that produce updates you could read in writing. If you cannot name two, you are not looking. You are defending a calendar that already failed you.
An owner time audit shows which recurring hours are safe to give up, by tagging each one as time, revenue or quality work.
The 58-hour owner killed Monday and Wednesday, moved status to a shared doc updated by noon Sunday, and kept Friday. The three 45-minute blocks fit. In week three he skipped one block to put out a fire he could have delegated. The project slipped four days. He put the block back and told his lead the fire rules in writing. That messy week taught him more than the clean schedule on paper.
Why do written answers beat a weekly systems meeting?
Owners often try to "make time" by adding a weekly systems meeting. The meeting fills with updates. Decisions slip to the edges. People leave with homework nobody does.
Flip it.
- Updates in writing before the window.
- The window is for decisions only.
- Cap each item at a few minutes.
- If it needs a longer working session, schedule that separately with only the people involved.
Protect the three short blocks as decision capacity, not as another stage for status theater.
One firm went from a Tuesday two-hour grind to three 45-minute windows and a shared decision log. In the first month the owner still answered too many items live on Slack between windows. We added a visible rule: if it arrived after the list cutoff, it waits unless money or safety is at risk.
He broke the rule twice in week two for preference. He wrote both down. Week three he held the line. Pings outside the windows fell from roughly fifteen a day to four. Without the log of broken rules, he would have sworn he was "pretty good" at protecting the blocks. The log made the leak obvious.
What the twelve weeks actually cost
Owners imagine a systems project as a second full-time job. Done poorly, it can feel that way. Done with a real hours budget, a firm around $2M with five or more staff usually lands closer to this shape: weeks 1 to 4 about three hours a week on decisions, mapping, and naming who owns what; weeks 5 to 8 about two hours on reviews, exceptions, and tightening rules that broke in the wild; weeks 9 to 12 about one hour on cadence, a short away test, and fixing what the test exposed.
That is roughly 24 to 30 focused hours across a quarter, not 200. The trap is scattering those hours into twelve half-started evenings. Focused means protected blocks where you answer decisions, not where you "work on systems" while answering Slack. Twenty minutes of daily async answers usually beats one heroic two-hour meeting. A voice note or a screen recording that clears five stuck items will move more than a calendar invite that gets rescheduled three times.
DIY costs owner attention the whole way. Done-for-you still needs your decisions. Nobody can install judgment you refuse to give. If you want zero involvement, you do not want a business that runs without you. You want a fantasy where the business installs itself.
Hours are only one of the things a systems project asks of you. The rest, from a named lead to plain honesty about the map, is in what installing systems asks of the owner.
What breaks the time math?
The math breaks when you treat the hours as optional. It breaks when you use the decision window to redo work instead of decide. If the item in the window is a task you could do in 20 minutes, it does not belong there. Send it out with an outcome and a deadline. The window is for decisions that unblock other people.
Another break point: waiting for a perfect two-hour Saturday. Owners who "do not have time" during the week often protect a fantasy of a future clear day. That day rarely arrives. Three short windows beat one mythical Saturday for twelve weeks straight. I watched an owner try to compress the whole front half into one marathon Sunday. He mapped for five hours, made eighteen decisions half-awake, and spent the next two weeks reversing six of them because the team had no context. We restarted with the 45-minute cadence. Slower on the calendar. Faster in the business.
This is not about binders. It is about a quarter where ownership moves off your phone. By week 12 you should see fewer permission pings, clearer owners on recurring work, and a short list of exceptions that still need you. If you see none of that, you spent the hours on activity, not decisions. Compare the cost of 24 to 30 focused hours now with the cost of another year at 55 hours where twenty of those hours are work a trained person could own. The second number is the one owners avoid looking at.
The honest version of "I don't have time" is often "I will not disappoint anyone else to create the hours." Disappointing a low-value recurring meeting is part of the price. If that feels impossible, the delay is not the twelve weeks. It is the boundaries.
Skip the sprint when you are in a live crisis (cash crunch, lawsuit, key person just quit), or when you will not give even two hours a week, or when nobody on the team can take a decision yet. Stabilize first, stay in operator mode on purpose for a season if you must, and name one imperfect lead before you start.
Seasonal peaks are a soft delay; schedule the start for the downside of the peak rather than using busyness as a permanent excuse.
On the shared screen that Monday, after we deleted the two meetings, he stared at three empty 45-minute blocks like they might fill themselves with guilt. They did not. Week three still had the fire he should have handed off. Week four the blocks held. The project was only partly back on pace.
He had not "gotten his life back." He had one ugly proof that the calendar could be rewritten on purpose, and a decision log that still showed two preference leaks in ink.
Frequently asked questions
What if my hours swing from week to week?
Keep the three windows fixed and let everything else move around them. When a week truly can't hold all three, keep one and move the other two within the same week instead of skipping. Skipped windows pile up decisions, and a backlog of decisions is what sends the team back to pinging you live.
Can my lead take over some of the decision windows?
Once a rule exists for a type of decision, yes: the lead answers those and brings you only what the rules don't cover. Early on, most items in a window need you, because the rules are still being written. Handing windows to the lead too soon tends to send preference questions straight back.
Do the windows have to be 45 minutes?
The cap matters more than the exact length. Forty-five minutes is long enough to clear a list of decisions and short enough to fit between client work. Longer blocks tend to fill with updates, or with you doing the work yourself, which is exactly what the window exists to keep out.
Can your calendar carry the hours?
If you want help setting that hours budget so the twelve weeks land, start here: systemstoscalegroup.com/getstarted
