The first move when your business feels stuck (it's not a new hire)
The first move is rarely a hire. It is almost always a question.
The business has hit a wall.
The revenue line is flat or close to it. The team is working hard. The pipeline numbers are softer than they should be. Leadership has been having the same Monday conversation for a few months now. Something has to change.
The reflex, almost universally, is to hire.
A new VP of marketing. A new RevOps lead. A new agency. A new fractional CMO. Sometimes a new CRO. The reasoning is intuitive: if the business has outgrown what the current team can produce, the answer is more team, more senior team, or better-pedigreed team.
I have watched a lot of companies make this move. Sometimes it works. Most of the time it does not, because the company hired against the wrong diagnosis. The right first move when a business feels stuck is rarely a hire. It is almost always a question.
This is a piece about what to ask, what to wait on, and how to tell when hiring will actually help and when it will quietly waste a year.
The hiring reflex and why it fails so often
The reason “hire someone” feels like the right first move is that it is the move that requires the least uncomfortable thinking.
A hire is an action. Actions feel like progress. A hire converts a fuzzy frustration (“we’re stuck”) into a concrete project (“we’re hiring a head of growth”). The org chart changes. The board sees motion. Leadership can point to a decision that was made. Inside the company, hope replaces frustration for a few months while the search runs.
What the hire does not do, in most cases, is diagnose what was broken in the first place.
A new VP of marketing inherits whatever was producing the stuck-feeling number, takes about six months to figure out which parts of it are structurally broken, takes another six months to attempt to fix the structural parts, and is roughly twelve months in before the business sees whether the hire made a difference. By that point the team has spent a hire’s full annual cost (which is meaningful), the previous year of work continued forward (which is also meaningful), and the strategic clock kept running.
If the diagnosis was correct, that twelve months was well spent. If the diagnosis was wrong, the business is now twelve months further into the wrong problem with a more senior person at the wheel.
Most hires in this state are made against incomplete diagnoses. Not because anyone is doing it carelessly. Because the diagnosis is genuinely hard, and “hire someone good and let them figure it out” sounds reasonable when the alternative is sitting with uncertainty.
The question to ask first
Before you hire anyone, ask one question of three different leaders, separately and on different days:
“If you had to bet on one specific reason our growth is not where we want it, what would you bet on?”
The point is not the answers. The point is whether the answers match.
If the three answers match, your leadership has a shared diagnosis. You probably know what is broken. You can hire against it with confidence.
If the three answers do not match, your leadership does not yet have a shared diagnosis. You have three different theories about what is broken, and you are about to hire someone to fix one of them, while the other two leaders quietly believe a different one. The hire will struggle inside that disagreement. Nobody will agree on whether they are doing the right work.
This single conversation, run honestly, will save more wasted hiring than any other intervention I have seen.
What to do with the gap
If the three leaders gave you three different diagnoses, you have a clear next move. It is not hiring. It is closing the gap.
Closing the gap takes a few weeks of focused work, not months. You bring in someone to do a real diagnostic. You look at the data. You walk through the operating system together. You name what is actually broken in plain language. You get the leadership team to agree on it, on paper, in writing.
This is the work that a Systems Audit is designed to do, but you can run a version of it internally if you have someone on the team who can be honest with you and who is not invested in defending a previous decision. The output is small. It is usually one or two paragraphs. Something like:
“The marketing is producing leads. The handoff between marketing and sales is breaking. We do not have agreed-upon definitions for what a qualified opportunity is. Three of the last six quarters had pipeline reviewed against three different definitions. The next move is not a hire. The next move is to define what we are measuring, fix the handoff, and then revisit whether we need senior help.”
Once the diagnosis is real and shared, two things happen. The first is that the team often does not need the hire anymore, because the actual problem turns out to be solvable with internal work and a small amount of outside help on the specific gap. The second is that, if you do still need to hire, you can write a job description against a real problem and recruit against a clear scope. The hire’s first year is dramatically more likely to succeed when they walk into a defined problem and a leadership team that agrees on it.
When hiring really is the right first move
There are a few situations where hiring is the right move first. Worth naming them.
The business genuinely lacks a function. If you do not have any marketing leadership at all, and the business has clearly outgrown what the founder can carry, the first hire is the move. The question is not whether to hire. It is whom and at what level.
The team is the bottleneck. If diagnosis is clear and the team simply does not have the bandwidth to execute the fix, hiring against the gap makes sense. Bandwidth is sometimes the bottleneck. It just is not usually the bottleneck people think it is.
A specific senior skill is missing. If the diagnosis is “we cannot operate at this stage without someone who has done X before,” and X is genuinely specialized, hire the X. Be honest about whether X is the actual missing skill or whether the missing thing is something else dressed up as X.
In the other situations, which are most situations, hiring first is the expensive shortcut. The cheaper, faster, and usually better move is the question.
The reframe
When growth stalls, the most natural feeling is that the team is not capable. Almost always, the team is more capable than it gets credit for. The thing holding the business back is not who is in the seats. It is the clarity about what the seats are supposed to be doing and the design of the system the seats are running.
A new hire cannot give you that clarity. The hire inherits whatever clarity already exists. If the clarity is partial, the hire’s first year is spent producing partial clarity. If the clarity is real, the hire’s first year is spent compounding it.
So before you hire, find out which one you have. Ask the question. Listen to the answers. If they match, hire. If they do not match, the next move is not the search. The next move is the work that makes the answers match.
That is the difference between hiring as a real move and hiring as a way to convert frustration into the appearance of progress. The first builds the business. The second buys you six months of feeling better and another twelve months of being stuck.
If your leadership team is not yet aligned on what is actually broken, a Systems Audit is the fastest path to clarity. Confidential, plain-language, no obligation. Either we have a fit for the next move, or you walk away with a clear written diagnosis you can use however you want.