How do you prevent POC scope creep when customers keep asking 'can you just...'?
Answer
Gate requests with a 2-minute "In-POC or Out-of-Scope" decision tree. If the feature wasn't on the day-1 charter, it's out. Pavilion research: 71% of stalled POCs failed because feature requests diluted focus. The move: document 3–4 "explicit out-of-scope items" on the POC deck (version control, custom fields, third-party integrations) so the customer self-edits.
The Decision Tree
``` "Can you add field-level audit logs?" → Is audit logging on the signed POC charter? No. → Does this block a success metric? No. → Decision: "That's a smart ask. Let me log it as a feature request for post-POC evaluation." → Timeline: Drop it in a shared backlog; revisit week 5 if POC is winning.
"Can you support our custom workflow?" → Is workflow customization in the charter? No. → Does this block a success metric? Check metric #2 (payroll accuracy)... No, it doesn't. → Decision: "This is valuable. For now, let's run the standard workflow to validate core functionality. We'll scope custom workflows into the contract." ```
Scope Creep Checklist
- Week 1: Customer requests 2–3 additions (normal). Log all in a "parking lot" doc shared with sponsor.
- Week 3: Push back on any new request that wasn't on day-1 charter. Frame as scope protection ("Let's nail these 3 metrics first.").
- Week 5: Review the parking lot. If POC is passing metrics, discuss whether 1–2 items unlock the deal. If POC is failing, items are irrelevant—kill the POC.
Language
Wrong: "We can't do that. It's not in scope." (defensive; shuts down conversation).
Right: "That's strategic. Here's the trade-off: adding that feature burns 4 days, which delays our validation of the core payroll workflow. You want us focused on nailing these 3 success metrics by day 35, right?" (collaborative; educates).
TAGS: POC_scope,feature_creep,scope_management,Pavilion,deal_momentum,negotiation
Source Stack
- Andreessen Horowitz "16 Startup Metrics": https://a16z.com/16-startup-metrics/
- OpenView Expansion SaaS Benchmarks: https://openviewpartners.com/expansion-saas-benchmarks/
- Bessemer "10 Laws of Cloud": https://www.bvp.com/atlas/10-laws-of-cloud
- First Round Review: https://review.firstround.com/
- Lenny\'s Newsletter benchmark archive: https://www.lennysnewsletter.com/
- HubSpot State of Sales Report: https://www.hubspot.com/state-of-marketing
Verified Financial Benchmarks (2024-2025)
| Metric | Verified figure | Source |
|---|---|---|
| Rule of 40 median (Series B+) | 34-42 | Bessemer |
| ARR per employee (Series B) | $130K-$190K | OpenView |
| ARR per employee (Series D+) | $230K-$320K | Bessemer |
| Top-quartile mid-market ARR growth | 45-65% YoY | Bessemer |
| Median runway at Series A | 22-28 months | Carta |
| Median founder dilution Series A | 18-22% | Carta |
| Median founder dilution through C | 52-62% total | Carta |
| PE-backed SaaS multiple at exit | 8-14x ARR | PitchBook |
| Median strategic acquisition (2024) | 6-9x ARR | 451 Research |
The Bear Case (Customer-Side Adoption Friction)
Three friction vectors:
- Budget reallocation in downturn — services/SaaS get aggressive cuts. 20-30% pipeline compression, 90-day cash buffer.
- Buying-committee expansion — Gartner: 6 → 11 stakeholders/decade. Each adds 30-45 days.
- Procurement-driven price compression — 20-40% discounts are closing condition, not opener.
Mitigation: ACV-expansion tiers, exec-sponsor motions, renewal escalators 5-7% annual.
See Also (related library entries)
Cross-references for adjacent operator topics drawn from the current 10/10 library set, ranked by tag overlap with this entry:
- q1915 — Is a HubSpot AE role still good for my career in 2027?
- q1727 — How does Datadog retain CRO talent in 2027?
- q1667 — How does ServiceNow retain CRO talent in 2027?
- q1644 — What is ServiceNow RevOps career path?
- q1598 — How does Snowflake compute pricing compare to BigQuery and Redshift?
- q1441 — How'd you fix COPC Inc's revenue issues in 2026?
Follow the q-ID links to read each in full.