12 min read
ROBERT
Wednesday, September 10, 2025 – 9:00 AM – Freight Technology Summit, Las Vegas
The conference badge felt heavy around Robert’s neck.
Robert Chen, CEO, Meridian Freight.
Ten years ago, that badge would have opened every door. Executives would have lined up to meet him. Analysts would have sought his opinion. Customers would have thanked him for keeping their supply chains running.
Now, he stood alone at the coffee station while everyone else clustered around the Axiom booth.
“The future of logistics is cloud-native,” the Axiom presenter was saying. “Modern APIs, real-time tracking, AI-optimized routing. No more legacy constraints.”
Robert watched the crowd. He recognized some of his own customers in the audience, nodding along, taking notes.
A woman approached the coffee station. Margaret Sullivan, CTO of Hartley Shipping. They’d worked together for fifteen years.
“Robert.” She smiled politely. “Good to see you.”
“Margaret. How’s the pilot going?”
She hesitated. “The Axiom pilot?”
“I heard you were testing their platform.”
“We’re… evaluating options. Everyone is.” She poured her coffee, avoiding his eyes. “You know how it is. Boards want to see innovation. Customers want modern interfaces. We have to explore alternatives.”
“Meridian has been your logistics backbone for twenty years.”
“And we appreciate that. We do.” Margaret finally met his gaze. “But Robert, honestly? Your system still runs on green screens. My team has to dial into a terminal to check shipment status. It’s 2025.”
“We’re working on modernization.”
“You’ve been working on modernization for ten years. At some point, the work has to be done.”
She walked away toward the Axiom booth. Robert watched her go.
At some point, the work has to be done.
Wednesday, September 10, 2025 – 2:00 PM – Conference Panel
The panel was titled “Legacy Modernization: Lessons Learned.”
Robert wasn’t on the panel. He sat in the audience, listening to consultants explain how to transform old systems into new ones. The same consultants who’d taken $47 million from Meridian and delivered nothing.
“The key is executive sponsorship,” one panelist said. “Transformation fails when leadership isn’t fully committed.”
Robert’s jaw tightened. He’d been fully committed. He’d staked his career on transformation. Three times.
“You also need a clear roadmap,” another panelist added. “Multi-year horizons. Phase gates. Proper governance.”
Roadmaps. Phase gates. Governance. All the things that had produced nothing but PowerPoints and invoices.
A question came from the audience: “What about companies that have tried and failed multiple times? Is there a point where transformation becomes impossible?”
The panelists exchanged glances.
“Every company can transform,” the first consultant said. “It just takes time, investment, and commitment.”
“But some companies,” the second added carefully, “may need to consider whether transformation is worth the investment. Sometimes the market has moved on.”
Sometimes the market has moved on.
Robert stood up and walked out.
Thursday, September 11, 2025 – 8:00 AM – Axiom Press Conference
The announcement came at 8 AM, timed for maximum media coverage.
“Axiom Logistics Announces Intent to File for IPO; Targets Q2 2026 Listing”
Robert read the press release on his phone, standing in the hotel lobby.
“We’re excited to take this next step in our growth journey,” said Catherine Bell, CEO of Axiom Logistics. “Our cloud-native platform has transformed supply chain management for hundreds of enterprises. An IPO will give us the capital to accelerate innovation and serve even more customers worldwide.”
The release included growth numbers. Revenue up 40% year-over-year. Customer count doubled. Platform processing over a million shipments daily.
A million shipments. Meridian still did three million. But the gap was closing.
Robert calculated the timeline. If Axiom filed in the next few months, they’d go public in mid-2026. Post-IPO, they’d have $500 million or more in the bank. They could hire the best engineers. Acquire the best technology. Undercut Meridian on pricing until the customers had no reason to stay.
A year. Maybe less. That’s how long Meridian had.
His phone buzzed. A text from his CFO, Carlos Vega.
Board meeting requested. Tomorrow. Emergency session.
Robert typed back: I’ll be on the first flight home.
Friday, September 12, 2025 – 2:00 PM – Meridian Boardroom, Atlanta
Eight directors around the table. Half of them looked scared. The other half looked resigned.
“The Axiom IPO announcement changes everything,” Carlos Vega said. “Our stock dropped 8% this morning. Analysts are downgrading us. Customers are calling about contingency plans.”
“What kind of contingency plans?” Board member Victoria Hartwell asked.
“They want to know what happens if Meridian fails. They’re asking about data migration, contract exit clauses, alternative providers.” Carlos spread the customer feedback across the table. “Fifteen of our top fifty accounts have initiated formal vendor evaluations in the last week.”
“So we’re losing customers,” Victoria said.
“We’re losing confidence. The customers aren’t leaving yet, but they’re preparing to leave. That’s almost worse.”
Robert listened, saying nothing. He’d been doing this for eight years. Watching the slow decline. Trying to stop it. Failing.
Board member James Crawford, the longest-tenured director, cleared his throat. “Perhaps it’s time to consider strategic alternatives.”
“What kind of alternatives?” Robert asked.
“Sale. Merger. Private equity recapitalization.” James looked around the table. “We’ve had inquiries. Not formal offers, but interest.”
“Interest from whom?”
“Garrison. Summit Capital. A few others.” James paused. “They see value in the customer relationships. The contracts. The cash flow. Not the technology.”
“So they’d strip us for parts.”
“They’d maximize value for shareholders. Which is our fiduciary duty.”
Eight years. Eight years of fighting for this company, and now the board was pricing the scrap value.
“There’s another option,” he said.
“We’ve tried transformation,” Victoria said gently. “Three times. $47 million. It doesn’t work for us.”
“I’m not talking about transformation.”
The room went quiet.
“Then what are you talking about?” James asked.
Robert looked at each director in turn. “I’m talking about building something new. Not fixing the old system. Not transforming it. Replacing it.”
“With what?”
“A modern platform. Built from scratch. AI-native architecture. Designed for the problems we actually have, not the problems we had in 1985.”
“Robert, we’ve tried—”
“We’ve tried to change a living system. I’m proposing we build a new one alongside it. In secret. With a small team. And launch it before Axiom goes public.”
The silence stretched.
“How small?” Victoria asked finally.
“Twelve people.”
“Twelve people to replace a system that runs $2 billion in logistics?”
“Twelve people who actually understand the domain, paired with engineers who understand modern technology. No consultants. No committees. No transformation theater. Just build.”
“That’s insane,” James said.
“So is spending another $50 million on consultants who’ve never shipped anything.” Robert leaned forward. “The previous approaches failed because they tried to change something while it was running. You can’t renovate a house while you’re living in it. But you can build a new house next door and move in when it’s ready.”
“And if it fails?”
“Then we’re in the same position we’d be in if we did nothing. Except we’d have tried.”
Victoria looked at him. “How long?”
“Eight months. We launch before Axiom’s IPO.”
“Budget?”
“$8 million. A fraction of what we spent on the previous attempts.”
“And you think twelve people can build what forty couldn’t?”
“I think twelve people who know what they’re building can succeed where forty people who didn’t failed. Domain knowledge is the missing piece. Every consultant we hired spent their first year learning what our veterans already know. By the time they understood the problem, the project was already behind schedule.”
The board members looked at each other. Robert could see the calculation in their eyes. Hope fighting with experience. Possibility fighting with precedent.
“Vote,” James said. “All in favor of authorizing the project.”
Five hands went up. Victoria’s among them.
“All opposed.”
Three hands. James included.
“Motion carries. 5-3.” James looked at Robert. “You have your project, Robert. Eight months. $8 million. Don’t make us regret this.”
Robert nodded. “I need one more thing.”
“What?”
“Complete secrecy. Nobody outside this room knows. Not the analysts, not the customers, not even most of our employees. We’re a dying company that’s gone quiet. That’s the story.”
“Why secrecy?”
“Because if Axiom knows what we’re building, they’ll accelerate their IPO. They’ll lock in customers before we can launch. Our only advantage is surprise.”
Victoria nodded. “A stealth startup inside a legacy company.”
“Exactly.” Robert stood. “I need to make some calls.”
Friday, September 12, 2025 – 6:00 PM – Robert’s Office
Robert sat with his phone and a legal pad. He’d drawn a line down the middle. Left side: What we need. Right side: Who.
On the left he wrote three things.
1. Someone who knows how to build product. Not enterprise software product management — real product. Customer-obsessed. Rapid prototyping. Starts in the field, not in a conference room.
2. Someone who knows how to build with AI and how to run a parallel organization. Not a consultant who talks about transformation. Someone who’s actually done it — stood up a separate team, built a new system alongside a legacy one, shipped it.
3. Engineers who can execute. AI-native. Fast. Willing to disappear for eight months.
The right side was mostly blank.
For number three, he had ideas. Good engineers existed. You could find them if you paid enough and the mission was real.
For one and two, he had nothing. His Rolodex was full of operators, board members, CFOs, and the consultants who’d taken $47 million from him. Not a single person who’d built a product from scratch in the last decade. Not a single person who’d run a successful parallel org transformation.
He called Victoria Hartwell.
“Victoria. Quick question. You sit on — what, four boards?”
“Six. Why?”
“I need two people. A product leader who’s actually built something in logistics. And someone who’s run a parallel organization — built a new system alongside a legacy one without the legacy org killing it.”
Victoria was quiet for a moment. “The product person. Have you heard of Zara Okafor?”
“No.”
“She was VP Product at Loadstar. Built their freight-matching platform from fifteen customers to twelve hundred. Before that, she worked loading docks at UPS. Not management — she loaded trucks. She wanted to understand the work before she tried to improve it.”
“Where is she now?”
“Independent. Consulting for logistics startups. I tried to recruit her for the Hartley board last year. She said she was waiting for something worth committing to.”
Robert wrote the name down. “And the second person?”
“That one I know. Dane Kowalski. He spoke at the Frontier Tech Leadership Summit in April. Ex-McKinsey, ex-VP Engineering at Coretek and Helix. At Coretek he built an AI-native production planning system as a parallel org — completely separate from their legacy ERP. Fourteen months, successful launch. At Helix he tried the same thing in place, embedded in the existing org. Nine months, total failure.”
“So he knows what works and what doesn’t.”
“He knows it from both sides, which is rarer. I’ll send you his contact.”
Robert hung up and looked at his legal pad. Two names. That was more than he’d had ten minutes ago.
He picked up the phone again. Victoria’s text had come through — Dane’s number.
Three rings.
“Dane Kowalski.”
“Mr. Kowalski, this is Robert Chen. CEO of Meridian Freight. Victoria Hartwell gave me your number.”
“Victoria. Sure. What can I do for you?”
“I have a legacy COBOL platform that runs $2 billion in logistics. Three failed transformations. $47 million spent. I have board approval to try something different — a parallel build. Twelve people, eight months, complete secrecy. I need someone who’s actually done this.”
A pause. “You said three failures?”
“The Aldric partnership. The Vantage experiment. The Platform Team.”
“Were any of those structured as a parallel org? Separate team, separate governance, no dependency on the legacy structure?”
“No. They all tried to transform in place.”
“Then you haven’t actually tried the thing that works.” Dane’s voice had sharpened. “You’ve tried three variations of the thing that doesn’t work. There’s a difference.”
Robert sat with that.
“Can I buy you a coffee?” he said.
“I’m in Chicago. But I’ll take a Zoom.”
Friday, September 12, 2025 – 11:30 PM – Robert’s Home Office, Buckhead
Robert couldn’t sleep.
The Zoom with Dane had run ninety minutes. The man drew on a whiteboard the entire time — parallel org structure, protection boundaries, migration gates. He’d done this before. Not theorized about it. Done it.
But Dane had also been direct about his limits. “I know how to structure the organization and the AI development methodology. I don’t know your domain. I don’t know freight. I don’t know your customers. You need someone for that.”
Robert had mentioned Zara Okafor.
“Get her,” Dane said. “Product and org design are the two things that have to be right from day one. Everything else you can iterate on.”
And then: “You’ll also need domain experts. Your veterans. Not as leaders — as sources. The best material for AI to learn from. The product person decides what to build. I’ll design how the team builds it with AI. The domain experts tell us why things are the way they are. But the direction comes from the customer, not from institutional memory.”
Robert had written that on his legal pad. Direction comes from the customer, not from institutional memory.
That was the insight the three previous transformations had missed. Not that domain knowledge didn’t matter — it did. But it was input, not strategy. The Aldric team had no domain knowledge and built the wrong thing. The Platform Team had domain people but let them drive the architecture. Neither worked.
The right model was different. A product person who starts with the customer. An AI builder who structures the org. Domain experts who feed the machine.
He picked up his phone and texted Victoria.
Do you have Zara Okafor’s number?
Three dots appeared. Then a contact card.
He’d call her in the morning.
End of Chapter 2