The 5-Minute Customer Report
How fast B2B software companies actually respond to inbound — a mystery-shop study of 200+ vendors. The gap between five minutes and five hours is your conversion rate.
Resources
Everything I've learned about customer conversations across the funnel — reports, playbooks, audits, and a couple of interactive things. Pick a lens, search, or just browse.
The playbook
Showing 68 of 68 resources
How fast B2B software companies actually respond to inbound — a mystery-shop study of 200+ vendors. The gap between five minutes and five hours is your conversion rate.
Three inputs (inbound volume, current response time, conversion baseline), one output: the revenue your response time is costing you.
PLG activation medians, broken out by ACV band, ICP, and time-to-first-value. The number you're benchmarking against is probably wrong.
What 47 deflection programs revealed about the gap between reported deflection rate and post-deflection CSAT. The cost was paid downstream.
Three inputs (inbound volume, current response time, conversion baseline), one output: the revenue your response time is costing you.
How fast B2B software companies actually respond to inbound — a mystery-shop study of 200+ vendors. The gap between five minutes and five hours is your conversion rate.
PLG activation medians, broken out by ACV band, ICP, and time-to-first-value. The number you're benchmarking against is probably wrong.
Twelve questions that map your full-funnel conversation quality — response time, activation, deflection, NRR — and surface the weakest link.
What separates 130%+ NRR teams from the rest. The throughline isn't a playbook — it's whether expansion conversations actually happen in product or in QBRs.
What 47 deflection programs revealed about the gap between reported deflection rate and post-deflection CSAT. The cost was paid downstream.
Average SaaS lead-to-first-touch is 17 hours. The conversion curve cliff-edges at five minutes. The math doesn't survive contact with intent.
What the Lead Response Management Study found, why the field never internalised it, and how it became table stakes again.
Demo no-shows aren't a calendar bug — they're a cooling problem. The structural fix isn't better reminders; it's removing the gap entirely.
The calendar is a friction layer that loses more deals than it protects. The alternative is the same conversation, at the moment of intent.
The form that filters out tire-kickers also filters out the buyer who was three seconds from raising a hand. The cost of the gate is invisible — until you measure it.
Consumer expectations are reshaping B2B buying behaviour. The buyer who configures a car in 90 seconds tolerates the 17-hour B2B response time less every year.
The calendar widget the prospect sees is a filter. The calendar your AEs run their week off is a graveyard. Both can be improved together.
A different shape of the SDR job — where the cold-call queue is gone and the AE handoff is the whole motion. What the comp model would have to look like.
SDR attrition isn't a labour-market problem; it's a job-design problem. The role you advertise is not the role they show up to.
The product moves faster than the Loom you recorded. Static onboarding goes stale; live onboarding doesn't.
Most PLG companies hit an activation rate they can't move, no matter how many emails they add. The ceiling is structural — and there's a way through it.
The reframe that separates growth teams from signup teams. Activated customers compound; raw signups don't.
Most free-trial signups disappear before they ever reach value. Re-engagement emails don't bring them back — because they arrive after the moment of confusion has passed.
Inputs: monthly signups; signups reaching your defined value milestone within 30 days; (optional) business type for benchmark cut. Logic: compute D30…
Your product is great at showing things and bad at conversing about them. It can display a tooltip, highlight a button, or play a tour — but it can't…
The CS scaling problem is simple to state and hard to live with: customers grow, the work to activate and support them grows with them, and headcount…
Here's a question worth auditing honestly: what fraction of your CS team's time goes to expansion — the conversations that grow accounts and drive…
A help article's half-life is how long before it's meaningfully out of date — and for fast-moving software products, it's short. Every release…