Reading Meridian's Engineering Topology
Meridian's engineering landscape β 340 engineers, 12 repos, 5 product lines. Three zones: Build, Pipeline, and Run & Observe. As you scroll, findings light up where cost, friction, and risk concentrate.
The $9.4M Question
Headcount grew 3.8Γ in 30 months. Output grew 1.9Γ. The gap isn't performance β it's structural friction compounding every quarter.
What leadership sees vs. what's actually happening
The 8% fiction: Leadership budgets 8% for tech debt. Only 3% reaches deliberate work β the rest gets absorbed by invisible rework and config overhead.
Every finding maps to a business lever
Every initiative reaches the board as Cost, Time, or Quality. The findings below map directly to those.
β Costs
β Time to Market
β Risk
Every finding below is tagged to one of these. You'll know immediately which board conversation it belongs in.
Your org has a speed limit
Every engineering org carries assets (accelerating delivery) and liabilities (slowing it down). The ratio is your Innovation Tax.
Meridian's score: $2.30 β every $1 of new capability costs $2.30 in structural overhead. You hire more engineers and go slower. That's the tax.
The Rework Loop
34% of PRs in payments-core touch the same 15 modules β 8% of the codebase generating 34% of all PR activity. Engineers re-solve the same structural problems every quarter.
Fix: Dedicate 1 team, 2 sprints to refactor the top 5 modules. Cost: ~$180K. Recovery: $1.3M/yr.
The Platform Bottleneck & Hardware Tax
Every product team waits on Platform for infra changes β 11-day average queue. Platform is a dependency in 67% of delayed features. One deploy freeze = five teams replanning.
Fix: Self-service tooling for top 5 platform requests. 4 engineers, 1 quarter. Recovery: $2.8M/yr.
The Knowledge Cliff
4 engineers hold context on Auth/Identity β the system touching every product line. They don't just hold knowledge β they translate between every team that touches auth, reconciling definitions in real time. Two departures = 4β6 month development halt across the org.
Fix: Non-negotiable. 1 sprint knowledge transfer + "shadow reviewer" program. Cost: ~$90K. Cost of inaction: incalculable.
The Integration & Dependency Tax
28% of effort maintains service boundaries built under different assumptions. "Fix" appears 3Γ more than "add." Each team burns ~40 hrs/quarter on version conflicts.
Fix: Lightweight API contracts + automated dependency governance. Investment: ~$100K. Recovery: $1.5M/yr.
The Invisible QA Loop
15% of engineering time goes to manual verification that never becomes a ticket β 51 FTE-equivalents of hidden labor. A phantom QA team on no org chart, invisible to every productivity tool in the building.
Fix: Target the top 10 manual verification patterns (60% of volume). 2 engineers, 1 quarter. Recovery: $6M/yr.
AI doesn't fix misalignment.
It scales it.
Every highlighted domain is already being touched by AI β code gen, automated testing, AIOps, copilot reviews, intelligent routing. The question: is AI amplifying aligned intent, or generating misaligned complexity at 10Γ speed?
At an Innovation Tax of $2.30, AI adoption amplifies $2.30 of friction for every $1 of capability. Fix the structural issues first β or AI compounds them faster than humans ever could.
Where pressure concentrates by team
Auth/Identity: red across Time + Quality. Payments: highest Cost burden. These two teams carry 60% of organizational friction.
5 actions. 6 months. $9.4M recovered.
| Action | Lever | Value | Time | |
|---|---|---|---|---|
| 1 | Auth knowledge transfer | Quality | Risk mitigation | 2 wks |
| 2 | Platform self-service | Time | $2.8M/yr | 3 mo |
| 3 | QA automation (top 10) | Cost | $6.0M/yr | 3 mo |
| 4 | Module refactor (top 5) | Cost | $1.3M/yr | 4 wks |
| 5 | API contracts + deps | Cost | $1.5M/yr | 3 mo |
No surveys. No interviews. Your actual artifacts.
2. Analyze β Semantic analysis of 14 months of engineering artifacts. Behavioral data, not opinions.
3. Map β Findings tied to specific teams, repos, and business levers.
4. Track β Recurring analysis catches new drift before it compounds.
This brief took 48 hours and a read-only connection.
Your repos, your issues, your team's actual language. Same methodology, same depth.
No disruption to your teams. Results delivered within one week.