The milestone ledger — what makes an account stick

Twenty-three milestones across setup, integrations and getting value, each derived from the table where the fact actually lives and never hand-ticked.

What it is

The list that defines a wired-in account: signed in, logo uploaded, business info filled in, team invited, website form connected and receiving leads, Meta and Google connected, texting applied and approved, email sending set up, SmartBuild connected and pulled, leads imported, first estimate sent, a customer opened one, a customer approved one, email and text flowing both ways, and even having reported a bug or asked for a feature. Each carries a weight and a plain hint explaining why it matters.

Also called: setup progress · am I set up properly · integration checklist · adoption milestones

See it
The milestone ledger — what makes an account stick
CustomerBuildingAmountStatus
Ivy BrubakerEquipment Storage$1,390Open
Gideon Alt30×40 Garage$13,170Sent
Gideon Alt30×40 Garage$16,210Paid
Sutter Kline30×40 Garage$10,700Paid
Ronan PetschHobby Shop$13,740Open
The milestone ledger grouped Setup / Integrations / Getting value, each row with a tick or blank, its date, and its hint. Sample data — no customer information appears here.
How it works
  1. 1Each milestone reads its own source table — a logo from invoice settings, texting from the registration row, a first estimate from the estimate links.
  2. 2Milestones that do not apply to an account (SmartBuild for a builder who does not use it) are marked not applicable and excluded from the score.
  3. 3The ledger shows the date each was reached.
  4. 4Setup and integration milestones drive the score; the value milestones are counted separately.
Why we built it

The engine names why they are derived: milestones are 'each derived from the tables where the fact lives, never hand-ticked.' The hints carry the reasoning per milestone — 'Single-user accounts churn'; 'The moment they get value'; 'Engaged enough to tell us what's broken.'

The problem
  • Hand-ticked onboarding lists drift away from what is actually configured.
  • 'Set up' meant different things to different people.
  • Missing integrations were only discovered when something failed.
Sound familiar?
What you get
Setup state is derived from reality and cannot be overstated.
The specific missing piece is named, with why it matters.
Irrelevant steps do not count against an account.

See it on your own jobs

Twenty minutes, your numbers, no slide deck. We’ll build one of your real buildings in front of you and send you the estimate link at the end — yours to keep either way.

or keep browsing features →