01 / 10
Your SaaS Strategy
Is Fighting Your
Product's Structure
10 dimensions determine which strategies are structurally viable for your product. Most teams never check them systematically.
Swipe →
02 / 10
The borrowed playbook problem
Most SaaS teams pick strategies before classifying their product. They copy what worked for Slack or Figma — without asking whether their product shares any of the structural properties that made it work.
Slack's PLG worked because of Slack's structural DNA. Copying the playbook without the structure is how teams spend quarters on strategies their product was never built to support.
03 / 10
What This Costs
What a structural conflict looks like
Dimension conflicts create drag that looks like execution failure — but no amount of execution fixes a structural contradiction.
Conflict
PLG motion + committee buying
PQL pipeline that never converts. Users want to buy. Purchase requires budget approval from someone who has never seen the product.
Conflict
Freemium + team-dependent activation
Ghost user problem. Solo user signs up. Product does nothing useful until more people join. User leaves before the product ever works.
Most products have multiple conflicts running simultaneously. They present as execution problems, but they're structural. The next 7 slides map the dimensions that cause them.
04 / 10
Dimension 1
Value Delivery Model
Workflow tool, system of record, or infrastructure? This constrains every other dimension. Get it wrong and the other nine fall like dominoes.
Workflow Tool
Users complete tasks. Value is speed and automation. Asana, Monday, Calendly.
System of Record
Users store and retrieve. Value is truth and compliance. Salesforce, HubSpot, Veeva.
Infrastructure
Users build on top. Value is capability and scale. Datadog, Stripe, Twilio.
05 / 10
Dimensions 2–3
Topology + Growth Motion
Single-player, multiplayer, or network-effect? Your topology determines which growth motions are viable. Quick check: does your product deliver meaningful value to one user — alone — before anyone else joins? If not, PLG will fight you at every step.
PLG (Product-Led Growth)
Requires individual value + self-serve onboarding
If your product needs team adoption to deliver value, PLG acquires users who will never activate.
Sales-Led
Viable when ACV justifies the cost
Multi-stakeholder buying, configuration-dependent value, and high switching costs all point here.
Community-Led
Needs network-effect topology
Without genuine network effects, community is marketing — not a growth motion.
06 / 10
Dimensions 4–5
Pricing + Buyer-User Map
Per-seat pricing on a single-user product creates zero expansion. A buyer who never touches the product creates a conversion wall no onboarding fixes.
Mismatch
Per-seat pricing where most accounts have one user
Hard net dollar retention (NDR) ceiling for your entire single-user segment. Expansion revenue structurally impossible.
Mismatch
Buyer who never uses the product + self-serve onboarding
Pipeline full of product-qualified leads (PQLs) with intent that structurally cannot convert. The person with budget authority never sees the value.
07 / 10
Dimensions 6–7
Activation + Retention Moat
How fast does value arrive? What keeps them from switching? A 14-day trial on a 30-day activation product guarantees failure.
Instant activation
Value in one session. Calendly, Loom.
Gradual activation
Initial value fast, full value over weeks. Notion, Airtable.
Team-dependent
No value alone. Slack, Figma, Lattice.
Data-dependent
Product empty at signup. Datadog, Gong.
08 / 10
Dimensions 8–10
Complexity, Expansion,
Positioning
How hard is it to implement, how much can accounts grow, and where does it sit in the market — all structural. All determined before you ship a single feature.
08
Complexity +
Time-to-Value
Days, weeks, or months before core value? Sets your trial model and CS requirements.
09
Revenue Expansion
Model
Seat, usage, module, or tier-based? Your net dollar retention ceiling is set by this choice.
10
Competitive
Positioning
Category creator, challenger, niche, or platform? Positioning comes from DNA — not marketing.
09 / 10
Key Takeaways
10 structural dimensions determine which strategies are possible for your product — not which strategies you admire.
Dimension conflicts create drag that looks like execution failure — but no amount of execution fixes a structural contradiction.
Figma, Salesforce, Datadog, and Calendly share almost no structural DNA. Their playbooks are not interchangeable.
Classification before strategy. Always.
10 / 10
Map your product across all 10 dimensions.
The DNA Analyzer takes 12 minutes and tells you which strategies are structurally viable for your product — and which ones you're fighting without knowing it.
Take the DNA Analyzer — Free during launch
productquant.dev/dna
The disagreement is the finding.