When to Hire Your First VP
The question founders ask is when to hire a VP. The more useful question is what level the next hire in this function should be, because the failure modes run in both directions and they are both expensive. Hire a VP to solve a problem a strong director would handle and you have bought overhead, politics, and someone who will be bored within a year. Hire a manager when you needed a VP and you spend two years discovering that the function has no strategy. This page is about telling those situations apart.
What’s inside
The question is level, not timing
What a VP actually adds
Four signals you need one
Three signals you do not, and what to hire instead
Too early versus too late
Builders and scalers
Where Blomma fits
The question is level, not timing
There is no headcount at which a company needs a VP. There is a set of problems that a VP solves and a director does not, and if you do not have those problems the title is expensive decoration.
The levels differ in one specific way: how much of the function’s direction the person sets versus executes.
A senior individual contributordoes the hardest work in the function and raises the standard by example. Solves quality problems.
A managergets a team of five to eight to deliver against a plan someone else largely set. Solves throughput and coordination problems.
A directorruns a function against goals, builds the team, and makes most of the tactical calls. Solves execution and scaling problems within a defined strategy.
A VPsets the function’s strategy, decides what the function will and will not do, hires and develops managers, and represents the function in company-level trade-offs. Solves strategy and cross-functional problems.
So the diagnostic is: is the thing that is broken quality, throughput, execution, or strategy? Founders reliably diagnose a strategy problem when they have an execution problem, because a strategy problem justifies a more impressive hire.
What a VP actually adds
Three things, and it is worth being clear because these are what you are paying for.
They decide what the function does not do.The defining VP capability. A director will execute the priorities they are given well; a VP will tell you two of them are wrong and why. If you do not want to be told that, you do not want a VP.
They build the layer below them.A VP hires and develops managers, which is a different skill from managing individuals and the one most commonly absent. This is what makes the hire compound rather than just adding capacity.
They hold their side of a company-level trade-off.In a room where product, sales, and engineering are negotiating a genuine conflict, a VP can represent their function’s interests and also accept an outcome against them. That is what makes an executive team possible.
If what you need is none of those — if you need the function to execute a plan you have already decided, faster and more reliably — you need a director, and you will get better results from a strong one than from a mediocre VP.
Four signals you need one
One. You are setting the function’s strategy yourself, badly.Not because you lack ability, but because you have four other functions and no time to think about this one properly. If you can name specific decisions in this function that are being made poorly because you are the one making them, that is the signal.
Two. The function has managers, or needs them within a year.Managing managers is the threshold. A function with three managers underneath needs someone whose job is developing managers, and a director in a small company often has not done that.
Three. The function’s cross-functional negotiations keep escalating to you.If every trade-off between this function and another arrives on your desk, you need someone who can hold that negotiation at their level.
Four. You are about to enter a stage in this function you have never operated in.Moving from founder-led sales to a real sales organisation, or from one product to a platform. Stage experience you do not have is the strongest argument for a senior external hire, and it is the one case where paying for seniority reliably returns.
Three signals you do not, and what to hire instead
The function is underperforming and you have not diagnosed why.A VP hired into an undiagnosed problem will spend two quarters diagnosing it, expensively, and may well conclude the problem is elsewhere. Diagnose first. Frequently the answer is that the function has no clear outcome or lacks the decisions to affect it, in which case fix that before hiring anyone.
You want to look more credible to investors or candidates.Real motivation, bad reason. A VP hired for signalling has no defined outcome, which is the first condition of an executive hire and the reason these fail.
You are overloaded and want someone to take work.That is a capacity problem, and a strong senior IC or a director will absorb more work for less money and less organisational disruption. A VP hired to absorb work will be underemployed and gone in a year.
In all three, the better hire is usually one level down and stronger — an excellent director rather than an adequate VP. A great director in a growing company frequently becomes the VP in eighteen months, having earned the context and the credibility.
Too early versus too late
Both failures are real and they look different.
Too earlyproduces a senior person with insufficient scope. They arrive expecting to set strategy for a function of twenty and find a function of four. They fill the time by involving themselves in work below their level — which is where most behaviour experienced as micromanagement originates — or by building process the company cannot absorb. They are bored, the team is frustrated, and the hire is written off as cultural.
Too lateproduces a function running on a strategy nobody owns. Symptoms: the function delivers but you cannot say what it is trying to achieve this year; its managers are all first-time and unsupported; and its cross-functional conflicts land on you monthly. The cost accrues quietly and shows up as a function that has been busy for two years without compounding.
On balance, slightly late is cheaper than slightly early, because a too-early senior hire actively damages the team below them while a too-late one costs opportunity. But the gap is smaller than founders assume, and the too-late version is the more common error in companies past a hundred people.
Builders and scalers
One distinction that determines whether a VP hire works, and it is not on most job specs.
Some senior leaders build functions: they arrive with four people and no process, and construct something. Others scale functions: they arrive with forty people and a working machine, and make it three times bigger without breaking it. Both are genuine skills. They are rarely the same person, and the CV does not distinguish them — both look like “VP at a company that grew fast.”
The question to ask in an interview is what the function looked like on their first day. A candidate who joined a forty-person function and grew it to a hundred and twenty may struggle badly with your eight-person one, because their instinct is to add structure and specialists you cannot support. A builder dropped into a large mature function may over-rebuild something that was working.
Work out which you need — usually a builder, if this is your first VP in the function — and screen for it explicitly.
Where Blomma fits
This decision is hard to make well because you are assessing a level in a function you may not know deeply, under pressure from the function’s current state, and often with a specific impressive candidate already in view — which is how the level question gets answered by the availability of a person rather than the needs of the company.
Blomma is an always-on AI career coach with no stake in your hiring. Use it to work out whether what is broken is quality, throughput, execution, or strategy, which determines the level and is where founders most often get this wrong. Use it to test whether you genuinely want to be told that two of your priorities are wrong — the honest answer determines whether a VP will work here at all. Use it to check the four conditions any senior hire needs before you open a search. And use it to think through the builder-versus-scaler question for your specific situation.
There is a second application worth naming: if the answer is to promote a strong director rather than hire above them, that person is about to do a job they have not done. Coaching is what turns that promotion into a success rather than a stretch assignment nobody supported..
The VP question is not about timing or headcount. It is about whether the problem in front of you is a strategy problem — and if it is not, one level down and stronger is almost always the better hire.