A focused, read-only pilot: connect one tracker and your AI tools, and we'll show you exactly what your AI compute costs per ticket, epic, and team — with a budget forecast and guardrails — without a single prompt leaving your environment. Free for design partners.
Not sure? Ask us — a 10-minute look at your setup tells us fast.
Read-only and metadata-only. Outlay runs on categories, token counts, and ticket IDs — prompt content and keys never leave your environment.
20-minute call to confirm fit, pick the tracker + usage source, and agree what "good" looks like.
Read-only access; we ingest the metadata and resolve spend to your tickets. ~30 min on your side.
We walk you through your real numbers — coverage, forecast, burndown, anomalies, savings.
Keep going (turn on guardrails + the optimization engine) or part as friends. Your data, deleted on request.
Nothing — design-partner pilots are free. In exchange we ask for candid feedback, and (if it lands) a reference. You also get influence over the roadmap and early pricing.
Read-only: one tracker (GitHub/Jira/Linear) and a way to read your AI usage (Claude Code transcripts, Cursor admin export, or the Anthropic admin API). No write access, no app changes.
No. Outlay runs on metadata only — task categories, token counts, ticket IDs. Prompt text, model outputs, and API keys never reach us, and our endpoints reject any payload containing them.
Then coverage from branch inference alone is low — which is exactly why Outlay also resolves the ticket from PR→issue links and an explicit one-line task tag (works even for remote/CI agents). We'll tell you your real coverage number in week one either way.
Deleted on request at the end. Per-deployment isolation throughout; you can leave anytime.
Map your AI spend to your roadmap and see exactly where it's going — and where it's about to go over.
Read-only · prompts never leave your environment · free for design partners