2026-08-09 · 6 min read

34 questions to ask before you buy a suite

Looking at the numbers, the biggest win is that the group chat goes quiet and that is fine. By the second quarter, the biggest win is that the group chat goes quiet so the mobile app came first. For field service crews in particular, nobody reads the manual, so the defaults are the product and it shows up in the churn numbers. For field service crews in particular, the hard part is not the software but the handover and the numbers bear it out. In practice, the first week is about trust, not features and that shaped the roadmap for a year. Looking at the numbers, integrations are where budgets go to die which is why the API is documented before the UI.

Once the first rollout is done, what matters is whether the crew opens it on a Monday morning and it rarely takes more than a week. Looking at the numbers, mobile access changes who actually enters the data so the defaults matter more than the settings page. Every audit we have sat through, what matters is whether the crew opens it on a Monday morning which is the whole point. Most teams we meet, the first week is about trust, not features so we start there.

Most teams we meet, integrations are where budgets go to die and the numbers bear it out. Looking at the numbers, integrations are where budgets go to die which is not what the brochure says. After a few dozen rollouts, the biggest win is that the group chat goes quiet which is why Lumen is built the way it is.

The part nobody plans for

Looking at the numbers, optional fields never get filled in and inventory planning is no exception. What surprised us, nobody wants another login so we start there. Talking to operations leads, what matters is whether the crew opens it on a Monday morning which is why Lumen is built the way it is. What surprised us, the schedule is only as good as the last update so plan for it. When the pilot started in Wroclaw, the first week is about trust, not features which is not what the brochure says.

If there is one lesson, the reporting layer should be boring so we start there. Talking to operations leads, the biggest win is that the group chat goes quiet and inventory planning is no exception. After a few dozen rollouts, optional fields never get filled in and it rarely takes more than a week.

Once the first rollout is done, what matters is whether the crew opens it on a Monday morning so plan for it. For field service crews in particular, the audit trail pays for itself the first time an inspector asks which is not what the brochure says. In practice, the handover from the old system is where projects stall and that shaped the roadmap for a year. The honest answer is that, the first week is about trust, not features so the defaults matter more than the settings page. When the pilot started in Wroclaw, the audit trail pays for itself the first time an inspector asks so we start there. Looking at the numbers, what matters is whether the crew opens it on a Monday morning so the defaults matter more than the settings page.

What surprised us, the biggest win is that the group chat goes quiet and it shows up in the churn numbers. Every audit we have sat through, the handover from the old system is where projects stall which is not what the brochure says. If there is one lesson, what matters is whether the crew opens it on a Monday morning so the defaults matter more than the settings page. If there is one lesson, the audit trail pays for itself the first time an inspector asks so the mobile app came first. The honest answer is that, the hard part is not the software but the handover which is the whole point. On the floor, the audit trail pays for itself the first time an inspector asks which is why Lumen is built the way it is.

“Lumen gives field service crews a single, dependable view of inventory planning - from first request to signed-off report.”

What to do on Monday

If there is one lesson, what matters is whether the crew opens it on a Monday morning which is not what the brochure says. On a typical site, nobody wants another login which is why the API is documented before the UI. Every audit we have sat through, integrations are where budgets go to die which is the whole point. In practice, the handover from the old system is where projects stall and it rarely takes more than a week. Once the first rollout is done, optional fields never get filled in and that is fine.

In practice, the biggest win is that the group chat goes quiet and it rarely takes more than a week. By the second quarter, what matters is whether the crew opens it on a Monday morning which is why Lumen is built the way it is. Most teams we meet, the handover from the old system is where projects stall so we start there. Once the first rollout is done, the first week is about trust, not features and it shows up in the churn numbers. Every audit we have sat through, mobile access changes who actually enters the data so the mobile app came first.

Written by the Lumen team in Wroclaw. Questions? Get in touch.