Chapter 60: The First Blueprint
.
---
The first thing Adrian did the following morning was cancel three meetings — not because they were unimportant, but because none of them were the most important thing on his calendar anymore.
At 6:12 a.m. he sat alone in his office with four project folders arranged across the desk, each one labelled in the same clean type he’d had his assistant apply the previous evening.
PROJECT ORION — ADVANCED AUTOMOTIVE SYSTEMS
PROJECT AETHER — NEXT-GENERATION COMPUTING
PROJECT ATLAS — RESILIENT COMMUNICATIONS
*PROJECT HELIOS — ADVANCED ENERGY STORAGE
The names were new. The problems underneath them weren’t — some of them had existed for decades, worked on by better-funded teams than the ones he’d have access to now, and abandoned or shelved for reasons that usually came down to money, patience, or both. What had actually changed was that Adrian had finally decided to put real resources behind solving them properly, rather than treating any one of them as a side project.
He opened the Orion folder first. The preliminary vehicle architecture filled the first page, dense with specifications he’d already read twice the night before. He turned it over, and the second page held something considerably more important than an engineering diagram.
A map of Nigeria.
He stared at it for several seconds. It showed industrial corridors, ports, power infrastructure, universities, transport routes, and population centres — not a finished proposal by any means, just a rough overlay his team had produced overnight after he’d given them a single instruction the evening before: *where would this technology matter most if it were built for a country rather than a market?*
That one question had already changed the direction of the entire project.
He picked up his phone. "Emma."
"Good morning."
"I need Robert in my office at seven."
"He’s already here."
Adrian glanced at the clock. 6:14. "Then send him in."
---
Robert entered a few minutes later carrying two coffees, setting one down beside Adrian without being asked.
"I assumed you’d be working," he said.
"You know me too well by now."
Robert looked at the four folders spread across the desk. "I’ve seen the preliminary proposals."
"And?"
"You’re serious about this."
"Very."
Robert pulled out the chair opposite and sat. "Then we should talk about something before this gets too large to steer easily."
"Go ahead."
"Your engineering teams are thinking like companies," Robert said. "Products, patents, manufacturing costs, market share, competitors — the ordinary things a good engineering team should be thinking about."
"They should be thinking about those things."
"But you’re thinking about something else entirely."
Adrian looked down at the Nigerian map. "I don’t want to build another collection of successful products, Robert. I want a technological foundation." He tapped the automotive folder. "If we build a vehicle whose most critical systems depend on foreign supply chains for every single component, we’ve created a product. That’s all it is — a product, vulnerable to whoever controls those supply chains." He moved his hand to the communications folder. "If our platform only functions when someone else’s infrastructure happens to be working, we’ve created another product, just as vulnerable in a different direction."
"And what do you actually want instead?"
"I want to build systems that make the companies stronger because the underlying technology itself has real, independent value — not because we happened to acquire the right patent at the right moment."
Robert studied him carefully for a long moment. "And the Nigerian map. Where does that fit into this?"
"That’s where the question stops being about engineering and starts being something bigger."
---
By 7:02, the room had filled considerably. Emma had joined them, along with the heads of strategy, manufacturing, engineering, and finance, all gathered around a table with a digital map covering the main screen — Nigeria sitting at its centre, exactly as it had on the second page of the Orion folder.
Adrian stood in front of it. "Everything we’ve already discussed for Orion, Aether, Atlas, and Helios remains valid. We’re adding one further objective on top of it."
The head of finance glanced sideways at Robert before asking, "Which is?"
"Technology transfer," Adrian said. "We’re not building these systems exclusively for European markets. We’re going to develop manufacturing capability that can eventually operate inside Nigeria itself."
Someone raised a hand near the back. "Direct manufacturing?"
"Eventually, yes."
"Automobiles?"
"Yes."
"Battery production, telecommunications infrastructure, consumer electronics — all of it?"
"All of it, in time."
The executive who’d asked hesitated before speaking again. "That’s a substantial expansion beyond anything we’ve scoped so far."
"It is."
"Why commit to something this large before we’ve even proven the first product works?"
Adrian looked back at the map. "Because I don’t want Nigeria to remain a market where other countries manufacture the things Nigerians actually need and then sell it back to them at prices decided somewhere else entirely." He let that sit for a moment before adding, "This isn’t charity. It’s business — the kind that happens to also build something worth building."
That got a small smile out of Robert.
Adrian noticed. "You’re amused."
"Because that’s almost word for word what I was about to say myself."
Adrian turned back to the screen. "We build the technology here first. We prove it commercially, on our own terms, in markets where the infrastructure already supports it. Then we establish manufacturing partnerships, and eventually our own facilities, in Nigeria — wherever and whenever the economics genuinely make sense, not before."
The strategy director spoke up. "Which sectors come first?"
"Energy," Adrian said without hesitating, and the map shifted to show power generation and transmission infrastructure layered across the country. "Then communications." Another layer appeared. "Then mobility. Then advanced electronics, last."
He looked around the table. "Those four sectors reinforce each other, which is exactly the point."
Robert nodded slowly, working through it out loud. "Reliable energy supports manufacturing. Manufacturing supports vehicles and electronics. Communications ties the whole digital infrastructure together. And all four, taken as a group, create genuinely skilled employment rather than just assembly-line jobs."
"Exactly that," Adrian said, returning to his chair. "The objective isn’t to make Aurora or Calder look philanthropic in a press release. The objective is to make them indispensable, because they build things people actually need and can’t easily get elsewhere."
---
At 8:15, the first technical briefing began, with Helios going first. Dr. Miriam Shaw, the battery researcher he’d met the previous week, stood in front of the display with three of her engineers beside her.
"We’ve reviewed your proposed energy-storage architecture," she said.
"And?"
"The chemistry is ambitious."
"That’s not really an answer."
She allowed herself a faint smile. "No, it isn’t." The screen behind her changed, and three battery architectures appeared side by side. "Current lithium-ion systems remain commercially dominant simply because the supply chain already exists, the manufacturing equipment already exists, and the engineering risks are well understood. Solid-state technology offers real advantages in energy density and safety — but the manufacturing problem underneath it remains genuinely difficult."
"Which specific problem?"
"Interfaces," she said. "Between the solid electrolyte and the electrode."
Adrian nodded, already following. "The chemistry itself isn’t actually the hard part."
"No. We need a manufacturing process that produces uniform interfaces at industrial scale, consistently, without defect rates that make the whole thing commercially pointless. That’s exactly where most serious solid-state programmes stall out and quietly get shelved."
"What would you need to actually solve it?"
"Time," she said. "Realistically, three years before I’d call anything we produce commercially credible."
"Too long."
She looked at him steadily. "Then we work faster."
"With more money?"
"With more people. More laboratories running in parallel. More simultaneous experiments than any conventional budget would normally allow — and permission to let most of them fail without consequence."
"You’d want me to fund the approaches that don’t work, too."
"Most executives wouldn’t agree to that."
"I’m not asking you to protect a quarterly earnings report, Dr. Shaw. I’m asking you to solve the problem." He nodded toward the screen. "However many failed attempts that actually takes."
Something shifted in her expression — not excitement exactly, something closer to responsibility settling into place. "Then we’ll solve it."
---
Aether followed immediately after. The objective had never been simply a better smartphone — that decision had already been made days earlier. The first prototype would combine a high-efficiency processor, dedicated AI hardware, advanced imaging, satellite connectivity, and a modular operating architecture built around local processing rather than permanent dependence on cloud infrastructure.
But Adrian added something that hadn’t appeared anywhere in the original proposal.
"Repairability," he said, and the electronics team looked up from their notes. "The device needs to be genuinely repairable, not repairable in the technical sense that voids the warranty the moment you try."
One of the engineers frowned. "That conflicts with several of our current miniaturisation targets."
"I know it does."
"The whole industry’s moving toward sealed construction for exactly that reason."
"And we’re going in the other direction."
"Why?"
"Because a device that becomes economically worthless the moment one component fails isn’t advanced engineering, whatever the marketing calls it. Design the architecture so the battery, display, communication module, and storage can each be replaced without destroying the device around them."
"That will increase the overall thickness."
"Then make the individual components smaller instead of sealing the whole thing shut."
A few people around the table smiled at that. The senior electronics engineer leaned back in his chair. "You’re asking us to solve two problems at once instead of one."
"I’m asking you to solve the right problem," Adrian said. "The easy one was never going to matter in five years."
---
By noon, Adrian had added one further requirement across every project on the table. Every major initiative would carry a Nigerian research pathway alongside it — not a marketing office, not a showroom, but a genuine pathway: university partnerships, engineering scholarships, apprenticeship programmes, manufacturing internships, dedicated laboratories, and eventually, once each piece was proven, actual production.
Robert reviewed the preliminary budget attached to all of it and looked up. "You’re committing more than two billion pounds before we’ve sold a single finished product."
"Correct."
"And you’re comfortable with that?"
Adrian looked out through the window at the city below. "No."
Robert raised an eyebrow. "That’s an unusually honest answer."
"I’m comfortable with the reason behind it, even if I’m not entirely comfortable with the number itself."
That answer stayed with Robert longer than he let on.
---
At 1:40 p.m., Geoffrey Crane called.
"I hear you’ve started something," Crane said, without any preamble at all.
"News travels quickly."
"It does when you’re spending billions of pounds in a single morning."
Adrian smiled slightly. "I assume you have an opinion."
"I have several."
"Let’s hear the useful one, then."
Crane laughed. "You’ve spent months acquiring companies scattered across half a dozen sectors — electronics, manufacturing, energy interests, communications. Half the City assumed you were just building a very expensive, very unfocused portfolio."
"And now?"
"Now you’re finally doing something sensible with all of it. You’re making them talk to each other."
That was precisely the realisation Adrian had reached only the night before. For months, every acquisition had been evaluated as an individual asset — a company, a production line, a patent portfolio, a supply contract, a management team, each judged entirely on its own terms. But the real value had never actually lived in ownership by itself. It lived in convergence. Calder’s manufacturing expertise could support Orion directly. Dominion’s precision electronics work could support Aether. The energy research underway for Helios could strengthen both of them at once, and communications could tie the entire ecosystem together into something none of the individual pieces could manage alone.
The acquisitions hadn’t been random after all, whatever they’d looked like from the outside at the time. They’d been pieces of something larger, and he simply hadn’t recognised the full picture until now. His Legendary Business Insight had stopped showing him individual opportunities one at a time and started showing him systems instead.
---
At 3:18, Adrian received the first serious engineering proposal from Calder’s automotive division. Its head stood beside a digital rendering of the vehicle, walking him through the changes.
"The prototype can be simplified," she said. "We reduce the initial number of variants down to one chassis, one battery architecture, and two motor configurations, with maximum component commonality between them."
"Good. How much does that save us?"
"Potentially thirty percent lower production complexity across the board."
"Do it," Adrian said.
She hesitated before continuing. "There’s one concern, though — your original requirement."
"Which one specifically?"
"Mass-market pricing. The advanced battery and integrated motor architecture will be expensive to produce initially, regardless of how much we simplify the variant count."
"Then the first production run isn’t the mass-market version at all," Adrian said. "We build the technology first, properly, as a premium prototype in limited production. Then we simplify it. Then we scale it. Then, once we’ve actually proven the technology works at scale, we bring the cost down to where it needs to be." He looked around at the assembled team. "Don’t confuse the first version of something with the final objective it’s working toward. Those are two different problems, and they need two different timelines."
---
At 5:06 p.m., Adrian finally returned to his office alone. Four projects, four research programmes, one strategy slowly emerging out of all of it — he opened his notebook and looked at what he’d written across the past several months. Acquisition targets. Companies. Debt structures. Negotiation positions.
He turned to a clean page and wrote something different.
BUILDING PORTFOLIO
Beneath it: Energy. Mobility. Communications. Computing. Advanced manufacturing.
And beneath all five, after a moment’s thought: *Nigeria — long-term industrial integration.*
He stared at the page for a while. For the first time since the layoff, since the flat in East London, since €47.18, the future of his portfolio wasn’t going to be determined by which company he could acquire next. It was going to be determined by what his companies could actually create.
His phone vibrated. The System.
---
*STRATEGIC DEVELOPMENT UPDATE
*Independent value creation detected.
Host has initiated multiple long-term technological development programmes without direct mission instruction.
Portfolio diversification recognised.
*External economic impact potential: SIGNIFICANT.
---
He waited for a reward notification to follow, the way it usually did.
None came. Instead, one further line appeared beneath the rest.
No immediate reward assigned.
He almost laughed out loud at that, alone in his office. "Fair enough," he said, and the panel dissolved without further comment.
He went back to the documents in front of him, and that, he realised, was exactly the point. Not everything worth building needed to come from a check-in notification. The System could accelerate his rise, provide capital when he needed it, reveal opportunities he’d never have found on his own. But if every real achievement stayed permanently dependent on the next reward arriving on schedule, then he hadn’t actually built anything of his own at all. He wanted companies whose value kept rising even if the System vanished tomorrow without warning. He wanted technology that could survive without him standing behind it. He wanted people capable of solving problems he couldn’t solve himself, and eventually, an industrial network capable of producing things that had always been considered too expensive, too difficult, or too ambitious for the ordinary market to seriously attempt.
His phone vibrated again. Not the System this time. Robert.
The investors are asking for a briefing. They want to know what we’re building.
Adrian looked at the four folders still open across his desk and typed back: *Tell them nothing yet.*
A second message arrived almost immediately. Why?
He looked through the glass at the engineers still working two floors below, lights still on well past the end of the ordinary day, and typed: Because I want the first thing they see to be real.
He set the phone down. Outside, London carried on exactly as it always did — cars crossing junctions, phones lighting faces on every pavement, factories somewhere in the distance preparing for another night shift, millions of people relying every day on technologies built by companies they’d never once think to thank.
He looked at the four folders one last time before closing them for the night. The world didn’t especially need another billionaire who simply owned more companies than the last one. It needed people willing to actually build things worth owning in the first place.
He opened the Orion folder again, and at the bottom of the first page, beneath the technical specifications, wrote one final line by hand.
Designed for Britain.
He paused, then added beneath it: Built for the world.
And after a longer pause than either of the first two lines had taken him: Eventually, built in Nigeria too.
He closed the folder.
The first blueprint was finished. The actual work was only just beginning.