What this covers
- Platform story versus saleable beta scope
- SKU, bundle, and trust-layer expression
- Pricing posture, plan logic, and pilot-to-paid commercial shape
Back to GTM checklist
In progressFounder decisions linked
GTM pillar
Offer, Product, and Pricing
Clarify what we are actually selling in beta, how the platform and SKUs fit together, and what commercial posture supports honest early selling.
Why it matters in GTM
A new SaaS business needs more than a compelling product vision. Buyers need to understand what they can buy now, what is bundled capability, and how pricing maps to the real offer.
Where we are now
The beta offer is clearer now and the first pricing material exists, but pricing rules and entitlement logic still need tightening.
Biggest gap
We still need the public pricing stance, cleaner entitlement rules, and a firmer rule for how this curated beta offer becomes repeatable beyond named-brand access.
Underlying items
The strategic and tactical work inside this pillar
In progressFounder decision
Platform and SKU architecture
The repo already supports a credible suite story: one platform, visible tools, and a built-in trust layer. The missing step is to translate that architecture into a beta sell-sheet that clearly separates what is saleable now, what is included infrastructure, and what is directional proof of the broader business unit.
Open tactical detailIn progressFounder decision
Pricing and commercial model
The pricing strategy is already serious and differentiated: the repo defines a ladder from point solutions to research infrastructure, and the external-signals work validates moving beyond pure seat-based SaaS. What is still missing is the beta commercial stance that makes this sellable without pretending billing, entitlements, and willingness-to-pay evidence are more mature than they are.
Open tactical detailDecisions to be made
Calls affecting this pillar
Decide now
Decide which price anchors become public in beta
Publish the current beta price anchors and keep everything beyond those anchors conversation-led: Starter at GBP 220 per seat per month, Foundation from GBP 1,500 per month, Growth from GBP 5,000 per month, and Enterprise as custom. Only do this if plan definition, entitlements, and usage tracking are tightened enough that the page stays honest.
Review on decisions pageDecide now
Choose the first delivery model for pilots
Treat high-touch assisted delivery as the best current fit for pilot maturity unless the founder wants to push harder toward pure SaaS. It preserves the software direction while matching the current state of onboarding, proof, and live customer support.
Review on decisions pageDecide next
Define Research Architect in buyer language
Define Research Architect narrowly for now as the pre-design context and brief-planning layer that helps teams gather the right context before they design research. Keep the broader gateway-to-all-projects ambition as direction until product architecture catches up.
Review on decisions pageDecide next
Clarify how Research Architect is included in beta access
For private beta, keep Research Architect available inside curated full-platform beta access for named-brand customers. Do not yet turn that into a blanket standard promise for every customer until the architecture and buyer-definition questions are firmer.
Review on decisions pageAppendix briefs
Evidence links