6 min read
MAYA
Friday, May 1, 2026 – 9:00 AM – The Warehouse
The final sprint.
Maya stood at the main whiteboard. The progress chart showed their full journey: the slow start, the February setbacks, the April breakthrough, the steady push through spring.
Ninety-four percent. Six percent to go. Two months.
“Here’s what’s left,” she said. “EDI integration for legacy partners. Customs documentation automation. Multi-currency reconciliation. Performance optimization for peak load.”
“Those are the hard ones,” David Park said. “EDI alone has two hundred variations.”
Harry stepped forward. “Walk us through EDI,” Dane said to him.
“Electronic Data Interchange. How companies exchange documents electronically. Purchase orders, invoices, shipping notices. Standardized in the 1970s. Updated never.”
“Never?”
“Different industries adopted different standards. Different companies implemented those differently. Then everyone made custom modifications.” Harry drew a diagram. “Partners using ANSI X12. Partners using EDIFACT. Partners using proprietary formats they call EDI but aren’t.”
“How many unique formats?”
“About two hundred. And every partner is slightly different.”
Maya looked at the timeline. Two months. Two hundred formats.
“We automate this,” she said. “Build a translation engine. Feed it examples, AI learns the patterns.”
“Like the domain knowledge model,” Harry said. “For data formats.”
Two weeks of building. Harry explaining EDI logic. David providing sample data. The AI learning patterns, generating translators.
The first results were mixed. Basic ANSI X12 worked. Proprietary variations broke.
“These are the old partners,” Harry said, looking at the failures. “The ones who predate standardization.” He pointed at a field. “Partner code ‘SEFRT.’ Southeast Freight. 1999 acquisition. They use a custom carrier code that maps to internal codes, but only for domestic shipments.”
“Only domestic?”
“International uses standard codes. Nobody knows why. Bill might have known.”
Within two weeks, the engine handled 150 of 200 formats. The remaining 50 would need manual work during migration.
Tuesday, May 5, 2026 – 12:30 PM – The Warehouse
Robert walked in during lunch.
“Axiom confirmed the IPO date. July 6. The roadshow starts next week.”
The room went still. They’d known it was coming — the S-1 had been filed in January — but the confirmation made it concrete.
Maya checked her phone. Already on TechSignal. Axiom Logistics Confirms July 6 IPO. Roadshow Begins May 12.
“Every analyst covering logistics is writing about Axiom today,” Robert said. “Nobody’s writing about us. That’s by design.”
“Our timeline hasn’t changed,” Maya said.
“Theirs just went public.” Robert looked around the room. “The world expects Meridian to die quietly while Axiom takes over.”
Harry was at his monitor later that afternoon when a market alert popped. Whitfield Capital Upgrades Axiom to “Strong Buy,” Sets $22 Price Target. The analyst’s line: “We’re not seeing the Meridian threat. Their platform is dated. Whatever they’re building internally, it’s not showing up in market share.”
Maya read it over his shoulder.
“They don’t know we exist,” Harry said.
“Twenty-two dollars values Axiom over a billion.”
“And we’re in a warehouse with camping chairs.”
“Tomorrow we start load testing,” Maya said. “Whitfield’s opinion won’t matter after July.”
Wednesday, May 13, 2026 – 6:00 PM – The Warehouse
The load test started at 6 PM.
A simulator generating production-level traffic. Three million shipments. Real routing. Actual database writes.
“Starting at 10%,” Kevin announced.
Response time: 1.2 seconds. Error rate: 0.01%. System load: 15%.
“25%.”
1.8 seconds. 0.02%. 35%.
“50%.”
2.4 seconds. 0.03%. 55%.
“75%.”
3.1 seconds. 0.05%. 78%.
“100%. Full production load.”
4.2 seconds. 0.08%. 92%.
“We’re close to the edge,” Kevin said. “But not breaking.”
“125%. Peak load.”
5.8 seconds. 0.2%. 98%.
“Holding. Barely.”
“Run it for six hours,” Maya said. “I’ll monitor overnight.”
She was still there at 6 AM. Six hours at peak load. No failures. Response time stable.
“The legacy system has 10% headroom on a good day,” Harry said when the team arrived. “We have 30%.”
“And we haven’t optimized yet.”
ZARA
Saturday, May 16, 2026 – 2:00 PM – The Warehouse
Feature parity day.
“100%,” Maya said. “Every feature in the legacy system has been replicated or improved in MeridianOne.”
The team cheered. Robert had brought champagne — better than the first bottle when they’d hit eighty percent.
“Milestone, not finish line,” Robert said. “We still need pilots. Real customers, real data, real problems.”
Zara took over. She’d been planning the pilot strategy since December, working from her customer map and Gloria’s relationship list.
“Three pilot customers,” she said. “Selected for maximum coverage.”
She pinned three cards to the wall map.
“Atlanta Express Shipping. Been with Meridian since 1992. Dispatch-heavy, volume shipper. They represent our core customer base — the people who live in the system eight hours a day. Renee’s operation.”
“Second: Hartley Shipping. Margaret Sullivan’s company. Mid-size, skeptical. She’s been with us twenty years but she’s already taken calls from Axiom. If we can win Margaret, we can win the fence-sitters.”
“Third: Pacific Northwest Logistics. They’re planning to leave for Axiom. Active contract negotiation. This is our chance to intercept.”
“Three very different customers,” Robert said.
“That’s the point. If we make all three happy, we can make anyone happy.”
Gloria nodded. “I know Margaret and the Atlanta Express team personally. Pacific Northwest is newer — David Park handled their integration.”
“Pilot structure,” Dane said from his whiteboard. “Four weeks per customer. Weeks one-two: shadow mode. MeridianOne runs alongside legacy, comparing results. No customer impact. We’re looking for discrepancies — any case where the new system gives a different answer.”
“Week three: non-critical operations switch to the new system. Tracking, reporting.”
“Week four: full migration. Legacy becomes backup.”
“Success criteria?” Robert asked.
Zara read from her Moleskine. “Zero data loss. Response time equal or better than legacy. Customer satisfaction 8 or higher. And at least two of three customers willing to recommend MeridianOne to others.”
“High bar.”
“We built a high system.”
Wednesday, May 27, 2026 – 8:00 PM – Gloria’s Kitchen
Gloria’s phone rang while she was making dinner.
“Gloria? It’s Margaret Sullivan.”
“Margaret. The pilot starts Monday.”
“I know. I wanted to call.” A pause. “I’ve been skeptical. After the failed transformations. The churn. I was ready to move to Axiom.”
“I know.”
“But you’ve always been straight with me. Thirty years. So I’m trusting you.”
“We won’t let you down.”
“You better not. Because if this fails, I’m taking my business to Axiom the next day.”
“It won’t fail.”
“How do you know?”
Gloria thought about the warehouse. About Zara going to dispatch centers before she’d even seen the codebase. About Dane’s narration pipeline extracting forty years of knowledge in months. About Maya building at the keyboard while Harry narrated edge cases beside her. About twelve people working like they knew the company was at stake — because it was.
“Because the people who built it started with the customer,” Gloria said. “Not the technology. Not the old system. The customer. And that’s never happened here before.”
Margaret was quiet. Then: “All right, Gloria. Let’s see what they’ve built.”
End of Chapter 9