A founder in a CEO community I'm part of posted something last week that I've experienced myself, and that I hear from almost every fast-growing company I work with.
He runs a B2B SaaS company that's highly profitable and, more recently, has been on a growth tear.
Until this point, he didn't need many company controls. By default, he was in most of the meetings, and he was the control: he reviewed every transaction and saw every deal close, every month.
Then headcount doubled. He hired three "middle" managers. And the cracks started showing:
Six-figure projects getting approved without him really being involved.
Monthly spend running 100% over the number he’d agreed on.
Three month projects taking six months.
Payroll up 2x, and he couldn’t quite say what it had bought.
So he asked the community:
How do I create a budget we actually stick to?
What KPIs should I be tracking?
How do I build accountability into the org without micromanaging?
How do I become a leader instead of just a doer?
Those sound like half a dozen different problems.
But really, it's just one: he'd become the bottleneck, and nothing had been built to replace him.
Why do growing companies lose control?
When a founder is involved in everything, the founder is the company's control system.
And that's usually fine (preferred, actually) for the first few million in revenue. For the first 10, maybe 15, employees.
You are the budget, because you see every dollar in and every dollar out. You are the dashboard, because you're in every meeting. And you are the deadline, because projects move with your cadence and, naturally, you move fast.
But eventually, growing quickly means you can't physically be everywhere all the time. The same involvement that made you the engine now makes you the bottleneck, and if nothing replaces you, things start to break.
If you're profitable, you may not notice it at first. Things may just get slower and more expensive, and each decision or hire you make will feel reasonable in isolation.
You may begin to have a sneaking suspicion that something isn't "right." That the team is too slow. That you've made one too many hires.
The fix isn't to fire everyone or get back into every meeting. It's to build — on purpose — what you used to provide by default.
That takes four things:
Direction: a plan people own (vision, forecast, budget, roadmap)
Visibility: a scoreboard that tells you how things are going without you in the room (KPIs, leading and lagging)
Accountability: commitments that get checked (the Accountability Rule and Bregman's five clarities)
Cadence: the rhythm that holds the other three together (your operating system)
1. Direction: a budget people actually own
The founder I mentioned in the introduction did have a budget. He agreed to a number with his COO, and then the team blew past it.
This is the most common shape of this problem. A number was set in a meeting, a side discussion, or Slack, and it was more of a hope than a formula with multiple inputs.
Here's how to build the formula:
Start with revenue run-rate: Roll your current numbers forward: if we keep doing what we're doing (no new hires, no big wins, no new products), where does the year land? That's your baseline revenue, not your goal.
Forecast revenue lever by lever: Pick the revenue number you actually want, or the growth rate you’re happy with, then name what gets you there: which channels bring more customers, where conversion improves, where price goes up, where churn comes down. Every number you change needs a reason.
Put a cost on every lever: This is the step most CEOs skip. If the forecast assumes a new salesperson, the salary, benefits, and software are in the plan too. More content means more content costs. Revenue assumptions without matching expenses aren't a plan. Then check that the margin you want still holds.
Build it with your team leads: Draft it yourself first, because you know the business best. Then walk each lead through it. They'll tell you where you've understaffed, where you underestimated how long something takes, and where you can push harder. Revise once or twice. A budget people helped build is one they'll defend.
Give every line an owner and revisit it: Each lead owns their lines and the initiatives behind them. Review budget vs. actuals monthly. Re-plan quarterly, because reality will drift from the plan, and that's normal.
Once the budget exists, it also becomes the filter for new spend. Set a threshold ($10K, $25K, whatever fits your size). Anything above that threshold that isn't already in the budget comes to you as a one-page write-up:
What does it cost?
What will it produce, and by when?
What happens if it doesn't? (Your kill criteria.)
Which plan priority does it serve?
What are we stopping in order to pay for it?
How do you decide yes or no? Say yes when the request serves a stated priority, has a measurable result and a date, and names the point where you'd kill it.
Say no, or "next quarter," when it doesn't map to the plan or nobody can tell you what failure looks like. Question 5 is the one most teams skip. It's why profitable companies add expenses constantly and almost never remove them.
Want a ready-to-use forecasting template? It's the exact one I used as CEO of Hampton to go from several hundred thousand dollars to about $10M in revenue, covering run-rate, forecast, expenses, OKRs, and owners. Grab the free $1 to $20M Planning Blueprint →
2. Visibility: a scoreboard, not a feeling
You used to know how things were going because you were there, 24/7. Now you need numbers that tell you exactly what's going on without you having to be in the room.
My suggestion is to initially keep it focused.
The CEO owns three: revenue, profit margin, and revenue per employee. That last one answers the "payroll doubled" question directly. If it's falling and you don't know why, headcount is outrunning output and it's time to revisit your hiring plan.
Your leadership team owns their own numbers, and there are roughly two kinds:
Team | Lagging (did we win?) | Leading (are we going to win?) |
|---|---|---|
Sales | New revenue booked this quarter | Qualified meetings held per week |
Customer success | Net revenue retention | Share of new customers who complete onboarding within 30 days |
Product/engineering | Roadmap commitments shipped on time this quarter | Milestones hit on the date agreed at kickoff |
It's important to realize that revenue is lagging. By the time you get the revenue number, it's too late; that number is baked.
Leading numbers give you time to change course. Your leadership team should be watching these feverishly and marking each one green, yellow, or red every week.
None of this means you stop looking at the numbers underneath. It means someone else owns them, and your job is to make sure they're tracking them and getting you the right data. When I ran Hampton, our north star was member retention, and I tracked it religiously. It was one of the biggest drivers of revenue: when retention was good, revenue was good, and when retention slipped, revenue followed. But I didn't own it. Our member experience team did. My job was knowing the number every week, asking the right questions about it, and making sure the team had what they needed to move it.
That's how it should work across the company. Your top-line numbers are built from numbers your team leads own. You don't need to manage every one. You need to never lose sight of them.
We'll talk about this more in the next two sections, but you should be able to ask every single team lead, every week, about their leading KPIs, so you always know what's coming down the pike. One of my values as a CEO was never being surprised, so we went through leading indicators every single week, 52 weeks a year.
3. Accountability: it starts with clarity
If you think accountability means "the team knows I’ll be annoyed if it's late," then you don't actually have a system, and that's why it breaks down. That's why things aren't shipped on time and why the landing page that should have taken three days took two weeks. It's why the product launch was 45 days over schedule.
People weren't clear on what they were accountable for, and that's on you.
Asana co-founder Justin Rosenstein calls clarity the one quality every startup needs to survive. He breaks it into three parts: clarity of purpose (why this matters), clarity of plan (what we'll do), and clarity of responsibility (who owns what, by when).
On that last one, here's a quote I absolutely love: "If zero people are responsible for something, nothing happens. If two people are responsible, it probably still won't happen."
My fix is what I call the Accountability Rule. Every commitment, whether it's made in a meeting, a plan, or a Slack thread, has four parts:
Owner: One name. Not a team, not "marketing," not two people.
Deliverable: The specific thing that will exist when it's done. "Landing page live," not "work on the landing page."
Due date: A real calendar date, agreed to by the owner, not just assigned to them.
Definition of done: What "finished" looks like, so nobody can argue about it later. This is the one most teams skip, and it's how a three-day project quietly becomes two weeks without anyone technically missing anything.
If a commitment is missing any of the four, it isn't a commitment yet.
The Accountability Rule makes each commitment clear.
Peter Bregman's “The Right Way to Hold People Accountable” (Harvard Business Review) covers what has to surround it: five things a leader has to make clear before holding anyone to anything.
Clear expectations: The outcome, how success is measured, and the approach. This is where the Accountability Rule lives.
Clear capability: Does this person have the skills and resources to deliver, or a way to get them?
Clear measurement: Agreed milestones with objective targets, checked on a schedule.
Clear feedback: Honest and ongoing. In Bregman's words, "People should know where they stand."
Clear consequences: Bregman gives three options: repeat, reward, or release. Repeat the steps if something was unclear. Reward if they delivered. Release if they didn't, despite real support.
Nice — or conflict averse — founders struggle most with #4 and #5, and those are the ones that matter most. The first three are process. Feedback and consequences are conversations, and uncomfortable ones. Founders who care about their people, or who are simply uncomfortable with directness, will soften the feedback and postpone the consequences.
The problem is that the team then learns that dates are suggestions and numbers are directionally important but not critical.
But trust me, letting it slide isn't kindness.
It leaves people without the information they need to get better. And Google's research backs this up.
In Project Aristotle, Google studied 180 of its own teams to figure out what made the best ones work (written up by Charles Duhigg in The New York Times). The number one factor was psychological safety.
And I don't mean that in the fluffy, "we're all winners" sort of way. What I mean is that people feel okay taking risks and sometimes failing, and they feel okay speaking up and disagreeing in public.
Now look at what came next: dependability (people finish quality work on time) and structure and clarity (people understand the expectations, the process, and the consequences of their performance), per Google's re:Work summary. That's the Accountability Rule and Bregman's five clarities, showing up in Google's data.
So safety and standards aren't a trade-off. They're the same system.
A safe team is one where people can hear hard feedback without fearing for their standing, and that's exactly what makes #4 and #5 possible to deliver.
Three habits make all of this stick:
Inspect what you expect: Follow up on every commitment at the same time, every time. Teams learn fast which dates actually get checked.
Make results visible: A shared scoreboard where reds get discussed openly beats any private nudge.
Go first: If the CEO's own deadlines slip, everyone's will.
Clear commitments, honest feedback, real consequences: that's accountability. And it only holds when Direction, Visibility, and Cadence are working too.
4. Cadence: the rhythm that replaces your presence
You used to be in every meeting.
Now your meetings and communications need to do that job for you.
Here are, roughly, the six different types of meetings and their purposes:
Meeting | What it's for |
|---|---|
1:1s | Coaching, unblocking, and feedback. The place for Bregman's #4. If it's turned into a status update, it's not doing its job. |
Team-specific meetings | Alignment and shared context. What everyone's focused on, what's blocked, and what the rest of the team needs to know. |
Numbers meeting | Budget vs. actuals. Each owner walks through their lines and explains the variances. This is where a 100% overrun gets caught in month two instead of month nine. |
All-hands | Everyone hears the same story at the same time: where we are against our goals, what's changed, and what matters next. It's also where you celebrate wins and reinforce the culture you want. |
Roadmap review | Are the big initiatives on track? Every commitment gets checked against its owner, date, and definition of done. Reds get discussed, not buried. |
Quarterly planning | Often combined with the roadmap review, this is where you re-plan. Update the forecast, budget, and priorities: what's working, what to kill, what to fund next. |
How often you run each one, and in what format, is where everyone has an opinion. Weekly or biweekly. Live or async. Zoom, Slack, or a doc. There's no right answer. Do what fits you, your team, and your company, and expect it to change as you all grow.
Mine did. At one point I realized my weekly 1:1s had turned into status recitals, and we were both sitting there wondering what the point was.
So I killed the weekly 1:1s as we knew them and replaced them with a written Friday update called the GROW report: Goals, Results, Obstacles, and What's Next.
1:1s became more optional, booked when someone actually needed coaching or a hard decision. I wrote about that shift in Killing 1:1s & The GROW Report.
Here's what my full system looked like:
Update type | Medium | Cadence | Participants | Objective |
|---|---|---|---|---|
GROW report | Weekly, Friday 10am ET | My direct reports | Weekly update, including a view of the numbers | |
The Sit-Down | Recorded Loom | Weekly (15 min) | Me → the entire team | Share important company, people, and team updates, highlight big wins and props, and build culture and camaraderie |
The Roundtable | Live Zoom + deck | Monthly, second Thursday (60 min) | The entire team | Review high-level goals vs. actuals (CEO), share team-wide roadmap updates (team leads), and share team highlights or spotlights (individuals) |
The Numbers | Zoom | Monthly (before the Roundtable) | Me → leadership team | Review actuals vs. forecast and discuss variances |
Team-specific | Up to each team | Up to each team | Functional team | Collaborate on team-specific work and let team leads share company-wide info with their staff |
Leadership & Roadmap Sync | Live Zoom + Notion roadmap | Biweekly, Wednesday 11am ET (60 min) | My direct reports | Cross-team collaboration, strategic discussions, and blockers. We'd also use this to build the new roadmap each quarter |
1:1s | Live Zoom | As needed (30 min) | My direct reports | If you'd like a coaching, leadership, or feedback session, it's up to you to schedule it |
The details matter less than the big picture. Are you reviewing actuals vs. forecast with the team leads? Are you regularly getting updates and making sure the team leads are reporting KPIs, lagging and leading? Are you actively driving momentum and urgency across the org?
So how do you go from doer to leader?
This is the question underneath all the others, and the answer is the four systems above. But structure alone doesn't make you a leader.
Your job has to change, too. A lot.
Most founders move through four stages: Operator (you do the work), Delegator (you begin to hand off tasks), Coach (you develop the people doing the work), and Multiplier (your team owns outcomes and grows other leaders).
The goal is to move toward Coach and Multiplier, and here's what that looks like in practice:
Hire people who are better than you in their lane: Senior operators who've done it before, not people you'll have to manage step by step.
Delegate outcomes, not tasks: Give people the context, set the constraints (budget, date, definition of done), then let them own how it gets done. Start with smaller, lower-stakes projects to build trust, and keep the feedback loop short.
Coach instead of correct: Start every 1:1 with "How can I help you win this week?" Your job is to remove obstacles, not to review their to-do list.
Act on what you see: When you let go, some people step up and some drop the ball. Both are information. Reward the first group, and have the hard conversation with the second.
Go first: Urgency, deadlines, accountability. Your team does what you do, not what you say. You still have to move fast and create urgency and momentum. This never goes away!
Bill Campbell, the executive coach to leaders at Apple and Google, put the new job simply: "The primary job of each manager is to help people be more effective in their job and to grow and develop."
You built the company by being everywhere.
Making every decision, checking every box, and outworking everyone in the building.
Contrary to popular belief, the next stage isn't about working less or taking your eye off the ball. It's about building more versions of you.
Better ones, actually: more skilled in their lane, clearer on what they own, and held to the same standard you've always held yourself to.
Ready to make the shift? From Founder-Operator to CEO-Coach is my free playbook for moving from doing the work to building the people who do it: hiring, onboarding, delegation, and coaching, with the templates I used.
If you liked this blog post, you might enjoy this other one on the 5 Effective Levels of Communication.
Or sign up for my weekly newsletter, Signal // Noise, where I share my honest notes on work, startups, life, and money. No bullshit or spam!
Looking For More?
—> Here are 3 ways I can help you:
