2026-06-30 · 4 min read

Pricing per seat, explained honestly

What surprised us, the schedule is only as good as the last update and that is fine. Once the first rollout is done, integrations are where budgets go to die and that is fine. In practice, mobile access changes who actually enters the data so plan for it. The honest answer is that, nobody reads the manual, so the defaults are the product so the defaults matter more than the settings page.

The honest answer is that, the spreadsheet survives longer than anyone admits so plan for it. If there is one lesson, optional fields never get filled in so plan for it. Talking to operations leads, mobile access changes who actually enters the data and it rarely takes more than a week. Once the first rollout is done, integrations are where budgets go to die which is why Harbor Stack is built the way it is. On the floor, exceptions are the real workflow so the defaults matter more than the settings page. On the floor, the biggest win is that the group chat goes quiet and it rarely takes more than a week.

The part nobody plans for

On the floor, sample tracking is a people problem wearing a software costume so we start there. Looking at the numbers, the spreadsheet survives longer than anyone admits which is the whole point. On the floor, the hard part is not the software but the handover and that shaped the roadmap for a year. For utility operators in particular, the first week is about trust, not features which is not what the brochure says. Looking at the numbers, a two-week pilot answers more than a three-month evaluation and sample tracking is no exception.

Talking to operations leads, the reporting layer should be boring so we start there. Once the first rollout is done, a two-week pilot answers more than a three-month evaluation so we start there. For utility operators in particular, the hard part is not the software but the handover so plan for it.

In practice, history matters more than dashboards when something goes wrong which is why Harbor Stack is built the way it is. After a few dozen rollouts, the handover from the old system is where projects stall so plan for it. Talking to operations leads, what matters is whether the crew opens it on a Monday morning so we start there. In practice, what matters is whether the crew opens it on a Monday morning and it shows up in the churn numbers. By the second quarter, the spreadsheet survives longer than anyone admits which is why the API is documented before the UI.

When the pilot started in Aarhus, mobile access changes who actually enters the data and sample tracking is no exception. Looking at the numbers, the schedule is only as good as the last update and it rarely takes more than a week. By the second quarter, history matters more than dashboards when something goes wrong which is why the API is documented before the UI. On the floor, optional fields never get filled in and that shaped the roadmap for a year. Once the first rollout is done, the handover from the old system is where projects stall and it shows up in the churn numbers. On the floor, mobile access changes who actually enters the data and that shaped the roadmap for a year.

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

Takeaways

In practice, sample tracking is a people problem wearing a software costume which is why Harbor Stack is built the way it is. On the floor, what matters is whether the crew opens it on a Monday morning and sample tracking is no exception. Every audit we have sat through, what matters is whether the crew opens it on a Monday morning which is why Harbor Stack is built the way it is.

The honest answer is that, the reporting layer should be boring and it rarely takes more than a week. By the second quarter, history matters more than dashboards when something goes wrong which is not what the brochure says. Looking at the numbers, the hard part is not the software but the handover which is why the API is documented before the UI. On the floor, the reporting layer should be boring and that shaped the roadmap for a year. For utility operators in particular, mobile access changes who actually enters the data so plan for it. The honest answer is that, the reporting layer should be boring which is the whole point.

Written by the Harbor Stack team in Aarhus. Questions? Get in touch.