This isn't just M&A. It's the "Blocker-Hunter" stack.
They are combining tools to find the friction (Fullstory), then fix the friction in real-time (Usetiful).
This isn't just M&A. It's the "Blocker-Hunter" stack.
They are combining tools to find the friction (Fullstory), then fix the friction in real-time (Usetiful).
It tells you what your survivors think.
It tells you nothing about the 91% who left.
It tells you what your survivors think.
It tells you nothing about the 91% who left.
This is the cost of an "Enabler-only" roadmap.
It's pure waste.
It's building features for the 9% of survivors, while the 91% churn.
This is the cost of an "Enabler-only" roadmap.
It's pure waste.
It's building features for the 9% of survivors, while the 91% churn.
The Blocker? Bot clicks and security scanners creating data noise.
The Fix? Filtering them out.
They are fixing the friction in their own measurement tools.
The Blocker? Bot clicks and security scanners creating data noise.
The Fix? Filtering them out.
They are fixing the friction in their own measurement tools.
Enabler Spend: An investment in NRR (keeping the 9% happy).
Blocker Spend: An investment in New ARR (fixing the leak to win the 91%).
Most teams are 100% focused on NRR, and have zero budget for New ARR.
Enabler Spend: An investment in NRR (keeping the 9% happy).
Blocker Spend: An investment in New ARR (fixing the leak to win the 91%).
Most teams are 100% focused on NRR, and have zero budget for New ARR.
This isn't a guess. It's a multiplier.
It's how you prove your product team isn't a cost center—they're your main growth engine.
Here’s how to calculate the ROI of their work. 🧵
This isn't a guess. It's a multiplier.
It's how you prove your product team isn't a cost center—they're your main growth engine.
Here’s how to calculate the ROI of their work. 🧵
Intercom & Braze are in an "AI arms race."
This isn't AI hype.
It's a massive bet on automating Blocker removal. The money is flowing to tools that can find and fix user friction, fast.
Intercom & Braze are in an "AI arms race."
This isn't AI hype.
It's a massive bet on automating Blocker removal. The money is flowing to tools that can find and fix user friction, fast.
Median SaaS growth slowed from 30% to 25% last year.
You can no longer hide a leaky funnel by pouring more VC money into the top.
Median SaaS growth slowed from 30% to 25% last year.
You can no longer hide a leaky funnel by pouring more VC money into the top.
A) New ARR
B) Net Revenue Retention (NRR)
C) Profitability / Margin
D) New Logo Count
A) New ARR
B) Net Revenue Retention (NRR)
C) Profitability / Margin
D) New Logo Count
(A feature that 1% of power users loved, but 99% of new users didn't need).
(A feature that 1% of power users loved, but 99% of new users didn't need).
Why? Weak Q4 guidance.
The market isn't rewarding "growth" anymore. It's punishing bloat and anything that smells like a leaky funnel.
Lean growth is the only thing that matters now.
Why? Weak Q4 guidance.
The market isn't rewarding "growth" anymore. It's punishing bloat and anything that smells like a leaky funnel.
Lean growth is the only thing that matters now.
This isn't a vague product metric.
It's a direct, measurable link between fixing friction and making money.
This isn't a vague product metric.
It's a direct, measurable link between fixing friction and making money.
- 50% on what fans loved (Enablers).
- 50% on what "fence-sitters" hated (Blockers).
The result?
The score jumped from 22% to 58%.
They built an engine to turn "meh" users into fans.
- 50% on what fans loved (Enablers).
- 50% on what "fence-sitters" hated (Blockers).
The result?
The score jumped from 22% to 58%.
They built an engine to turn "meh" users into fans.
Braze launched its Agent Console.
Customer.io has AI-driven segments.
The AI agent "arms race" is on.
This isn't about hype; it's about automating Blocker-removal at scale.
Braze launched its Agent Console.
Customer.io has AI-driven segments.
The AI agent "arms race" is on.
This isn't about hype; it's about automating Blocker-removal at scale.
(Mine: "Forcing me to book a demo just to see the product.")
(Mine: "Forcing me to book a demo just to see the product.")
Their Product-Market Fit (PMF) score was a dismal 22%. The benchmark for success is 40%.
Here's the 4-step engine they built to fix it—and jump to 58%. 🧵
Their Product-Market Fit (PMF) score was a dismal 22%. The benchmark for success is 40%.
Here's the 4-step engine they built to fix it—and jump to 58%. 🧵
Translation: A messy, disjointed user experience is now a death sentence.
Your product's Blockers are more visible to users than ever.
Translation: A messy, disjointed user experience is now a death sentence.
Your product's Blockers are more visible to users than ever.
Their first score was a dismal 22%.
The benchmark for success is 40%.
They were failing.
Their first score was a dismal 22%.
The benchmark for success is 40%.
They were failing.
The capital is flowing directly to this one problem.
If your customer engagement platform isn't building this, it's already a legacy tool.
The capital is flowing directly to this one problem.
If your customer engagement platform isn't building this, it's already a legacy tool.
10,000-person waitlist.
They let in 10 users a week.
Watched them get stuck.
Fixed the product.
Then let in the next 10.
They weren't testing features. They were hunting Blockers.
10,000-person waitlist.
They let in 10 users a week.
Watched them get stuck.
Fixed the product.
Then let in the next 10.
They weren't testing features. They were hunting Blockers.
A) We use the "40% Very Disappointed" test
B) We track NPS / CSAT
C) We just look at retention/revenue
D) We... don't.
A) We use the "40% Very Disappointed" test
B) We track NPS / CSAT
C) We just look at retention/revenue
D) We... don't.
That's $15.6M per employee.
This isn't magic. It's not a "feature-first" strategy. It's a "Blocker-first" strategy.
That's $15.6M per employee.
This isn't magic. It's not a "feature-first" strategy. It's a "Blocker-first" strategy.
Why? Control.
Self-hosting, custom code, and "Human in the Loop" modules.
It's not just automation, it's orchestration. A key difference for building real systems.
Why? Control.
Self-hosting, custom code, and "Human in the Loop" modules.
It's not just automation, it's orchestration. A key difference for building real systems.
A) Building new features (Enablers)
B) Fixing friction (Blockers)
A) Building new features (Enablers)
B) Fixing friction (Blockers)
Start obsessing over your unhappy *non-users*.
Find the friction, gaps, and frustrations that stop them from converting.
Find their Blockers.
Start obsessing over your unhappy *non-users*.
Find the friction, gaps, and frustrations that stop them from converting.
Find their Blockers.