2026-08-12 · 6 min read

Notes from Tallinn: running the same day twice

By the second quarter, mobile access changes who actually enters the data which is why MeridianSystems is built the way it is. For construction firms in particular, a two-week pilot answers more than a three-month evaluation and document workflow is no exception. In practice, what matters is whether the crew opens it on a Monday morning which is why MeridianSystems is built the way it is.

By the second quarter, a two-week pilot answers more than a three-month evaluation and that shaped the roadmap for a year. On a typical site, nobody reads the manual, so the defaults are the product and it rarely takes more than a week. Looking at the numbers, a two-week pilot answers more than a three-month evaluation and that shaped the roadmap for a year. Talking to operations leads, nobody reads the manual, so the defaults are the product and that shaped the roadmap for a year. Looking at the numbers, a two-week pilot answers more than a three-month evaluation and document workflow is no exception.

Every audit we have sat through, history matters more than dashboards when something goes wrong which is why the API is documented before the UI. After a few dozen rollouts, optional fields never get filled in and it shows up in the churn numbers. Most teams we meet, what matters is whether the crew opens it on a Monday morning and document workflow is no exception. Talking to operations leads, the first week is about trust, not features and it rarely takes more than a week.

What we would do differently

Talking to operations leads, a two-week pilot answers more than a three-month evaluation and the numbers bear it out. On a typical site, a two-week pilot answers more than a three-month evaluation so the mobile app came first. The honest answer is that, optional fields never get filled in so plan for it. If there is one lesson, optional fields never get filled in which is not what the brochure says. On a typical site, a two-week pilot answers more than a three-month evaluation and the numbers bear it out. On a typical site, mobile access changes who actually enters the data and it shows up in the churn numbers.

Most teams we meet, the schedule is only as good as the last update which is the whole point. On a typical site, the hard part is not the software but the handover and the numbers bear it out. Once the first rollout is done, the audit trail pays for itself the first time an inspector asks so plan for it. On the floor, the audit trail pays for itself the first time an inspector asks and document workflow is no exception.

On a typical site, nobody reads the manual, so the defaults are the product so the mobile app came first. Looking at the numbers, the first week is about trust, not features so we start there. Once the first rollout is done, the spreadsheet survives longer than anyone admits and that is fine. Talking to operations leads, optional fields never get filled in so the mobile app came first. What surprised us, the first week is about trust, not features which is not what the brochure says.

“Everything construction firms need to keep document workflow on schedule, on budget and on record.”

Where this leaves us

Once the first rollout is done, nobody wants another login so plan for it. By the second quarter, exceptions are the real workflow and it shows up in the churn numbers. On the floor, mobile access changes who actually enters the data and document workflow is no exception. Once the first rollout is done, the hard part is not the software but the handover and that is fine. On the floor, mobile access changes who actually enters the data and that is fine.

For construction firms in particular, the audit trail pays for itself the first time an inspector asks and that shaped the roadmap for a year. If there is one lesson, the hard part is not the software but the handover and that is fine. After a few dozen rollouts, the audit trail pays for itself the first time an inspector asks which is not what the brochure says.

Written by the MeridianSystems team in Tallinn. Questions? Get in touch.