Do I need to complete the Audit before a Sprint?

Strongly recommended. A sprint scoped without friction data cannot be guaranteed. If you have existing drop-off data, we'll review it before scoping — the guarantee requires a baseline metric agreed upfront.

Who implements the redesign?

Your engineering team implements. We deliver Figma files with full component annotations, a developer handoff package, and an A/B test plan. Implementation is not in scope.

What is the minimum commitment?

Audit + Plan is a standalone 2-week engagement. Design Sprint is a fixed 4–6 week project. Design OS retainer requires a 3-month minimum, then month-to-month with 30 days written notice.

What if the metric doesn't improve?

If the agreed conversion metric doesn't improve by 20% after shipping and A/B testing, we redesign the failing flow at no charge. One iteration sprint is delivered within 30 days of the post-ship review call confirming the shortfall.

Is there a SOC 2 or GDPR compliance requirement?

We operate on a read-only basis with your analytics data. We do not collect, store, or process end-user personal data. SOC 2 or GDPR compliance is not claimed — if your procurement requires a specific compliance framework, let's discuss before scoping.

Product Design for B2B SaaS

Led by Jake McMahon

Founder, ProductQuant · LinkedIn

Fix the exact screens that bleed your activation.

Q: What does the guarantee cover?

Every sprint has a written target metric agreed before work begins. If the redesigned flow does not produce a 20% or greater relative improvement in that metric — as measured by your A/B test after shipping — we deliver one iteration sprint at no charge.

Stop shipping redesigns that don’t move the needle. We find your costliest drop-off, redesign it in a 4–6 week sprint, and guarantee a 20% lift — or we redesign it again free.

+20% activation or second sprint is free.

Book a design strategy call See how it works →

Three ways to engage

Audit + Plan 2 weeks
One-time · from $8K

Design Sprint 4–6 weeks
Fixed price · $20K–$40K

Design OS Monthly retainer
$12K–$18K/mo

All sprints: Figma files · developer handoff · A/B test plan
Sprint + Design OS: 20% lift guarantee or iteration free

What’s actually costing you right now

✗

Design decisions based on opinion, not data. Activation hasn’t moved in months and nobody can point to which screens are bleeding it.

You’ve shipped redesigns that felt right. Without friction data tied to a specific metric, you’re optimising by intuition — and the activation ceiling stays where it is.

✗

You know the product has UX problems. But there’s no quantified list of what to fix first, ranked by what each fix is actually worth.

Heatmaps give you impressions. Session recordings give you examples. Neither gives you a prioritised revenue impact list. That’s what the audit produces.

✗

When the board asks what design contributed to activation and retention this quarter, the answer is a story — not a number.

Every sprint includes a written target metric, a post-ship review call, and A/B data. The board gets a number. Not “we redesigned the onboarding and it feels better.”

Three tiers. One continuous method.

Audit → Sprint → Design OS

Each tier builds on the last. The Audit is the recommended entry point — every sprint and retainer month starts from friction data, not from opinion.

Tier 1 · Diagnosis

Know which redesign is worth the most, before committing a dollar.

A friction inventory showing the revenue cost of every drop-off point — so you know exactly where the redesign ROI is before committing. Two weeks to pinpoint the exact screens bleeding your activation, with the dollar impact of each fix calculated.

$8K – $15K

One-time · Fixed price

Full-funnel dropout map — every step, percentage attached
Friction inventory — prioritised list with revenue impact per item
Heatmap + session review — top 10 highest-traffic screens
Competitor reference audit — three to five direct competitors, flows only
Sprint brief — included if you proceed; not an extra cost
60-minute readout call — recording + written summary

Guarantee does not apply to the Audit tier — the audit diagnoses; it does not redesign.

Start with an Audit →

Tier 2 · Redesign

Design Sprint

Four to six weeks. Focused redesign of one high-impact flow, tied to a specific metric.

$20K – $40K

Fixed price per sprint

Sprint brief confirmation — target flow + metric agreed in writing
Design exploration — two to three directions, one selected with rationale
Full Figma delivery — all screens, all states, all edge cases
Component annotations — every spacing, state, and interaction spec
Developer handoff package — written notes for anything outside Figma
A/B test plan — tool, traffic split, minimum sample size
Post-ship review call — 30 minutes, four to six weeks after shipping

20% relative improvement or one iteration sprint at no charge. In writing.

Scope a Sprint →

Tier 3 · Ongoing

Design OS

Monthly retainer. Continuous design motion against a live friction inventory.

$12K – $18K

Per month · 3-month minimum

One sprint per month — next-highest-impact item from the inventory
Friction inventory update — new dropout data reviewed monthly
A/B results log — outcomes from shipped flows recorded and linked
Design system maintenance — new components added each sprint month
30-minute monthly check-in — async substitute available
Context maintained — no re-briefing; every sprint starts from the last data point

Sprint guarantee applies per sprint within the retainer, on written agreement.

Discuss Design OS →

The guarantee

20% lift or we redesign at no charge.

This is in the service contract — not in the marketing copy.

How it works

Every sprint has a written, agreed target metric before work begins.

If the redesigned flow does not produce a 20% or greater relative improvement in that metric — as measured by an A/B test after shipping — we deliver one iteration sprint at no charge. The metric is chosen before the sprint starts, not retrospectively.

Example: baseline onboarding step 3 completion 40% → target 48% (40% × 1.20). If the result is 46%, the guarantee triggers. The iteration sprint is scheduled within 30 days of the post-ship review call.

What the guarantee covers

The specific flow scoped in the sprint brief. The metric agreed in writing before sprint start. One iteration sprint at no charge if the metric does not reach the 20% threshold.

What the guarantee does not cover

Metrics outside the agreed sprint scope. The Audit tier. Cases where the client does not ship the redesign or does not run an A/B test within 90 days of delivery.

What this guarantee is NOT

It is not a money-back guarantee. It is a redo commitment — one iteration sprint delivered at no charge, tied to the failing flow. A refund is not the mechanic.

Why 20% relative, not absolute

20% relative improvement (e.g., 40% → 48%) is operationalisable, verifiable by A/B test, and meaningful at every baseline level. It is the contract threshold — not a marketing number.

Honest comparison

vs. Hiring a senior designer · vs. Brand agency · vs. DIY

All three comparisons a buyer runs before signing. Addressed directly — not framed as an attack.

Criterion	ProductQuant	Senior in-house hire	Brand / marketing agency
Time to first output	2 weeks (Audit). Sprint starts within 2 weeks of signed contract.	60–120 days to recruit, onboard, and reach productive output	3–6 months to project delivery
Cost structure	Fixed, bounded investment per tier. No equity, no benefits overhead.	$120K–$180K/yr total comp before equity. Open-ended.	Variable by project. Often scoped broadly at $80K+
Primary output	Analytics-led friction audit + redesigned conversion flows, developer-ready	General product design across whatever backlog the team assigns	Brand identity, marketing sites, campaign assets
Success measured by	Specific conversion metric agreed before sprint starts — activation rate, step completion, etc.	Shipping velocity and stakeholder satisfaction	Client approval and aesthetic outcome
Metric guarantee	Yes — 20% relative improvement or failing flow redesigned free	No contractual metric guarantee	No conversion outcome guarantee
What you inherit	Figma files, annotations, developer handoff, A/B test plan, friction inventory	One person's design decisions, undocumented unless they choose to document	Brand guide, visual assets — rarely conversion-focused
When it makes sense	Need a specific flow improved with a measurable outcome. Series A/B. CFO wants a bounded investment.	Need design in daily standups. Post-PMF, high design volume. Design is core function.	Need a brand identity system, campaign materials, or marketing site — not product UX

These paths are not mutually exclusive. An Audit + Sprint can define exactly what your first in-house designer inherits — so their first week is productive rather than spent reverse-engineering what exists.

The method

D.R.I.V.E. From friction data to shipped redesign.

Every sprint runs this sequence. Each phase has defined deliverables. Nothing is a black box.

Diagnose

Read-only analytics access. Full user journey mapped: where users enter, where they drop, what they do in between. Every dropout point quantified as a percentage. Revenue impact calculated at confirmed MRR per user.

Full-funnel dropout map (signup to activation)
Heatmap and session review — top 10 highest-traffic screens
Competitor reference audit — three to five products, flows only
Friction inventory with revenue impact per item

Research

User session deep-dives, behavioural segmentation, and pattern analysis. Three to five session reviews on the target flow. Runs in parallel with Diagnose during the Audit tier.

Session recordings reviewed for the target flow
Behavioural pattern identified from session data
Cohort segmentation where analytics permit

Iterate

Two to three design directions explored for the target flow. One direction selected with documented rationale tied to friction data — not designer preference. Full Figma delivery: all screens, all states, all edge cases.

Design exploration: two to three directions
Direction selection with documented rationale
High-fidelity Figma files — every screen, every state

Validate

A/B test plan written as part of sprint close — not as an afterthought. Tool recommendation (PostHog, Optimizely, VWO, LaunchDarkly), traffic split, minimum sample size for 95% confidence, and what to measure.

A/B test plan — tool, split, sample size, metric
Post-ship review call — four to six weeks after client ships
Guarantee assessment at post-ship review

Embed

Developer handoff package: Figma developer mode, written notes for any interaction that cannot be expressed in Figma, component annotations for spacing, states, and colour. Design rationale documented so the next person who touches the flow has the decision history.

Component annotations — spacing, states, typography, colour
Written handoff notes for complex interactions
Design rationale documentation
Design system additions — new components and states added to the library

Who this is for

Built for B2B SaaS leaders whose job depends on users converting.

Four roles. Each gets something specific.

VP Product / CPO

Know exactly which flow redesign will move your activation metric before you commit a sprint.

Head of Growth

Turn drop-off data into a numbered list of redesign bets — ranked by revenue impact.

Founder / CEO

A redesign that ships with a written guarantee. Not another “it looks better” from your designer.

Product Design Lead

A senior analytics partner who owns the hypothesis, the data, and the outcome — not just the Figma file.

Common thread: You’ve shipped a redesign before that didn’t move the numbers. You’re done with opinion-based design.

Clarity saves time

What This Is Not

Here’s what we don’t do — so only the right conversations get started.

×Brand identity or marketing site design. We focus on in-product conversion flows: onboarding, activation, upgrade.
×An open-ended design system rebuild. We create reusable components for your sprint flow, not a company-wide overhaul.
×A junior designer you have to manage. Jake (founder, ex-product lead) is your direct counterpart on every engagement.
×Engineering implementation. We deliver pixel-perfect Figma files, annotations, and a developer handoff package. Your team builds it.
✓What it actually is: Analytics-first redesign of your highest-impact conversion bottleneck. Written metric target. Written guarantee. One person accountable for the result.

The founder

The designer who measures success by your conversion rate.

Jake McMahon runs every engagement personally — no juniors, no account managers.

Jake McMahon · Founder, ProductQuant

$15K–$500K ticket-size deals closed using this system · Built an agency to $1.5M ARR in 12 months · Masters in Behavioural Psychology

“I’ve been on your side of this. I’ve sat in roadmap reviews where ‘improve onboarding’ was a vague action item for six months. I’ve shipped redesigns that looked good in Figma and didn’t move the activation needle.

That’s why every engagement starts with analytics, not assumptions. I connect to your PostHog or Amplitude before I open Figma. Every screen change has a measurable hypothesis behind it — and a written target agreed before work begins.

I hold a Masters in Behavioural Psychology. I’ve spent 8+ years leading product in B2B SaaS. I know what makes users act, and I know how to measure whether a design decision worked.”

What I won’t do:

—Redesign without a defined metric it’s accountable to
—Deliver Figma files without a developer handoff package and A/B test plan
—Promise a visual improvement without measuring the conversion outcome
—Recommend a full redesign when a single flow fix will do the job

Written into the scope

Four commitments. Before we start.

Before we redesign anything, you know exactly what’s costing you conversions. Every commitment is in writing before the project starts.

One agreed metric.

We define the conversion target before any design work begins. Not after. Not retrospectively. If we can’t agree a measurable target, we don’t start the sprint.

Data before design.

Your analytics tool is connected and read before we open Figma. Every screen change is argued from dropout data, not designer intuition or stakeholder preference.

Written scope.

Every deliverable is specified in writing before the project starts. The flow, the screens, the handoff format, the A/B plan. No scope creep without a scope change document.

20% or we redesign free.

If the agreed metric doesn’t move by 20% relative after shipping and A/B testing, we deliver one iteration sprint at no cost. Written into the contract.

Is this the right fit?

This is a specific offer for a specific situation.

It works well for a narrow ICP. If you don’t fit it, say so before scoping — not after.

Good fit

B2B SaaS at Series A or Series B — product-market fit found, activation or retention not where it should be
Director of Product, VP Product, or CEO who needs design ROI in metrics, not aesthetics
CFO declined a senior designer headcount — bounded investment preferred
You have analytics instrumented (PostHog, Amplitude, Mixpanel). Without data, the audit has nothing to map.
Head of Design with accumulated design debt — needs a system the team can own
Head of Growth who needs a specific flow redesigned and A/B tested in under 6 weeks

Not a fit

Pre-product-market fit, pre-revenue — no analytics data means no friction audit, and no guarantee
Brand identity, marketing design, social creative, or campaign materials — scope is product UX only
You need a designer in daily standups and Slack all day — engagement model doesn’t cover that
Engineering implementation included — we deliver design and handoff; your team implements
You need a full brand and visual identity system from scratch — a narrow use case, negotiate separately

Frequently asked

Questions

PostHog, Amplitude, Mixpanel, Hotjar, FullStory. Read-only access only — we never request write permissions or admin credentials. If analytics are not instrumented, the audit proceeds on public signals and session heuristics, clearly marked as inference-based, at a reduced scope and rate.

Strongly recommended. A sprint scoped without friction data cannot be guaranteed — the guarantee requires a baseline dropout rate agreed upfront. If you already have existing analytics reports showing dropout rates per screen, we’ll review them before scoping. If they’re of equivalent quality to the Audit output, we can proceed directly to a sprint.

Figma file with developer mode enabled, component annotations (spacing, interaction states, typography, colour specs), written handoff notes for any interaction that cannot be expressed in Figma alone (animation timing, API-dependent states), and an A/B test plan specifying the tool, traffic split, minimum sample size, and metric. Engineers should not need to ask any questions about what was designed.

The specific flow scoped in the sprint brief. The metric agreed in writing before sprint start. One iteration sprint at no charge if the metric does not improve by 20% relative in your A/B test. The guarantee does not cover: metrics outside the agreed scope, the Audit tier, cases where the redesign is not shipped within 90 days, or cases where no A/B test is run. This is in the service contract — not in the marketing copy.

You do. We design the test — tool recommendation, traffic split, minimum sample size for 95% confidence, and what to measure. Your engineering team runs it using whatever A/B testing capability is in place (PostHog, LaunchDarkly, Optimizely, VWO, or a feature flag in codebase). Setting up the A/B testing tool is not in scope.

Month-to-month after the 3-month minimum, with 30 days written notice to cancel. One pause per year, up to 30 days, without penalty — 10 business days advance notice required. If a ProductQuant-side delay affects your shipping timeline, the delay is credited against the following month’s retainer.

We operate on a read-only basis with your analytics data. We do not collect, store, or process end-user personal data — only aggregated metrics and session heuristics. SOC 2 or GDPR compliance is not claimed as a selling point here. If your procurement process requires a specific compliance framework, raise it before scoping and we’ll address it directly.