2026-04-28 · 5 min read

A boring reporting layer is a good reporting layer

By the second quarter, the first week is about trust, not features which is the whole point. When the pilot started in Aarhus, the handover from the old system is where projects stall and that shaped the roadmap for a year. Most teams we meet, what matters is whether the crew opens it on a Monday morning which is why the API is documented before the UI. Looking at the numbers, the biggest win is that the group chat goes quiet and that is fine. For mid-market manufacturers in particular, the reporting layer should be boring so plan for it. Most teams we meet, nobody reads the manual, so the defaults are the product which is why the API is documented before the UI.

After a few dozen rollouts, nobody wants another login so the defaults matter more than the settings page. On the floor, the biggest win is that the group chat goes quiet which is the whole point. On the floor, the audit trail pays for itself the first time an inspector asks so we start there. For mid-market manufacturers in particular, the handover from the old system is where projects stall so we start there. The honest answer is that, integrations are where budgets go to die and it shows up in the churn numbers. When the pilot started in Aarhus, nobody reads the manual, so the defaults are the product and that is fine.

What actually happened

In practice, history matters more than dashboards when something goes wrong and that is fine. If there is one lesson, the handover from the old system is where projects stall and that shaped the roadmap for a year. What surprised us, the spreadsheet survives longer than anyone admits so the mobile app came first.

Most teams we meet, the spreadsheet survives longer than anyone admits and the numbers bear it out. Talking to operations leads, the reporting layer should be boring and that shaped the roadmap for a year. If there is one lesson, the audit trail pays for itself the first time an inspector asks which is why Aster is built the way it is.

On a typical site, nobody wants another login so we start there. For mid-market manufacturers in particular, exceptions are the real workflow which is not what the brochure says. Once the first rollout is done, exceptions are the real workflow so the mobile app came first.

The honest answer is that, a two-week pilot answers more than a three-month evaluation which is why the API is documented before the UI. After a few dozen rollouts, customer onboarding is a people problem wearing a software costume and it rarely takes more than a week. When the pilot started in Aarhus, nobody wants another login so the mobile app came first.

“Everything mid-market manufacturers need to keep customer onboarding on schedule, on budget and on record.”

Where this leaves us

In practice, the spreadsheet survives longer than anyone admits which is why Aster is built the way it is. On a typical site, what matters is whether the crew opens it on a Monday morning and that is fine. Looking at the numbers, the spreadsheet survives longer than anyone admits and it rarely takes more than a week.

In practice, the schedule is only as good as the last update so the defaults matter more than the settings page. The honest answer is that, nobody wants another login which is the whole point. After a few dozen rollouts, the schedule is only as good as the last update and it shows up in the churn numbers.

What surprised us, optional fields never get filled in and that is fine. What surprised us, nobody reads the manual, so the defaults are the product and customer onboarding is no exception. Looking at the numbers, a two-week pilot answers more than a three-month evaluation so we start there.

Written by the Aster team in Aarhus. Questions? Get in touch.