You wrote the job posting for someone who's “done this before.” Here's what usually happens to them once you hire them.

The hire isn't the bottleneck. The comparison set is.

A good opportunity, on its own, doesn't feel obviously good. It only feels good next to the twenty other opportunities you've already priced, sized, and ranked. Without that set, every new idea carries a perceived opportunity cost that's effectively infinite — because there's nothing to weigh it against. That's what paralyzes a smart, capable hire: not a shortage of ideas, a shortage of a system to judge them by.

And the downside risk is real enough to justify the caution. McKinsey's own research puts it at nearly seven in ten mergers failing to achieve the revenue synergies expected of them — and separately, roughly six in ten roll-ups fail to capture their intended synergies within two years, with add-ons that do get done pricing at a premium (5.7x vs 4.5x at the small end) precisely because buyers are competing for the few that look de-risked. Culture and fit account for a lot of that gap. So does buying opportunistically instead of buying toward a shared direction.

A number is not a plan

The other version of this failure looks more deliberate but isn't. Someone identifies a market adjacent to the one you're already in, picks a revenue target — ten million over three years, say — and stages it: one million in year one, three in year two, ten in year three. It looks like a plan because it has numbers and a timeline. It has no products, no services, no features, and nothing that ties the target back to a specific action that unlocks it. It's a hope with a ramp attached.

The bullseye: where capability, demand, and technology overlap

Every opportunity you're evaluating sits somewhere in three circles: what your company is actually good at, what the market is actually asking for, and what technology actually exists to solve it. Most ideas land in one circle, or maybe two. The ones worth pursuing land in the small space where all three overlap — the bullseye. That's the same net-score logic our software runs when we map a client's opportunity set: not “is this a good idea in isolation,” but “does this hit capability, demand, and available technology at the same time.”

Most growth plans skip this and jump straight to a number, because scoring three circles against each other is harder than picking a target and hoping. It's also the only version of the exercise that tells you, before you spend anything, whether an idea is a real bet or just an appealing story.

Sense, interpret, control

Take a bullseye opportunity in an emerging technology domain with no analyst coverage yet — too early, too niche, nobody's written the market report. You can still build a real plan; you build it from your own environment instead of someone else's research. Break it into what you're sensing, what you're interpreting from that data, and what action you take on it. For sensing: what has to be measured, where the hardware has to physically live, what conditions it has to survive, and where the gap is between what you can already sense and what you'd need to. For deployment: not a hypothetical market, but your actual existing customers' actual operating environments — which ones plausibly fit today.

That gives you something no market report would: an internal count of real environments you can already reach, and a staged investment tied to staged, checkable revenue — not a straight-line ramp to a target.

Illustrative structure only — not a real client's figures.

Every stage names the target companies in that space, why the IP matters, whether they already have demonstrated sales, and what gets iterated before the next dollar moves. That's what turns a spreadsheet row into something a sales team can actually be compensated against — which is the step most plans never reach, and the reason growth targets don't show up in anyone's incentive plan.

The portfolio, not the single bet

No single bet, however well-built, should carry the whole target. Spread it across risk tiers, sized to what you can absorb if any one of them misfires — and sized so the whole set passes what's really a comfort test as much as a financial one: can your executive team sleep on this. Not every bet needs to land. Some won't. Some will land exactly as planned. Occasionally one lands bigger than planned, in the good direction. A portfolio built to survive the first outcome and capture the third is what makes the second one bearable.

You have to know this before you hire — not hope the hire brings it

Handing someone a target number and a blank mandate isn't delegation, it's deferral. It's also a hiring trap: the candidates confident enough to build a real plan from nothing, absorb some bets misfiring, and still convince you the rest will land — they exist, but they're rare, and a comp package built to offset the risk that a hire “doesn't deliver” prices exactly those people out. You end up selecting for the safer, less capable candidate while budgeting as if you'd hired the rare one.

A corporate intelligence center, not a hire

What we're actually building with you is closer to a standing corporate intelligence center than a consulting engagement: a system that keeps scoring the bullseye, keeps sensing and interpreting what's changing in your technology and your market, and keeps the portfolio balanced against your actual product roadmap — year one, year two, out to year five. The goal isn't a plan you review once. It's watching, month after month, as the things you said you'd build in September 2026 start showing up as real product lines, real customers closed, and real revenue by the time you're standing in front of your own executive team a year later.