Back to Offer, Product, and Pricing
In progressOwner: Founder + DesmondFounder decision required

Workstream

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.

Why this matters

Pricing is where the platform stops being a story and becomes a business. It shapes who can buy, how quickly deals move, and whether the suite feels coherent.

Because the thesis pushes beyond seat-based SaaS, the launch posture has to feel both intentional and simple enough to explain in one conversation.

Current state

The repo already supports a clear pricing architecture: Starter / point-solution entry, Foundation, Growth, and Enterprise, with confidence built in at every level and price scaling by workflow scope, knowledge depth, and organisational reach.

The unresolved issues are commercial posture and operability. A founder pricing conversation sheet now exists, but beta still needs a call on how much of this is public, how pilots convert to annual contracts, and how plans translate into actual entitlements, usage limits, and commercial FAQs.

The delivery model is also not fully locked. Enterprise SaaS is the default stance, but the strategy docs explicitly keep assisted and software-under-service delivery modes open for pilots, which affects onboarding design, support posture, and pricing simplicity.

The external-signals document makes the pricing direction more defensible than the current workstream copy shows. Coatue's per-output thesis supports the move away from pure seat pricing, Vista's data-sovereignty argument reinforces why knowledge value belongs in the commercial model, and Thoma Bravo's mission-critical lens supports the long-term infrastructure tier as the real destination rather than the point-solution wedge.

Checklist

What still has to happen

Foundation

The minimum decisions and assets needed so the launch story is coherent rather than aspirational.

BlockedLaunch critical

Choose the beta pricing posture

The tier structure is ready; the public versus conversation-led selling stance still needs founder sign-off.

Private preview

The hardening work required for founder sharing, pilot conversations, and limited buyer-facing use.

In progress

Tie plans to entitlement, usage, and contract logic

Billing docs already acknowledge runtime entitlement checks, but plan definition, usage limits, metering, and contract mechanics are still underbuilt.

Ready for betaLaunch critical

Create beta-ready commercial collateral

A founder pricing conversation sheet now exists, so the minimum live-call pricing material is in place even though richer packaging can still follow.

What exists

Value-based pricing thesis

The pricing model already explains why value should scale with research activity, knowledge reuse, and organisational reach rather than only seats, while the strategy context keeps enterprise SaaS as the default with possible assisted delivery modes for pilots.

Buyer-readable plan draft

A buyer-readable pricing page already exists, which puts the company ahead of many early-stage products on commercial articulation even before the deck and FAQ are packaged.

Commercial-operating caveat

The repo is honest about where the pricing system is still operationally thin: plan definition, usage limits, billing, and metering are not yet complete.

External validation for pricing direction

The investor-market analysis gives the commercial model stronger backing than a normal early-stage pricing draft: it explicitly supports a shift from per-seat logic toward work delivered, while reinforcing why proprietary knowledge and infrastructure depth should matter economically.

What is missing

  • There is still no founder-approved answer on how much pricing to expose publicly during beta.
  • Willingness-to-pay evidence, pilot-to-paid terms, and commercial FAQ / procurement support are still thin.
  • The outcome-oriented and programme-oriented packaging ideas are strategically supported but not yet translated into a founder-approved beta offer shape.

Open strategic questions

  • Choose the beta pricing posture: publish indicative tier pricing and keep selling conversation-led, or hide more detail until packaging and proof are tighter.
  • Confirm whether Starter / point-solution pricing is part of the external story from day one or a quieter wedge used mainly in direct conversations and expansion paths.
  • Define the pilot-to-annual commercial bridge: free pilot with break clause only, or explicit post-pilot pricing and conversion terms.
  • Confirm whether beta is sold primarily as enterprise SaaS, assisted do-it-together delivery, or a software-under-service wedge for pilot customers.
  • Decide whether beta packaging should stay subscription-first in public while privately exploring outcome-style or programme-style offers for early pilots.