Baseline
Basic responses
- Cost / month
- $2,500
- Gross margin
- 87.5%
- Cost / user
- $2.50
Cost modeling for teams building AI products
A new feature changes more than the product. ProfitCtl helps you model the spend, compare your options, and decide what to ship.
Try the demoMIT licensed. Runs locally. No sign-up.
Watch the 30-second overviewA 30-second overview
See why more revenue can still mean a lower operating margin. Follow one comparison, from the command to the decision.
The animation could not load. Use the play control to retry.
In these illustrative saved scenarios, the steady-state example has $2,000 in revenue, a 95% operating margin, and $2.00 cost per user. The pilot has $6,500 in revenue, a 69% operating margin, and $12.40 cost per user. Recurring revenue is $2,000 in both. These are sample figures, not customer results.
01 / ProfitCTL in action
Run the product in your browser. Follow a fictional AI SaaS from healthy margins to higher usage, then compare a cheaper route.
$ profitctlWatch real commands run against the sample scenarios. Choose a story step to inspect its result.
One product. Four decisions.
A fictional AI SaaS starts with 1,000 users, a $20 plan, and a 60% margin target.
The scenarios use made-up rates, not live provider prices. The real ProfitCTL CLI calculates every result on your device. The story repeats automatically; choosing a step holds its result.
Adjust this separate illustration to explore usage and pricing.
How many people use the product?
Monthly usage per active user.
The recurring revenue from each user.
Both options use $400 monthly overhead and $1.50 per user in other variable costs.
Basic responses cost $0.01 per request. Research-enabled responses cost $0.08 per request.
This example calculates gross margin. Fees, growth distributions, and full stress tests belong in your CLI scenario.
Baseline
With the feature
Research adds $4,200 per month. The modeled margin stays above 60%.
An adjustable illustration using sample costs. Your real decisions need your own rates, usage, and evidence.
02 / The workflow
Follow the same workflow with your own saved scenarios, cost sources, simulations, and explicit guardrails.
Describe usage, pricing, model calls, and infrastructure. Keep each cost tied to its source and assumptions.
Compare a feature, model, deployment, or pricing plan. See the effect on revenue, recurring margin, and cost per user.
Test margin and cost targets, including growth and tail risk. Keep the decision evidence in your review.
Use the same scenario where your team makes decisions.
03 / Keep the evidence
A cost estimate is useful when you can explain it. ProfitCtl keeps sources, confidence, and profitability targets alongside the result.
Yes. Save pricing, fixed and variable costs, usage, and targets in a YAML scenario. Compare it with another option, then inspect the output.
Use simulations and growth scenarios to test margin and cost limits. Tail-risk checks help expose outcomes that an average alone can hide.
The open-source local CLI, Codex skill, and CI output are available. Hosted workspaces, saved team history, and approvals are planned.
04 / Make it yours
Start with a saved comparison. Then replace the assumptions with your own costs and usage.
View on GitHubThis source-based quick start requires Git and Go. Release installation is covered in the documentation.
git clone \
https://github.com/IntelIP/ProfitCtl
cd ProfitCtl
go run . compare \
examples/hybrid_steady_profit.yml \
examples/hybrid_profit.yml