Who Should We Hire Next to Unlock Growth in B2B SaaS?

Direct answer: In B2B SaaS, your next hire should close the widest gap between where your strategy is headed and what your organization can actually execute today. Don't hire for a title or a benchmark headcount ratio — use the McKinsey 7S framework to find which of the seven elements (Strategy, Structure, Systems, Shared Values, Style, Staff, Skills) is throttling growth, then hire the person who unblocks it. Often the answer isn't "another AE" — it's a RevOps lead, a product-led-growth owner, or a first VP who imposes the operating rhythm your systems can't produce on their own.

Founders default to the most visible bottleneck — usually "we need more salespeople." But adding capacity to a broken engine just burns runway faster. The 7S model forces you to diagnose the whole system before you spend a hire.

Why "who to hire next" is a systems question, not a headcount question

Growth in B2B SaaS is a compounding machine: acquisition, activation, retention, and expansion all feed each other. A single new hire changes more than one variable. Hire a VP of Sales when your onboarding leaks customers, and you've accelerated churn. Hire a senior engineer when your roadmap has no owner, and you've added throughput to a rudderless team.

McKinsey 7S is useful here precisely because it treats the company as an interdependent system. The three "hard" elements (Strategy, Structure, Systems) and four "soft" elements (Shared Values, Style, Staff, Skills) have to align. A hiring decision is really a bet on which element, once strengthened, pulls the other six into alignment.

Walking through McKinsey 7S for your next SaaS hire

Work each element in order, and write down the honest answer — not the aspirational one.

1. Strategy. What's your primary growth motion for the next 12–18 months — sales-led, product-led, or channel/partnerships? Good looks like a single dominant motion with a clear ICP and a named next milestone (e.g., "cross $X ARR by landing mid-market"). If you can't name the motion, no hire will fix that — you have a strategy gap, not a staffing gap.

2. Structure. How does work and accountability flow today? Good looks like clear ownership of the pipeline stages that matter for your motion. Ask: who owns activation? Who owns expansion revenue? If two people own it, nobody does. Structural ambiguity often reveals the missing role.

3. Systems. What repeatable processes and tooling actually run without a founder in the room? Good looks like a functioning CRM, a defined sales/onboarding process, and reporting you trust. If your dashboards are guesswork, your first hire might be RevOps or a data-literate ops lead — not a quota carrier.

4. Shared Values. What does the team genuinely optimize for — speed, craft, customer obsession? Good looks like values that predict how people behave under pressure. A senior hire who clashes with these will underperform regardless of pedigree.

5. Style. How do leaders actually make decisions and manage? Good looks like a management approach the next hire can plug into. A founder who won't delegate shouldn't hire a "VP to own it" and then override them — that's a wasted six-figure salary.

6. Staff. Who do you have, and where are they stretched past their level? Good looks like knowing which current people are one promotion away from the gap, so you hire around them rather than over them.

7. Skills. What capability does the org lack entirely? Good looks like naming the specific skill that no one on the team possesses — enterprise selling, PLG experimentation, technical marketing, finance discipline. That named skill gap is usually your hire.

The synthesis: the element with the biggest misalignment relative to your Strategy points to your next hire. Weak Systems → RevOps/ops leader. A new motion (Strategy shift) with no owner (Structure/Skills gap) → the VP for that motion. Overloaded Staff blocking the founder from strategy → a strong #2 or Chief of Staff.

How Percision helps — and when a spreadsheet or consultant is enough

Running 7S well takes disciplined analysis and honest inputs. Disclosure: I work on content for Percision (percision.app), a strategic intelligence platform — so treat this as one option, not the only one.

Percision can run your business context through structured reasoning across 27+ frameworks, including 7S, and produce a board-ready diagnosis of where your alignment breaks down, along with scenario analysis on different hiring bets. If you want to pressure-test "VP of Sales vs. RevOps lead vs. senior PM" against your ARR trajectory and burn, it can model those paths and export the reasoning with an audit trail — in minutes rather than a multi-week engagement. It's positioned as a co-pilot: it structures the analysis; your leadership team decides. BCG and Harvard Business School researchers have found generative AI can meaningfully improve knowledge-worker output on well-scoped tasks — diagnostic framing like this is a good fit — but the same research flags a "jagged frontier" where AI confidently gets nuanced judgment wrong, so human review is non-negotiable.

When you don't need a platform at all: if you're a 10-person team and the bottleneck is obvious (founder is the only closer, pipeline is real), a whiteboard and a weekend is enough. When a human consultant is the better call: if the real problem is founder/leadership dynamics, org politics, or a genuine strategy pivot, you need a person in the room who can facilitate hard conversations — that's not a software problem.

Use the tool for structured diagnosis and financial modeling. Use a human for the messy, relational, and political parts.

FAQ

Should a Series A SaaS company hire a VP of Sales or a RevOps lead first? Diagnose your Systems element. If your sales process and data are shaky, RevOps first makes future AE hires far more productive. If your process is solid and you simply need scale on a proven motion, the VP of Sales is the unlock.

How do I know if my problem is strategy, not staffing? If you can't state your dominant growth motion and your ICP in one sentence, hiring won't fix it. 7S puts Strategy first for exactly this reason — resolve it before you spend a role.

Can I run McKinsey 7S myself? Yes. It's a set of honest questions, not a proprietary calculation. Tools help you move faster and reduce blind spots, but the framework is fully usable on your own.

Want a structured 7S diagnosis and hiring-scenario analysis for your SaaS company? You can run your context through Percision and keep your leadership team in control of the decision.