<un>peelFounder GTM briefing

Appendix brief

Pricing and packaging direction

The pricing logic is already unusually sophisticated for this stage. The unresolved part is not structure, but what commercial posture to expose during beta, how explicit to be publicly, and how much of the platform-plus-SKU model should be visible before commercial operations are fully built. The external-signals work gives this direction more confidence by validating both the knowledge moat and the shift away from pure per-seat logic.

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 beta pricing posture, pilot-to-paid rules, contracting assets, 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 launch confidence

Beta still needs a founder-level call on how overt pricing should be. The repo currently supports both an explicit tiered page and a more conversation-led stance, but it does not yet lock which posture is the rule.

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

The most practical current posture is to keep indicative pricing visible enough to signal seriousness, while still treating beta sales as conversation-led rather than self-serve. That matches the current maturity of packaging, entitlements, and proof better than pretending the system is ready for frictionless checkout.

In other words: show enough structure to prove there is a business, but keep enough flexibility to learn before the company over-commits to public pricing rules that the operating layer cannot yet support.

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.