<un>peelFounder GTM

Appendix brief

Pricing and packaging direction

The public pricing direction is now explicit: Starter at 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. The remaining work is founder sign-off on those figures, package contents, assisted-beta rules, and operational enforcement.

Key takeaways

  • The repo already contains a coherent value-based pricing architecture from point solutions through enterprise infrastructure.
  • Packaging is aligned to workflow scope, knowledge value, and organisational reach rather than crude seat growth.
  • The commercial shape is still partly coupled to delivery mode: enterprise SaaS is the default, but assisted and software-under-service pilot motions remain open in strategy.
  • The biggest missing pieces are final figure and inclusion approval, pilot-to-paid rules, contracting assets, operational entitlements, and willingness-to-pay proof.
  • External market context supports the direction: Vista validates making the connected evidence layer economically meaningful, and Coatue validates exploring outcome-style packaging beyond simple seat counts.

What is strong already

The pricing model explains why traditional seat-based pricing is weak in an AI-assisted research workflow and proposes a more defensible scaling logic: workflow scope, knowledge depth, and organisational reach.

This ties naturally to the platform-plus-SKUs shape. Smaller point solutions can create adoption and lower-friction entry, while higher levels sell the connected system and organisation-wide infrastructure.

The external-signals strategy materially strengthens that reasoning. Coatue's per-output framing supports the move away from pure seat pricing, while Vista's data-sovereignty thesis supports charging for the connected evidence layer rather than treating it as a side feature.

What still blocks commercial readiness

Pricing visibility is decided and the EUR tiers are already public. The founder-level call is now whether the figures and inclusions are correct, whether Starter is truly sellable during assisted beta, and how exceptions are controlled.

Commercial basics underneath pricing are also incomplete. Billing definitions, usage metering, contracting language, and procurement assets are not yet packaged into a finished selling system.

The delivery model also matters here. Strategy still leaves room for assisted and software-under-service pilot delivery, so the final pricing posture cannot be treated as a pure self-serve SaaS decision yet.

The Thoma Bravo-style mission-critical destination is strategically useful, but it should not be oversold as current truth. The pricing story needs to separate the long-term infrastructure destination from what beta customers are actually buying now.

Most practical beta posture

Keep the public EUR tiers as anchors while treating beta sales as founder-led and assisted rather than self-serve. Published prices must not be mistaken for fully enforced entitlements or low-touch delivery.

Every beta proposal should state users, included products, support, manual work, sample costs, success criteria, evidence rights, and the annual conversion path.

A sensible near-term compromise is to keep the public model subscription-led and tiered, while privately testing outcome-style or programme-style packaging in pilot conversations. That uses the Coatue logic as strategic direction without forcing the beta contract model to outrun operational readiness.