THE BUILD — Renovation Project OS Brain
THE BUILD — Renovation Project OS Brain
For a renovation that finishes. One orchestrator plus ten specialists that model the budget with a contingency reflecting what you are actually opening up, sequence the trades so nobody waits on anyone, and price what each week of delay really costs you.
Renovations overrun on money and on time, and those are the same problem. The budget script models your scope with a contingency derived from the type of work rather than a flat ten percent, because structural work and anything involving old wiring behave nothing like a kitchen swap. It also prices delay: if you are paying rent elsewhere or carrying a bridging loan, every week of slip has a number, and knowing that number changes which corners you are willing to cut. Most people discover it retrospectively.
build_budget.py
Models scope cost with contingency weighted by work type rather than a flat percentage, calculates cost of delay per week from your carrying costs, and flags where contingency is already spent against a stated completion percentage. Every OS Brain in this drop carries its own executable component, so the judgement calls stay with you and the arithmetic stops being a matter of opinion. Runs anywhere Python runs, and the specialists still work on their own if you never open it.
Say it in plain words — it works out the rest
Inside · orchestrator + 10 specialists
Where it refuses to skip ahead
- No budget without weighted contingency — a flat ten percent on structural work is a guess dressed as a plan.
- No quote comparison until scope matches — builders price what they were shown, and they were shown different things.
- No variation without a written price — verbal variations are the single largest source of renovation disputes.
- Contingency gone before halfway means stop — pressing on from there is how projects end unfinished.