Skip to main content

Launch Pricing & Billing

This page documents the Tevis launch and billing model used across:

  • Website launch pages
  • Internal admin launch/billing surfaces
  • Tevis Core launch and billing APIs

Launch Phases​

Phase 1: Early Access​

  • Early Access lane (guided): high-touch support, limited seats, premium price.
  • Self-service lane (self_service): can remain closed initially.
  • Waitlist remains open for pipeline growth.

Phase 2: Founding​

  • Self-service opens in waves.
  • Early Access lane can continue in parallel.
  • Seat availability and lane toggles are managed by Tevis staff.

Phase 3: General Availability​

  • Broad self-service availability.
  • Guided support can remain as a premium lane.

Billing Model​

Monthly billing follows:

monthly_bill = base_subscription + usage_charges

Base Subscription​

Covers autonomous baseline operation and account-level orchestration.

Usage Charges​

Scale with delivered output (metered events), keeping price aligned with value.

Core Data Model​

  • launch_settings: phase, seat caps, lane open/closed toggles, pricing defaults.
  • launch_leads: lead capture + progression across tracks and statuses.
  • subscriptions: base contract per account.
  • invoice_periods: durable billing periods and invoice lifecycle.
  • usage_ledger_events: immutable usage events with idempotency keys.
  • billing_webhook_events: stored Stripe webhook events for replay/debug.
  • support_threads + support_messages: conversation-first support history.

API Surface​

Public​

  • POST /api/launch/leads
  • GET /api/launch/public-state
  • POST /api/billing/webhooks/stripe

Admin​

  • Launch settings/dashboard and lead management under /api/admin/launch/*
  • Lead lifecycle progression endpoints:
    • PATCH /api/admin/launch/leads/{lead_id}/payment
    • POST /api/admin/launch/leads/{lead_id}/provision
    • POST /api/admin/launch/leads/{lead_id}/activate
  • Billing operations and Stripe simulation under /api/admin/billing/*
  • Support conversation operations under /api/admin/support/*

Authenticated Flight Director​

  • GET /api/auth/onboarding-state
  • PATCH /api/auth/onboarding-state

Stripe Readiness (MVP)​

Tevis is implemented as Stripe-ready even before live Stripe keys are configured:

  • Webhook endpoint exists
  • Signature verification path exists
  • Admin simulation endpoint exists for fake payload testing
  • Webhook events are persisted for operational replay/debug

Source Of Truth​

Detailed planning artifact:

  • docs/plans/pricing-billing-architecture-draft.md