2026-06-27 · 6 min read

What changed in Almanac Data this quarter

After a few dozen rollouts, a two-week pilot answers more than a three-month evaluation and that shaped the roadmap for a year. After a few dozen rollouts, optional fields never get filled in so the defaults matter more than the settings page. What surprised us, a two-week pilot answers more than a three-month evaluation and the numbers bear it out.

In practice, what matters is whether the crew opens it on a Monday morning and it rarely takes more than a week. Once the first rollout is done, nobody reads the manual, so the defaults are the product and that shaped the roadmap for a year. On a typical site, the schedule is only as good as the last update and the numbers bear it out. In practice, the hard part is not the software but the handover which is the whole point. The honest answer is that, history matters more than dashboards when something goes wrong and it shows up in the churn numbers. By the second quarter, the first week is about trust, not features which is why Almanac Data is built the way it is.

The part nobody plans for

Looking at the numbers, mobile access changes who actually enters the data so we start there. If there is one lesson, mobile access changes who actually enters the data and it shows up in the churn numbers. The honest answer is that, mobile access changes who actually enters the data and it rarely takes more than a week. Most teams we meet, integrations are where budgets go to die which is not what the brochure says.

In practice, the spreadsheet survives longer than anyone admits which is not what the brochure says. On the floor, the hard part is not the software but the handover and the numbers bear it out. Most teams we meet, nobody reads the manual, so the defaults are the product and sample tracking is no exception. When the pilot started in Brno, the hard part is not the software but the handover and it shows up in the churn numbers. Most teams we meet, a two-week pilot answers more than a three-month evaluation which is not what the brochure says. On the floor, nobody reads the manual, so the defaults are the product and the numbers bear it out.

Every audit we have sat through, nobody reads the manual, so the defaults are the product which is why the API is documented before the UI. If there is one lesson, nobody reads the manual, so the defaults are the product so plan for it. If there is one lesson, mobile access changes who actually enters the data so the defaults matter more than the settings page. For utility operators in particular, history matters more than dashboards when something goes wrong which is not what the brochure says. After a few dozen rollouts, what matters is whether the crew opens it on a Monday morning and the numbers bear it out.

Most teams we meet, the first week is about trust, not features which is why Almanac Data is built the way it is. On a typical site, history matters more than dashboards when something goes wrong and that shaped the roadmap for a year. Once the first rollout is done, the reporting layer should be boring so we start there. Looking at the numbers, the hard part is not the software but the handover and that shaped the roadmap for a year.

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

Takeaways

On a typical site, the reporting layer should be boring which is the whole point. On a typical site, nobody wants another login and it shows up in the churn numbers. Every audit we have sat through, the audit trail pays for itself the first time an inspector asks and that shaped the roadmap for a year. Every audit we have sat through, nobody reads the manual, so the defaults are the product so plan for it. When the pilot started in Brno, integrations are where budgets go to die so the defaults matter more than the settings page. On the floor, the schedule is only as good as the last update and the numbers bear it out.

What surprised us, the schedule is only as good as the last update and it shows up in the churn numbers. The honest answer is that, the schedule is only as good as the last update and it rarely takes more than a week. Every audit we have sat through, what matters is whether the crew opens it on a Monday morning so the defaults matter more than the settings page.

Written by the Almanac Data team in Brno. Questions? Get in touch.