The discovery-to-close playbook for six-figure B2B deals

Most enterprise deals don't die at the close. They die six weeks earlier, in the middle of the cycle, when nobody noticed the buyer went quiet.

You had a strong first call. Budget was confirmed. A champion was engaged. Then a few weeks passed, a procurement review started, and suddenly the champion stopped returning calls. The deal lingered in the CRM as "verbal commit" for another 90 days before someone finally marked it lost.

This isn't a closing problem. It's a process problem. Enterprise deals at the $100K-$500K ACV range require a specific operational discipline that most B2B sales teams never build. They run SMB plays at enterprise scale and wonder why cycles take 9-12 months instead of 3.

According to Bain & Company's research on enterprise B2B sales, the average enterprise deal involves 6 to 10 decision-makers and takes 12-18 months to close for contracts above $250K. Win Rates for complex enterprise opportunities sit at 15-20% for teams without a formal stage-gate process, versus 35-40% for teams with one.

The difference isn't talent. It's a stage-by-stage enterprise sales playbook that maps exactly what needs to happen at each point in the cycle, what signals to watch, and what breaks things when you skip steps.

This guide covers the full journey. Discovery through contract. What to ask, who to map, when to push for proof of concept, how to negotiate without giving away margin, and what the final 10% of the deal actually requires to close.

Discovery isn't a screening call. That distinction matters more than most AEs realize.

Screening calls filter for budget and fit. Discovery calls build a map of the organizational pain, the politics, and the actual buying journey ahead. Get this wrong and everything downstream — your proposal, your POC, your negotiation — rests on assumptions instead of intelligence.

A strong enterprise discovery call answers five things:

1. What's the current state and the gap? Not "what problem do you have" — buyers give you the PR version of that. Ask: "Walk me through how you handle [process] today" and then "where does that process break?" Specifics surface when you make it procedural.

2. What has the organization already tried? This is the most underused question in B2B sales. "What have you already tried to fix this?" reveals the history of failed initiatives, the internal politics around the problem, and the level of urgency the org actually feels. If they've tried nothing, urgency is low. If they've tried three things and failed, you're dealing with a burning problem.

3. Who else feels this pain? Get the stakeholder map started on the first call. Ask: "Besides yourself, who else in the organization deals with this issue on a daily basis?" Then: "Who would need to sign off on a project like this?" You're building the political map before the buyer even knows you're doing it.

4. What does success look like in 12 months? This defines how you'll structure your commercial proposal later. If the VP of Revenue says "I want sales cycle down from 90 days to 45," that's a measurable outcome you can price against. Vague success criteria produce stalled deals.

5. What does the evaluation process look like? Ask directly: "How does your organization typically evaluate vendors for a project of this scope?" This tells you whether you're dealing with a formal RFP process, a champion-driven internal sale, or something more informal. It also tells you who else is in the room you haven't met yet.

The first call ends with three things confirmed: a clear business problem, at least two stakeholders named, and a defined next step with a date. If you're leaving the call without those three, you're being polite rather than effective.

For more on how qualification discipline connects to where you focus your pipeline effort, the article on strategic sales focus for B2B teams covers the deal selection framework in detail.

Enterprise deals don't have a buyer. They have a buying committee. And the single biggest mistake AEs make is running the entire deal through one champion while everyone else remains invisible.

Multi-stakeholder mapping is the process of identifying, understanding, and building relationships with every person who can influence, block, or accelerate the deal. It's not optional at $150K+. Without it, you're one vacation or one reorganization away from losing a deal you thought you owned.

The typical enterprise buying committee for a $200K software or services deal includes:

• Economic buyer — controls budget, rarely in early meetings. Often a CFO, VP Finance, or division president. They care about ROI and risk, not features.
• Champion — your day-to-day contact, internally motivated to make this happen. Their credibility is on the line if the project fails.
• Technical evaluator — IT security, architecture, or technical leadership. Their default answer is "no" until proven safe and compliant.
• End user representatives — the people who'll actually use whatever you sell. Their adoption determines whether success metrics get hit.
• Legal/procurement — enters late and slows everything down if you haven't pre-cleared major contract terms early.

Map these roles by the end of the second meeting. You don't need to have met everyone yet, but you need to know they exist.

For each stakeholder, get clear on: their position on the initiative (active sponsor, passive supporter, neutral, or blocker), their primary concern (cost, risk, capability, adoption), and whether they've been briefed by your champion or are operating on assumptions.

The stakeholders you haven't met are where deals die. That technical evaluator who never showed up in meetings but then blocked the deal in week 14 because of a security concern? You should have found that person by week three.

A practical approach: ask your champion directly after meeting two or three: "Is there anyone else in the organization who might raise concerns about moving forward with a project like this?" Champions know who the blockers are. Most AEs just never ask.

A proof of concept either accelerates a deal or kills it. There's rarely a neutral outcome.

AEs often treat POCs as a way to de-risk a deal when the buyer hasn't fully committed. That's backwards. A POC where the buyer hasn't confirmed they'll buy if it succeeds is free consulting work. You've just extended the cycle by 4-8 weeks and handed your evaluation criteria to your competitors.

Here's the rule: never agree to a POC without a mutual success plan signed before it starts.

A mutual success plan defines:

• Success criteria — specific, measurable outcomes the POC needs to hit. If the buyer can't define what success looks like before you start, they're not ready for a POC.
• Timeline — a bounded evaluation period. Four weeks maximum for most software or services POCs. Anything open-ended drags indefinitely.
• Decision process — who reviews the results, when the review meeting happens, and what happens next if criteria are met. "We'll evaluate internally" is not a decision process.
• Commercial intent — a verbal or written confirmation that meeting the success criteria leads to a purchase decision. Not a guarantee, but a commitment to evaluate fairly with a defined outcome.

With those four things in place, a POC becomes a closing mechanism. Without them, it's a distraction.

For services deals (consulting, fractional leadership, advisory), the POC often takes the form of a paid diagnostic or discovery sprint rather than a free trial. This is actually stronger positioning. Paying for the diagnostic signals buyer seriousness and produces findings that justify the full engagement. Fractional CRO engagements often start this way — a four-week revenue diagnostic that maps exactly what the full engagement would fix.

One more thing about POCs: if a buyer asks for a POC and you're already 60% through the deal cycle with strong signal from the economic buyer, consider whether a reference call from a similar customer would serve the same purpose faster. POCs take time you could spend closing.

Most enterprise sales teams don't know what good looks like because they measure absolute outcomes (did it close?) rather than process health (is it progressing at the right rate?).

Here are the benchmarks that matter for six-figure B2B deals:

The cycle length gap is the most striking. Teams running a structured enterprise sales playbook close deals in roughly half the time of teams that don't. The reason isn't that they push harder. It's that they surface blockers early (before they become killers), align stakeholders before the evaluation is complete (instead of after), and create internal urgency through a mutual action plan rather than external pressure from the AE.

Win Rate data from Gartner's enterprise B2B research puts average competitive Win Rates in complex sales at 17% for teams without a defined methodology versus 34% for those with MEDDIC, MEDDPICC, or equivalent. The methodology matters less than the discipline of applying any methodology consistently.

If your enterprise sales cycle is longer than 12 months for deals under $200K ACV, the problem isn't the buyer. It's your process.

Enterprise commercial negotiation is where most AEs give away margin they didn't need to give away.

This happens for one reason: the commercial conversation starts too late. Pricing lands as a number in a proposal after weeks of conversations, and the buyer's first instinct is to push back. The AE, who hasn't anchored value before presenting numbers, responds by discounting. The deal closes at 20% below list because nobody established what success was worth before framing what it costs.

Here's the sequence that prevents that:

Anchor value before anchoring price. Before any commercial conversation, confirm with the economic buyer what solving this problem is worth. "You mentioned this is costing you roughly 15% of sales rep productivity. With 40 reps at $150K OTE, that's approximately $900K annually in wasted capacity. Does that feel about right?" Now $180K doesn't feel expensive. It's a 5-month payback.

Present options, not line items. Give buyers three investment options (good, better, best) rather than a single price. This shifts the negotiation from "yes or no" to "which one." The middle option is usually where deals close, and the presence of the higher option makes it feel reasonable.

Name the variables before the buyer does. When presenting pricing, explicitly list what can and can't flex: "The investment is $180K. Timeline is fixed at six months because earlier milestones depend on completion. What can flex is payment schedule and scope phasing." You're defining the negotiation parameters before the buyer starts trading.

Never discount without getting something. Every pricing concession should come with a scope reduction, a shorter payment timeline, a reference commitment, or a contract length extension. "I can reduce to $155K if we compress the timeline to four months and you commit to a case study." Trading down without getting anything teaches buyers that your pricing is arbitrary.

Fair warning: this approach requires more preparation than most AEs invest. But the return is significant. Teams that run structured commercial conversations average 12% discount versus 22% for those that don't, according to internal benchmarks from enterprise software companies. That's 10 points of margin on every deal.

If your team needs a structured framework for this kind of commercial discipline, an advisory engagement focused on enterprise deal execution can build the playbook in 60-90 days.

Legal and procurement is where enterprise deals go to die slowly. It's also entirely preventable.

Most AEs treat legal as a post-close formality: sign the deal, send it to their counsel, wait. Enterprise procurement works differently. It's a parallel process that starts running the moment the organization identifies a serious vendor. And if you haven't prepared for it, the review can add four to eight weeks to your cycle — or surface a blocker that kills the deal in week 16.

Three things to do before procurement enters the picture:

Pre-clear major risk areas early. By meeting three or four, ask your champion: "Does your legal team have standard requirements around data residency, SLAs, or indemnification that vendors typically flag?" You're not asking for the full contract yet. You're surfacing potential blockers before they become surprises. If your standard terms conflict with their standard requirements, better to know in month two than month eight.

Get your champion to sponsor the procurement process. Procurement works for the business, not the vendor. A champion who actively advocates internally for a fast review timeline (because the project is time-sensitive) will move procurement faster than any external pressure you apply. Make the internal urgency case for your champion before they enter procurement review.

Use the mutual action plan as a scheduling tool. When you have a mutual action plan with milestone dates, procurement review gets scheduled as a specific activity with a timeline rather than an open-ended process. "Legal review: weeks 14-16, with contract execution by week 17" is a managed timeline. "Legal will review when they have capacity" is not.

Worth noting: for larger deals, consider asking your champion for a brief legal pre-call to review your master service agreement before it enters formal review. Most enterprise procurement teams appreciate this because it reduces the back-and-forth in formal review. Legal teams who've seen your contract once tend to move faster the second time.

Every stage of an enterprise deal has a failure mode. Most of them are predictable. Here's the pattern.

The pattern across all of these: enterprise deals break when process discipline breaks. The AE chasing a deal and the buyer managing multiple priorities aren't on the same schedule. The only way to create alignment is a shared timeline (mutual action plan) and a shared definition of what success means at each milestone.

Deals don't die from lack of effort. They die from lack of structure.

Enterprise deals give you constant signals about their health. Most AEs ignore them until a deal goes cold. By then, recovery takes weeks.

Track these signals across every active enterprise deal:

Access signals measure stakeholder engagement. Are you getting introductions to new stakeholders, or has the champion stopped connecting you with others? When introductions stop, deal momentum usually has already slowed. When you get an introduction to the economic buyer, the deal is accelerating.

Response time is one of the most reliable health indicators. A champion responding in hours is engaged. One responding in days is managing other priorities. When response time from a previously active contact extends to a week or more without explanation, surface it directly: "You've been less available than usual — is there something shifting internally?"

Meeting attendance changes are often the first visible signal of deal movement. When the champion starts attending calls with additional stakeholders, the deal is advancing internally. When previously engaged stakeholders stop showing up, investigate.

Executive engagement is the strongest positive signal in any enterprise deal. When the buying organization's VP or C-level starts requesting calls or attending meetings without being invited, they've already decided internally. Your job shifts to not losing what's already won.

Internal urgency signals are harder to observe but critical to track. Ask your champion periodically: "Has anything changed internally on the priority or timeline for this project?" Budget cycles, reorganizations, competitive threats, and board mandates all create urgency that your champion can feel before you can see it. Tap into that awareness.

The absence of signals is itself a signal. A deal where nothing moves for three weeks is dying, even if no one has said so. Create a threshold: if there's been no substantive activity on an enterprise deal for 15 business days, treat it as at-risk and intervene. Don't wait for the CRM to tell you what a calendar already knows.

The close is not a conversation. It's the result of conversations you already had.

If your enterprise deal reaches verbal agreement and then stalls before signature, one of three things is happening: the champion doesn't have the internal authority to push it through, there's a stakeholder concern that was never surfaced and resolved, or the deal lacks a credible internal reason to prioritize signing now rather than next quarter.

All three of these are symptoms of upstream gaps, not closing problems. But they still need to be solved.

For authority gaps: Build an executive sponsor relationship before you need it. If your champion is a director and the decision requires VP approval, make sure you've had at least one substantive meeting with that VP before the close conversation. An AE asking a VP to approve a deal they've never been involved in is asking for a favor. An AE whose executive contacts have endorsed the project is confirming a decision.

For unstated concerns: In the final phase of the cycle, ask your champion directly: "If this doesn't get done this quarter, what would that be about?" This surfaces blockers in a way that invites honest answers rather than defensive ones. Champions who think the deal is going to close will answer. Champions who are managing a concern they haven't told you about will usually reveal it here.

For urgency creation: The most effective close mechanism is always internal to the buyer, not external pressure from the AE. Find the business event that makes this quarter matter more than next quarter: a Q2 product launch that requires the capability, a fiscal year budget that expires, a board commitment to a metric that this project supports. Your champion needs to be able to say to their organization "we need to get this done in Q2 because of X" where X is something they own, not something you want.

The mutual action plan closes deals because it builds that internal timeline collaboratively. By the time the contract is ready to sign, both parties have been working toward a specific date for weeks. The signature isn't a new ask. It's the natural conclusion of a process both sides committed to.

For teams that want to build this enterprise sales playbook into a repeatable operating system, a structured advisory engagement focused on enterprise deal execution can reduce cycle time and lift Win Rates in the first 90 days.