The engagement, in order
| When | What | How it runs |
|---|---|---|
| Day 0 | The free audit. | Thirty minutes. You name the constraint in your own words, and it is written down before anything gets built. One page, dated, yours to keep. |
| Week 1 | Interviews. | Owner first, then the people who run the day. We map how work really moves, from the call or the lease to the money in the bank, not the org-chart version of it. |
| Week 2 | The KPI pull. | The numbers your business already produces, from the property management software, the books and the spreadsheets, next to industry benchmarks. Nothing new gets installed to do it. |
| Week 3 | The constraint map. | Three to five constraints, ranked by what each one costs. It decides everything that gets built. A constraint that costs little stays on the map and waits. |
| Day 30 | The first build, live on your data. | The most expensive constraint gets built first, inside the software you already run, on a staging copy of your data. The first working screen goes up in a day. Live once you have watched it work. |
| Weekly | Sixty minutes, the same way. | The number, the bottleneck, the one-page plan, the fix on screen, the next action. One working build a month, in your software, with its before and after. |
| Day 90 | The re-score. | The same yardstick, run again, beside day zero. Movement in the numbers the diagnosis started from, or a plain statement that it has not moved yet. |
| Day 180 | The next department. | The re-score picks the next constraint. Someone from the first department teaches the next one, on their own work. Done when you own what was built. |
The weekly hourruns the same way every week: the number, the bottleneck, the one-page plan, the fix on screen, the next action.