TL;DR
- This is a fast self-audit, not a theory exercise. It helps classify the product as it exists today.
- The audit covers 10 dimensions: value model, topology, growth motion, pricing, buyer-user map, activation, moat, complexity, expansion, and positioning.
- The useful part is not just the answers. It is the contradictions the answers reveal.
- Run it with leadership, not alone. The disagreements usually point to the real strategic confusion.
Most SaaS teams start with a playbook before they start with classification.
They debate PLG, pricing, onboarding, sales motion, content, or category strategy before agreeing on what kind of product they actually have. That is backwards.
A product that is multi-stakeholder, team-dependent, and slow to activate should not be expected to behave like a single-user self-serve tool. A single-player product should not inherit a seat-based expansion plan just because other SaaS companies do. Strategy gets cleaner when the product gets classified first.
This audit is designed to do exactly that. It is deliberately simple enough to run quickly, but it is still strong enough to expose where a team's assumptions about the business stop matching the product's actual structure.
The 10-Dimension Product DNA Audit
For each dimension, choose the option that best describes the product as it is today, not where you hope it will be in 12 months.
1. Value delivery model
Is the product mainly a workflow tool, a system of record, an intelligence layer, an automation platform, or infrastructure? This matters because value model shapes adoption, pricing logic, and moat formation.
2. User topology
Is the product single-player, multiplayer, network-based, marketplace-driven, or multi-stakeholder? Topology changes everything from pricing to activation to how realistic network-effect claims really are.
3. Growth motion
Does the business actually run product-led, sales-led, partner-led, community-led, or hybrid? Teams often describe the motion aspirationally instead of operationally. The audit should reflect current reality.
4. Pricing architecture
Freemium, free trial, per-seat, usage-based, flat/tiered, and custom pricing each assume different things about activation speed, user structure, and revenue expansion.
5. Buyer-user map
Is the buyer the same person as the user, a second-level approver, or a committee? This is one of the fastest ways to tell how far a self-serve motion can realistically go on its own.
6. Activation pattern
Does value appear instantly, through one clear aha moment, gradually over time, only after team participation, or only after integrations and setup? If you misclassify this, trial design usually breaks.
7. Retention moat
Is retention mainly held up by data lock-in, workflow embedding, network density, ecosystem depth, habit loops, or no meaningful moat yet? Most companies overclaim this dimension.
8. Complexity and time-to-value
Is the product simple or complex, and does value arrive fast or slowly? This dimension helps explain why some teams keep benchmarking themselves against companies with very different economics.
9. Expansion model
Does revenue expand through seats, usage, feature/module adoption, tier upgrades, or cross-sell? If the expansion model is wrong, pricing, NDR targets, and board expectations all get distorted.
10. Competitive positioning
Is the product a category creator, differentiator, niche specialist, or disruptor? This determines the content mix, the sales narrative, and what you are actually positioning against.
Use the Product DNA framework if you want the fuller version of this audit.
This quick audit is a strong entry point. The full framework is better when you need to map the dimensions into a strategic plan.
What to Look For After You Answer
The most useful output is not the list of choices. It is the tension between them.
PLG viability
If the product is single-player or lightweight multiplayer, has the buyer close to the user, activates quickly, and is relatively simple, PLG becomes much more plausible. If it is multi-stakeholder, team-dependent, and complex, pure self-serve becomes structurally harder.
Pricing alignment
Per-seat pricing fits multiplayer topology much better than single-player topology. Usage-based pricing fits variable consumption much better than fixed workflow products. Freemium assumes activation can happen fast enough for free users to see value before they disappear.
Contradictions
These are often the best signal:
- Freemium + team-dependent activation: free users churn before they ever trigger the group behavior that creates value.
- PLG + multi-level buyer: users can try, but cannot buy cleanly.
- Per-seat + single-player topology: the expansion ceiling stays much lower than the model assumes.
- Category creator + self-serve-first motion: the market may not yet understand the problem well enough for that motion to work cleanly.
If leadership gives different answers to the same dimensions, that is not noise. It usually means the company is already trying to run multiple conflicting strategies at once.
What to Do Instead of Jumping to a Playbook
Run the audit first, then use it to simplify the next strategic conversation.
- Compare answers across functions. Product, growth, sales, and leadership often describe the product differently.
- Name the biggest contradiction. Do not try to solve every dimension at once. Find the structural mismatch that is most distorting the strategy.
- Choose the next playbook from the audit, not from trend pressure. If the product is not ready for pure PLG, say so. If the pricing unit is wrong for the topology, fix that before rewriting the pricing page.
- Repeat the audit when the product changes meaningfully. DNA is not permanently fixed, but it should only be updated when the product has genuinely changed.
The goal is not to create a new internal ritual. It is to stop spending quarters on strategies that were structurally misaligned from the start.
Use the audit to find the next strategic conversation, not to end it.
If the audit reveals tension around PLG, pricing, activation, or GTM, follow that contradiction into a deeper diagnosis instead of papering over it.
How to Use the Audit With a Leadership Team
The audit gets much more useful when it is run across functions instead of by one person alone. Product, growth, sales, and leadership often answer different dimensions differently because each team sees a different slice of the product.
- Run it independently first. Do not let the group converge too early.
- Compare the answers side by side. Look for repeated disagreement around pricing, buyer-user map, activation, and positioning.
- Ask which answer is operationally true today. Not which answer sounds more ambitious or more fundable.
Those disagreements are usually where the strategic leverage sits. If growth says the product is PLG-ready and sales says the buyer is still a committee, that tension matters more than a polished offsite narrative.
FAQ
How often should we run a Product DNA audit?
Usually when the product, pricing model, buyer map, or growth motion changes materially. Running it quarterly without real product change is probably overkill.
What if the team disagrees on multiple dimensions?
That usually means the business is running different assumptions in parallel. Start with the disagreement that most directly affects pricing, activation, or growth motion.
Can a product sit between categories on a dimension?
Yes, but force yourself to choose the dominant reality today. The point of the audit is clarity, not perfect nuance.
What should we do right after the audit?
Pick the biggest contradiction and tie it to one concrete strategic decision: PLG, pricing, activation, content, or positioning. That makes the audit actionable.
Sources
About the Author
Jake McMahon writes about the structural layer underneath SaaS growth: pricing, activation, topology, buyer-user alignment, and the systems teams need before they borrow somebody else's playbook. ProductQuant helps companies classify their products before they commit to the wrong strategy.
This article is part of the Product DNA series, focused on practical diagnostics teams can run immediately.
Classify the product first. Then pick the strategy.
If the team keeps arguing about PLG, pricing, or GTM without agreement, the missing piece is often classification.