The $200 Million Dealership Dilemma
Walk into the back office of a heavy machinery dealership or a commercial truck distributor generating $200 million in annual revenue, and you will almost certainly find monitors displaying monochrome green or amber text on a black background.
IBM AS/400 (now IBM i) and COBOL-based Dealer Management Systems like legacy CDK, Reynolds & Reynolds, or proprietary terminal setups have anchored dealership operations for thirty years.
Typical Dealership Terminal Interface:
╔═══════════════════════════════════════════════════════════════════════╗
║ COMMAND ===> WRKORD ║
║ OPT ORDER# CUSTOMER STATUS HRS TECH LOCATION ║
║ 2 WO-8891 MIDWEST LOGISTICS IN-PRG 4.2 TM4 BAY-08 ║
║ 2 WO-8892 AGGREGATE HAULAGE WAIT-PRT 1.8 RJ1 BAY-03 ║
║ F3=EXIT F5=REFRESH F12=CANCEL F21=PRINT WORK ORDER ║
╚═══════════════════════════════════════════════════════════════════════╝These systems are legendary for stability. They do not crash. They calculate floor-plan financing down to the fifth decimal place.
The catch? They are impossible to connect to mobile devices, require months of training for new staff, and make modern customer transparency impossible.
Why "Big-Bang" Replacements Are Financial Suicide
When dealership leadership decides to fix the problem, their first instinct is usually to commission a wholesale replacement: buy a massive cloud ERP, spend 24 months in committee meetings, and attempt to switch the entire dealership over on a single Monday morning.
Industry data shows that over 70% of big-bang legacy replacements fail, experience massive cost overruns, or leave the business functionally paralyzed during the cutover week. Parts shipments get lost. Technician time goes unbilled. Fleet customers flee to competing dealers.
The Strangler Fig Modernization Pattern
Instead of attempting to assassinate the legacy system overnight, we deploy the Strangler Fig pattern.
Just as a strangler fig vine wraps around a host tree, growing until it gradually and seamlessly replaces the host, we wrap modern API interfaces around the legacy core:
Strangler Modernization Architecture:
[ Modern Mobile Tech App ] [ Customer Transparency Portal ]
│ │
└──────────────┬───────────────┘
▼
[ Modern Next.js / Node API Gateway ]
(Auth, Validation, Real-Time Webhooks)
│
┌────────────┴────────────┐
▼ ▼
[ Modern PostgreSQL ] [ AS/400 CDC Connector ]
(Fast Search, Documents) │
▼
[ Legacy AS/400 / DB2 Engine ]
(Accounting, General Ledger)Phase 1: High-Friction Mobile Workflows
We build a dedicated Flutter mobile application for workshop technicians. Technicians clock in, scan VIN barcodes, snap photos of damaged components, and voice-dictate repair notes. A lightweight sync service translates these actions into the legacy system's job clocking registers.
Phase 2: Parts Catalog & Inventory Transparency
We replicate the legacy parts catalog into an indexed PostgreSQL search engine. Counter staff and customers can search by part number, visual schematic, or supersession history with instant 10ms autocomplete.
Phase 3: Gradual Ledger Decoupling
Over 18 to 24 months, secondary functions—scheduling, customer communications, warranty tracking—migrate entirely to the modern cloud stack. The legacy system is relegated to what it does best: general ledger accounting, until the final replacement becomes a routine administrative task.
Real-World Financial Return
By decoupling user experience from the legacy backend:
- Technician Billable Hours: Increased by 14% because mechanics no longer walk across the facility to log into fixed green-screen terminals.
- Warranty Rejection Rate: Dropped from 9.4% to 1.2% through automated photo validation before work order closing.
- Implementation Risk: Zero days of dealership downtime.
