This report reads how you described your company in the interview. Your exact words are shown on the side, next to the point they support.
Fast growth, with coordination starting to break.
As the team grows, that becomes the bottleneck.
Then don't take them back for 60 days.
Acceleration is the stage where growth outpaces how the company is organized. Revenue and headcount climb fast, but the way people coordinate hasn't caught up. Work slips between teams, and too much lands on the few people at the top.
Revenue tripled, you hired 43 people in a year, and things are falling through the cracks. You also described what comes next: real structure, clear ownership, and managers who manage. That is the Projectile stage. You can see it, but the company isn't working that way yet.
The growth is working. What holds companies back at this stage is usually coordination: who decides what, and how teams hand work to each other. Companies that get through it build a layer of managers who own decisions in their area, so the founders stop being the link between every team.
Speed and instinct come before process. People move fast and figure it out as they go.
Results are what count. Hitting the number is how people earn standing.
What a company celebrates shows what it values. Here, people become heroes for closing a deal or shipping something big. Big pieces of work also tend to come back to you after you hand them off, so informal authority still counts for more than the org chart.
You said it yourself: the people doing the quiet work that holds everything together don't get celebrated.
This culture is good at speed and big wins. It is weaker at rewarding the work that keeps things running, like coordination, documentation and helping colleagues. At your size you need more of that work, and the people doing it are the ones most likely to feel overlooked and leave.
Pick one recurring moment, such as the all-hands or a weekly update, and recognize a specific piece of quiet work by name every time. Name the person and say what it made possible.
We score five parts of how leaders behave, based on what you described rather than what you believe. Each runs from 0 to 10. Higher isn't automatically better. Read each score as a description, except the last one, where a high score is a warning sign.
Do leaders grow people, or use them up?
Lower half. When you lost a customer, you fixed the process instead of blaming someone, which is a good sign. But the people who keep things running go unrecognized, and growing people barely came up.
How hard do leaders push for more?
High. Revenue tripled and the company hired 43 people in a year. The pace you described is relentless.
Do leaders decide, hand off, and let the handoff stick?
Middle. You take ownership, but mostly by catching what others drop. This score goes up when leaders hand a decision to someone with real authority and it stays with them.
Are leaders motivated by personal gain or by the company's purpose?
Middle. Your concern for frustrated engineers comes across as genuine. The company's mission itself hardly came up.
When a decision needs making, is it clear who makes it?
High, and the most important score in this section. On paper the leadership team shares decisions. In practice they come to you and your product lead, and people know to escalate fast.
Leaders push hard and fix problems personally, but haven't yet built people who can decide without them. That pattern gets a company to fifty people. It is also what makes the next fifty hard.
Take your next ten escalations. For each one, ask who should have decided it, and what they were missing: information, authority, or confidence. The most common answer tells you what to fix first: the role, the rules, or the person.
Every company makes five strategic choices, often without saying them out loud. We read them from how you talk about the business. Each choice has two reasonable ends; what matters is whether the combination fits where you are.
Bold. Hiring 43 people before the infrastructure was ready is a large bet that growth will continue.
Short. Everything you described was about now. Nothing looked a year or more ahead, at the market or at the product.
Middle, with little evidence either way. You described the product without talking about new markets or new directions. Ask about this in a full assessment before relying on it.
Focused. One product, one customer segment, and one way of growing.
Slightly outward. Losing a big customer led straight to a process fix, so what customers say does reach decisions. Most of what you talked about was internal.
You are making a big, concentrated bet while looking only a short way ahead. That works while growth continues. If growth slows, or the new hires take longer to pay off, there is no plan B and no early warning, because nobody is looking far enough ahead to see it coming.
Add a 12-month look-ahead to one leadership meeting each quarter: the revenue you expect, the headcount it supports, and the one signal that would make you slow hiring.
Twice you described how something is supposed to work, then how it actually works. The leadership team is supposed to make decisions, but in practice it's mostly you. Team leads formally own their areas, but in practice the work lands on you or your product lead.
You already know the formal structure isn't working. Because you personally cover the gap, the cost stays hidden until something breaks that you can't catch.
You said people know they escalate fast. That means escalating is expected, and it probably gets rewarded with quick answers. New hires pick this up within weeks and stop building their own judgment, because nothing asks them to.
With 43 new people in a year, the habit has spread widely. Changing it will take more than a new org chart.
Decisions keep flowing to you while the company keeps growing, and one person can only clear so many.
The failure usually comes all at once. A cluster of escalations arrives in the same week and things stop getting decided. On your current path, expect that within the next year.
This week
List the three decisions that come to you most often.
Next two weeks
For each one, write down who decides, who needs to be told, and what would justify escalating it to you. Share it with the people involved.
Next 60 days
Don't take those three decisions back. Each time one comes back to you, count it and note why.
What good looks like: the count falls over the 60 days, and the reasons decisions came back tell you what to fix next.
Companies at your stage usually need attention in these six areas. "Didn't come up" doesn't mean you ignore it, only that it didn't appear when you described your challenges. Use it as a list to check.
| Area | In the interview | What we heard |
|---|---|---|
| Pay and keeping peopleCheck this first | Didn't come up | You said some of your best engineers are frustrated, but nothing about how you keep them: pay, equity, or career paths. |
| Hiring and succession | Came up | Hiring speed dominated: 43 people in a year. Less was said about how roles are designed or the quality of candidates. |
| Manager support | Came up | You named the gap yourself: managers who do the work instead of managing. Nothing is in place yet to fix it. |
| Improving performance | Came up | After losing a big customer, you ran a full review and fixed the process. |
| Forecasting and planning | Didn't come up | Nothing about expected revenue or the capacity you will need. |
| Marketing and pricing | Didn't come up | Revenue tripled, but how that growth was won and priced wasn't discussed. |