This is the working commercial reference for what can be described as live, beta, selected-customer-only, or directional. Final founder approval is still required, and technical owners should confirm any status before it becomes a contractual promise.
Working rule
- Do not promise the full designed product set to every buyer.
- Use the current GTM roadmap as the freshness source for delivery status.
- Label beta access explicitly and name the expected support model.
- Keep selected-customer access inside named proposals rather than turning it into general packaging.
- Put a date on directional capability or leave it out of the offer.
Current commercial maturity map
| Product or capability | Working external treatment | Commercial rule | |---|---|---| | Quant Surveys | Live core product | Saleable now; describe active roadmap improvements separately from the mature core. | | Discussion Groups | Live core product with V2 improvements in test | Saleable now; do not imply every V2 improvement is generally available until released. | | Guided Interviews | Integrated product workflow | Confirm operational readiness and delivery support for each beta proposal. | | Trust Centre | Live capability; July 2026 launch tranche closed | Safe to demonstrate and sell, subject to the approved claims register. | | Insight Navigator | Active build / controlled beta | Show and offer only with a clear beta label, agreed scope, and founder-assisted support. | | Segment Lens | In build; customer-beta target in the August-September roadmap window | Use as dated beta direction until the customer surface and first beta lens are ready. | | Research Guard | October V1 beta target | Do not describe as generally live; selected demonstrations or tests must be labelled honestly. | | Research Architect | October V1 target; product shape still evolving | Selected preview only where Product confirms readiness; not a default plan promise yet. |
What to say in conversation
- `The mature core is available now, and selected beta capabilities can be added where the scope and support model are agreed.`
- `We will be explicit about what is live, what is beta, and what is on the dated roadmap.`
- `Curated beta access does not mean every designed capability is generally available or included in every plan.`
Commercial guardrails
- Every proposal should list included products and their maturity explicitly.
- The website, pricing page, one-pager, demo, proposal, and onboarding plan must use the same maturity labels.
- Beta access needs a named owner, support boundary, feedback expectation, and exit or conversion path.
- Product maturity changes only when the roadmap and technical owner agree that the customer-facing state changed.
- Any quote or logo expectation should be discussed early and recorded separately from product access.
Founder choices still open
- Approve the maturity label and commercial rule for each product.
- Decide which beta capabilities can be offered to every qualified pilot versus selected named customers only.
- Decide whether the current pricing-page inclusions should show beta products, or only the mature core with beta access handled in proposals.