Enterprise Sales Playbook for B2B SaaS Founders

Enterprise deals stall because founders sell to the user who loves the product instead of the buyer who controls the budget — use MEDDIC to find the real economic buyer and champion, build a business case in their numbers, and run a paid pilot before you ever send a contract.

Quick Answer

• If your demos "go well" but never close → pre-qualify for budget authority before the first call, because talking to someone who can't sign a PO is a dead end no matter how good the demo is.
• If you can't name the economic buyer on a deal → map the org chart and find a champion with a personal stake in the outcome, because deals stall when no one internally is motivated to push them forward.
• If your pitch is a feature demo → replace it with a one-page ROI calculator using the prospect's own numbers, because buyers act on cost-of-inaction math, not feature lists.
• If you're offering unlimited free trials → switch to a paid or success-based pilot with written success criteria, because a capped, structured pilot produces real proof instead of an open-ended trial nobody feels urgency to finish.
• If a deal is stuck in procurement or legal → have your security documentation (SOC2, DPA) and your pricing "no-go" zone ready in advance, because most delays there come from missing paperwork, not real objections.

1. The Problem

Direct answer: Founders often spend many months pursuing enterprise deals that never close. Enterprise SaaS deal sizes are typically large, yet a large share of initial demos never convert to a signed contract. The root cause usually isn't the product — it's that founders sell to users (who love the product) instead of selling to buyers (who need risk mitigation, cost justification, and measurable ROI).

For example: imagine a founder who runs dozens of "qualified" demos over several months with zero deals closed. A postmortem usually reveals the same pattern: nearly all the conversations were with mid-level managers who could say "yes" to a trial but couldn't say "yes" to a purchase order. The fix is to red-flag any contact without budget authority by week 2 of outreach, rather than discovering the gap months later.

2. Core Framework

MEDDIC for SaaS (Extended):

• Metrics: What KPIs will the champion use to justify the cost? (e.g., "reduce manual data entry by 40%")
• Economic Buyer: The person with P&L authority. Often not the person using your tool. Their incentives are different (cost savings, competitive edge, compliance).
• Decision Criteria: The official list of requirements (RFP or informal). Map your features to their exact words.
• Decision Process: Number of stakeholders, stages, and timeline. Example: "Procurement requires a 3-vendor comparison, security review takes 2 weeks, final signoff needs VP + CFO."
• Implicate Pain: The cost of doing nothing. Quantify it in the prospect's own terms — dollars per month of delay, not vague urgency.
• Champion: A person inside the org who will sell on your behalf. They need to be credible, connected, and motivated.

Direct answer: MEDDIC works because it forces you to identify a champion with a personal, often leadership-visible mandate tied to the pain your product solves, and an economic buyer who cares about a specific number — because a deal with no motivated internal advocate and no quantified business case rarely survives procurement, no matter how good the product is.

Real-world application: MEDDIC is especially useful against larger, established incumbents, because a well-qualified champion with board-level pressure to fix a specific, measurable problem (e.g., audit failures, compliance risk, headcount cost) can outweigh brand-name recognition. If the economic buyer only cares about a hard number — say, the cost of a few full-time salaries — align your entire pitch to that number instead of your feature list.

3. Step-by-Step Execution Guide

Step 1: Pre-Qualify Before the First Call

Goal: Eliminate tire-kickers in <30 minutes.

• Use lead scoring: revenue >$50M, >200 employees, public company or PE-backed (easy to identify via Crunchbase)
• Send a qualification email: "To see if this is a good fit, could you answer: Who would be the economic buyer for purchases over $50k? What's your current tool stack for this problem? What's the deadline for solving it?"
• If they can't answer within 2 business days, they're not serious. Pause outreach.
• Tool: Clay.com or ZoomInfo for data enrichment. Budget? Manual LinkedIn scraping.

Step 2: Map the Org Chart & Find the Champion

Goal: Identify 3+ stakeholders by week 2.

• Use LinkedIn Sales Navigator to see who reports to the VP/Director of your target department.
• Look for: people who comment on industry pain points (e.g., "Manual reconciliation is wasting my team hours every week"), who have been at the company 2+ years, who are active in internal groups.
• Example outreach (email): "Hi [Name], I saw your post about [pain]. We've helped companies automate that exact process. Want to see how? If it's useful, happy to intro to your procurement team."
• Champion red flags: They ask for a "free trial for 30 days" (low motivation) or say "I'll need to check with legal first" (no authority to move forward).

Step 3: Build a Business Case (Not a Feature Demo)

Goal: Show a clear, prospect-specific ROI.

• During discovery, ask: "What is the hourly cost of your team doing [manual process]? How many hours per month? What's the error rate and what does each error cost?"
• Create a 1-page ROI calculator in Google Sheets. Share during the second meeting.
• Example calculation (illustrative, not a real customer's numbers):
  • Labor cost: 10 employees x 5 hours/week x $40/hour = $2,000/week
  • Error cost: 3% error rate on $2M monthly transactions = $60k/month
  • Total annual pain: $120k (labor) + $720k (errors) = $840k/year
  • Your tool cost: $150k/year
  • Illustrative ROI: 4.6x in year 1
• Use their terms. If they call it "operational risk" not "labor cost," rename the column.

Step 4: Run a Pilot (Controlled, Not Free)

Goal: Prove value without giving away the farm.

• Pilot structure: 45 days, with a success criteria agreed upon in writing (e.g., "reduce manual entry by 75% per user").
• Never do an uncapped free trial. Use a "paid pilot" ($5k–$15k for 45 days) or a "success-based pilot": they pay only if they achieve a specific milestone.
• You provide a dedicated onboarding manager. They provide 1–2 super-users who will give daily feedback.
• A well-run pilot with weekly check-ins and a clearly documented set of wins gives the champion something concrete — real usage data — to present internally when asking the CFO for budget approval. Document every win as it happens; don't wait until the end to reconstruct the story.

Step 5: Navigate Procurement and Legal

Goal: Secure the contract with no deal-killing terms.

• Procurement's job is to reduce price. Prepare your "no-go" zone: you can discount 10–15% for multi-year, but never give usage-based pricing below your COGS.
• Security questionnaire: Pre-write answers for SOC2, GDPR, HIPAA. Upload to a portal (e.g., TrustArc or Secureframe). Avoid custom responses.
• Legal friction points: Data ownership (yours stays with you), auto-renewal (non-negotiable for recurring revenue), liability cap (standard is 1x subscription fees; fight for higher if low risk).
• Timeline: Budget 4–6 weeks for procurement & legal after verbal yes. Speed it up by offering a discount for closing within 30 days.

Direct answer: Decide your pricing "no-go" zone and pre-write your security documentation before procurement ever asks for them, because most enterprise deal delays at this stage come from scrambling to answer standard questions, not from genuine renegotiation.

Step 6: Close with a "Champion Letter"

Goal: Make it easy for the champion to get final approval.

• Draft a 1-page recommendation memo for the champion to forward to the CXO.
• Include: The problem, the pilot results (with numbers), the payback period (e.g., "tool pays for itself in a few months"), and the risk of not acting.
• Template snippet: > "I'm recommending [your company] after a 45-day pilot. We saw a significant reduction in manual data entry, equivalent to real annual savings in labor. The implementation is fast, and the alternative we evaluated requires a much longer rollout with no proven ROI. The risk of delay is that we'll miss our deadline to automate compliance."

Step 7: Post-Close Expansion (Within 90 Days)

Goal: Grow usage and seat count before renewal.

• Day 1 post-signing: Send a welcome email to the champion and their team with a timeline for rollout.
• Week 4: Present a usage report showing which features are being used, and where there's friction. Offer a free training session for the broader team.
• Month 3: Present an "expansion proposal" to the economic buyer—show that by increasing seat count, their per-seat cost drops, and new use cases (e.g., another department) can be added.
• Vendors that run quarterly ROI reviews and make the expansion case easy for the buyer to champion internally tend to see seat count grow over time and churn risk drop, because the tool becomes embedded in more of the customer's workflow rather than owned by one department.

4. Common Mistakes to Avoid

Direct answer: The single most common mistake in enterprise sales is optimizing for the person who likes your product instead of the person who can approve spending on it — nearly every other mistake on this list is a variation of that same error.

1. Selling to the end-user only. Users have different incentives (ease of life). Buyers have different incentives (cost savings, competitive advantage). Always map to the buyer's metrics.
2. Giving massive discounts upfront. A steep, unprompted discount signals desperation. Instead, offer a modest discount (10–15%) for multi-year commitments. Price is a signal of value.
3. Sending the CEO to every call. CEOs can stall enterprise process. The CEO should only appear for the final "executive buy-in" meeting. Too much visibility suggests a lack of internal process.
4. Ignoring the security questionnaire. A single missing SOC2 report can kill a deal. Get SOC2 Type II before your first enterprise prospect. It typically costs tens of thousands of dollars a year, but a missing report can single-handedly kill deals worth many multiples of that.
5. Over-customizing features before closing. Don't build custom integrations before you have a signed contract. Offer a "roadmap commitment" instead. Build only after the PO is received.

5. Key Metrics to Track

Metric	Definition	Directional Target (Enterprise)
Time to First Meeting	Initial contact → first call	As fast as your process allows, typically within a business week
Conversion: Demo to Pilot	% of demos that start a paid pilot	Track your own trend; a rising rate signals better pre-qualification
Pilot Success Rate	% of pilots that convert to paid ACV	The majority of well-run, properly scoped pilots should convert
Average Sales Cycle	First contact → closed-won	Commonly several months for true enterprise deals; varies by industry
ACV : COGS Ratio	Annual contract value vs. cost of sales (team + tools)	Higher is healthier; watch the trend over time
Champion Churn	% of deals lost because champion left role	Keep low by staying in touch with your champion regularly
Net Dollar Retention (NDR)	Revenue from existing accounts vs. churn	Track over time; growth here compounds faster than new logos alone

Tracking tools: Use a CRM (HubSpot or Salesforce) with pipeline stages matching the steps above. Manually update notes weekly.

6. Checklist

Pre-Outbound Phase

• [ ] Target accounts list: >500 employees, >$50M revenue, in an industry with clear pain (healthcare, finance, manufacturing)
• [ ] LinkedIn Sales Navigator: List saved with "Decision Maker" filter (VP/Director/Head of)
• [ ] MEDDIC framework template created (1-sheet per account)
• [ ] Security documentation ready: SOC2 report, data processing agreement, vulnerability scans
• [ ] ROI calculator built in Google Sheets (customizable per prospect)

During Deal Phase (Weeks 1–4)

• [ ] First call: Confirm they have budget authority or can introduce the economic buyer
• [ ] Org map created: at least 3 stakeholder names and roles
• [ ] Champion identified (ask: "What's your personal motivation? What happens if this doesn't happen?")
• [ ] Pilot proposal sent: 45 days, paid, with explicit success criteria
• [ ] Draft of champion letter started (with blanks for their data)

Pilot Phase (Weeks 4–10)

• [ ] Daily monitoring: track user adoption from week 1
• [ ] Weekly check-in: champion + 1 super-user, with data dashboard
• [ ] Mid-pilot review: send ROI calculation update with real numbers
• [ ] Legal contract sent: first draft only after pilot success is confirmed

Close & Post-Close Phase (Weeks 10–16)

• [ ] Procurement call: budget 2–3 rounds of revisions
• [ ] Final pricing: offer a modest discount for a 2–3 year contract
• [ ] Champion letter delivered to CXO before the final decision meeting
• [ ] Signed contract: celebrate
• [ ] Day 1 onboarding: send setup guide + schedule kickoff call within 5 days
• [ ] Month 3 expansion proposal: create with use case for second department
• [ ] Quarterly business review (QBR) scheduled: first one at end of month 3

FAQ

Do I need a dedicated enterprise sales team to run this playbook?

No. A founder can run this process solo through the first several deals. Formalize it into a team once deal volume justifies dedicated roles for prospecting, pilots, and account management.

What if I don't have SOC2 yet?

Start the process as early as possible — it takes months, not weeks. Until you have it, expect some security-conscious enterprise prospects to stall or disqualify you, and prioritize accounts with lighter compliance requirements in the meantime.

How long should I expect an enterprise deal to take?

Plan for a multi-month sales cycle once procurement and legal are involved. The exact length depends heavily on your ACV, industry, and whether the buyer already has budget allocated.

Final note: Enterprise sales is a game of leverage, not relationships. You don't need a friend in the company — you need a champion with a problem that's making their life difficult, and a solution priced well below the cost of that problem. Everything else is noise.

Sources

1. Force Management / MEDDIC Sales Academy — origin and documentation of the MEDDIC/MEDDPICC B2B sales qualification framework referenced throughout this playbook.
2. AICPA, SOC 2 Trust Services Criteria — the compliance framework referenced for enterprise security reviews.

Evidence and scope

Review date: 2026-09-10.

Reproducible use. Apply the steps to a named audience, owner, and measurement period; keep the assumptions with the work so a result can be reviewed and repeated.

Limit. This is an operating framework, not a guarantee of pipeline, revenue, ranking, or regulatory compliance.