gtm-domain-library
Go-to-market domain knowledge for consumer marketplace, membership, subscription and AI-feature products: sharpening an ICP until it excludes someone, running a real user-interview panel, differentiating when the capability is rentable, launch-post anatomy, the value-metric pricing tree, the four-part deal test, and stage metrics with cohort-typed retention and the weekend test. Open it as a reference when a product or go-to-market decision needs a framework instead of an opinion. Not a wizard and not company context: it holds no client, account or market-specific facts.
naderelewa · 已有 AI 审核记录
安装与使用
运行命令前先阅读来源与依赖说明。复制命令不会自动安装或执行。
npx skills add naderelewa/Product-to-Prod --skill gtm-domain-library技能说明
name: gtm-domain-library description: "Go-to-market domain knowledge for consumer marketplace, membership, subscription and AI-feature products: sharpening an ICP until it excludes someone, running a real user-interview panel, differentiating when the capability is rentable, launch-post anatomy, the value-metric pricing tree, the four-part deal test, and stage metrics with cohort-typed retention and the weekend test. Open it as a reference when a product or go-to-market decision needs a framework instead of an opinion. Not a wizard and not company context: it holds no client, account or market-specific facts."
Go-to-market domain library
A framework is not advice. It is a way of being wrong in public, on purpose, early enough to fix it.
This library holds seven go-to-market frameworks in one place, written so that any product team can use them without knowing anything about the team that assembled them. Each framework lives in its own reference file, and each one is an original write-up that credits the originator of the classic method it draws on inline, so you can always see where an idea came from.
What this is, and what it is not
It is a reference layer: domain knowledge that stays true across companies. Open the section you need, use the mechanism, close it.
It is not:
- A wizard. Nothing here interviews you or writes files. The verbs that ship alongside this library do that, and they open these sections when a decision needs one.
- Company context. There are no client names, no accounts, no internal identifiers and no market data specific to one business anywhere in this library. That separation is deliberate: context belongs to whoever runs the product, frameworks belong here.
- A number bank. Every market number here was filled from a sourced record and carries its evidence inline, or is shown as an open gap. See the number policy below.
How to use it
- Open reference first. Read the section that matches the decision in front of you. Do not read all seven; a framework you did not need is a framework you will misapply.
- Offer, never impose. These sections produce candidate answers for a human to accept, sharpen or reject. Nothing here is a verdict.
- Say which part is evidence and which part is your read. Every claim you take out of here into a real document carries a tag:
FOUND(read this cycle from a named source, with a locator),CALCULATED(computed, with the math shown),INFERRED(reasoned from evidence, reasoning stated),CONSTRUCTED(synthesised from several sources),HYPOTHESIS(speculation, never load-bearing),NEEDS-CONFIRMATION(waiting on a named person). A framework never upgrades a guess into a fact.
The doctrine constants
Frameworks from different traditions contradict each other. These contradictions are resolved once, here, and every section below obeys the resolution rather than restating its own version.
The headline doctrine
Lead with the outcome the user came for, in the user's own words. The capability is the how, never the headline. Test it by deleting the technology word from your pitch. If the sentence still says what you do and for whom, you are positioned on the problem. If it collapses, you are positioned on the technology, and every competitor renting the same capability sounds exactly like you.
Time to first value: one definition
Time to first value is the elapsed time from a person's first open of the product to the first outcome they actually came for, measured inside that same first session. Not the install. Not the account. Not the tour. The outcome.
- The target:
[HYPOTHESIS: no durable market source found], no published dataset states an elapsed first-open-to-first-value time for any consumer product class. Every duration figure in circulation was traced to one vendor's own customer base or to a survey of practitioner opinion, and each was struck on that basis. Measure yours, write it here, and keep it the only one in the library. - The weekend test is the unaided version of the same gate: can a stranger reach that outcome with no human help, using only what ships with the product? A product that needs a call, a demo or a founder in a chat window to reach first value has no unaided path, and every acquisition channel you open will leak.
This is the only place in the library where the target is stated. Other sections refer to it and never restate it, so there is exactly one canonical constant to keep current.
Retention is always cohort-typed
A retention number without its cohort type is a rumour. Two kinds, never comparable:
- Open cohort: everyone who first used the product in a period, including the people who tried once and vanished. Measured against the whole intake. Always the lower number, and always the honest one for asking "is this working".
- Closed cohort: a qualified subset only, for example the people who reached first value, or paying members. Measured forward from the moment they qualified. Structurally higher, useful for asking "does the value hold once they get it".
Rule: every retention figure in this library, and every retention figure you publish, names its cohort type in the same sentence. Comparing a closed-cohort number to an open-cohort benchmark is the most common way teams convince themselves a leaking product is fine.
Reply rate is not join rate
Recruiting people to talk to you has two separate conversion steps, and quoting one as the other is how interview programmes get planned at a fraction of the outreach they need:
- Reply rate: the share of personalised outreach that gets any reply at all.
- Reply-to-completed rate: the share of those repliers who actually sit through an interview.
Outreach volume needed is your target panel size divided by the product of those two rates. Both rates are separate slots in this library and are never collapsed into a single "conversion" figure.
阅读完整来源 ↗