Average discount at 22% is well above the 10% benchmark, yet win rate sits at just 19%. The problem isn't price - it's perceived value. Prospects don't see enough differentiation to justify the ask, so your team discounts to compensate. But discounts don't fix positioning. They just erode margins while the real problem festers.
System leak / year
€5.8M
Modelled, if unaddressed
Upside / year
€2.3M
If correctly addressed
Engine confidence
39%
Ranking score, sector-weighted
GRIP score
56
0 to 100
Day 14
H1 confirmed or killed against the 14-day test on page 09.
Day 30
€2.3M confirmed or killed: page 10 watch numbers must move.
The rest of this document defends that sentence with four kinds of evidence: cohort percentiles, the company's own intake values, named peer cases where the public record clears our bar, and the conditions under which the engine would rule it out.
13 sections · ~14 min read
02
Bookmark
If you only read this page
Diagnosis, the proof we read it from, the first move.
€5,834,700 of modelled system leak per year if unaddressed.
Pillar model on your four GRIP scores (formula on page 03). Of that, €2.3M is treated as recoverable within 90 days: the bound every leverage figure in this report respects.
Why this hypothesis, not the other ones
3 hypotheses were scored and 11 contradiction rules tested against your 31 answers. The field is close: the ranking below is the engine's best call, and the 14-day test on page 09 decides it:
Positioning eroded, discounts compensate
39%
Acquisition masks a retention leak
03
Deep dive
Why this is the leading hypothesis
Sector weight, confidence math, and what it costs you per year.
Top hypothesis · rank 1confidence 39%
Positioning eroded, discounts compensate
22% discounts AND 19% win rate: prospects don't see enough differentiation.
Win rate sits at p25 (19%), against cohort median of 25%.
The confidence math
Raw severity
38 / 100
Pattern strength before sector weighting
Sector weight
× 0.95
Vertical-specific tuning for SAAS
Sector answers (Q16-31)
0
Your Q16-31 answers against the cohort median, summed for this pattern's GRIP dimension, capped at ±8 points
04
Cohort
Your numbers against the peer cohort
Eight metrics, percentile placement, and the gap to median.
Win rate
19% · p25
p10 14%p50 25%p90 39%
-6.0%
vs median
Net revenue retention
96% · p19
05
Pattern
Named companies that ran your pattern
Named companies, public sources, every claim checkable.
Every peer case is a named company tied to a public, on-the-record source. Where the company stated it themselves we quote them; otherwise we state the finding and cite where it sits on the record. Nothing is invented. For this pattern we have not yet cleared three to that bar, so we show none here rather than fabricate.
06
Landscape
The full GRIP pillar landscape
Where the binding pillar sits relative to the other three.
Alternative hypothesis · rank 2confidence 31%
Acquisition masks a retention leak
€45.0M ARR with NRR 96%: new logos hide retention drag.
Two peer cases that ran this pattern
SlackPre-IPO (filed Apr 2019, USD ~400M ARR)
What the public record showsSlack's Net Dollar Retention Rate was 143% as of January 31, 2019, as disclosed in their S-1 filing. This metric was highlighted in the prospectus, with Slack noting that their Net Dollar Retention Rate is a reflection of the rapid pace of adoption that often occurs as usage spreads within and across teams.
07
Conditions
When this answer changes
The conditions under which the engine over- and under-fires this pattern.
Alternative hypothesis · rank 3confidence 29%
Systemic GTM misalignment
Multiple metrics below benchmark: a structural GTM problem.
Buyer-specific leverage math
Gap model: your 19 against a cohort median of 25, a gap of 24% of the median, × 35% recovery = 8.4% of ARR; 8.4% × ARR €45,000,000 = €3,780,000 per year
If correct, recoverable upside ≈ €2,333,880 per year · median time to confirm or kill: 90 days.
One peer case that ran this pattern
SegmentSeries A pivot (6 months runway left)
Twilio acquired CDP Segment for a $3.2 billion price tag in October 2020, and Segment became a division of Twilio with Peter Reinhardt continuing as Segment CEO. A little more than eight years before the Twilio acquisition, Segment almost died an early death when it seemed to be out of money and ideas.
08
AI Answer Market
Who owns the AI answer in your market
What the AI engines tell buyers who ask for your category: and where you stand.
Buyers increasingly open their shortlist by asking an AI engine. We put 15 buyer questions for your category to 1 engines and recorded who gets named. Only questions that do not contain your name are scored: an engine that is asked about you will always name you, and that would hand any company a share of voice it has not earned.
Your category · Revenue operations platformChatGPT
You are barely present in the AI answers. Clari holds the ground when a buyer asks for Revenue operations platform.
Visibility
20/100
Share of voice
7%
Verdict
Low presence
Avg. rank when named
4.0
Share of voice in the AI answers
How often each player is named across all 15 answers. You are in amber.
09
Action
The next 14 days
Three phases, with owners, success metrics, and the failure mode to avoid.
Your numbers in this constraint
Metric
You
Cohort p25
Cohort p50
Cohort p75
Your p
Average discount (lower better)
22%
8%
10%
16%
p15
Win rate
19%
19%
25%
31%
p25
10
Verify
The 30-day verification plan
The number that tells you the diagnosis was right or wrong.
By the end of day 30, success looks like
3+ of 5 won deals where discount talk precedes price quote confirms positioning, not pricing, is the constraint.
Your specific watch numbers
Average discount
22%
p15 · cohort p50 10%
Win rate
19%
p25 · cohort p50 25%
Day-30 math: Gap model: your 22 against a cohort median of 10, a gap of 100% of the median, × 50% recovery = 50% of ARR, capped at 25%; 25% × ARR €45,000,000 = €11,250,000 per year, bounded by the €4,578,525 the system can recover
If by day 30 the confirm-rule has not cleared, the diagnosis was wrong. Escalate to the full Report rather than doubling down on the wrong fix.
The five KPIs that tell you whether it worked
11
Execute
The 90-day execution sequence
Three phases with explicit go / no-go gates.
01
Day 1 to 30
Phase 1: Diagnose and first test
22% discounts AND 19% win rate: prospects don't see enough differentiation.
Go / no-go gate. Baseline locked. First hypothesis test live in production motion. Confirm-rule on page 10 either cleared or definitively failed.
Cumulative if confirmed
€2.3M
per year
02
Day 31 to 60
Phase 2: Iterate to a winning variant
Run the second iteration of the experiment. Hold every other lever constant. The variant either beats baseline by 1.5x or it does not: there is no other reading.
Variant beats baseline by 1.5x on the headline KPI from page 10. Failure here means the binding constraint was misdiagnosed; escalate to the Report.
12
Negative
Every pattern the engine tested
The ones it retained and the ones it ruled out are all part of the answer.
Trust is built as much by the patterns the engine ruled out as by the one it surfaced. The table below is every contradiction rule the engine tested against your intake, the trigger threshold for each, and whether it cleared.
Rule
Pillar
Your value
Trigger threshold
Verdict
Pipeline full but win rate weak
I
4.6x · win 19%
pipe ≥ 3.5x AND win < 21%
fired · suppressed
NRR low but churn low (no expansion)
R
96% NRR · 12% churn
13
Next
What to do with this
Run it yourself, prove it deeper, or have an operator run it with you.
Pulse (today)
Free
31 intake questions, vertical-aware
1 leading hypothesis, sector-weighted ranking
5 cohort metrics + 3 vertical extras
Up to 3 named peer cases, each tied to a public source
14-day action with confirm-rule
Delivered in under 1 hour
Report (upgrade)
€750
the full 12-pillar diagnostic (8.5× deeper)
Full GRIP per-pillar diagnostic, all four pillars
15 cohort metrics with provenance + audit trail
10 peer cases with full source verification
31%
Systemic GTM misalignment
29%
The rule that fired: your 22% · win 19% crossed the trigger discount > 13% AND win < 23%, and no competing pattern did.
What would change the answer: a rival pattern fires at NRR < 100% AND churn ≤ 8%; you are at 96% NRR · 12% churn, so it stayed dormant.
€2.3M of identified leverage: 5% of your €45M ARR.
Each step adds the next hypothesis's leverage to the prior cumulative. Today's ARR is anchored on the left; the rightmost bar is your reachable ceiling if all the retained hypotheses confirm.
Each leverage figure is buyer-anchored: cohort gap × your ARR × recovery factor, capped by hypothesis confidence. Independent fixes: the engine does not double-count. If H1 and H2 partially overlap (e.g. same metric), the cumulative is an upper bound rather than a forecast. The three figures are bounded in sequence by the €2.3M the system can recover (page 03): unbounded they would sum to €6.1M, which would count the same revenue twice.
The proof
01Win rate at p25 (19%) is well below cohort median.
02Net revenue retention at p19 (96%) is well below cohort median.
03Annual churn at p30 (12%) is well below cohort median.
04Average discount at p15 (22%) is well below cohort median.
05GRIP G (Guidance) at 49/100 is in the constrained band.
The first move
In Gong or Chorus, pull 5 won-deal call recordings from the last 60 days. Search the transcripts for 'discount', 'budget', 'price' and timestamp the first mention.
Softmax over weighted severity against the alternative patterns, capped at 85%. A ranking score, not a probability.
Median time to fix
90 days
Planning assumption per GRIP dimension (60 to 120 days), not a measured cohort
Leverage if correct
€2,333,880
Gap model: your 22 against a cohort median of 10, a gap of 100% of the median, × 50% recovery = 50% of ARR, capped at 25%; 25% × ARR €45,000,000 = €11,250,000 per year, bounded by the €4,578,525 the system can recover
Domain note · Only 1 peer case (Wistia 2017, kept under win-high-disc-high) is S-1-grade clean. Slightly downweight 0.95 because the pattern is real but the case library is thin and the diagnosis often overlaps with win-low-disc-low (positioning failure is the deeper cause). Consider running disc-high-win-low and win-low-disc-low as a coupled hypothesis pair.
Your numbers in this constraint
Metric
You
Cohort p25
Cohort p50
Cohort p75
Your p
Average discount (lower better)
22%
8%
10%
16%
p15
Win rate
19%
19%
25%
31%
p25
These are the inputs the binding-constraint rule fires on. Move the bottom one toward the cohort median and the leverage math on page 03 turns from theoretical to your audit.
This answer flips when…
Engine over-fires when
Series A SaaS with low ACV (under ~$5K) often shows high discount rates because of monthly-billing experimentation, not a value-perception failure. Below ~$10K ACV, read this signal cautiously: the discounting is usually pricing experimentation rather than a positioning problem.
Engine under-fires when
When your headline discount rate looks normal but the team is giving away free months or extending trials, the value-perception problem hides behind the published number. Those non-monetary concessions will not show up in discount rate: tally them separately to see the true giveaway.
What it costs you per year (modelled)
Guidance
€1.1M
Score 49/100 · weight 20% · realisation 40%
Resources
€1M
Score 58/100 · weight 20% · realisation 45%
Implementation
€1.1M
Score 67/100 · weight 25% · realisation 50%
Performance
€2.6M
Score 50/100 · weight 35% · realisation 55%
One formula, per GRIP dimension: ARR × 0.60 × dimension weight × (100 − score) / 100 × realisation. The four legs sum to the €5.8M system leak per year. Of that, €2.3M is treated as recoverable within 90 days (a flat 40% recovery, the same rate the full Report applies): the bound every leverage figure in this report respects.
Why we think it is this
Win rate at p25 (19%) is well below cohort median.
Net revenue retention at p19 (96%) is well below cohort median.
Annual churn at p30 (12%) is well below cohort median.
Average discount at p15 (22%) is well below cohort median.
What would have changed our mind
Pipeline coverage at p76 (4.6x) sits above cohort median.
p10 90%p50 110%p90 138%
-14.0%
vs median
Annual churn
12% · p30
p10 3%p50 8%p90 19%
+4.0%
vs median
Pipeline coverage
4.6x · p76
p10 2xp50 3.5xp90 6x
+1.1x
vs median
Average discount
22% · p15
p10 4%p50 10%p90 25%
+12.0%
vs median
What is your median sales cycle in days, from first qualified opportunity to closed-won?
78 days · p57
p10 0 daysp50 90 daysp90 270 days
-12.0 days
vs median
How many months does it take to recover the cost of acquiring a new customer (CAC payback)?
21 months · p33
p10 3 monthsp50 15 monthsp90 33 months
+6.0 months
vs median
What % of your AE team hit quota last fiscal year?
58% · p47
p10 30%p50 60%p90 90%
-2.0%
vs median
If you closed every gap to median
+€2,333,880 per year
Engine-estimated upside from probability-weighted recovery of leakage across all four GRIP pillars, not just the binding one.
Source: Bessemer State of the Cloud 2024 · OpenView 2024 SaaS Benchmarks.
What happened. Slack was growing top-line aggressively via bottom-up team adoption, but in the S-1 disclosed that 575 enterprise accounts (>USD 100K ARR) accounted for ~40% of total revenue, signaling the SMB long tail was carrying high churn risk against concentrated enterprise expansion.
What they did. Slack doubled down on enterprise expansion via the Enterprise Grid tier, added cross-team channels and admin controls, and tracked Net Dollar Retention on the cohort that mattered: seat-growing enterprises.
Outcome. Slack's Net Dollar Retention Rate was 143% as of January 31, 2019, indicating existing customer cohorts paid more each year than the prior even after losses.
What the public record showsTwilio's Dollar-Based Net Expansion Rate was 155% for the year ended December 31, 2015 and 167% for the six months ended June 30, 2016, according to their S-1 registration statement.
What happened. Twilio's usage-based pricing meant new customers landed small (often with a single SMS or voice use case) but the success of the business depended on those accounts ramping consumption over time. The risk: customers who never expanded would create a leaky bucket masked by new logo growth.
What they did. Twilio invested in developer relations, hired solutions engineers to drive consumption growth inside accounts, and released new products (Voice, Video, Authy) to widen the surface area inside each customer.
Outcome. Dollar-Based Net Expansion Rate was 155% for FY 2015 and 167% for the first half of 2016, disclosed in the S-1.
What happened. Segment's original product was a class-attendance app called Classmetric, with negligible traction. With six months of runway left, founders Peter Reinhardt and team realized none of the surface metrics could be fixed inside the current product. The constraint was strategic: wrong product, wrong customer.
What they did. The team had built an internal analytics tool to integrate with multiple tracking services. They open-sourced it as analytics.js. Within days, demand from external developers proved an entirely different ICP existed. They pivoted Segment to a customer data platform built on that integration layer.
Outcome. Segment reached USD 1.5B unicorn valuation by 2019 and was acquired by Twilio in November 2020 for USD 3.2B.
Clari leads the answer at 27%, 20 points ahead of you. Gong, Aviso sit behind.
CompetitorShare of voiceRankvs you
Clari27%1.3+20
Gong20%1.7+13
Aviso13%2.0+7
BoostUp13%2.5+7
Who takes the AI answer instead of you
Ranked by how many of your buyer questions each rival wins when the AI leaves you out. This is who to displace first.
CompetitorAnswers takenContested
Clari31
Gong30
Aviso20
BoostUp20
Where the answer goes to a competitor
Buyer questions where rivals are named and you are not: the AI is shortlisting your competitors to your buyer.
Best revenue operations platforms for B2B SaaS
named instead: Clari, Gong, Aviso
Which tools improve sales forecast accuracy for a Series B SaaS company
named instead: Clari, Gong
Software for pipeline inspection and deal reviews
named instead: Clari, BoostUp
How do I detect at-risk deals in my CRM pipeline
named instead: Gong, BoostUp
Alternatives to spreadsheets for revenue forecasting
named instead: Aviso, Salesforce Einstein
This is a one-time snapshot. The AI answer market moves every week as the engines re-read the web. The GRIP OS tracks your position continuously and alerts you when a competitor takes your place.
These are the inputs the binding-constraint rule fires on. Move the bottom one toward the cohort median and the leverage math on page 03 turns from theoretical to your audit.
01
Day 1 to 3
Owner
CEO + CRO
What ships
In Gong or Chorus, pull 5 won-deal call recordings from the last 60 days. Search the transcripts for 'discount', 'budget', 'price' and timestamp the first mention.
Your numbers on this step5 won-deal threads is enough: at your €52K ACV those 5 deals carry about €260K of closed ARR you can read a pattern from.
Success metric
Baseline locked. Source attribution captured for every open opportunity.
Do not
Do not skip the baseline. You will not be able to read the result without it.
02
Day 4 to 7
Owner
CRO
What ships
If the discount conversation starts before pricing has been quoted in 3+ of the 5 calls, you have a positioning failure, not a price failure.
Your numbers on this stepYour average discount 22% vs cohort p50 10%. Read the 5 threads for the trigger: rep discipline, deal-desk policy, or competitive pressure.
Success metric
Hypothesis test framed in one sentence and shipped in production motion.
Do not
Do not test two changes in the same week. You will not know which moved the number.
03
Day 8 to 14
Owner
CRO + Head of Sales
What ships
Block 90 minutes this week to rewrite the first slide of the discovery deck and the first 90 seconds of the demo around the buyer's pain in their own words. Test on the next 5 calls.
Your numbers on this stepH1 leverage, bounded by what the system can recover: €2.3M/year. The rewrite is cheap (2 hours or less); the test is the next 10 first meetings.
Success metric
Go / no-go decision documented with the number, not the feeling.
Do not
Do not announce results before the confirm-rule on page 10 is met.
Estimated time
2 hours
Tools needed
Gong, Salesforce
Hypothesis
#1 · 39%
Confirm rule. 3+ of 5 won deals where discount talk precedes price quote confirms positioning, not pricing, is the constraint.
Metric
Your value
Predicted day 30
Target by day 30
Signal you watch for
Win rate
19%
21% (≈30% of gap)
25% (close gap to p50)
Currently p25; move toward p50
Net revenue retention
96%
100% (≈30% of gap)
110% (close gap to p50)
Currently p19; move toward p50
Annual churn
12%
11% (≈30% of gap)
8% (close gap to p50)
Currently p30; move toward p50
Experiment activation
0 / 1
1 / 1 if owner ships
1 / 1 by day 7
The 14-day action ships fully
Board confidence
baseline
7+ if KPIs hold
7+ at day 30
0-10 self-score from CEO + CRO
Predicted column assumes that 30% of the gap to the cohort p50 closes within 30 days. That is a planning assumption, not a calibrated forecast: the engine's expected value if H1 confirms; reality varies with execution speed.
The decision tree at day 30
If the confirm-rule cleared
Continue execution at the same cadence. Re-baseline at day 60. Move budget toward scale, not toward new diagnostics.
If it did not clear
Escalate. The full GTM Intelligence Report (€750) widens the diagnostic surface from 31 questions to the full 12-pillar assessment and re-ranks the pattern field.
Go / no-go gate.
Cumulative if confirmed
€2.3M
per year
03
Day 61 to 90
Phase 3: Scale the winning variant into the operating model
The variant moves from experiment to default. Tooling and onboarding update to reflect the new motion. Board memo at day 90 documents the move with the number, not the narrative.
Go / no-go gate. Variant established as the new baseline. Re-baseline cohort metrics at day 90. Re-run the Pulse intake to verify the binding pillar has moved.
48 deals/quarter at €52K ACV only accounts for €10.0M/year of your €45.0M ARR. Either your base is mostly legacy, or deal volume is underreported.
Cross-vertical hygiene
The cohort, the peer cases, and the action templates were drawn exclusively from the SAAS anchor library, never borrowed from another sector. Sophie (the Caugia LLM) is not in the critical path of this render: same intake always produces the same Pulse.
90-day execution sequence with milestone gates
Board-level report, ~45 pages, 1 hour turnaround
Have it run with you
The 14-day plan above is yours to run. If you would rather not run it alone: Tom Meijer, Caugia’s founder and an ex-GTM executive, takes the constraint on as a fractional operator: one to two days a week, two slots, progress reviewed weekly on your live GRIP score. The Report fee is credited in full.
The Report picks up where the Pulse stops: the full 12-pillar diagnostic, at the founding price. The Report fee is credited in full against an Execute engagement.
The Pulse is a first diagnostic read, not the full diagnosis. If the 30-day confirm-rule did not clear, the Report is the right next step. If it did clear, the Report is the right next step sixty days later, for the next constraint.
