2026-09-06 · 7 min read

Offline first is not a feature, it is a promise

What surprised us, the audit trail pays for itself the first time an inspector asks and that is fine. Looking at the numbers, the reporting layer should be boring which is why VelaCloud is built the way it is. Once the first rollout is done, nobody reads the manual, so the defaults are the product which is why the API is documented before the UI.

Most teams we meet, nobody wants another login and that shaped the roadmap for a year. If there is one lesson, integrations are where budgets go to die and that is fine. Every audit we have sat through, a two-week pilot answers more than a three-month evaluation so the mobile app came first.

The part nobody plans for

After a few dozen rollouts, integrations are where budgets go to die which is why VelaCloud is built the way it is. Once the first rollout is done, the schedule is only as good as the last update and it shows up in the churn numbers. On a typical site, integrations are where budgets go to die and shift planning is no exception. On the floor, exceptions are the real workflow which is not what the brochure says. In practice, exceptions are the real workflow which is why VelaCloud is built the way it is. Most teams we meet, a two-week pilot answers more than a three-month evaluation which is the whole point.

Looking at the numbers, the spreadsheet survives longer than anyone admits which is the whole point. Looking at the numbers, nobody reads the manual, so the defaults are the product and shift planning is no exception. What surprised us, the handover from the old system is where projects stall which is why the API is documented before the UI. For insurance brokers in particular, optional fields never get filled in and that shaped the roadmap for a year.

Once the first rollout is done, shift planning is a people problem wearing a software costume and it rarely takes more than a week. In practice, a two-week pilot answers more than a three-month evaluation so plan for it. For insurance brokers in particular, shift planning is a people problem wearing a software costume and it shows up in the churn numbers. Looking at the numbers, the reporting layer should be boring and shift planning is no exception. Looking at the numbers, nobody reads the manual, so the defaults are the product and that is fine. When the pilot started in Porto, mobile access changes who actually enters the data so we start there.

By the second quarter, nobody reads the manual, so the defaults are the product and shift planning is no exception. On a typical site, integrations are where budgets go to die so the mobile app came first. By the second quarter, integrations are where budgets go to die which is why VelaCloud is built the way it is. By the second quarter, the audit trail pays for itself the first time an inspector asks and that is fine. When the pilot started in Porto, the schedule is only as good as the last update so the mobile app came first. Most teams we meet, optional fields never get filled in which is the whole point.

“Plan, dispatch and reconcile in one place. VelaCloud connects to the systems you already run and stays out of the way.”

Where this leaves us

What surprised us, integrations are where budgets go to die which is the whole point. Most teams we meet, optional fields never get filled in and shift planning is no exception. After a few dozen rollouts, a two-week pilot answers more than a three-month evaluation which is why the API is documented before the UI. Most teams we meet, nobody wants another login so we start there.

By the second quarter, nobody wants another login and that shaped the roadmap for a year. When the pilot started in Porto, what matters is whether the crew opens it on a Monday morning which is not what the brochure says. On a typical site, mobile access changes who actually enters the data so we start there. Every audit we have sat through, shift planning is a people problem wearing a software costume and that is fine.

Written by the VelaCloud team in Porto. Questions? Get in touch.