Your ICP Is a Person. Your Buyer Is a Committee of Six.

Six people can kill your deal. Your ICP document only describes one of them.

Most founders write an Ideal Customer Profile as a single character sketch: job title, company size, tech stack, maybe a pain point or two. Then they build every part of the GTM motion around that one person: the messaging, the outbound sequence, the demo script, the pricing page. It works right up until the deal reaches the room that actually decides, and that room has six people in it, only one of whom you ever talked to.

This isn't a sales execution problem. It's a design problem, and it starts upstream of outbound, upstream of the demo, in how the ICP itself got built.


The Buyer You Designed For Doesn't Decide Alone

New research from Influ2's 2026 buying committee survey puts the average enterprise buying group at 6 to 10 stakeholders, with 42% of deals involving 5 to 9 people and a growing share pushing past ten. Each of those people is evaluating the deal against a different question. The champion is asking whether this will make them look good. The economic buyer is asking whether the ROI math survives a board meeting. The technical evaluator is asking whether this breaks something they own. Legal and procurement are asking what happens if this vendor disappears in 18 months. None of them are asking the question your ICP document assumes is the only one that matters.

If your positioning, your case studies, and your demo are all built to answer one buyer's question, you're winning the conversation with the person who has the least leverage to actually close the deal.

Buying Group Cartography, Not Persona Guessing

The fix isn't a bigger ICP document. It's a different unit of design. Instead of describing one persona, you map the group: who sits in each of the six recurring roles (champion, economic buyer, technical buyer, end user, procurement/legal, executive sponsor), what each one needs to see before they'll sign off, and what artifact answers that need. That's buying committee cartography: the discipline of treating the account, not the contact, as the thing you're selling to.

The biggest GTM redesign we make with early-stage founders isn't a new positioning statement. It's replacing "who is our buyer" with "who are our six buyers, and what does each of them need to stop blocking."

In a GTM audit we ran for a Series B vertical SaaS company last quarter, the team had a sharp, well-tested ICP: VP of Operations, 200-1,000 employees, specific tech stack triggers. Their win rate against that persona was strong. Their win rate on deals that reached procurement was under 20%. The gap wasn't the pitch. It was that nothing in their GTM motion, no content, no case study, no page on the site, was built to move a security reviewer or a CFO from neutral to yes. They had one message doing the work of six.

Rebuilding GTM Architecture Around the Group

Three moves fix this, and none of them require new headcount.

First, map the roles before you map the accounts. For your specific ICP, name the six roles that show up in a typical deal and write down, in one sentence each, what that role needs to be true before they stop being a blocker. This becomes the actual spec for your content and messaging, not a persona bio, a decision brief.

Second, build one artifact per role, not one deck for the whole room. The economic buyer needs a one-page ROI case with their own numbers in it. The technical buyer needs an architecture doc, not a feature list. The end user needs to see their actual workflow, not a generic demo. Most founders have one asset trying to do all four jobs, and it does none of them well.

Third, sequence your champion enablement around the committee, not the close. Your champion is going to carry your case into rooms you'll never be in. Hand them a pitch deck built for the one person you talked to, and they'll walk into procurement under-armed. Hand them a one-pager per stakeholder instead, and you've turned a solo champion into a six-person internal sales team you never had to hire.


The Real Cost of Skipping This

Teams that keep GTM architecture built around a single persona don't lose deals in the first call. They lose them in the quiet, seperate rooms: the security review, the budget reconciliation, the legal redline, where nobody from your side was ever there to answer the actual question.

Buying groups aren't shrinking. They're the default unit of enterprise B2B now, and your GTM system either accounts for that or keeps quietly losing to a room you never designed for.

If your ICP still describes one person and your close rate drops every time a deal reaches procurement, the fix isn't a better pitch. It's a different architecture.

Book a Revenue Diagnosis call with RivoAxis and we'll map the buying group your current GTM motion is actually built for, and the one it's losing to.

Book Your Revenue Diagnosis
Previous
Previous

MCP vs AI in Event Tech: What's Actually New, and What's Just a Chatbot

Next
Next

You're Not Ready to Hire a GTM Engineer. Build This First.