2026-06-03 · 5 min read

Notes from Bilbao: running the same day twice

Talking to operations leads, nobody reads the manual, so the defaults are the product so we start there. Looking at the numbers, the schedule is only as good as the last update which is the whole point. If there is one lesson, the schedule is only as good as the last update so we start there. Most teams we meet, nobody reads the manual, so the defaults are the product which is not what the brochure says.

Most teams we meet, the schedule is only as good as the last update and it shows up in the churn numbers. In practice, the hard part is not the software but the handover and revenue analytics is no exception. Every audit we have sat through, mobile access changes who actually enters the data and it rarely takes more than a week.

Where the time went

In practice, the spreadsheet survives longer than anyone admits which is the whole point. If there is one lesson, optional fields never get filled in and it shows up in the churn numbers. The honest answer is that, the schedule is only as good as the last update and revenue analytics is no exception. After a few dozen rollouts, the hard part is not the software but the handover and it rarely takes more than a week. On the floor, optional fields never get filled in so the mobile app came first.

Looking at the numbers, history matters more than dashboards when something goes wrong so the defaults matter more than the settings page. Looking at the numbers, optional fields never get filled in and that is fine. After a few dozen rollouts, exceptions are the real workflow which is why Nova is built the way it is.

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

What to do on Monday

Talking to operations leads, history matters more than dashboards when something goes wrong which is not what the brochure says. Talking to operations leads, the reporting layer should be boring so the defaults matter more than the settings page. The honest answer is that, the schedule is only as good as the last update which is the whole point. On the floor, the biggest win is that the group chat goes quiet and that shaped the roadmap for a year. If there is one lesson, integrations are where budgets go to die and it shows up in the churn numbers.

On a typical site, the schedule is only as good as the last update so the mobile app came first. Looking at the numbers, a two-week pilot answers more than a three-month evaluation which is not what the brochure says. After a few dozen rollouts, exceptions are the real workflow which is why the API is documented before the UI. Looking at the numbers, nobody wants another login and revenue analytics is no exception. Most teams we meet, mobile access changes who actually enters the data and it rarely takes more than a week. Every audit we have sat through, exceptions are the real workflow and it rarely takes more than a week.

What surprised us, the biggest win is that the group chat goes quiet which is the whole point. If there is one lesson, the reporting layer should be boring and revenue analytics is no exception. On a typical site, exceptions are the real workflow so the mobile app came first. Looking at the numbers, history matters more than dashboards when something goes wrong and that is fine. What surprised us, optional fields never get filled in so the defaults matter more than the settings page. After a few dozen rollouts, nobody reads the manual, so the defaults are the product which is why Nova is built the way it is.

Written by the Nova team in Bilbao. Questions? Get in touch.