LeanScale // BUILD LOG SNAPSHOT 2026-09-02 Start a conversation
PUBLIC BUILD LOG · REBUILT DAILY

We do not talk about velocity. We publish it.

LeanScale is a go-to-market consultancy that builds its own tooling — dashboards, calculators, portals, migration plans — and ships it while the engagement is still running. Every figure here is generated from our deploy and commit history. Client names are withheld. The numbers are not.

2,214 DEPLOYS
12 WEEKS · 80 DAYS · 255 REPOS · 6,075 COMMITS
MEDIAN BUILD9s
LIVE PROPERTIES271
ACTIVE STREAK59d
PEOPLE SHIPPING15
01 / CADENCE

80 days of signal.

One spoke per day, clockwise from 15 JUN. Length and brightness are that day's production deploys. Hover a spoke and the centre reads it out.

2026-06-15 → 2026-09-02
Monday 15 June: 10 deploysTuesday 16 June: 21 deploysWednesday 17 June: 23 deploysThursday 18 June: 11 deploysFriday 19 June: 2 deploysSaturday 20 June: no deploysSunday 21 June: no deploysMonday 22 June: 11 deploysTuesday 23 June: 12 deploysWednesday 24 June: 11 deploysThursday 25 June: 32 deploysFriday 26 June: 3 deploysSaturday 27 June: no deploysSunday 28 June: no deploysMonday 29 June: 5 deploysTuesday 30 June: 12 deploysWednesday 1 July: 56 deploysThursday 2 July: 26 deploysFriday 3 July: no deploysSaturday 4 July: no deploysSunday 5 July: no deploysMonday 6 July: 31 deploysTuesday 7 July: 24 deploysWednesday 8 July: 55 deploysThursday 9 July: 46 deploysFriday 10 July: 36 deploysSaturday 11 July: 3 deploysSunday 12 July: 1 deployMonday 13 July: 28 deploysTuesday 14 July: 55 deploysWednesday 15 July: 45 deploysThursday 16 July: 36 deploysFriday 17 July: 132 deploysSaturday 18 July: 14 deploysSunday 19 July: 1 deployMonday 20 July: 63 deploysTuesday 21 July: 86 deploysWednesday 22 July: 39 deploysThursday 23 July: 166 deploys, busiest day in the windowFriday 24 July: 89 deploysSaturday 25 July: 4 deploysSunday 26 July: 3 deploysMonday 27 July: 41 deploysTuesday 28 July: 41 deploysWednesday 29 July: 32 deploysThursday 30 July: 40 deploysFriday 31 July: 72 deploysSaturday 1 August: 8 deploysSunday 2 August: 3 deploysMonday 3 August: 41 deploysTuesday 4 August: 29 deploysWednesday 5 August: 43 deploysThursday 6 August: 32 deploysFriday 7 August: 48 deploysSaturday 8 August: 8 deploysSunday 9 August: 53 deploysMonday 10 August: 44 deploysTuesday 11 August: 28 deploysWednesday 12 August: 36 deploysThursday 13 August: 12 deploysFriday 14 August: 45 deploysSaturday 15 August: 7 deploysSunday 16 August: 4 deploysMonday 17 August: 46 deploysTuesday 18 August: 43 deploysWednesday 19 August: 19 deploysThursday 20 August: 36 deploysFriday 21 August: 36 deploysSaturday 22 August: 26 deploysSunday 23 August: 3 deploysMonday 24 August: 13 deploysTuesday 25 August: 27 deploysWednesday 26 August: 12 deploysThursday 27 August: 9 deploysFriday 28 August: 42 deploysSaturday 29 August: 3 deploysSunday 30 August: 3 deploysMonday 31 August: 22 deploysTuesday 1 September: 10 deploysWednesday 2 September: 5 deploys
59LONGEST STREAK
166BEST DAY · 23 JUL
73 OF 80 DAYS SHIPPED
SHIPPED · 73 DAYS RECORD · 166 DEPLOYS QUIET · 7 DAYS

Every spoke carries its date and exact count as text. 7 quiet days are shown, not smoothed away.

02 / TREND

One spike is a launch. Twelve is a habit.

Three facts about the same 12 weeks: how much shipped, how much of the estate moved, and how many people had their hands on it.

DEPLOYS PER WEEK PEAK 450
Week of 15 JUN: 67 deploysWeek of 22 JUN: 69 deploysWeek of 29 JUN: 99 deploysWeek of 6 JUL: 196 deploysWeek of 13 JUL: 311 deploysWeek of 20 JUL: 450 deploysWeek of 27 JUL: 237 deploysWeek of 3 AUG: 254 deploysWeek of 10 AUG: 176 deploysWeek of 17 AUG: 209 deploysWeek of 24 AUG: 109 deploysWeek of 31 AUG: 37 deploys, week still in progress Week of 15 JUN: 16 properties touchedWeek of 22 JUN: 20 properties touchedWeek of 29 JUN: 25 properties touchedWeek of 6 JUL: 30 properties touchedWeek of 13 JUL: 46 properties touchedWeek of 20 JUL: 48 properties touchedWeek of 27 JUL: 48 properties touchedWeek of 3 AUG: 89 properties touchedWeek of 10 AUG: 37 properties touchedWeek of 17 AUG: 28 properties touchedWeek of 24 AUG: 21 properties touchedWeek of 31 AUG: 21 properties touched, week still in progress Week of 15 JUN: 7 people shippingWeek of 22 JUN: 9 people shippingWeek of 29 JUN: 5 people shippingWeek of 6 JUL: 7 people shippingWeek of 13 JUL: 10 people shippingWeek of 20 JUL: 11 people shippingWeek of 27 JUL: 9 people shippingWeek of 3 AUG: 9 people shippingWeek of 10 AUG: 11 people shippingWeek of 17 AUG: 9 people shippingWeek of 24 AUG: 10 people shippingWeek of 31 AUG: 6 people shipping, week still in progress

Production deploys per week. The 11-week average is 198; the week of 20 JUL peaked at 450. The last point sits past the dashed line — a part-week still in progress, not a decline.

03 / PIPELINE

9 seconds from push to live. 2,214 times.

The whole route from a commit to a live property, instrumented end to end — including the stage where things break.

01 · COMMIT
6,075
Commits pushed

Across 255 repositories. 44 of them active in the busiest single week.

02 · BUILD
9s
Median build

Push to live, median. 7.6 hours of compute bought the entire quarter.

03 · REVIEW
335
Preview builds

Every one reviewed on a real URL before production saw it.

04 · PRODUCTION
80%
Shipped first time

2,214 of 2,753 attempts. 539 failed.

539

builds failed in 12 weeks, and we publish that too. A 100% success rate would only mean we were not deploying often enough to find out.

04 / THE ESTATE

271 live properties. One dot each.

No names, no screenshots, no logo wall — that is the deal we made to publish any of this. The shape of the work survives the redaction.

157 INTERNAL 106 CLIENT-FACING 8 PUBLIC
Custom app124
Enablement19
Calculator & tooling14
Handoff & kickoff14
Dashboard & reporting13
Diagnostic13
Internal R&D13
QBR11
Weekly sync11
Client portal10
Research9
Library8
Proposal & scoping8
Micro-app4
ONE DEPLOY EVERY 52 MINUTES

The next 52 minutes are spoken for. The ones after that are open.

Tell us what your go-to-market motion is missing. The first working version usually exists before the second call.