Manage your Token limits
based on data.
A team hits its limit and asks for more. Navigara answers in seconds, against rules you set.
Trusted by engineering teams
The Checkout team needs 30% more tokens
$14,300 → $18,590 per month · raised by the team lead · answered in 1.4s
- $2.4MENG-2841 · Guest checkout rewrite, 3 of 5 sprints
- $900KENG-2903 · Card vault migration, on track
- $450KENG-2917 · Address validation, in review
The tokens being asked for move this queue 75% faster.
Cheapest unit of delivery in the org, and it has been on its ceiling since the 4th. At this team’s rate, the $4,290 it is asking for buys roughly 51 more ETV a month. The same money at the Mobile team’s rate buys 9.
The person approving your AI budget has never seen your roadmap.
Approve everything and the ceiling means nothing. Decline on instinct and you throttle whichever team happened to ask.
Nobody has given them anything to judge with.
The amount is not the question
Whether $12,000 is a lot depends on what the last $12,000 produced.
Volume is not delivery
Commit counts inflate when work gets cheaper to produce.
The loudest team is not the neediest
Requests arrive in the order teams think to send them.
The biggest number on the screen is almost never the problem.
Token spend is not normally distributed, so a list sorted by spend puts the heaviest agent users on top and the answer writes itself. Add what each team delivered and the order comes apart.
| Team | Devs | Cap | Spent | Delivered | AI spend / ETV | Roadmap aligned | Perf |
|---|---|---|---|---|---|---|---|
Checkout team26d at cap | 22 | $14,300 | $14,180 | 168 ETV | $84.40 | 87% | +14% |
Payments team | 16 | $10,400 | $8,940 | 74 ETV | $120.81 | 68% | +6% |
Platform team | 14 | $9,100 | $8,610 | 37 ETV | $232.70 | 54% | +3% |
Search team19d at cap | 12 | $7,800 | $7,760 | 83 ETV | $93.49 | 76% | +9% |
Mobile team | 12 | $7,800 | $7,340 | 16 ETV | $458.75 | 31% | -8% |
Growth team | 14 | $9,100 | $6,020 | 63 ETV | $95.56 | 82% | +11% |
| Org | 90 | $58,500 | $52,850 | 441 ETV | $119.84 | ||
Sorted by spend, the Checkout team is the obvious cut. Sorted by cost per ETV, it is the cheapest thing you own.
Set the rules and the policy once. We automate the rest.
You write the conditions under which a team earns more room, and the limits follow. Three factors are on screen below, around twenty more are available, and none are on by default.
Set once, by the person who owns the budget
- Roadmap alignmentabove 75%
- AI efficiencycost per ETV falling
- Engineering performancedelivered ETV rising
- + 20 other factors
- Checkout team✓ 87% Roadmap alignment, above 75%, clears✓ -22% AI efficiency, cost per ETV falling, clears✓ +14% Engineering performance, delivered ETV rising, clearsLimit raised
Cheapest unit of delivery in the org, and it has been on its ceiling since the 4th.
- Payments team✕ 68% Roadmap alignment, above 75%, misses✓ -4% AI efficiency, cost per ETV falling, clears✓ +6% Engineering performance, delivered ETV rising, clearsHeld at current
Alignment is under the bar and the cap is not binding. More tokens would not move it.
- Platform team✕ 54% Roadmap alignment, above 75%, misses✕ +9% AI efficiency, cost per ETV falling, misses✓ +3% Engineering performance, delivered ETV rising, clearsLimit reduced
Sixty percent of the month went to maintenance and fixes with no issue behind it.
- Search team✓ 76% Roadmap alignment, above 75%, clears✓ -14% AI efficiency, cost per ETV falling, clears✓ +9% Engineering performance, delivered ETV rising, clearsLimit raised
Second cheapest unit of delivery, and it hit the ceiling on nineteen of thirty days.
- Mobile team✕ 31% Roadmap alignment, above 75%, misses✕ +34% AI efficiency, cost per ETV falling, misses✕ -8% Engineering performance, delivered ETV rising, missesLimit reduced
Forty percent of the spend went to fixing work the same team shipped last quarter.
- Growth team✓ 82% Roadmap alignment, above 75%, clears✓ -18% AI efficiency, cost per ETV falling, clears✓ +11% Engineering performance, delivered ETV rising, clearsLimit raised
Every rule passes. The team is cheap per unit because it stops work that is not landing.
Six decisions, none of which reached anyone’s inbox. The two teams on their ceilings got more room, paid for by the two spending on work nobody sequenced.
What a team actually experiences.
Nothing is silent and nothing is final. Every decision carries its reasoning, and a person is one click away.
- 01
The cap binds
A team draws down its budget and stops.
- 02
It asks for more
One click. No business case, no thread to chase.
- 03
Answered in seconds
Approved or declined against your rules, reasoning attached.
- 04
Escalate any time
Not convinced? It goes to a person, same evidence attached.
- 05
Re-checked next month
If the numbers behind it move, a person is warned.
Give us a fixed budget. We will handle the distribution.
A flat per-seat cap splits the budget by headcount, which has nothing to do with who converts tokens into shipped work. The total below does not move. Only the split does.
The Mobile team sits on its floor, at 40% of the flat cap. No policy can take a team to zero, and the floor is a number you set.
Three numbers tell you if the budget is working.
What the AI added in capacity, what each engineer of it cost, and how much of it went to the roadmap. Each one against a target you set.
How much more can my team ship?
Engineers of capacity the output is worth, on top of the people actually employed.
What does that capacity cost?
What one engineer’s worth of added capacity costs a month in AI spend. Lower is better.
Is that capacity on the roadmap?
How much of the output it bought lands on roadmap priorities, not just volume.
An automated limit is a cap with better aim. It can still be aimed badly.
Output data is easy to misuse. The last of these four is where we suggest starting.
Team level by default
Both are available. Team is the default, because a number beside a name gets optimised.
Every team has a floor
A rule can restrict a limit, never remove it. You set the floor.
A mandate beats a metric
Alignment is scored against the work a team was given, not the roadmap in the abstract.
Propose before it applies
Review mode drafts the decisions first. Switch it on when you stop disagreeing.
What this changes.
Answer whether a team deserves more tokens with numbers, not a feeling
Stop throttling the team shipping the most roadmap because it had the biggest bill
Take the exception queue off your desk without giving up the ceiling
Tell the board the AI line moved because delivery moved
Stop managing AI on vibes.
Let Navigara do it.
Start in review mode: the policy drafts the decisions and you compare them against your own. Turn it on when the two stop disagreeing.