LaunchWeek.ai

Back to Day 4: Convert

Enterprise POC Management: How to Run a Proof of Concept Without Burning 6 Months

Most founders selling to enterprise hit POCs (proof of concept) wrong. They say yes to every "can we trial this?" request, hand over a free instance, and lose 3-6 months while the prospect "evaluates" with no path to closing. The deal goes cold; the engineering time is gone; the founder concludes "enterprise is just slow." It isn't slow — it's that enterprise sells the same way enterprise buys, and you weren't running the playbook. POCs are a tactic with a structure, exit criteria, and timeline. Done right, they close 6-figure deals in 60 days. Done wrong, they're free consulting for prospects who never had budget.

A working POC playbook answers: when to offer one (not always), what success criteria to set (mutual + measurable), how to scope (no scope creep), how to staff (their team + your support, not your team building for them), how to time-bound (30-60 days; never "until done"), how to commercial-close (price + paper-process started during, not after), and how to walk away (POCs end one of three ways — close, extend with reason, or kill).

This guide is the playbook for running enterprise POCs that actually close. Companion to Sales Playbook, B2B Procurement Navigation, Annual Contract Negotiation, Demo Request Flow, High-Touch Onboarding, and Beta Program.

What Done Looks Like

By end of this exercise:

  • Decision framework: when do we offer a POC (vs. trial / paid pilot / direct close)?
  • Standard POC framework with phases and timelines
  • Success-criteria template (signed by both sides)
  • Pricing for POC (free vs. paid pilot — when each)
  • Internal POC roles (DRI, exec sponsor, engineering escalation)
  • POC kill criteria (when to walk)
  • Mutual close plan with paper-process starting Day 1
  • POC win-rate target (60%+ if you're picking the right ones)

This pairs with Sales Playbook, B2B Procurement Navigation, Annual Contract Negotiation, Demo Request Flow, High-Touch Onboarding, Beta Program, Sales Demo Calls, Sales Onboarding Ramp, First Sales Hire, First Customer Success Hire, Pricing Strategy, Pricing Packaging Tier Design, Trust Center & Security Page, Customer References, and Win Loss Analysis.

When to Offer a POC

Most early-stage founders offer POCs to anyone who asks. That's the mistake. POCs are expensive — engineering hours, AE time, opportunity cost on the next deal — so the first decision is whether this opportunity warrants one.

Help me decide if a POC is the right move.

The qualification framework — only POC if ALL of these are true:

**1. Champion identified**
There's a specific person at the prospect who wants this and will fight internally.
"Sales-shopping" prospects without a champion = no POC.

**2. Economic buyer identified**
You know who can actually sign the contract (not your champion's manager who'll delegate; the person with the budget).
"We're still figuring out budget" = no POC.

**3. Budget confirmed (range, not exact)**
"Yes, we have $50K-$150K available for this category in this fiscal year" = good.
"We'll figure out budget once we like the product" = bad.

**4. Mutual success criteria already drafted**
You and they agree on 2-4 specific, measurable outcomes the POC will demonstrate.
Vague "we want to see how it works" = no POC.

**5. Timeline confirmed**
"We need this in production by [date]" = good.
"Whenever; no rush" = no POC (unless you have nothing else).

**6. Procurement / legal pre-cleared**
Their procurement team has been notified; MSA review can run in parallel.
"We'll deal with legal at the end" = high probability deal stalls there.

**7. ACV justifies the cost**
Your fully-loaded POC cost (engineering + AE + executive time) shouldn't exceed 25% of expected ACV.
$10K ACV × 25% = $2,500 max POC investment.
$100K ACV = $25K POC investment.

When some are missing:
- 1-2 missing: do a structured trial instead (free product access; no engineering)
- 3+ missing: back to "demo and follow up" stage; not POC-ready

The honest framing: POCs are for late-stage opportunities, not lead-qualification. If they need a POC to decide if they want what you sell, you haven't sold yet.

For my company:
- Average ACV
- POC cost estimate
- Win rate today

Output:
1. POC qualification checklist
2. Cost-per-POC estimate
3. Conditions to walk

The mistake to avoid: offering a POC to break a stuck demo cycle. If they keep saying "show me again," more demos won't help — but a POC won't either. They're not buying. Move on.

POC vs Trial vs Pilot — What's the Difference

Help me distinguish the formats.

The four formats:

**1. Free trial (self-serve)**
- Standard product access; time-limited (14-30 days)
- Self-onboarded; minimal CS support
- Cost: ~$0 for you (engineering already shipped)
- Best for: SMB / mid-market product-led-sales

**2. Hands-on trial (light-touch)**
- Same product, but with onboarding session + check-in
- 30-day; AE + CS engaged but not building
- Cost: ~$1-3K of AE/CS time
- Best for: mid-market $20K-$50K ACV

**3. POC / Proof of Concept**
- Custom-scoped evaluation against specific success criteria
- 30-60 days; AE + CS + maybe engineering
- Includes integrations, custom configs, sometimes minor product work
- Cost: $5K-$25K of internal effort
- Best for: enterprise $50K+ ACV with specific use case

**4. Paid pilot**
- POC with discounted price ($10K-$50K for 60-90 days)
- Same depth as POC; but commercial commitment
- Convertible to full annual contract
- Best for: enterprise $200K+ ACV; high-stakes decisions

When to pick what:

| ACV | Format |
|-----|--------|
| <$10K | Self-serve free trial |
| $10K-50K | Light-touch trial |
| $50K-150K | POC |
| $150K+ | POC or paid pilot |
| Strategic deals (logo / category-defining) | Paid pilot or full launch |

The case for paid pilots over free POCs:
- Filters out tire-kickers (anyone who won't pay $10K won't pay $100K)
- Anchors price expectation
- Commits prospect to outcomes (not just "we'll evaluate")
- Procurement starts early (paid = paper)

For my company:
- Typical deal size
- POC win rate today

Output:
1. Format-by-deal-size guide
2. Free POC vs paid pilot recommendation

The 2026 trend in enterprise SaaS: paid pilots replacing free POCs. Free POCs got abused in the 2010s-2020s — companies would run 3-5 simultaneously with no intent to buy. Paid pilots ($10K for 60 days, convertible to annual) filter the actual buyers. Reasonable founders charge.

Designing the Success Criteria

This is the single most-skipped step. POCs without explicit success criteria become "we'll just see how it goes" — which never ends.

Help me design success criteria.

The criteria template:

**Format**: 2-4 outcomes, signed by both sides at POC start.

For each criterion:
- Specific (not "improve performance"; rather "reduce p95 query latency to <200ms")
- Measurable (with stated method)
- Achievable in the POC scope
- Time-bound (within POC duration)
- Owned (who measures, who confirms)

Example for a data SaaS:
1. Ingest 30 days of historical data (success: > 95% completeness)
2. Run 5 example queries with results in <500ms (success: 5/5 hit target)
3. Integrate with [their data warehouse]; sync working in production environment
4. Demonstrate weekly executive report generation (success: report shipped to 3 named execs)

Example for a workflow SaaS:
1. Migrate 3 existing workflows from incumbent (success: feature parity for those 3)
2. Train 5 named users to mastery (success: 5/5 complete certification)
3. Show 30% time reduction on workflow X (success: time-to-complete benchmarked vs baseline)
4. Pass internal security review (success: security questionnaire signed by their CISO)

Both sides sign:

POC Success Criteria — [Prospect] x [Vendor]

POC duration: [X] days, starting [DATE], ending [DATE]

Success criteria (we both agree on these as definition of "done"):

  1. [Criterion] — measured by [method] — owned by [person]
  2. [Criterion] — measured by [method] — owned by [person]
  3. [Criterion] — measured by [method] — owned by [person]

If 3+ of [N] criteria succeed, [Prospect] commits to:

  • Submitting paperwork through procurement
  • Targeting commercial close by [DATE within 30 days of POC end]
  • Annual contract value: $[range]

If criteria fail, [Vendor] commits to:

  • No charge (or refund if paid pilot)
  • Honest "go / no-go" recommendation

[Champion signature] [AE signature] [Date]


Why this matters:
- Forces both sides to agree on what "good" looks like BEFORE evaluation begins
- Prevents goalpost-moving ("yeah, you hit those, but now we want X too")
- Gives champion ammunition for internal advocacy
- Makes the close conversation a checklist, not a debate

The non-obvious benefit: writing this upfront often kills bad POCs. If they won't sign criteria, they're not serious — better to know now than 60 days in.

For my company:
- Sample success criteria
- Sign-off process

Output:
1. Success-criteria template
2. Owner per criterion
3. Sign-off cadence

The pivotal moment: the prospect refuses to commit to criteria + timeline + close-on-success. This is the single best filter. Real buyers commit because they want to buy. Tire-kickers refuse because they don't. If they refuse, walk — the POC won't end well.

The 60-Day POC Structure

Help me run the 60-day POC.

The phases:

**Week 0: Pre-kickoff (5 days before official start)**
- Mutual success criteria signed
- Kickoff scheduled with champion + economic buyer + key technical contact
- Slack / Teams shared channel set up
- MSA / DPA / security questionnaire delivered to their procurement (parallel track)
- Statement of Work (SOW) drafted

**Week 1: Kickoff + setup**
- Kickoff call (60 min, all hands)
- Their team gets access; ours gets context
- First integration / data load completed
- Day 5: first check-in; "are we on track?"

**Week 2-3: Build-out**
- Their team works with our product
- Our CS engineer available 4 hours / week for support
- Weekly check-in (30 min)
- Address blockers within 24h

**Week 4: Mid-point review**
- Demo progress to economic buyer (if they weren't in kickoff)
- Re-confirm success criteria still relevant
- Surface any scope creep; resist it
- Procurement / legal status check

**Week 5-6: Outcome demonstration**
- Their team runs the success-criteria evaluation
- Document results
- Mid-point usage stats reviewed: are 5 named users actually using it? (If 0/5 active, POC is failing.)

**Week 7: Decision week**
- Formal review of success criteria
- Score each: pass / partial / fail
- Three outcomes:
  - 3+ pass → execute commercial close
  - 1-2 pass → discuss extension or walk-away
  - 0-1 pass → kill; honest "this isn't a fit"

**Week 8: Commercial close**
- Pricing finalized
- Contract redlines; legal close
- Day 60: signed
- Transition to full-customer onboarding

**Cadence**:
- Daily: Slack channel; respond within 4h business hours
- Weekly: 30-min check-in (Tue or Wed)
- Monthly milestone: kickoff, mid-point, decision

For my POC playbook:
- Standard duration
- Typical cadence

Output:
1. Phase-by-phase plan
2. RACI per phase
3. Cadence template

The mistake most teams make: running POCs without time-boxed phases. Without phase gates, scope creeps; the POC drifts; week 8 arrives with no decision. Force the structure.

Roles & Responsibilities

Help me staff a POC.

The roles:

**Vendor side**:

- **AE (Account Executive)** — DRI for the deal; runs commercial; weekly cadence
- **CSE / Sales engineer** — technical lead; primary day-to-day contact
- **CS / Onboarding** — once technical setup done; user enablement
- **Engineering escalation** — for blockers; not building features
- **Executive sponsor** — for high-stakes deals; mid-point review and close

**Prospect side** (must be staffed; if not, POC fails):

- **Champion** — person who wants this; carries internal politics
- **Technical lead** — does the integration work
- **End users** (3-5 named) — actually use the product
- **Economic buyer** — signs the contract
- **Procurement contact** — handles paperwork in parallel
- **Security review owner** — handles security questionnaire

If prospect can't name champion + technical lead + economic buyer, POC will fail.
If they can't commit 5 named end users, the criteria-validation will fail.

**The critical anti-pattern**:

Vendor builds for prospect.

Bad: "We'll build the integration to your data warehouse."
Good: "We'll guide YOUR team to build the integration. Estimated 2 days of their work. Our SE is available for questions."

Why: if you build it, they don't own it. Day 61 (post-close), you find their team can't use it. Churn risk.

If they can't / won't dedicate technical resources, the deal isn't real.

**The exception**: paid pilot at high ACV. Then you build (because they paid for it).

For my company: [team size]

Output:
1. Vendor team
2. Prospect roles required
3. Anti-pattern guardrails

The single biggest predictor of POC success: does the prospect have a technical lead committed to the integration. If yes, 70% close rate. If no, 10% close rate. The presence of skin-in-the-game from their side is the signal.

Scope Creep Defense

Help me defend against scope creep.

The classic creep patterns:

**1. "Can you also..."**
Mid-POC: "While we're at it, can you also support our SSO?"
Defense: "That's a great future ask. For this POC, our scope is [original]. Let's add SSO to the post-close roadmap."

**2. "Our other team wants to evaluate too"**
Suddenly the POC has 3 teams.
Defense: "Each team is a separate evaluation. Let's complete this one first; happy to do another POC for [other team]."

**3. "We need this custom feature to evaluate"**
The unscoped feature ask.
Defense: "Help me understand — is this required for the success criteria, or a future need? If required, let's update the criteria together (and timeline). If future, table for post-close."

**4. "Our procurement just woke up; they need 6 weeks"**
The post-criteria-met procurement stall.
Defense: Procurement was meant to run in parallel from Day 1. If they're starting now, escalate to executive sponsor on both sides.

**5. "Let's extend by another 30 days"**
The classic stall.
Defense: "Help me understand the gap. What changes in 30 days that doesn't change in 7?"
Real reason: budget delayed, internal politics, reorg. Surface it.

**6. "We want to test more use cases"**
The expanding evaluation.
Defense: "More use cases = post-close roadmap, not POC scope. Our criteria validate the foundational fit."

**The reframe**:

Every "can you also" is really one of:
- Genuine new requirement → update criteria + timeline together
- Stall to avoid commercial close → name it; escalate
- Champion buying time for internal politics → support them; don't expand scope

The discipline: any scope change = both sides re-sign success criteria and timeline.
No re-sign = original scope holds.

For my POCs:
- Most common creep
- Mitigation that worked

Output:
1. Top 3 creeps you face
2. Scripted responses
3. Escalation rule

The scope-creep mindset shift: say yes to value, no to scope expansion. "Yes, that's valuable — let's add it to the implementation roadmap post-close" is fundamentally different from "yes, we'll do it now." The first builds momentum; the second torpedoes timeline.

The Commercial Close Track (Run in Parallel)

Help me run commercial in parallel.

The principle: commercial work happens DURING the POC, not AFTER.

Why: enterprise procurement is the bottleneck. MSA, DPA, security review, vendor onboarding — these add 30-90 days if done sequentially. Done in parallel, they finish around the time the POC does.

The parallel tracks:

**Day 1**:
- Send MSA / DPA / SOW to prospect's legal / procurement
- Send security questionnaire response (or trust-center link)
- Pricing range communicated

**Day 7**:
- First MSA redlines back
- Security review status confirmed
- Vendor-onboarding form (their internal process) submitted

**Day 21**:
- MSA redlines closed (or escalated)
- Final pricing proposal delivered

**Day 30** (mid-point):
- Pricing accepted in principle
- Contract paper close to final
- Legal sign-off pending criteria validation

**Day 50**:
- Final paper ready for signature
- Pricing locked
- Order form ready

**Day 60**:
- POC criteria validated → sign

If commercial isn't running in parallel, you'll close the POC successfully and then wait 90 days for procurement. Total deal length: 150 days. With parallel: 60 days.

The unforced error: "let's not bring legal in until we know it's a fit." Then "fit" is decided Day 60, and procurement starts Day 60. Deal delayed by 30-90 days.

For my deals:
- Procurement avg cycle
- Typical post-POC delay

Output:
1. Parallel-track schedule
2. Owners
3. Day-by-day commitments

The honest framing for procurement: start it Day 1, even if your champion says "not yet." If their procurement isn't running in parallel, the POC will close and the deal will stall. Push politely; cite "we want to be ready for commercial close on Day 60."

When to Kill a POC

Help me know when to kill.

Kill signals:

**Week 2 signals**:
- Champion goes silent (no response > 5 days)
- 0 of 5 named users have logged in
- Technical lead unassigned

Kill verdict at week 2: rare; usually push and re-engage

**Week 4 signals**:
- Mid-point review never scheduled or attended
- Economic buyer never engaged
- Multiple "can you also" expansions
- Active users < 50% of target

Kill verdict at week 4: time to escalate or kill

**Week 6 signals**:
- Success-criteria milestones missed with no plan
- Procurement / security review hasn't started despite asks
- Champion lost their job / reorg
- Budget reallocated to other priority

Kill verdict at week 6: kill

**The kill conversation**:

"Hey [champion], I want to be transparent.

Looking at where we are vs where we agreed to be by week 6:

I'm not seeing the path to a Day-60 close based on current trajectory.

Three options:

  1. Re-scope: reduce criteria to what's achievable; extend by 30 days IF there's a real reason (specific blocker we can name)
  2. Pause: this isn't the right time; let's reconnect in [Q+2]
  3. Walk: this isn't a fit; appreciate your time

Which is honest about where you are?"


The kill is a gift to both sides:
- You free up engineering / AE time for live deals
- They stop pretending they're going to buy
- You preserve the relationship for future ("when timing is right, come back")

The opposite — running zombie POCs to month 4 — destroys forecasts and morale.

For my POCs:
- Top kill signals
- Owner of kill decision

Output:
1. Kill criteria
2. Kill conversation script
3. Cadence to review

The 2026 reality: enterprise pipeline forecasts are fiction without disciplined kill rules. AE optimism keeps zombie deals on the board for quarters; sales leaders forecast off zombie pipeline; revenue misses; layoffs. Killing POCs honestly is the kindest thing you can do.

Pricing the POC

Help me decide free vs paid POC.

The decision matrix:

**Free POC works when**:
- ACV < $50K
- Strategic logo (the customer name matters more than the contract value)
- Engineering effort < $5K of internal time
- Champion needs the win; political pressure to "earn the budget"

**Paid pilot works when**:
- ACV > $100K
- Engineering effort > $10K of internal time
- Custom integration / data work required
- Multiple POCs running; want to filter

**Pricing the paid pilot**:

For $100K ACV: $10-15K paid pilot, 60-90 days, convertible to annual.
For $500K ACV: $30-50K paid pilot.
For $1M+ ACV: $50-100K paid pilot.

The pricing rule: 10-15% of expected first-year ACV.
Higher than 20% → pricing the trial like a sale; prospect won't bite.
Lower than 5% → prospect doesn't take it seriously.

**Convertibility**:

Standard: pilot fee credits 100% against first-year contract if signed within 30 days of pilot end.
After 30 days, credit drops or expires.
Creates urgency without being aggressive.

**Free POC framing**:

Don't say "free trial" — say "joint evaluation."
The framing matters: free trials are commodity; joint evaluation is partnership.
Both sides invest; both sides commit.

For my deals: [size]

Output:
1. Free vs paid recommendation per deal-size band
2. Pricing for paid pilot
3. Conversion-credit terms

The 2026 trend: mid-market follows enterprise. Paid pilots used to be enterprise-only ($1M+ ACV). Now mid-market ($50K+ ACV) increasingly uses them. The discipline of "we both invest in evaluating" filters out unserious buyers and shortens cycle times.

Common POC Mistakes

Help me avoid POC mistakes.

The 10 mistakes:

**1. POC without champion**
You're pitching procurement that has no internal advocate. Won't close.

**2. POC without success criteria**
"Let's see how it goes" = never ends.

**3. POC where you build for them**
You become their consultant. Day 60: they don't own anything; can't sustain post-close.

**4. POC without procurement in parallel**
Day 60 success = Day 150 close.

**5. Indefinite extensions**
"Just one more month" 4 times = 4 months wasted.

**6. POC with no economic buyer engagement**
Champion + technical lead can't sign $200K. Get the economic buyer in by mid-point.

**7. Free POC for unqualified prospect**
You're paying to educate the market. Disqualify before POC.

**8. POC with vague pricing**
"We'll figure out price after the POC." Sticker shock kills deals at the end.

**9. Multi-team POCs (one POC; two prospect orgs)**
"Our marketing team also wants to try." Now you have two failures masked as one.

**10. Skipping the kill conversation**
Zombie POCs eat resources. Kill at week 6 if signals are clear.

For my company: [worst mistakes]

Output:
1. Top 3 you've made
2. Mitigations
3. Process changes

The single most-painful POC mistake: letting a POC drift past its end date without a decision. The drift normalizes; the team accepts limbo; the deal never closes. Force the decision conversation at Day 60 even when you're afraid of the answer.

What Done Looks Like

A working POC playbook delivers:

  • Clear "POC vs trial" decision logic by ACV
  • Standard 60-day structure with phase gates
  • Mutual success criteria signed Day 0
  • Both sides staffed (champion + technical lead + economic buyer + 5 users)
  • Commercial track running in parallel from Day 1
  • Mid-point review with course-correct or kill
  • Day 60 decision (no extensions without specific reason + new timeline)
  • POC win rate > 60% (because you're picking the right ones)
  • Average POC duration ≤ 75 days (with kill at Day 60-75)
  • Post-close customer activation rate matching non-POC customers

The proof you got it right: your engineering team isn't burning cycles on stalled POCs; your AEs aren't carrying zombie deals in the forecast; and when a POC closes, the customer transitions to onboarding without a "now what?" moment.

See Also

← PreviousDiscount & Promotion Strategy: When Discounts Help, When They Train Bad Behavior, and How to Run Promotions That Don't Erode Your PricingNext →Land and Expand: Build the Expansion Revenue Engine