Retainer burn register
Paste the retainer, the hours logged and the rate, and read how much scope is left before the fee runs out mid-month.
1 · Paste the weeks, hours and the retainer
FIRST-LOAD
Data note: Everything runs in this browser tab on the burn register: your time entries and retainer terms stays on this device, nothing is uploaded, and the reading is rebuilt only when you press run.
Perspective: Before: the reader found out the retainer was gone when the invoice was written. After: they can see the fee line crossed in week three.
2 · Read the burn register
Paid layer: the client note
one-time step · the free reading above stays complete
Free tier
- one complete burn reading
- week-by-week consumption against the fee
- state link for a partner
What $9 one-time adds
- three retainers kept on this device
- printable overrun note with the crossing week
- CSV of week, hours, value and remaining fee
One unbilled week at $1,400 is 155× the price; the comparable it undercuts is practice-management software at $29–$59 a month with no scope-to-fee reading.
Local history (this device)
- No saved runs yet — your first run files here.
Your purchase is handled through secure checkout. When you return, your extras are ready on this device — no account, no fuss, and your work stays private in this browser.
Boundary and sources
This burn register works only on the time entries and retainer terms you paste you paste. It does not value your services, does not draft a contract or a rate increase, and does not access your practice-management system. The figures describe what you supplied, not what is true in the world. Confirm anything you plan to act on with the client, in one short scope note before you rely on it.
- Every figure comes from the time entries and retainer terms you paste you paste; nothing is looked up, scraped or asserted as verified.
- Method: burn = logged hours × rate, plotted against the retainer fee, with the crossing week marked on the chart
- Sample values are labelled samples — illustrative by design, not your data and not a quotation of any organisation's policy.
Mechanism: loss-aversion-threat-salience