What is Ghost%?
Last updated June 6, 2026
Ghost% is a single metric that shows how much engineering work a team actually delivers, measured against a pre-AI baseline. DevGhost estimates the cognitive effort behind every code change — expressed in the hours a mid-level developer who knows the codebase and works without AI would need — and compares the team's average daily output to that baseline. At 100%, the team delivers roughly one reference developer's day of difficulty per working day; above 100%, it delivers more — the leverage that modern tooling and AI provide.
The formula
Ghost% = (average daily effort ÷ baseline) × 100
The baseline
The baseline — the "Ghost norm" — is 3 hours of focused, productive code output per working day. That figure reflects the deep-work capacity of one reference developer — sustained focus, not an eight-hour clock. "Effort" is the estimated difficulty of the changes a team shipped; average daily effort spreads that difficulty across the days work actually happened.
How to read it
The result falls into four bands — a starting point for a conversation, not a grade:
- 120% and above — the team consistently delivers more than the pre-AI baseline.
- 100% to 120% — at or above the baseline.
- 80% to 100% — slightly below the baseline.
- Below 80% — well below the baseline.
Why it rises with AI
When a team adopts AI and delivers more difficulty per day than the pre-AI baseline, Ghost% climbs above 100%. That gap — the AI leverage — is the headline number DevGhost surfaces: how much extra a team produces beyond what was normal before these tools existed.
What Ghost% is not
Ghost% is a probabilistic estimate produced by algorithms and AI — not a measurement of any individual's ability, diligence, or worth, and not a statement of fact about a person. It is built as a team- and portfolio-level signal for owners and managers, not an automated verdict on an individual, and it must not be the sole or primary basis for decisions about people such as hiring, pay, promotion, or dismissal. Read it as a pointer to where to look, then look.
It needs no time tracking, no screen capture, and no keystroke logging. DevGhost reads only the code changes themselves.