Repo path
reporting/founder-gtm/artifacts/private-beta/commercial/pricing-conversation-sheet.md
Founder-facing EUR pricing sheet for private-beta conversations, including tier anchors, assisted-delivery boundaries, and pilot-to-paid decisions.
Repo path
reporting/founder-gtm/artifacts/private-beta/commercial/pricing-conversation-sheet.md
Notes
No additional notes recorded.
Mapped workstreams
Mapped appendices
Raw source preview
Raw, unprocessed file text shown below.
# Pricing conversation sheet This is a founder-review cheat sheet for private-beta commercial conversations. Public EUR tiers are already the working direction; the remaining decisions are final figures, inclusions, beta delivery boundaries, and the pilot-to-paid path. ## Current public pricing anchors ### Starter - EUR 260 per seat per month - For a team buying a focused product rather than the connected platform. - Confirm which products can genuinely be sold and supported this way during beta. ### Foundation - From EUR 1,750 per month - For teams running research on <un>peel and keeping the resulting work connected. - This is the normal entry point for the connected platform. ### Growth - From EUR 5,850 per month - For teams that also need imported prior research and cross-method evidence connected with platform-run work. ### Enterprise - Contact us - For wider organisational access, governance, procurement, and infrastructure requirements. Respondent and sample costs are separate pass-through usage unless a proposal explicitly says otherwise. ## Default talk track - `We price according to the level of system and organisational use a team needs, not only by seats.` - `Starter is for focused use. The connected platform starts at Foundation.` - `Foundation keeps research run on the platform connected. Growth adds imported research and broader evidence reuse.` - `For private beta, we agree the workflow, product maturity, support model, and conversion path before the engagement begins.` ## Private-beta commercial rules to approve - Reserve a free strategic pilot for an account with clear brand or signal value, important product learning, and a credible paid-conversion path. - Use a paid pilot or Foundation entry for other qualified buyers. - Put the users, included products, founder support, manual work, success criteria, evidence rights, and conversion decision into every pilot proposal. - Do not give identical access to every account. Access follows the agreed product-maturity map. - Set an explicit end point and annual-price bridge before a pilot starts. ## What the price does not yet prove - A published tier does not mean every entitlement, limit, or meter is fully enforced in product. - It does not make Research Guard, Research Architect, Segment Lens, or every Insight Navigator workflow generally available. - It does not include respondent or sample cost unless stated. - It does not promise low-touch enterprise onboarding while delivery remains assisted. ## What not to say - Do not quote the superseded GBP prices. - Do not describe the model as purely seat-based SaaS. - Do not lead with Starter when the buyer wants the connected system. - Do not make free pilots the default. - Do not promise a product or entitlement that the current beta map cannot support. - Do not improvise discounts, usage limits, security commitments, or procurement terms. ## Founder approval required - Sign off EUR 260 / EUR 1,750 / EUR 5,850 as the external figures. - Approve the inclusions, exclusions, users, usage limits, and respondent-cost treatment for each tier. - Confirm whether Starter remains visible and sellable during the assisted beta. - Define who qualifies for free strategic access versus a paid pilot. - Approve the pilot-to-annual conversion rule, discount authority, and support boundary. Once approved, this becomes the source for the website, sales deck, proposals, and pricing FAQ.