<un>peelFounder GTM
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.

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

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 final EUR pricing sign-off, cleaner entitlement rules, and an approved product-maturity map for assisted beta selling.

Underlying items

The strategic and tactical work inside this pillar

Open checklist slice
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 detail
In 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 detail

Founder decisions

Calls affecting this area

Open readiness checklist
Needs a call

Approve the EUR pricing and beta package rules

Keep the public anchors at Starter EUR 260 per seat per month, Foundation from EUR 1,750 per month, Growth from EUR 5,850 per month, and Enterprise as contact us. Approve the included capabilities explicitly and keep unenforced usage limits, support exceptions, and pilot-to-annual terms inside proposals and live conversations.

Review in readiness checklist
Needs a call

Approve the assisted private-beta delivery model

Use a productized assisted-beta model: defined onboarding, a named support channel, scheduled reviews, bounded priority-fix commitments, an agreed evidence or quote ask, and an explicit route into a paid annual plan. Do not allow the beta to become open-ended consulting.

Review in readiness checklist
Come back later

Decide how to explain Research Architect in normal buyer language

Explain Research Architect as the place where teams gather the right context and shape the brief before designing research. Keep the bigger 'front door to every project' story as the future direction until the product is ready to support it.

Review in readiness checklist
Needs a call

Approve what is live, beta, selected-customer-only, or directional

Use one maturity-labelled commercial map backed by the current roadmap and technical confirmation. Allow curated access where appropriate, but never turn access to the full designed product set into a blanket promise or describe future capability as generally live.

Review in readiness checklist