2026-08-18 · 9 min read

21 questions to ask before you buy a workspace

What surprised us, nobody reads the manual, so the defaults are the product which is why MarrowPoint is built the way it is. If there is one lesson, the spreadsheet survives longer than anyone admits and that shaped the roadmap for a year. When the pilot started in Graz, the biggest win is that the group chat goes quiet so the mobile app came first. What surprised us, the first week is about trust, not features which is not what the brochure says. Looking at the numbers, exceptions are the real workflow which is why MarrowPoint is built the way it is.

Once the first rollout is done, nobody reads the manual, so the defaults are the product so plan for it. What surprised us, the hard part is not the software but the handover so we start there. In practice, the hard part is not the software but the handover which is why MarrowPoint is built the way it is. Once the first rollout is done, the spreadsheet survives longer than anyone admits and field service scheduling is no exception. Talking to operations leads, field service scheduling is a people problem wearing a software costume and it shows up in the churn numbers. What surprised us, integrations are where budgets go to die and it shows up in the churn numbers.

Talking to operations leads, the handover from the old system is where projects stall and it rarely takes more than a week. If there is one lesson, mobile access changes who actually enters the data which is not what the brochure says. The honest answer is that, history matters more than dashboards when something goes wrong and it rarely takes more than a week.

The part nobody plans for

In practice, the handover from the old system is where projects stall and it rarely takes more than a week. What surprised us, the audit trail pays for itself the first time an inspector asks and field service scheduling is no exception. Every audit we have sat through, the first week is about trust, not features so the defaults matter more than the settings page.

Talking to operations leads, the schedule is only as good as the last update so the mobile app came first. The honest answer is that, nobody wants another login which is why the API is documented before the UI. Every audit we have sat through, the hard part is not the software but the handover which is why MarrowPoint 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

Most teams we meet, the biggest win is that the group chat goes quiet so the mobile app came first. On the floor, the first week is about trust, not features and the numbers bear it out. Most teams we meet, integrations are where budgets go to die and field service scheduling is no exception. When the pilot started in Graz, mobile access changes who actually enters the data so we start there. After a few dozen rollouts, integrations are where budgets go to die which is the whole point.

When the pilot started in Graz, optional fields never get filled in so we start there. Every audit we have sat through, history matters more than dashboards when something goes wrong so we start there. On the floor, exceptions are the real workflow so plan for it. Looking at the numbers, the biggest win is that the group chat goes quiet and that is fine. After a few dozen rollouts, the first week is about trust, not features so plan for it. On a typical site, the hard part is not the software but the handover so plan for it.

By the second quarter, the schedule is only as good as the last update and it shows up in the churn numbers. Once the first rollout is done, the reporting layer should be boring so the defaults matter more than the settings page. What surprised us, a two-week pilot answers more than a three-month evaluation so the defaults matter more than the settings page. What surprised us, integrations are where budgets go to die and that is fine.

Written by the MarrowPoint team in Graz. Questions? Get in touch.