Four ways to buy from ProductQuant.
A self-serve toolkit. A focused sprint. A team workshop or cohort program. A comprehensive growth package. Most buyers only need to understand the difference between these four before they know where to start.
Four options. Most buyers only need one.
Everything we sell fits into one of these four buckets. Pick the one that matches how your team learns and the size of the problem you need to fix.
A self-serve toolkit for one topic
Buy a toolkit when you need a framework, template, scorecard, or decision system your team can run without outside help. Good for one clear topic — pricing, onboarding, JTBD, PLG, personas, or AI.
- Lowest-cost way to start with ProductQuant
- Best for teams that know the topic and can implement on their own
- Immediate download, no scheduling required
A focused sprint for one clear problem
Book a sprint when you know the problem and want ProductQuant to help solve that one thing directly — with clear deliverables and a defined timeline.
- Good for analytics, activation, churn, pricing, onboarding, or experiment setup
- Clearer scope and faster buying decision than a broad package
- Best when one bottleneck is actively hurting growth right now
A team workshop or cohort program
Join a workshop or cohort program when you want your team to build a real skill — not just read about it. Sessions use live data, real products, and structured frameworks so the learning sticks.
- Good for product managers, analysts, and early-stage founders
- Half-day workshops and 3-6 week cohort programs available
- Much lower cost than a consulting engagement
A comprehensive growth package
Buy a package when the problem is bigger than one sprint — when multiple parts of the business need to be connected and a real operating system needs to be installed or run over time.
- The Foundation installs the core system in 4-6 weeks
- Growth LAB guides your team over three months
- Growth OS carries more of the execution externally
Choose based on your situation, not the most expensive option.
Example: "We need a better pricing framework" or "We need a better onboarding review process." You want the system, not a consulting engagement. Browse toolkits →
Example: analytics are unreliable, activation is stalling, churn is rising, or pricing needs a specific review. You want expert help — but not a broad, months-long package. See all sprints →
Example: your PM or analyst wants to run JTBD research properly, understand churn analysis, or learn product analytics on live data — with feedback, not a YouTube tutorial. See workshops →
Example: the team does not trust the data, decisions are fragmented, experiments are inconsistent, and multiple parts of the business need to be connected properly. See growth packages →
One problem. One sprint. Clear deliverables.
Each sprint is scoped to one job. You get hands-on help without committing to a broad engagement. Most sprints run 1-4 weeks with a fixed price.
Fix measurement first.
When the team does not trust the numbers, events are missing, or dashboards do not answer real business questions.
Fix one part of the customer journey.
When new users are stalling, activation is weak, or churn needs a dedicated diagnosis instead of a full-system rebuild.
Fix one commercial decision.
When pricing is the issue, packaging is unclear, or you need one pricing or experimentation project with clear deliverables.
If someone on your team can say "we need help with analytics" or "we need help with churn," a focused sprint is probably enough.
If three or four parts of the business are broken at once, a single sprint usually will not solve the real issue. That is when a growth package makes more sense.
Fixed scope, fixed timeline, and a much easier buying decision than a broad engagement.
Learn by doing, with real data and real products.
Half-day team workshops and 3-6 week cohort programs for product managers, analysts, and founders who want to build a real skill — not just hire someone to do it for them.
Not sure which format is right? See all workshops and cohort programs → — that page explains the difference and helps you pick.
When the problem is bigger than one sprint.
These are the comprehensive engagements. The only real question is how much ongoing help you need after the system is installed.
The Foundation
For teams that need the core product and growth system set up properly for the first time.
- Best first package for most B2B SaaS teams
- Installs the system underneath all future work
- Everything stays with your team after handover
Growth LAB
For teams with people who can execute, but who want ProductQuant guiding the operating layer over time.
- Use this when your team can ship
- Ongoing analysis, prioritization, and guidance
- Good after The Foundation or when system basics exist
Growth OS
For teams that need ProductQuant to carry more of the operating and execution burden directly.
- Use this when internal execution capacity is thin
- Broader support and output than LAB
- Best for companies that need momentum fast
One question narrows it down fast.
Can you name the problem clearly? And does your team want to learn to fix it, or just have it fixed?
Buy a toolkit.
You need a framework or template for one topic and your team can run it without outside help. Browse toolkits →
Book a focused sprint.
The issue is clear and you want ProductQuant to help fix it directly — with clear deliverables and a short timeline. See sprints →
Join a team workshop or cohort program.
You want your team to build a real capability — not just have someone do it for you once. See workshops →
Buy a growth package.
Multiple parts of the business need to be fixed together. The Foundation, Growth LAB, or Growth OS.
These are the routes most buyers actually take.
Someone buys a toolkit to get the framework, then books a focused sprint if they want expert help implementing that specific area.
A PM joins a cohort program to build the skill, then the company books a sprint when they want hands-on delivery of that same area.
Common when the system needs to be installed first, then the internal team wants ongoing guidance to use it properly.
Common when the company needs the system installed and also needs more execution support than the internal team can handle on their own.
Plain-English answers to the main questions.
Should I book a sprint or buy a growth package?
Book a sprint if the problem is narrow and easy to name. Buy a package if multiple connected problems need to be fixed together as a system.
What is the difference between a workshop and a sprint?
A workshop builds a skill inside your team. A sprint delivers an output. A workshop teaches you how to run churn analysis. A sprint runs it for you and gives you the findings.
What if I am not sure what I need?
That usually means you should book a short call. We can tell you whether the right answer is a toolkit, a workshop, a sprint, or a package — or nothing yet.
Can I start small and move up later?
Yes. Many buyers start with a toolkit or workshop, then book a sprint, then move into a larger package only if the broader system needs more work.
Are the cohort programs live or recorded?
Live, in small groups. You work on your actual product, not generic exercises. That is why the learning sticks in a way a course or video does not.
Do sprints include implementation?
Most sprints deliver analysis, findings, and a clear action plan. Some include implementation. Each sprint page lists exactly what is included before you buy.
Common questions before buying.
We already have an internal data team
Your data team is probably drowning in requests rather than building diagnostic systems. ProductQuant doesn't replace your analysts — it gives them a product growth framework they can run autonomously. The question isn't whether you have data people. It's whether they're organised around finding growth levers or answering ad hoc queries. Usually it's the latter. We fix the framework, not the headcount.
Too expensive — we're pre-revenue or early stage
If you're pre-revenue, the Foundation isn't the right fit yet — that's honest. Sprints start at $497 and solve one specific problem: activating your first users, diagnosing why trial users drop off, or validating your pricing hypothesis. That's the entry point. If you're post-revenue but the price feels large, use the ROI calculator above — most teams find payback is under 6 weeks on even a modest MRR base.
We tried consultants before and got a deck, not results
That's the right concern, and it's why every engagement ends with a working system, not a presentation. The Foundation delivers a Growth DNA Report plus instrumented analytics in your actual product — PostHog, Mixpanel, whatever you use. The deliverables table in the proposal lists exactly what's handed over. If I don't deliver the diagnosis within 14 days, you get a full refund. A deck isn't a deliverable — a working experiment backlog and a wired activation funnel are.
We need to see it work first
Two options. Start with a Sprint — $497, one week, one specific problem solved. You see the quality of the output before committing to anything larger. Or take the 14-day guarantee on Foundation: the risk is entirely mine — if you don't have a clear diagnosis in two weeks, I refund the full engagement fee. Most clients pick option two because the Foundation output is ten times more valuable than a Sprint for the same payback period.
Our CEO needs to approve this
Completely normal. I'll send you two things: the one-page ROI summary (takes 2 minutes to read) and a PDF version of the proposal formatted for executive review. Most CEOs approve within 24 hours when they see the payback period is under 8 weeks and the guarantee removes downside risk. Send me their name and I'll write the exec summary directly to them.
We don't have time to onboard a consultant
The onboarding is one 30-minute call and a 10-question async form — that's it. Everything else is async: I review your analytics, send findings, and push deliverables to a shared folder. There's no standing weekly meeting unless you want one. Most founders spend less than 2 hours total on coordination throughout a Foundation engagement. The heavy lifting is on my side, not yours.
What makes this different from hiring a full-time PM?
A senior PM costs $120K–$180K per year, takes 3 months to hire, and another 3 months to fully context-load. A Foundation engagement is delivered in 3 weeks for $2,497. More importantly, a full-time PM optimises for execution inside your current framework — ProductQuant questions the framework itself. You find out whether you're building the right thing before you hire someone to build it faster. Most clients use the engagement to define the spec for that first PM hire.
We already use Amplitude / Mixpanel / GA4 — why do we need this?
The tool is not the system. Amplitude, Mixpanel, and GA4 are infrastructure — they capture and store events. They don't tell you which event sequence predicts trial-to-paid conversion for your specific user cohorts, or why your Month 2 churn is higher than Month 1. Those answers require a framework layered on top of the tool. Most teams using these platforms are utilising about 15% of what the tool can tell them because nobody has built the question architecture. The Foundation builds it.
Tell us the problem. We will tell you the simplest thing to buy.
If a toolkit is enough, we will say that. If a workshop is enough, we will say that. If you need a sprint or a larger package, we will explain which one and why. We do not push you toward the most expensive option.