2026-06-21 · 4 min read

What changed in TesseraCore this quarter

What surprised us, mobile access changes who actually enters the data which is why TesseraCore is built the way it is. Most teams we meet, the handover from the old system is where projects stall and that shaped the roadmap for a year. Looking at the numbers, the hard part is not the software but the handover which is why TesseraCore is built the way it is. What surprised us, exceptions are the real workflow so plan for it. After a few dozen rollouts, exceptions are the real workflow which is the whole point.

Once the first rollout is done, the spreadsheet survives longer than anyone admits so the mobile app came first. The honest answer is that, history matters more than dashboards when something goes wrong so the mobile app came first. Most teams we meet, mobile access changes who actually enters the data and it shows up in the churn numbers. On the floor, customer onboarding is a people problem wearing a software costume which is why TesseraCore is built the way it is. On the floor, a two-week pilot answers more than a three-month evaluation and it shows up in the churn numbers.

The part nobody plans for

Every audit we have sat through, history matters more than dashboards when something goes wrong and that is fine. By the second quarter, the schedule is only as good as the last update and that is fine. When the pilot started in Rotterdam, the first week is about trust, not features and the numbers bear it out. What surprised us, nobody wants another login so the mobile app came first.

In practice, nobody wants another login which is why the API is documented before the UI. In practice, nobody wants another login so we start there. Once the first rollout is done, nobody reads the manual, so the defaults are the product and customer onboarding is no exception. Every audit we have sat through, exceptions are the real workflow so we start there.

Talking to operations leads, nobody wants another login so we start there. On the floor, mobile access changes who actually enters the data which is why TesseraCore is built the way it is. In practice, nobody wants another login which is why the API is documented before the UI.

Once the first rollout is done, the audit trail pays for itself the first time an inspector asks and it rarely takes more than a week. After a few dozen rollouts, the biggest win is that the group chat goes quiet which is the whole point. Talking to operations leads, optional fields never get filled in so we start there. Most teams we meet, the schedule is only as good as the last update and that shaped the roadmap for a year.

“TesseraCore gives construction firms a single, dependable view of customer onboarding - from first request to signed-off report.”

What to do on Monday

By the second quarter, mobile access changes who actually enters the data and that is fine. When the pilot started in Rotterdam, the hard part is not the software but the handover which is why TesseraCore is built the way it is. By the second quarter, history matters more than dashboards when something goes wrong so the defaults matter more than the settings page. If there is one lesson, the spreadsheet survives longer than anyone admits so plan for it.

When the pilot started in Rotterdam, nobody wants another login which is the whole point. Looking at the numbers, history matters more than dashboards when something goes wrong which is why TesseraCore is built the way it is. Once the first rollout is done, mobile access changes who actually enters the data which is why TesseraCore is built the way it is. When the pilot started in Rotterdam, customer onboarding is a people problem wearing a software costume and it rarely takes more than a week. After a few dozen rollouts, nobody reads the manual, so the defaults are the product so the mobile app came first.

Written by the TesseraCore team in Rotterdam. Questions? Get in touch.