Founder GTM Reporting

This is a draft founder cheat sheet for live pricing conversations in private beta.

What this sheet is for

Use this as the default explanation:

"We price the platform by the level of system a team needs, not just by seats."
"If you only want one tool, we can do seat pricing. If you want the connected system, pricing starts at Foundation."
"The quality and trust layer is built in throughout, so teams are not paying extra just to make the research usable."
"When we talk budget, we usually anchor first against tool spend you already have, then look at the hours and rework this should save."
"For private beta, we are happy to talk in indicative ranges first, then shape the final proposal around the workflows, support model, and organisational reach involved."

GBP 220 per seat per month
Best for: teams that want one tool only, not the connected platform
Use when: someone wants a better survey tool, a better discussion forum, or a standalone questionnaire reviewer without the wider system

From GBP 1,500 per month
Best for: teams that want research run on the platform to stay connected, reusable, and easier to build on
Use when: the buyer wants access to the real connected platform rather than a point solution
Working beta scope can still land around GBP 1,500 to GBP 3,000 per month depending on workflow, support, and team setup

GBP 5,000 to GBP 10,000 per month
Best for: teams that want imported past work connected across methods so insight travels further and the business can keep learning from it
Use when: they need platform-run research plus external research connected and queryable together

GBP 15,000 to GBP 40,000+ per month
Best for: broader organisational access, governance, and deeper infrastructure value
Use when: multiple teams or markets need direct access to customer knowledge

Foundation connects studies run on <un>peel so research does not disappear after the project ends.
Growth adds imported external research, so platform-run studies and past work can be connected and queried together.
Enterprise extends that connected evidence system across broader organisational access, governance, and infrastructure needs.

"Private beta conversations will usually start with scope, workflow, and support level first."
"For strategic named-brand or especially high-signal accounts, we may use a free pilot with a clear quote path if the work delivers value."
"That free strategic lane should be reserved for accounts with strong logo or signal value, strong product learning value, and a believable path to paid conversion."
"For other buyers, we should usually move into a paid pilot or Foundation pricing earlier."
"If we structure a pilot, we then define the bridge into annual pricing once the pilot shape is agreed."
"The exact commercial shape may vary slightly if the beta is sold as high-touch assisted delivery rather than pure software access."

do not describe the model as purely seat-based SaaS
do not lead with Starter if the buyer is clearly asking for the full connected system
do not make free pilot sound like the default for everyone
do not imply every customer gets the same fixed beta deal regardless of scope
do not position trust as a paid add-on
do not over-explain future outcome-based pricing in first conversations

How much pricing should be public on the website
Whether the beta stays mainly conversation-led or exposes more detail up front
How pilot-to-annual pricing is framed once the first private beta customers convert

Treat this as founder review material for now. Once approved, it can become: