Savings

Cut the waste, and prove it worked.

Earlyman ranks the fixes by what they would save, tests each one, and only counts a saving once its verdict is in.

Savings · sample weekSample data

Saved so far, verified

$4.20 a week

1Same file read again and again$4.20 a weekestimateTestingSaved
2Big model on a small task$2.60 a weekestimateTestingTesting
3Retries on a broken tool$1.10 a weekestimateTestingRolled back

Nothing counts as saved until its verdict is in.

  • FindPatterns that waste tokens, found in your own sessions.
  • TestEach fix gets a baseline and a verdict date.
  • Keep or roll backA change that did not help is rolled back.
How it works

How savings are tested. One fix at a time, against a baseline.

  1. 01Find the wasteEarlyman spots patterns that burn tokens in your own sessions, such as the same file read again and again.
  2. 02Test one fix at a timeEach fix starts with a baseline and a verdict date, so before and after can be compared fairly.
  3. 03Keep what workedA fix that saved money is kept. One that did not is rolled back, and nothing counts until the verdict is in.
Try it

Clear what needs you.

The real layout, with sample data. Nothing you click is sent or saved.

Earlyman · HomeInteractive demo · Sample data

Good morning. 4 things need you. Most urgent: a stuck agent is still costing money.

5-hour session62%heads-up at 80 % · resets in 1 h 40 m
This week · all models38%resets Sunday
This month · all vendors$412 of $600Claude Code, API keys, GPU pods
Needs you4 open
  • An agent has made no progress for 2 hA tool call is still pending. Stop it or start it again.$3.10 / h
  • PR #214 broke a rule: force push to mainBlocked before it ran. The agent carried on.1 rule
  • Search subagents run on the largest model418 of 483 this week. A smaller model is enough for search.−$38 / week
  • This session has run for 9 hHand off to a fresh session to stop paying for old context.−$6 / day

Questions

Does Earlyman change my setup on its own?

Only small changes marked safe, and each one is listed with its verdict date. Any change can be rolled back in one step.

How do I know a saving is real?

Each fix is compared against its baseline over the same kind of work, and shows saved as zero until its verdict lands.

What kind of fixes does it suggest?

Things like avoiding repeated reads, using a smaller model for small tasks, and stopping retries on a broken tool.