Skip to content
Senior web & app development · 20 capabilities
oakstone.digital
Case study / Meridian Ops

Less admin. More operating leverage.

Integrating a scattered toolchain behind one internal app removed the copy-paste work between systems.

Industry
Professional services
Duration
12 weeks
Division
Apps & Software
Year
2025
Meridian Ops — professional services web development project by Oakstone
Apps & Software / delivered
31 hrs
coordinator time recovered weekly
−92%
data-mismatch invoice disputes
5 → 1
places to look for a job status
The challenge

Meridian ran a field services operation across five systems that did not speak to each other: a CRM, a scheduling tool, two client portals and an accounting package. Coordinators moved data between them by hand, and the same job reference existed in four slightly different forms.

Errors surfaced as invoicing disputes weeks later, which is the most expensive place to find them.

The move

We agreed a single source of truth per field, then built typed integrations with idempotent writes, retry handling and a replayable event log. A coordinator-facing tool sat on top, designed around the six decisions that fill their day.

Every sync surfaced its own health: record counts, lag and failure rate, alerting a named owner rather than a shared inbox.

The result

Coordinators recovered around 31 hours a week collectively, and invoicing disputes traced to data mismatches fell to almost nothing over the following quarter.

The integration layer has since absorbed two further systems without a rewrite, which was the point of building it as a product rather than a script.

Stack
Node.jsTypeScriptPostgreSQLBullMQRedisOpenAPISentry
Team

One integration lead, two engineers, one designer part-time

Constraints
  • Two of the five systems had no sandbox environment
  • Field ownership was genuinely disputed between departments
  • Coordinators could not be taken off live work for long sessions
What we would do differently

We spent the first fortnight building integrations before the source-of-truth argument was settled, and had to redo two writers. Settle field ownership on paper first, even when it feels like a political rather than technical task.

Shadowing coordinators in twenty-minute slots worked far better than scheduled workshops, and produced a better interface than the workshops would have.

A better brief starts here

Your next proof point is waiting.

Bring us the hard thing. We will bring a point of view, a senior team and a clear next step.

Start a conversation