Meridian Financial: What a 60-Day Operational Intelligence Audit Revealed

Meridian Financial has 340 employees. Mitori observed workflow behavior across 222 active seats over a 60-day period, spanning finance, operations, HR, customer service, and legal/compliance. Observation focused on structural workflow evidence only: app usage patterns, window focus, and task timing, not keystrokes, screenshots, or document contents.

The observation graph stabilized around six promotable workflow families by Day 60. Those workflows were not guessed from templates; they were promoted only after recurrence, user coverage, and evidence thresholds were met.

AP Processing ranked first because it combined the highest absolute savings with strong fit and early rollout readiness. The workflow spans seven steps, was observed across eight AP clerks, and averages 42 minutes per run. The main bottleneck is Validate against PO, a four-minute step with a 12% exception rate.

Claims Processing still modeled meaningful value, but it stayed out of Wave 1 because the document-validation step had a 14% exception rate and settlement governance introduced harder policy constraints. The sequencing decision was driven by control maturity, not by lack of economic upside.

Wave 1 focused on AP Processing and Email Triage & Response because they offered fast payback and lower governance drag. Wave 2 handled Claims Processing and Contract Review after policy hardening. Wave 3 expanded into onboarding and reporting once the control loop was proven.

The Meridian case is a useful illustration of what operational intelligence should produce: a traceable evidence base, an explicit commercial case, a sequenced rollout order, and a control model that survives scrutiny from finance, operations, and technology leaders.