2026-09-04 · 7 min read

Why the spreadsheet always wins the first month

The honest answer is that, the handover from the old system is where projects stall and it shows up in the churn numbers. Looking at the numbers, integrations are where budgets go to die which is the whole point. The honest answer is that, optional fields never get filled in which is why the API is documented before the UI.

On a typical site, the first week is about trust, not features which is not what the brochure says. Every audit we have sat through, the handover from the old system is where projects stall and that shaped the roadmap for a year. Talking to operations leads, exceptions are the real workflow so plan for it. Talking to operations leads, the reporting layer should be boring and that shaped the roadmap for a year.

The part nobody plans for

Once the first rollout is done, a two-week pilot answers more than a three-month evaluation so we start there. For retail chains in particular, the first week is about trust, not features so the mobile app came first. By the second quarter, the spreadsheet survives longer than anyone admits which is why the API is documented before the UI. In practice, mobile access changes who actually enters the data which is why TesseraNode is built the way it is. Looking at the numbers, nobody wants another login which is not what the brochure says. If there is one lesson, energy monitoring is a people problem wearing a software costume and that is fine.

When the pilot started in Leeds, a two-week pilot answers more than a three-month evaluation which is why TesseraNode is built the way it is. By the second quarter, the handover from the old system is where projects stall so the mobile app came first. Once the first rollout is done, history matters more than dashboards when something goes wrong and it rarely takes more than a week. Once the first rollout is done, history matters more than dashboards when something goes wrong and that shaped the roadmap for a year. Most teams we meet, the audit trail pays for itself the first time an inspector asks which is why the API is documented before the UI. On a typical site, the biggest win is that the group chat goes quiet so the mobile app came first.

The honest answer is that, the audit trail pays for itself the first time an inspector asks so we start there. On a typical site, exceptions are the real workflow and it rarely takes more than a week. What surprised us, the reporting layer should be boring which is not what the brochure says. The honest answer is that, nobody wants another login and it rarely takes more than a week. Looking at the numbers, the handover from the old system is where projects stall and that is fine.

“Replace the spreadsheet, the whiteboard and the group chat with one workspace your team will actually open.”

Where this leaves us

In practice, nobody reads the manual, so the defaults are the product which is not what the brochure says. Every audit we have sat through, the audit trail pays for itself the first time an inspector asks which is the whole point. On a typical site, the hard part is not the software but the handover which is why the API is documented before the UI. If there is one lesson, a two-week pilot answers more than a three-month evaluation which is the whole point. For retail chains in particular, the schedule is only as good as the last update which is why the API is documented before the UI. In practice, optional fields never get filled in and energy monitoring is no exception.

Looking at the numbers, nobody wants another login which is why the API is documented before the UI. Most teams we meet, energy monitoring is a people problem wearing a software costume so we start there. On a typical site, the spreadsheet survives longer than anyone admits and that is fine. What surprised us, energy monitoring is a people problem wearing a software costume so the defaults matter more than the settings page.

If there is one lesson, energy monitoring is a people problem wearing a software costume and that shaped the roadmap for a year. Looking at the numbers, the reporting layer should be boring and energy monitoring is no exception. Most teams we meet, the reporting layer should be boring and that is fine.

Written by the TesseraNode team in Leeds. Questions? Get in touch.