Build for Zero: How We Built a Zero-Emission Construction Planner
A deep dive into Build for Zero: the zero-emission construction planner that replaced spreadsheet-based energy calculations with a production platform for estimation, planning, and monitoring.
Zero-emission construction sounds like a hardware problem: batteries, electric equipment, grid connections, charging schedules. In practice, the first bottleneck is often software. Contractors need to know what a site will demand per phase, which energy mix is feasible, where grid limits bite, and whether the plan still works once construction starts.
Build for Zero was created to make that planning process repeatable. The platform replaces spreadsheet-based energy calculations with a structured calculation engine and monitoring layer for zero-energy residential construction. It supports estimation, planning, and live performance tracking from one source of truth.
The operational problem
Before Build for Zero, the calculation process depended on complex spreadsheets. They contained valuable methodology, but they were slow to use, difficult to audit, and hard to standardise across contractors. Each project carried the risk that a formula, assumption, or copied sheet would drift from the intended model.
The second problem was feedback. Actual energy performance after construction was disconnected from the estimation phase. That meant project teams could not easily compare predicted energy demand against real outcomes, and completed projects did not automatically improve the next estimate.
What we built
We built Build for Zero as a production platform around three core layers: a calculation engine, a project workflow, and a live monitoring layer. The goal was not to make a prettier spreadsheet. The goal was to encode the methodology into a repeatable, auditable process that multiple stakeholders could use consistently.
| Layer | What it does | Why it matters |
|---|---|---|
| Calculation engine | Turns project assumptions into structured energy calculations. | Reduces manual errors and makes estimates repeatable across projects. |
| Project workflow | Keeps project data, assumptions, calculations, and stakeholders in one system. | Creates a shared source of truth instead of scattered sheets and folders. |
| Monitoring layer | Tracks actual energy performance against predicted performance. | Closes the loop between estimation and real-world operation. |
From spreadsheet logic to software logic
A spreadsheet can hide complexity inside cells. Software cannot. Moving the model into a platform forced every assumption to become explicit: inputs, validations, dependencies, calculation steps, permissions, and outputs. That is where much of the value came from.
The calculation engine made the process easier to test and easier to change. When a rule changes, the update happens in one place. When a project is reviewed, the assumptions can be traced. When a contractor repeats the process, the methodology does not depend on the one person who knows the spreadsheet best.
The monitoring loop
Planning only matters if it survives contact with reality. Build for Zero connects estimation to live monitoring, so teams can compare actual energy performance against the original prediction. That makes underperformance visible early and gives teams the data they need to intervene.
This also creates a learning loop. Completed projects are no longer just archived. They become reference points for the next plan: which assumptions held, which ones drifted, and where the model needs refinement.
Results
- Estimation time was reduced by 40% by replacing a 40-tab spreadsheet process with a structured calculation engine.
- 150+ sites can be tracked through one platform with project data, calculations, and performance metrics in one place.
- Live dashboards compare actual versus predicted performance, making early intervention possible when buildings underperform.
- Three construction firms actively use the platform for zero-energy projects, with more onboarding.
What made the project work
The project worked because it started with a concrete operational workflow, not a vague transformation ambition. The workflow already existed. The spreadsheet already proved the business need. The task was to turn that fragile process into a system that could be used, audited, monitored, and improved.
That is also the pattern we look for in other construction software and AI projects: a repeated workflow, high operational value, clear inputs, measurable outputs, and a team that owns the process. When those ingredients are present, custom software can replace the workaround without adding unnecessary complexity.
Where this goes next
Zero-emission construction will only get more operationally demanding as grid constraints, equipment availability, reporting requirements, and planning complexity increase. The companies that handle this well will not rely on isolated spreadsheets. They will build operating systems around the workflows that matter.
Build for Zero is one example of that shift: practical software, real data, and enough intelligence to help teams make better decisions without removing human control.