Winning enterprise deals: three principles for navigating group buying

Executive overview

Enterprise deals take 6–18 months and involve multiple stakeholders, hidden processes, and organisational gatekeepers most founders never map. Ignoring any one of them is why deals collapse after months of effort.

The fix is a three-part framework: map every stakeholder, understand the buyer's internal process, then run both as a proactive plan — "plan the wedding" — rather than reacting to whoever shows up.

The best product rarely wins; the best sales process paired with a good product does.

The three stakeholder groups

• Leadership holds final decision authority; large deals represent strategic transformation for them
• Managers will live with the outcome — their jobs are at risk if the product fails to deliver ROI
• Users influence product preference but rarely hold final authority
• Map all three groups before any demo; identify who the actual decision maker is for each deal
• User preference and leadership preference frequently conflict — the company with the better sales process wins that tension

The buyer's internal process

• Every enterprise company runs its own buying process; ask early: "How do you usually make a decision like this?"
• Key stages to map: discovery call, demo (often multiple, one per stakeholder group), pilot, security review, legal review, procurement
• Procurement's job is to stop deals or get the lowest price — make friends with them early, not at the end
• RFP processes pit all vendors simultaneously; knowing one is coming changes how you position
• Security and legal won't use the software but carry veto power — treat them as stakeholders
• Not asking about the process is the most common reason founders "lose" deals they thought they had

Planning the wedding

• "Plan the wedding" means entering every deal with a proactive map from discovery to close, not reacting to buyer requests
• The biggest pitfall: doing a demo, agreeing to a pilot, then drifting through months of extensions with no path to revenue
• Break large deals into structured stages; a paid pilot with defined success criteria is the bridge to a full contract
• Set success criteria before the pilot begins — not after
• Run legal, security, and procurement in parallel with the pilot, not sequentially after it
• Bring in customer success, onboarding, and implementation partners during the pilot to de-risk delivery
• Buyers who feel looked after see you as a partner, not a vendor — this differentiates you from competitors regardless of product quality

Structuring the discovery call

• Lead with the strategic narrative ("manifesto") before the demo — articulate the transformation the software enables
• This positions you as a thought partner and rises above competitive noise
• Use discovery to surface: what problem they're solving, what else they've evaluated, and who else is involved
• Only after discovery does a tailored demo make sense

Building towards the enterprise motion

• Define your ideal customer profile (ICP) first — selling to the same type of buyer repeatedly makes stakeholders, process, and messaging predictable
• Develop a manifesto: the transformation narrative that makes leadership lean in and book demos
• Run a consistent set of sales and marketing activities (a "Broadway show") to generate and progress enterprise opportunities