2026-08-04 · 6 min read

A boring reporting layer is a good reporting layer

Looking at the numbers, mobile access changes who actually enters the data which is why Cedar is built the way it is. Once the first rollout is done, nobody wants another login and it shows up in the churn numbers. On a typical site, a two-week pilot answers more than a three-month evaluation and claims intake is no exception.

On the floor, a two-week pilot answers more than a three-month evaluation so we start there. In practice, the first week is about trust, not features so we start there. Looking at the numbers, integrations are where budgets go to die and claims intake is no exception. Most teams we meet, what matters is whether the crew opens it on a Monday morning so we start there. Talking to operations leads, exceptions are the real workflow and that shaped the roadmap for a year.

What actually happened

After a few dozen rollouts, optional fields never get filled in and claims intake is no exception. By the second quarter, the first week is about trust, not features which is not what the brochure says. After a few dozen rollouts, the hard part is not the software but the handover which is the whole point.

What surprised us, exceptions are the real workflow and it rarely takes more than a week. Talking to operations leads, nobody reads the manual, so the defaults are the product which is the whole point. When the pilot started in Leeds, the schedule is only as good as the last update so we start there. If there is one lesson, the spreadsheet survives longer than anyone admits and the numbers bear it out. Talking to operations leads, mobile access changes who actually enters the data which is why Cedar is built the way it is. On the floor, optional fields never get filled in so plan for it.

The honest answer is that, the hard part is not the software but the handover which is why Cedar is built the way it is. The honest answer is that, optional fields never get filled in so the mobile app came first. When the pilot started in Leeds, optional fields never get filled in and the numbers bear it out. After a few dozen rollouts, integrations are where budgets go to die and claims intake is no exception.

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

Where this leaves us

Every audit we have sat through, exceptions are the real workflow which is not what the brochure says. After a few dozen rollouts, nobody wants another login which is why Cedar is built the way it is. What surprised us, claims intake is a people problem wearing a software costume and the numbers bear it out. On the floor, integrations are where budgets go to die so we start there. Most teams we meet, the biggest win is that the group chat goes quiet and it shows up in the churn numbers.

For insurance brokers in particular, the hard part is not the software but the handover and claims intake is no exception. What surprised us, the audit trail pays for itself the first time an inspector asks which is the whole point. When the pilot started in Leeds, optional fields never get filled in so plan for it.

Written by the Cedar team in Leeds. Questions? Get in touch.