12 min read
ROBERT
Monday, September 15, 2025 – 8:00 AM – Meridian Headquarters
Robert sat in his corner office, watching the city wake up.
The rest of the company had no idea. Outside the warehouse, Meridian continued its slow decline. Customers churning. Employees leaving. Stock flat. The industry narrative: a dinosaur waiting to die.
His phone buzzed. A news alert.
Axiom Logistics Confirms Q2 2026 IPO Timeline
The countdown was real now. Nine months.
Robert had learned to live two lives. The public CEO, managing decline, keeping the board calm, maintaining the appearance of a company fighting for survival. And the secret sponsor, visiting the warehouse every week, watching twelve people build the impossible.
Patricia knocked on his door. “The board meeting in five.”
“Any surprises?”
“Same agenda. Revenue decline, customer churn, ‘strategic options.’” She paused. “Are we going to tell them about the warehouse?”
“Not yet.”
“They’ll ask about transformation plans.”
“Tell them we’re evaluating options.” Robert stood and straightened his tie. “The same thing we’ve told them for six months.”
“How long can we keep this up?”
“As long as we need to.”
Wednesday, September 17, 2025 – 2:00 PM – Meridian Boardroom
The quarterly board meeting felt like a funeral rehearsal.
“Revenue is down 8% year-over-year,” Carlos Vega reported. “Customer retention is at 89%, down from 93% last year. Five of our top fifty accounts are in active discussions with Axiom.”
Victoria Hartwell leaned forward. “What’s the timeline?”
“For what?”
“For when this becomes terminal.”
Carlos hesitated. “If current trends continue, we hit negative cash flow in Q3 2027. Bankruptcy by Q1 2028.”
The room was silent. Robert knew the numbers were wrong. The warehouse would change everything. But he couldn’t say that.
“What about strategic options?” James Crawford asked. “We’ve had interest from private equity.”
“We’ve had interest in our customer contracts,” Robert corrected. “Not in the company. They’d strip us for parts.”
“That might be the best outcome for shareholders.”
“The best outcome for shareholders is a successful transformation.” Robert kept his voice steady. “We’re working on it.”
“Another transformation?” James shook his head. “We’ve tried three times. $47 million. Nothing to show.”
“This is different.”
“How?”
Robert wanted to tell them. Twelve people. AI-native development. Real progress this time. But he couldn’t. Not yet. Not until they were sure.
“I can’t share details,” he said. “But I’m asking for six more months of patience.”
“Six months is a long time when you’re bleeding customers.”
“Six months is nothing compared to three failed transformations. Trust me.”
The vote was 5-3 again. Same split as when they’d approved Prometheus. Victoria and four others giving Robert the benefit of the doubt. James and two others ready to sell.
After the meeting, Victoria caught Robert in the hallway.
“How close are they?” she asked quietly.
“Close to seventy percent. Accelerating. On track for July.”
“And you really think this works?”
“I really think we have a chance. For the first time in ten years, I really think we have a chance.”
Dane was waiting for him in the parking lot. He’d flown down from Chicago for the week, as he did every month — three days in the warehouse, reviewing cadence, adjusting the build rhythm, then back to his consulting practice.
“How bad was the board?” Dane asked.
“Five-three. Same split. Crawford wants to sell.”
“Crawford always wants to sell. That’s his job on the board — to represent the exit option.” Dane opened his car door. “The question is whether Victoria holds.”
“She holds. For now.”
“Then we have our window.” Dane looked at the Meridian headquarters building. “You know the biggest risk right now isn’t the technology. It’s you. The more the main org sees you visiting the warehouse, the more questions they ask. Patricia’s already fielding calendar inquiries from the VP of Engineering.”
“I know.”
“So stop visiting on Thursdays. Vary the days. And stop parking in visitor parking at the warehouse — use the side street.” Dane’s voice was the same calm, firm tone he’d used in the feature-a-day argument with Harry. “Protection isn’t secrecy theater. It’s operational discipline. One curious IT admin, one overheard conversation, one confused parking attendant — that’s how parallel orgs get discovered. I’ve seen it happen.”
Thursday, October 9, 2025 – 10:00 AM – The Warehouse
The new process was working, and the energy was different. Focused. Calm. Ready.
Maya ran the morning standup. “We have nine months to launch. Current status: 70% feature parity. Target: 100% by March, pilots in April-May, launch July 5.”
“Why July 5?” Deepa asked.
“Axiom’s IPO is July 6,” Robert said. He’d started attending standups more often. “We launch the day before.”
“Is that symbolic or strategic?”
“Both. The press will cover Axiom’s IPO. We want them to already be talking about us when the bell rings.”
Harry spoke up. “The remaining thirty percent is the hard stuff. Integration points. Migration scripts. Performance optimization. These aren’t features we can build in isolation.”
“What do you need?”
“Real data. We’ve been testing with synthetic data. Now we need production volumes. Millions of shipments. Real carrier feeds. Actual customer configurations.”
Maya nodded. “We can get sample data. Anonymized. But it’ll take coordination with the main IT team.”
“Without telling them what we’re doing?”
“Without telling them the full picture.”
Monday, October 27, 2025 – 3:00 PM – The Warehouse
The data problem was worse than expected.
“The legacy system has 47 different data formats,” David Park explained. “They’ve evolved over thirty years. Some of it is EBCDIC. Some is ASCII. Some is whatever format a contractor used in 1998 and nobody cleaned up.”
“Can we normalize it?”
“We can normalize most of it. But some of the older formats have quirks that aren’t documented anywhere.”
Harry stepped forward. “Show me the 1998 format.”
David pulled up a sample. Columns of numbers and codes that looked like gibberish.
“This is the Southeastern acquisition,” Harry said. “I remember this. The contractor was named Bill. He used a custom encoding for carrier IDs because he wanted them to sort alphabetically but also group by region.”
“That’s insane.”
“That was Bill. But I can decode it.” Harry grabbed a marker and started writing on the whiteboard. “First two digits are region. Next three are carrier type. Then six digits for the actual ID, but reversed.”
“Reversed?”
“Bill was left-handed. He found it easier to type numbers backward.”
The room stared at Harry.
“I’m not making this up,” Harry said. “I spent two weeks with Bill in 1999 untangling this. It’s burned into my memory.”
Thursday, November 20, 2025 – 6:00 PM – The Warehouse
Thanksgiving was approaching. The team faced a choice.
“We can take the holiday weekend,” Maya said. “Or we can push through on the performance optimization.”
“What’s at stake?”
“If we take the break, we hit feature parity in late March. If we push through, we hit it in mid-March.”
“Two weeks difference.”
“Two weeks that could make or break the customer pilots.”
Harry looked around the room. The veterans were tired. The engineers were tired. Everyone was tired.
“We’ve been going hard for seven months,” he said. “The worst thing we could do is burn out now.”
“So we take the break?”
Dane spoke from the whiteboard where he’d been silently tracking feature velocity. “We take the break. All of us. Non-negotiable.” He capped his marker. “At Helix, we hit this exact moment at month five. The team wanted to push through. I let them. By month seven, two engineers had quit and the survivors were making more bugs than features. That’s what killed us — not the pace, the refusal to recover.”
“I thought your whole thing was a feature a day,” Sofia said.
“My whole thing is a feature a day sustained over fourteen months. You don’t sustain anything by grinding people into dust during the holidays.” Dane looked at Harry. “Take the break. Come back Monday. The two weeks we ‘lose’ we’ll make back in January when everyone can think straight.”
Robert spoke up. “I’ll be here Thanksgiving day. My wife understands. Anyone who wants to work can work. Anyone who needs rest should rest.”
In the end, half the team worked through the holiday. The other half came back Monday, refreshed and ready.
By December 1, they’d closed the performance gap.
Wednesday, December 3, 2025 – 4:00 PM – The Warehouse
Robert arrived with Gloria for an unscheduled meeting. He closed the door to the small conference room.
“Axiom lost another two customers this quarter,” he said. “Not to us. To frustration. They’re growing so fast that their support quality is dropping. Customers are complaining about response times, missed SLAs.”
“That helps us,” Maya said.
“It helps us if we can reach those customers before Axiom fixes the problem.” Robert pulled out a folder. “I’ve set up a subsidiary. MAI Research LLC. Separate entity, no Meridian branding. When we’re ready for customer outreach, we do it through MAI.”
“MAI?”
“Meridian AI. But nobody outside this room knows that.”
Harry frowned. “Why the secrecy? We’re already secret.”
“Because when we approach customers for pilots, we can’t have Axiom finding out. If they trace MAI back to Meridian before we launch, they’ll counter-program. Undercut pricing. Lock customers into long-term contracts.” Robert looked at Maya. “The shell company buys us time. We approach customers under NDA, demo the platform, get commitments. By the time Axiom figures out who MAI is, we’ll be public.”
“When do we start outreach?”
“After feature parity. February or March. Gloria will identify the targets.”
Gloria nodded. “I already have a list. Customers who are unhappy with Axiom. Customers who are still loyal to us but worried. Customers who’ve been with Meridian for decades and would love a reason to stay. And most interesting, new smaller market customers who couldn’t afford us before the rewrite.”
Maya looked at the MAI Research letterhead. Clean, professional, anonymous. Nobody would connect it to a warehouse in Atlanta.
“This is the part that feels like a spy movie,” she said.
“This is the part where we win,” Robert corrected.
GLORIA
Saturday, December 13, 2025 – 11:00 AM – The Warehouse
Gloria was mapping customer migration paths.
The platform was nearly complete. Feature parity at 88%. But building the system was only half the battle. Getting customers onto it was the other half.
“Each customer has customizations,” she explained to Maya. “Configuration settings, contract terms, integration points. We can’t just flip a switch.”
“How many unique configurations?”
“Two thousand active customers. Maybe three hundred unique configuration patterns.”
“So we template the common patterns and handle edge cases manually?”
“That’s the plan. But the edge cases are the important customers. The ones who’ve been with us longest. The ones with the most complex needs.”
Maya thought about it. “What if we could generate migration scripts automatically?”
“From what?”
“From the configuration data itself. Feed it to the AI, have it generate the migration logic for each pattern.”
Gloria had learned to trust Maya’s instincts. “Show me.”
They spent the afternoon building a migration generator. Feed in a customer’s configuration, get out a script that would move their data to the new platform.
“This works for simple cases,” Gloria said, testing. “But what about the really old configurations?”
“Like what?”
“We have customers who’ve been with us since the 1980s. Their configurations have layers of legacy that nobody understands.”
“Harry understands.”
“Harry understands some of it. But even Harry can’t know everything about every customer.”
Wednesday, December 24, 2025 – 9:00 AM – The Warehouse
Wednesday morning. The team gathered for what Robert called a “pulse check” — a morning together before the final push.
“Feature parity: 90%,” Maya announced. “We’re ahead of schedule.”
The team cheered. Robert had brought champagne. Real champagne, not the cheap stuff.
“Three months ago, we were at sixty-eight percent and falling behind,” he said. “The board was ready to sell. The industry was writing our obituary. And twelve people in a warehouse were quietly building the impossible.”
“Still building,” Harry corrected. “We’re not done yet.”
“No. But we’re close.” Robert raised his glass. “To the twelve. The craziest, bravest, most talented people I’ve ever worked with.”
“To the twelve.”
Gloria watched her colleagues drink. Seven months of shared purpose. Seven months of learning and building and failing and succeeding. She’d spent thirty-five years at Meridian, and these seven months had been the best of her career.
“You know what I realized?” she said to Maya. “This is the first time anyone’s asked me what customers actually need. Not what the system can do. What they need.”
“That’s the whole approach,” Maya said. “Domain knowledge first. Technology second.”
“It sounds obvious when you say it.”
“Everything obvious was once revolutionary.”
Wednesday, December 31, 2025 – 11:00 PM – The Warehouse Roof
End of the month. The team on the roof.
They sat in folding chairs looking at the city lights. Somewhere out there, Axiom was probably working late too. Probably in a fancier building, with catered food and a DJ.
Here, they had folding chairs and pizza boxes.
Robert stood at the edge of the roof, looking at the skyline.
“Six months to launch,” he said. “Seven months in. And we’re going to make it.”
“What happens after?” Kevin asked.
“After we launch?”
“After we win. What happens to Meridian?”
Robert turned to face the team. “Meridian becomes something new. A company that learned from its failures. A company that figured out how to combine domain knowledge with modern technology. A company that didn’t give up.”
“And Axiom?”
Robert shrugged. “They’ll survive. They’re a good company with good technology. But they won’t be the only option anymore. That’s what matters.”
The fireworks peaked. Midnight arrived.
“Happy New Year,” Gloria said.
“Happy New Year,” everyone echoed.
Harry looked at Maya. “Six more months.”
“Six more months,” she agreed. “And then we change everything.”
End of Chapter 8