9 min read
Reader Signal
Lower current readership momentum right now.
ZARA
Wednesday, March 4, 2026 – 9:00 AM – The Warehouse
Zara noticed it during the morning standup. The veterans weren’t waiting for questions. Before Sofia could ask about carrier scoring, Gil was already at the whiteboard explaining the algorithm.
“The base score starts with reliability metrics,” Gil said. “On-time percentage, damage rate, claims history. That’s 60% of the score.”
“What’s the other 40%?” Sofia asked.
“Relationship factors. Tenure, volume commitments, contract terms.” Gil drew a diagram. “And then there’s the override layer. Customer-specific adjustments. If a customer has a preferred carrier, we boost that carrier’s score for their shipments.”
“Even if it’s not optimal?”
“Even if it’s not optimal. That’s in the spec Gloria gave you.”
“No, it isn’t.” Gil smiled. “That’s what I’m telling you now. Before you build it wrong.”
Twenty minutes of conversation. By the end, Sofia had a complete picture that would have taken three specification rounds and two rework cycles.
Zara wrote in her Moleskine: The loop is self-correcting. Veterans volunteer knowledge before being asked. That’s the inflection point.
She’d seen this at Loadstar — the moment a product team stopped needing a project manager to broker information and started sharing proactively. At Loadstar it had taken a year. Here it had taken four months.
Friday, March 6, 2026 – 2:00 PM – The Warehouse
The weekly demo for Robert.
Zara framed it. She’d started doing that in June — presenting each module not as a technical achievement but as a customer capability. Robert didn’t need to know the architecture. He needed to know what a dispatcher could do on Monday that they couldn’t do on Friday.
“Quote to booking is complete,” she said. “A dispatcher at Atlanta Express can now get a rate in two seconds instead of thirty-seven. One screen. Five clicks instead of eleven. We’ve already tested with three dispatch workflows.”
“Tracking is at 85%,” Maya said. “Real-time. The legacy system delays GPS updates by up to an hour. Ours stream in real time.”
“Exception handling is at 75%,” Zara continued. “Unified interface. One screen instead of three. We showed it to Renee at Atlanta Express. She cried.”
“She did not cry,” Gloria said.
“She said ‘I’ve been asking for this for eleven years’ and then went quiet for about fifteen seconds. Close enough.”
Kevin pulled up the comparison dashboard.
Quote generation: Legacy 30 seconds, New 2 seconds
Tracking latency: Legacy 60 minutes, New real-time
Exception resolution: Legacy 3 days average, New 4 hours
Portal response: Legacy 47 seconds, New 2.3 seconds
Robert stared at the numbers.
“47 seconds to 2.3?” Victoria Hartwell was on the screen — Robert had invited her to the video demo.
“Legacy checks seventeen databases in sequence,” Maya said. “We have a unified data model.”
“You’ve done this with twelve people?”
“Twelve people, a structured knowledge pipeline, and AI tools,” Dane said. “The people bring the domain expertise. The AI amplifies their reach. The methodology keeps it organized.”
Victoria was quiet for a moment. “I’ll talk to James Crawford. He should see this in person.”
After the demo, Robert texted Nora.
“47 seconds to 2.3. Same functionality. 12 screens to 1.”
Forty minutes later:
“Now build the thing the legacy system can’t do. The gap your customers don’t know they’re missing. That’s where you beat Axiom, not just match them. — NV”
Robert forwarded the text to Zara.
Monday, March 9, 2026 – 7:00 AM – Atlanta Express Shipping
Zara went back into the field. Nora’s text had landed.
She spent two days at dispatch centers — not watching this time, but asking a different question. Not “what’s broken?” but “what would you do if the system could do anything?”
Renee thought about it. “I’d want the system to tell me about problems before the customer calls. Right now, I find out about a delay when the shipper calls me screaming. By then I’m behind.”
“You want predictive exception alerts.”
“I want to know that a snowstorm in Michigan is going to delay six shipments before the first shipper calls. Then I call them first. I’m not explaining a problem — I’m delivering a plan.”
Zara wrote it down. Three words: Proactive exception notification.
The second dispatcher said something different. “I want to see all my shipments on a map. Not a list. A map. With the weather. With the traffic. With the carrier locations. So I can see trouble before it reaches the shipper.”
The third: “I want to confirm delivery with a photo. The shipper asks ‘did my stuff arrive?’ and I have to call the carrier, who calls the driver, who may or may not pick up. If the driver could snap a photo at delivery, I’d have proof in real time.”
None of these features existed in the legacy system. None of them existed in Axiom’s platform either.
Wednesday, March 11, 2026 – 10:00 AM – The Warehouse
Zara pinned the new feature list to her wall map. Blue pins for existing features they were rebuilding. Green pins for new capabilities the legacy system had never offered.
“Proactive exception alerts. Map-based shipment visualization. Photo confirmation at delivery.” She looked at the team. “These are the things that make dispatchers choose us over Axiom. Not feature parity. Feature advantage.”
“We’re not at feature parity yet,” Maya said.
“I know. But when we launch, we need both. Parity on the table stakes. Advantage on the things that win hearts.”
Dane pulled up his whiteboard. “How much additional build time?”
“Proactive alerts are mostly infrastructure. We already have the GPS and weather feeds. Maya — how long to build the predictive model?”
“Two weeks for a basic version. A month for something reliable.”
“Map visualization?”
“Kevin’s already prototyped that. It’s a front-end exercise.”
“Photo confirmation?”
“That’s a mobile integration. Different platform. We’d need a driver app.”
Dane drew the options. “We can do alerts and visualization within the current timeline. Photo confirmation pushes us past the deadline.”
“Then we launch with alerts and visualization. Photo confirmation goes in wave two.” Zara circled the two green pins. “These are our differentiators. Axiom matches us on speed. Nobody matches us on proactive intelligence.”
Harry was watching the exchange. Zara and Dane, working the priorities like a rally team — Zara navigating, Dane driving. He didn’t feel left out. He felt like the map they were navigating from.
DANE
Tuesday, April 7, 2026 – 9:00 AM – The Warehouse
Robert brought two board members to the warehouse. Victoria Hartwell and James Crawford. Victoria had seen the video demo. James hadn’t seen anything.
Dane had structured the presentation. Not a technical walkthrough — a methodology demo. Show them how twelve people could do what two hundred consultants couldn’t.
“The approach has three pillars,” Dane said, standing at his whiteboard. “Product-led prioritization, domain narration, and AI-amplified development.”
He drew the diagram. Zara’s customer map feeding into the build priority. Veteran narrations feeding the knowledge model. The AI translating domain knowledge into testable code. Engineers reviewing and refining. A continuous loop.
“Each module starts with a customer need,” Dane said. “Not a system specification. Not an architecture diagram. A dispatcher trying to do their job.”
“Show me,” James Crawford said. He was a former banker. Not impressed by whiteboards.
Zara took over. “Pick a scenario.”
James thought. “A hazmat shipment. Lithium batteries. Cross-border, Mexico to Canada.”
Harry typed the scenario into the system. Five seconds later: complete route, documentation requirements, three carrier options with pricing, compliance alerts, estimated transit time.
“That takes an hour in our current system,” James said.
“We built that capability in two weeks,” Maya said. “Harry narrated the hazmat routing rules. Ruth provided the compliance logic. Gloria mapped the customer workflow. Kevin and Deepa built it.”
“Two weeks.”
“Two weeks of building. Three months of accumulated domain knowledge making those two weeks possible.”
James looked at the screen for a long time. Then at the twelve people in the room. The veterans with their binders and reading glasses. The engineers with their hoodies and multiple monitors. The product person with her Moleskine. The org architect with his whiteboard marker.
“How soon can you launch?” he asked.
“July 2026,” Zara said. “Feature parity plus two capabilities the legacy system has never had.”
“What capabilities?”
“Proactive exception alerts — the system warns dispatchers about problems before customers call. And map-based visualization — dispatchers see all their shipments in real time with weather and traffic overlays.”
“Axiom has that?”
“Axiom has neither.”
Wednesday, April 15, 2026 – 4:00 PM – The Warehouse
End-of-month review. Robert sat with Zara, Dane, and Maya.
“Crawford called me this morning,” Robert said. “He used the word ‘remarkable.’ James Crawford has never used that word about anything at Meridian.”
“We’re at 80%,” Maya said. “Accelerating. Three months to feature parity and launch.”
“Risks?”
“Integration testing,” Dane said. “We’ve built the modules. We haven’t stressed them all together under production load. That’s the next phase.”
“Customer migration,” Zara added. “We can build the best platform in the world. If customers can’t move their data onto it, it doesn’t matter.”
“And people,” Maya said. “Five months of intensity. The team is holding, but we need a break.”
Robert raised his eyebrows.
“A week off in September,” Dane said. “Full stop. Recharge.”
“In the middle of the most critical project in company history?”
“Because it’s the most critical project in company history. I watched the Helix team collapse at month ten because we sprinted through month seven. A week now buys three months of sustainable velocity through launch.”
Robert looked at Zara.
“He’s right,” she said. “Kwesi told me last week I sound different on the phone. Not tired. Distant. When the product person is too burned out to hear the customer, the product is in trouble.”
“Take the week,” Robert said. “Come back sharp.”
Thursday, April 30, 2026 – 6:00 PM – The Warehouse Roof
Last sunset before the September break.
The whole team on the roof. Camping chairs, Thai takeout from the place around the corner. A tradition that had started in April when Harry and Maya went up to escape the whiteboard fumes and everyone else followed.
Robert had come for this one.
“Two months to go,” he said. “Eighty percent done. The board believes. Two board members who voted against us are now advocates.”
“What happens after we launch?” Deepa asked.
“We keep building. The platform isn’t finished at launch. It’s finished when customers say it’s finished.”
“And what happens to us?”
“The twelve of you will always be the founders. Whatever comes next, you built this.”
Gloria raised her Thai iced tea. “To the twelve.”
They raised their cups.
The sun went down behind the Atlanta skyline. Zara was already making notes in her Moleskine — dispatch workflows she wanted to observe during the break, competitors she wanted to study. Dane had his arms crossed, watching the team, calculating nothing for once. Maya was talking to Harry about something that made them both laugh.
Harry turned to the group. “This is the most fun I’ve had in forty years.”
“You’ve been saying that every month,” Sofia said.
“It’s been true every month.”
End of Chapter 7