The tracker proves the velocity. The velocity sells the engine.
This is not a tracker product. It is a velocity proof system. You don't sell the dashboard — you sell the operating method that produces the dashboard. Buyers see the readout, then they want the engine.
1 · What it is
A re-usable timed-session tracker. Drop in a session window (start → end) and a list of items. The tracker computes:
Time elapsed / time remaining with live countdown.
Items shipped, broken down by type (page · doc · api · section · fix).
£ market value at a configurable rate-card.
Velocity — items/hour and £/hour.
Comparison panel — what an agency, in-house team, or solo dev would have taken.
Live feed — last items shipped with timestamps and prices.
Today's session: The Build-a-thon (1pm 02 May → 1pm 03 May 2026). Future sessions append a new dict to TRACKER_SESSIONS in main.py — days, weeks, months, hours, sessions, all supported by the same engine.
Set at the conservative end of UK agency rates. A bespoke landing page from a small agency runs £2-5k. A custom API endpoint with validation runs £1-3k. A small dashboard section runs £400-1,000. A typed validation/hardening fix runs £200-600 depending on complexity. The tracker uses the lower bound on purpose — when the readout still says £10K+ in a day, it's a floor, not a ceiling.
3 · Why velocity becomes the sale
Most operators show finished things. You show the rate at which finished things appear. That changes the conversation.
"He's not lying. He's not exaggerating. He's not asking me to believe. He's already done it — last night, in twelve hours, eleven items, £15,000 of agency-equivalent work. So what does he do this month if I back him?"
The tracker collapses the entire investor / partner / employer due-diligence question into a single readout. They don't have to take your word — the receipt is right there.
4 · Who buys it
Buyer
What they get
Why they pay
Agencies
White-label tracker for client engagements
Prove velocity to retain clients · justify retainers
Operators running build-sprints
Single-session tracker per sprint
Live proof for stakeholders mid-sprint
Investors evaluating teams
Read-only dashboard sent by founder
Velocity as due-diligence signal
Founders / freelancers
Personal tracker, multi-session
Receipts when raising · pitching · hiring
You · Sovereign
Your own kingdom-pace ledger
Memory · proof · velocity discipline
5 · Pricing tiers
Single Session
£99/mo
One open tracker · single buyer · personal use
Multi-Session
£499/mo
Up to 50 sessions · custom rate-card · team account
Agency White-Label
£2,400 install
Embed in agency portal · agency branding · client-facing
Sovereign Edition
Not for sale
The original. Stays in the kingdom.
6 · The doctrine line
"I'm not showing enough. That's the leverage. When I send the tracker, they see the velocity. They don't have to believe me — the receipt is right there. That's not a pitch. That's an invitation."
7 · Re-usability schema
Every session is a single dict in TRACKER_SESSIONS:
{
"id": "buildathon-may-2026",
"label": "The Build-a-thon",
"subtitle": "24-Hour Sovereign Build Sprint",
"start_iso": "2026-05-02T13:00:00",
"end_iso": "2026-05-03T13:00:00",
"items_attr": "BUILDATHON_ITEMS",
"active": True
}
Future weeks-long or months-long sessions: same dict, longer window. Hours-long session: same dict, shorter window. Multi-session view: list of dicts. The compute function handles them all.
8 · How it dual-homes (per Build-a-thon doctrine)
Original lives in the Build-a-thon ledger as build #10 (page) and #11 (this MD).
Duplicate of the page → Hub Directory pill on the dashboard.
Duplicate of MD-433 → Sovereign Library (NUMBERED_MASTER_DOCS).
Tracker is not a dashboard pin — per dashboard MD policy (MD-273+ go to Library only).