Knowledge loss calculator
When an engineer leaves, the cost isn't just hiring a replacement. It's the interpretive layer that walks out the door. See what each departure actually costs.
Your inputs
Model a specific departure, or a typical one for your team.
Years at the company
Affects replacement multiplier
For remaining engineers consumed by transfer
1 = tribal knowledge only, 10 = comprehensive
Recruiting, comp differential, signing, for a comparable replacement.
112 hours of remaining team time spent transferring context.
144 hours re-trying ruled-out approaches and re-deciding what was already decided.
3-month ramp at ~50% productivity for the replacement.
Declared-state records capture the interpretive layer that usually exits with the departing engineer. The decisions and rationale stay in the record, and the re-discovery cost shrinks significantly.
Build the context layer →Email yourself these results
A copy to share with your team, no signup required.
What one person knows should not leave with them.
See this on your team’s questions, not ours.