AI adoption · Navigara
Who on your team uses AI,
and how deeply?
Navigara reads your AI tools’ own usage data and scores every engineer on five habits. One level each. One next step each. No survey.
curl -fsSL https://navigara.com/cli | shRun it on a laptop. First adoption data in seconds.
- Curious 1
- Regular 7
- Fluent 10
- Delegator 5
- Orchestrator 5
Trusted by engineering teams




Adoption is five habits, not a feeling.
Claude Code, Codex, Cursor and Copilot report what they do: every prompt, every agent minute, every tool call. Navigara turns that into five habits per person, each with a target. Hands-off is this engineer’s lowest habit, so it is the next step.
How the score is earned. A picture, not this engineer’s data.
What it is
Agent minutes per prompt before a person steps in. Short prompts with constant corrections are pairing; a long run is delegation.
Agent minutes per prompt1.2 min of 6 min target
Do this first
Give the agent a whole task in one prompt. Now 1.2 min, target 6.
Then try
- Write the acceptance criteria into the prompt, so the agent knows when it is done.
- Let the agent run the tests and fix its own failures before it comes back to you.
Five scores average into one level.
Each level is a fifth of the score, over the trailing 90 days, recomputed every day. A team’s level is the average of its active people: one person is one vote. Coach, do not rank.
- 1Curious0–20%Tries AI now and then.
- 2Regular20–40%Uses AI most weeks, mostly for quick questions.
- 3Fluent40–60%AI is a daily habit.
- 4Delegator60–80%Hands whole tasks to agents and lets them finish.
- 5Orchestrator80–100%Runs several agents at once, and work goes on while away.
Every engineer gets a next step, not a rank.
The next step is the habit with the lowest score. This Fluent engineer uses AI 5.2 days a week, but their prompts run 1.2 minutes before they step in (target: 6). Their own page shows that one habit and what to do first, not a ranking of the team.
One engineer, one page. It shows their own level and one habit to work on, never a leaderboard.
Give the agent a whole task in one prompt. Now 1.2 min, target 6.
Then try
- Write the acceptance criteria into the prompt, so the agent knows when it is done.
- Let the agent run the tests and fix its own failures before it comes back to you.
Put the level next to the work it delivered.
Levels show habits, not output. So the adoption page plots every team by level and by delivered work per person. In this illustrative company Payments, the highest-level team, delivers 8.1 ETV per person a week; Data delivers 3.4. Then the price of that work, per team and per week, is one click away in AI spend, and the capacity it added in AI ROI.
ETV is the unit of delivered work on the performance page. Illustrative teams, not customer results.
- Payments8.1 ETV / person / weekDelegator · 105 people · $84 per ETV
- Platform6.2 ETV / person / weekFluent · 82 people · $71 per ETV
- Mobile5.0 ETV / person / weekFluent · 93 people · $96 per ETV
- Data3.4 ETV / person / weekRegular · 70 people · $128 per ETV
One command. First adoption data in seconds.
curl -fsSL https://navigara.com/cli | shOne command per laptop
Installs the Navigara CLI, signs in, uploads past Claude Code and Codex sessions and streams new ones. Cursor and Copilot report live, with no history upload. A whole team: the same installer through your MDM.
Usage within minutes, habits the next day
AI spend shows up in minutes. The five habits and the first dots appear the next day; a level needs 90 days of history, which the Claude Code and Codex upload brings with it.
No source code leaves the machine
The tools send usage metadata: sessions, models, cost, tokens, durations, tool names. Prompt text is optional and can be switched off. Read-only everywhere.
Developer AI adoption questions.
What does developer AI adoption measure?
Five habits per person, read from the AI tools’ own telemetry: how often they use AI, how long agents run, how much they hand over per prompt, how many agents run at once, and how long agents run with nobody steering. Each habit is scored against a target, over the trailing 90 days, and recomputed every day.
Does higher developer AI adoption mean better productivity?
Only if delivered work moves too. The adoption page plots every team by level and by ETV per active person, and the AI spend page prices that work per team and per week. When usage climbs and delivery stays flat, you see it on the same screen.
See your team’s
AI adoption by tomorrow.
Free trial, one command on each laptop, no survey. Where Claude Code or Codex history is already on the laptop, every person gets a first level the next day.