Editable scenario workbook
Model attempted tasks, successful tasks, retries, cache share, tools, fixed costs, payment fees, and target margin without rebuilding formulas.
Early-access validation
Price an AI product without hiding the expensive users
A planned workbook and client report for turning task economics into plan prices, usage caps, stress tests, and a decision your customer or team can audit.
Launch edition
$29
One-time · not on sale yet
Plan and usage-cap builder
Translate per-task economics into customer tiers, included usage, overage pricing, and a minimum viable monthly price.
Power-user stress test
Compare median, heavy, and failure-prone customers before a flat plan quietly turns negative.
Client decision report
Summarize the assumptions, selected model, expected spend, margin guardrail, and recommended pricing action in a client-readable format.
Model-routing comparison
Test a single-model baseline against a lower-cost routing scenario while keeping quality assumptions explicit.
Quote review checklist
Check the costs commonly omitted from AI automation quotes: support, human review, tool calls, failure handling, and payment fees.
The decision flow
From usage to a guarded price
- 1. Baseline: import the workload, model, volume, cache share, and failure rate.
- 2. Load costs: add tools, review, support, fixed infrastructure, and payment fees.
- 3. Stress usage: compare median and power-user scenarios against the same plan.
- 4. Set guardrails: choose included usage, overage, routing, and a minimum margin.
- 5. Explain: export the assumptions and recommendation for a client or internal review.
What remains free
The core answer is not paywalled
The public AI Cost-per-Task calculator and free Cost-to-Price Brief continue to show model cost, success-adjusted cost, fixed-cost allocation, fully loaded cost, and the scenario price floor. The paid edition is for reusable workflows, multiple customer tiers, stress testing, and client-ready delivery.
Use the free pricing brief →No checkout, no charge
Tell us whether this would solve a real pricing decision
Checkout stays closed during validation. You can review the exact scope and send a short early-access note. That note is used to decide what to build; it does not reserve a purchase or create a payment obligation.
Share my use case →