FUNNEL DIAGNOSTIC · 48-HOUR READ

Jake McMahon · ProductQuant

8+ years B2B SaaS · Behavioural Psychology + Big Data (Masters)

We score your funnel on 5 breaklines and name the worst one.

A 48-hour read of your activation, retention and revenue funnel. Five breaklines graded RED, AMBER or GREEN against your own data. The worst red becomes the headline. Thirteen sections and ten ranked fixes, for a flat $500.

Book the Read → See what’s included ↓

Delivered in 48 hours with all 13 sections present, or full refund and you keep the draft.

WHAT GETS SCORED

Activation Truth Whether your activation metric actually predicts retention, graded from your data rather than a template

Time-to-Value How long it takes a new user to reach real value, measured instead of assumed

Top fixes 10 fixes ranked by what they are worth, each tagged with the team that owns it

Event Reality Whether your events capture the actions that move revenue, or just the easy ones

Fixed price · 48-hour read

We tell you exactly what breaks between signup and paid.

One report. Five graded breaklines. Ten ranked fixes. The worst one is named as the headline, so your team knows what to fix first and in what order.

ACTIVATION

"Why did activation drop last month?"

We find the moment users stall before they reach value, and size what the stall costs you. Graded against your own data, not a best-practice checklist.

MONETISATION

Our trial-to-paid number is basically a guess.

We trace it to the exact event gap, then either give you the number or specify the export that produces it.

RETENTION

"Which retention signals actually matter?"

We grade each one and cut the ones that predict nothing, so you keep the handful of signals that move revenue.

PRODUCT TEAM

Nobody can prove the new feature is being used.

We find the missing events and name the exact properties to add, in a form your engineers can implement without a follow-up call.

YOU CAN’T STATE ACTIVATION WITH CONFIDENCE

Three people, three definitions of activated

“Ask three people what an activated user is and you get three answers. Ask for the number and the subject changes. We have been shipping against a definition nobody agreed on, and every roadmap decision rests on it.”

VP Product · B2B SaaS, $8M ARR

We instrumented what was easy, not what matters

“We track button clicks and page views. But the questions that actually drive decisions, which features correlate with retention and which moments predict expansion, we cannot answer. The events are there. The answers are not.”

Head of Product · Series B

“Fix activation” has been on the backlog for two quarters

“Every retro ends the same way: we should fix our activation definition. Then nobody knows where to start, because nobody agrees what the funnel is supposed to do. So it slides another quarter.”

Product Manager · B2B SaaS

Dashboards exist, but nobody opens them

“We built 12 dashboards last year and the view count tells the story. The numbers do not match what customer success sees, so nobody trusts them enough to make a call. Decisions run on opinion instead.”

CEO · $5M ARR

WHAT THE READ TYPICALLY FINDS

Most funnels break in the same five places.

The break is rarely the one people expect. It is usually a definition nobody agreed on, or a first-value moment that arrives too late to change the outcome.

In a typical read, one or two breaklines come back RED and carry most of the cost. The rest are AMBER. Grading all five is how you find which red is expensive and which is merely untidy.

The activation metric does not predict retention

Teams define activation around a feature milestone, then discover that users who reach it churn at the same rate as users who do not. The number looks healthy and tells you nothing.

Events fire, but not for the actions that matter

Tracking exists and is unreliable in a specific way. The actions tied to revenue have no coverage, while the easy-to-capture clicks are duplicated and named three different things.

Revenue capture is invisible from inside the product

Without billing data joined to product events, nobody can say which behaviours precede an upgrade. The answer usually exists. It sits on the other side of a system boundary.

WHY AN EXTERNAL READ

Your team built this funnel. They cannot read it cold.

The people who instrumented your product made reasonable decisions at the time. Those decisions accumulated into a funnel definition that reflects engineering convenience as much as it reflects your business.

An outside read asks the uncomfortable question first: is the number everyone quotes actually measuring what the business thinks it measures? That question is very hard to ask from inside the team that built it.

TIMELINE

Forty-eight hours from complete access to a graded read.

HOURS 0-4

Access and Framing

Read-only access to your analytics, your billing data and your current funnel definition. We confirm in writing that the clock has started. No write access, no code changes, no access to user records.

→

HOURS 4-18

Scoring

All five breaklines graded RED, AMBER or GREEN against your own data. Every grade carries the query or export behind it, so you can check the working rather than take our word for it.

→

HOURS 18-30

Traces

The 2 cross-cutting lenses, Buyer-User Split and Usage Topology, annotate the grades rather than being graded themselves

→

HOURS 30-48

Ranking + Delivery

Ten fixes ranked by what they are worth, not by how easy they are, each with the team that owns it named. 30-minute walkthrough call. Recorded, so your team can refer back without booking another meeting.

Hour 48: the report lands, or we have refunded you and you keep the draft.

WHAT YOU GET

13 sections that turn a vague funnel worry into a ranked fix list.

Hours 0-4 · Access

Access and framing across 5 breaklines

Three items, all read-only: analytics access, billing data, and your current funnel definition. We confirm in writing that the clock has started within one business day of receiving them.

Data tier established before grading begins, so you know what a read can and cannot support
Event Reality checked first, because it decides how far the other four grades can be trusted
5 breaklines recorded exactly as your team states them
5 billing and trial-to-paid access verified, or the gap named explicitly

Hours 4-18 · Scoring

Every breakline graded against your data, 5 queries behind the grades

Each breakline is scored against your own data and carries the query that produced the grade. Nothing is scored from a template, and nothing is scored from what other companies usually look like.

All five breaklines graded, each with the query behind it
Every grade carries 5 queries you can check behind the grades
Activation Truth tested against retention rather than against a milestone
Time-to-Value measured from signup to first real value, not to first login

Hours 18-30 · Traces

The two cross-cutting lenses

Buyer-User Split and Usage Topology explain why a red is red, which is usually the difference between a measurement problem and a product problem.

2 lenses applied as annotation, never graded separately
Buyer-User Split applied wherever the person who pays is not the person who uses
Usage Topology mapped, so you can see which behaviours sit on the path to value
Event Reality findings listed with the exact event or property that is missing

Hours 30-42 · Ranking

Ten fixes, ranked and owner-tagged

Each fix is documented with enough detail that a founder, a growth lead or an engineer can pick it up without another call. The ranking is by what the fix is worth, not by how quickly it can be done.

Ten fixes ranked by value, each tagged (ACT), (RET) or (MON)
The exact event names and properties to add, where events are the problem
The precise export or join to produce, where billing data is the problem
One prescribed next step, named plainly, with the reason it comes first

Hours 42-48 · Delivery

13-Section Report + Recorded Walkthrough

Every major finding is walked through live, the priority decisions are written down, and the recording is structured so your team can work from it without you in the room. Clarification is included for 7 days after delivery.

All 13 sections present, with the five grades and the ranked fixes
A 30-minute recorded walkthrough with the priority discussion captured in writing
A re-read offer after your fixes land, so you can watch the grades move
Everything above for $500, with no hourly billing or scope creep

On the cost of bad data: every product decision made without a trustworthy activation number is a coin flip dressed up as strategy. If your team is shipping against a metric nobody has tested, this is the cheapest way to find out.

FIT CHECK

Your product has users. Nobody can state your activation number with confidence. Here is how to tell if this read is the right move.

GOOD FIT

Self-serve or freemium B2B SaaS, seed to Series B

PostHog, Amplitude, Mixpanel or similar already running

The situation

You instrumented months ago and have been adding events since. Dashboards exist and nobody trusts them. Three people give three different numbers for activated users, and trial-to-paid is either unknown or disputed.

What you leave with

All five breaklines graded against your own data
The 10 fixes ranked by what they are worth, each tagged with the team that owns it
One prescribed next step, so nobody has to decide what to do first

A corrected activation number your team can defend in the next planning meeting.

NOT A FIT

Pre-product, no analytics tool, or data is not the bottleneck

Wrong stage or wrong problem

When this read does not apply

If you have not set up an analytics tool yet, there is nothing to read. If the events are sparse enough that no funnel can be drawn, the read becomes an instrumentation scope instead, and we tell you that before you pay.

Better starting points

Activation Deep Dive

If a red grade needs the build done rather than specified.

Focused Sprint

If your analytics are solid and you need one specific question answered.

The Foundation

Full growth work across every layer, where analytics is one piece rather than the whole job.

What this read does not cover

The diagnostic delivers the grades, the ranked list and the prescribed next step. Your team does the implementation. If you want the build itself, that is the next step the report names.

Implementing the fixes, which your team does or we do as a separately scoped build
Building dashboards from scratch, which the ranked list specifies but does not construct
Ongoing analytics management, which is the monthly engine rather than the 48-hour read

For the full growth diagnostic → The Foundation

Jake McMahon · ProductQuant

Jake McMahon

8+ years building retention, activation, and growth programs inside B2B SaaS · Behavioural Psychology + Big Data (Masters)

I run this read myself. Not a team of analysts, and not an automated report generator. Every breakline is graded by hand against your data, and every grade carries the query behind it so you can check the working.

Most audits hand you a list of things that are broken. This one hands you five grades and a ranked list, with the worst red named as the headline and the first fix prescribed. Your founder sees the number. Your growth lead sees the ranking. Your engineer sees the exact properties to add.

I won’t do this:

Grade your funnel from a template without reading your data
Flag a red without naming what it costs you
Recommend a fix without specifying the event, the property or the export
Pretend PostHog, Amplitude and Mixpanel fail in the same ways, because they do not

Which analytics platforms can you read?

Amplitude, Mixpanel, PostHog, Segment, GA4, Heap and custom-built stacks. Read-only access is all that is needed. The process is the same on every platform. What changes is which platform-specific gaps we look for first.

Teams Jake has worked with

PRICING

One price. A graded funnel and a ranked fix list, 48 hours after access.

$500

one-time · fixed price

48-hour read

All five breaklines graded, with the query behind every grade
Ten fixes ranked by value, each tagged (ACT), (RET) or (MON)
The two cross-cutting lenses · 2 lenses applied as annotation: Buyer-User Split and Usage Topology
One prescribed next step, named plainly with its reason
30-minute recorded walkthrough call
All assets formatted for your founder, PM, and engineer
Everything stays with your team permanently

Delivered in 48 hours with all 5 13 sections, or full refund and you keep the draft.

Book a 30-minute call →

Delivered in 48 hours from complete access with all 13 sections present, or full refund and you keep the draft. We confirm the clock start in writing, and the refund is automatic if we miss it. If your data cannot support a graded read, we tell you before you pay and scope what is possible instead.

Questions.

Or book a call →

Which analytics platforms can you read? +

Amplitude, Mixpanel, PostHog, Segment, GA4, Heap and custom-built stacks. Read-only access is all we need. The process is identical regardless of platform, and a custom stack typically surfaces more gaps than a managed one.

Do we need to give you admin access? +

No. Read-only is sufficient for the whole read. We specify exactly what we need at kickoff, which is normally a guest login or a read-only API key.

What if our events are a mess? +

That is usually why people come. If the events are sparse enough that a funnel cannot be drawn, the read becomes an instrumentation scope, and we tell you before you pay rather than after.

What do we own at the end? +

Everything. All 13 sections, the five grades with their queries, the ten ranked fixes, the lenses, and the walkthrough recording. All of it stays with your team permanently.

What happens after the read? +

You get ten ranked fixes and one prescribed next step. If your team has capacity, they implement it. If you want the build done for you, the report names the next step, and the $500 is credited against it within 30 days.

What is the guarantee? +

Delivered in 48 hours from complete access with all 13 sections present, or full refund and you keep the draft. Complete access, delivered and section present all have written definitions, so neither side has to argue about whether it was met.