What's the ideal POC timeline and success criteria to avoid feature requests disguised as trials?
Answer
POCs should run 2–4 weeks (30–45 days max) with 3 pre-defined success metrics signed off before day 1. OpenView data shows POCs extending past 45 days see 60% higher abandonment. SaaStr consensus: If you can't measure it in that window, it's not a POC—it's a multi-month pilot (different animal, different pricing).
Pre-Launch Checklist
| Item | Owner | Why |
|---|---|---|
| Success metrics (3 KPIs) | AE + Customer | Prevents "we'll see what happens" |
| Data migration scope | SE + CTO | Realistic; avoids "wait, can you do X?" |
| Kickoff date & team roster | Account Exec | Named sponsor on customer side |
| Rollback / exit plan | Legal + Support | Clear if POC flops |
| Weekly sync rhythm | SE | Track metrics; unblock fast |
Sample Success Metrics
Example: HR Tech Platform
- Metric 1: Import 100% of employee records without manual intervention (data quality).
- Metric 2: Run payroll cycle 3x with zero discrepancies vs. legacy system (accuracy).
- Metric 3: All 5 department leads can generate a headcount report in <5 min (adoption).
All 3 must hit by day 35. If 2 of 3 hit, you have a decision point: extend 14 days (cost to you) or move to contract.
Red Flags
- "Can you add field-level permissions for HR?" → This is a feature request, not POC validation.
- "We need to test with our full team (200 users)." → You're now a pilot; renegotiate SLA and contract scope.
- Sponsor goes radio silent week 2. → You have 10 days before POC dies. Force a sync.
TAGS: POC_management,timeline,success_metrics,SaaStr,OpenView,deal_risk
Anchor Citations
- CB Insights State of Venture / Sales Tech: https://www.cbinsights.com/research/
- Bessemer Cloud Index + State of the Cloud: https://www.bvp.com/atlas/state-of-the-cloud
- Crunchbase News (funding + M&A): https://news.crunchbase.com/
- SaaS Capital industry survey + valuation: https://www.saas-capital.com/research/
- PitchBook venture + private markets: https://pitchbook.com/news
- a16z Marketplace / SaaS frameworks: https://a16z.com/category/saas/
Operator Benchmarks (2025 Data)
| Metric | Verified figure | Source |
|---|---|---|
| Median SDR fully-loaded cost | $95K-$130K/yr | Pavilion + BLS |
| Median outbound SDR meetings/mo | 8-14 | Bridge Group 2025 |
| Median LinkedIn InMail response | 8-14% | LinkedIn Sales |
| Median cold email reply (warm list) | 6-11% | Outreach/Apollo |
| Median demo-to-close (mid-market) | 24-32% | OpenView |
| Median deal cycle ($25-100K ACV) | 45-90 days | Bridge Group |
| Median pipeline-to-quota coverage | 3.5-4.5x | Pavilion |
| Median CAC inbound-led SaaS | $8K-$15K | OpenView PLG |
| Median CAC outbound-led SaaS | $22K-$45K | Bridge + OpenView |
The Bear Case (Operational Concentration)
Three concentration risks:
- Customer concentration — any single >20% of revenue is asymmetric.
- Channel concentration — 60%+ from one channel is existential.
- Geographic concentration — NA-centric exposed to NA macro/regulatory.
Mitigation: customer top-1 < 20%, channel top-1 < 40%, geography top-region < 70%.
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:
- q1150 — How do you coach a brand-new manager who was promoted from top IC last quarter and is still trying to close their old deals?
- q1103 — What's the best discovery question to ask when a buyer says they're "just exploring" with no clear timeline?
- q730 — How do you design a capacity model that accounts for rep tenure, training ramp, and territory variance?
- q687 — What content should marketing create to help sales close specific deal types, and how do we avoid shipping content sales never reads?
- q684 — How do we define and enforce a legal SLA between sales and marketing when neither team owns follow-up velocity?
- q261 — How do you structure win-back outreach for prospects who went silent after demo (60-90 days dark)?
Follow the q-ID links to read each in full.