Two descriptions of the same company
Product DNA is the set of structural facts about what you have built: pricing shape, value delivery, expansion path, the roles involved in buying and using it, how long first value takes, how much complexity the product carries, what makes a customer stay.
GTM DNA is the set of facts about how that product can reach and convert buyers: which segment can adopt it today, what the buyer already believes, which motion the deal size and cycle support, which channels reach those buyers, what the sales team has to prove.
| Product DNA asks | GTM DNA asks |
|---|---|
| What does this cost to deliver? | What will this segment pay? |
| How long until first value? | How long is the buyer willing to wait? |
| What makes a customer stay? | What makes a buyer choose us first? |
Both are descriptions, and both are usually written by different people at different times. That is where the trouble starts. The product document gets written by founders and engineers. The growth plan gets written by whoever owns revenue. Nobody is asked to put the two side by side.
Why the mismatch is expensive
A mismatch does not usually announce itself as a strategy problem. It arrives as a symptom. Trials that start and never activate. A sales team closing deals that churn in month three. A pricing page that describes a product the buyer never experiences. Paid acquisition that works at a cost per signup nobody can afford at the retention you actually have.
Each symptom gets treated on its own. Activation gets a new onboarding flow. Churn gets a save offer. Acquisition gets a new channel. None of those fixes touch the underlying disagreement, so the symptoms move rather than disappear.
The expensive part is not the wasted spend on any one tactic. The real cost sits in the months spent optimising a motion the product cannot support.
The ten sentences
The practical version of this work is short. Write ten sentences that describe your product structurally, and get the people who disagree to sign them.
Pricing and value delivery. Expansion and the path to it. Who uses it and who approves it. How long until first value. What complexity the product carries and who absorbs it. What actually keeps a customer. How buyers find you. What the sale has to overcome. Which segment can adopt this now. What you would have to change to serve the segment you want.
The exercise works as a disagreement detector rather than a writing task. The sentences where two departments write something different are the ones that cost money, and they are usually the sentences nobody has written down before.
What this is, and what it is not
This is a structured course with six modules and eighteen lessons, built around profiles, exercises and a decision plan. It is designed for software founders and product teams who already have a product in market and a growth plan that is not working as expected.
This is not a growth playbook, and it will not hand you a channel. It does not tell you what to build next. It gives you a way to describe what you have built precisely enough that a growth decision can be made against it, and a way to find the places where your current plan assumes something the product does not do.
If you want to test the thinking on your own product before committing to anything, the free diagnostic is the place to start.
How to use it on your own product
Start with the retail question rather than the strategic one. Take your last ten closed deals and write down, for each, what the buyer thought they were getting and what the product actually delivered in the first month. Where those diverge, you have a sentence that needs writing.
Then take your last ten churned accounts and do the same. The pattern in the divergence is your Product DNA asserting itself against your GTM DNA.
That exercise costs an afternoon and produces the first draft of the document this course exists to help you finish.
Further Reading
The Product DNA + GTM DNA course is the structured version of this work. If you want to test the thinking before committing to anything, the free team diagnostic is the place to start. For the measurement side of the same problem, our event taxonomy guide covers how the tracking has to be shaped before any of this can be measured. For the analytical side, the SaaS Product DNA Toolkit covers pricing, activation, retention and expansion structure.
Two outside sources are worth reading alongside this. Rahul Vohra describes in First Round Review how Superhuman turned the question of whether the product fits into a survey with a number attached. The Sean Ellis product/market fit survey, run with GoPractice, is the free version of that question; Ellis benchmarked close to a hundred startups before treating 40 percent as the threshold.