Start with a saved scenario.
Then make it your own.

1. Choose how to run it.

For a native binary, use the release installation guide. It covers version pinning, checksum verification, macOS and Linux installation, and Windows archives. Evaluator prereleases must be selected explicitly.

To run the current source, install Git and Go, then use the commands below in your terminal.

git clone https://github.com/IntelIP/ProfitCtl
cd ProfitCtl
go run . compare examples/hybrid_steady_profit.yml examples/hybrid_profit.yml

Native CLI startup needs no provider key. Paid assessment features use separate provider configuration.

2. Read the decision, not just the revenue.

The saved examples compare a steady-state contract with a pilot contract. These are synthetic fixtures, so their numbers illustrate the model.

The pilot example books more revenue, while the steady-state example has the higher operating margin and lower cost per user. This shows why an up-front payment and sustainable recurring economics are different questions.

The comparison output includes revenue, recurring revenue, fees, booked and operating margins, cost per user, covenant results, and the leaders for each metric.

3. Replace the assumptions.

A scenario is a YAML file containing the business inputs you want to test.

• Costs: fixed and variable costs, including infrastructure, model calls, tools, and payment fees.
• Pricing: subscriptions, usage pricing, plan mixes, or contract terms.
• Usage: users, growth, and simulation inputs.
• Targets: the margin and cost limits that define an acceptable outcome.
• Evidence: sources, capture dates, confidence, and notes for your cost assumptions.

profitctl simulate -f your-scenario.yml
profitctl compare baseline.yml candidate.yml
profitctl validate -f your-scenario.yml

Use the installed CLI for these commands. The equivalent source invocation begins with go run ..

4. Know what the website demo shows.

The interactive demo calculates a basic gross-margin comparison with fixed sample costs. It runs in your browser. It does not fetch provider prices or run the full CLI simulation.

Your CLI scenarios can include payment fees, contract effects, cost provenance, and simulation settings. Treat an estimate as decision evidence only after you check its assumptions against your own usage and rates.

The local CLI, Codex skill, and CI output are available today. Hosted team workspaces and approvals are planned.