# Launch Playbook

## Sell the outcome, not the abstraction

Do not lead with "framework" by itself.

Lead with what Thymos helps a team get:

- governed AI execution
- better auditability
- safer tool use
- a Rust implementation teams can own and extend

## What teams actually buy

### 1. Team license

Sell source access for internal use.

Include:

- private repository access
- release notes
- upgrade rights for a defined period
- example projects and implementation guides

### 2. Deployment pack

Sell the path from source code to production rollout.

Include:

- starter services or reference apps
- infrastructure and CI patterns
- deployment guides
- security and operational checklists

### 3. Enterprise support

Sell trust and speed for bigger teams.

Include:

- onboarding workshops
- architecture reviews
- migration help
- response-time commitments

## Best first buyers

Start with teams that already feel the pain Thymos addresses:

- internal AI platform teams
- regulated workflows that need auditability
- companies building tool-using AI systems with real side effects
- teams replacing brittle prompt orchestration with a runtime model

## Packaging principles

- keep the core story technical and concrete
- show the crate map and execution model
- include examples that prove the model is real
- make the paid offer about adoption, support, and operational confidence
- avoid pretending this is a generic agent SaaS

## Pricing shape

Good framework businesses usually combine more than one pricing motion:

- one-time team license
- annual updates and support
- paid onboarding or architecture packages
- custom enterprise contracts

## What not to do

- do not charge like a chatbot app if you are not selling a hosted app
- do not sell only "access to code" with no rollout path
- do not make the commercial tier about vague future features
- do not hide the hard parts of adoption; package them
