Chapter 92: The First Prototype

Chapter 92: Chapter 92: The First Prototype

---

Chapter 92: The First Prototype

Monday morning began before sunrise.

By six, the design studio was already full.

Engineers stood around workstations displaying three-dimensional models of the vehicle architecture. Battery specialists had arrived from Cambridge during the night, having driven down rather than waited for the morning train. Software engineers were connecting systems diagrams across several screens, cables trailing between workstations in a way that would make the fire safety officer wince when he eventually noticed. James Fletcher moved between them with a coffee in one hand and a tablet in the other, the specific energy of a man who had clearly not slept properly and had decided caffeine was an acceptable substitute.

Adrian walked in at 6:18.

Nobody noticed him at first. He stopped near the entrance and watched.

This wasn’t a finished company. There was no polished showroom, no production vehicle, no carefully rehearsed presentation. Just people trying to solve a difficult problem, in the specific chaotic way that difficult problems actually got solved before anyone had time to make them look tidy for an audience.

James finally noticed him.

"You’re early."

"So are you."

"I’ve been here since five."

"That’s not healthy."

James looked at the coffee in his hand. "Neither is this."

Adrian smiled. "What’s the first problem?"

James turned toward the main screen, where the vehicle model was already rotating slowly.

"Everything," he said. "We have a battery architecture that isn’t finished, an electromagnetic drive system that costs too much, a cooling system still under development, and software that doesn’t have a vehicle to control yet. In that order, roughly."

"Sounds manageable."

James stared at him. "That’s billionaire optimism."

"No. It’s project planning."

James laughed despite himself and pulled up a Gantt chart that ran off the edge of the screen. "We’ve broken the vehicle into twelve major systems. If any one of them misses its development target, the prototype date moves. All twelve. Not eleven."

"How long?"

"Twenty-eight months, as currently scheduled."

Adrian shook his head. "Too long."

"I knew you’d say that."

"How much can we realistically reduce it?"

"Maybe twenty-four, if the battery and drivetrain teams work in true parallel rather than sequentially."

"Make it twenty."

James frowned. "That’s aggressive."

"Twenty-four was already aggressive. Twenty just tells us what becomes possible when we stop treating the original schedule as fixed."

James studied him for a moment, the way he did when he was deciding whether an instruction was worth pushing back on or worth simply testing. Then he turned back to the engineers.

"All right." He pointed at the screen. "Let’s find out what’s actually load-bearing in this timeline and what’s just habit."

---

The first real decision of the day was the battery.

Emily arrived at eight with two members of her Cambridge team and placed a new cell on the table with the careful reverence of someone presenting something that had cost considerably more in failed attempts than it looked like it should.

"This is the redesigned structure," she said.

James picked it up, turning it over. "It looks the same."

"That’s because the improvement is inside, not on the surface." She connected the cell to a test rig on the bench. "New electrode arrangement, reduced internal resistance, and a different thermal interface layer between the cells."

"Performance?"

She glanced at Adrian before answering, a habit he’d noticed her developing over the past few weeks — checking not for permission but for whether he wanted the cautious version of the number or the honest one.

"Early tests show twelve percent improvement."

"That’s useful," James said.

"It’s not the thirty percent target."

"No."

Adrian looked at her directly. "Can it reach thirty?"

"We don’t know yet. The physics allows for it. Whether we can manufacture it reliably at that level is a separate question."

"Then don’t design the vehicle around thirty. Design around what you actually have in hand today."

James nodded immediately, already reworking numbers in his head. "Design around twelve. Leave the architecture room to absorb more if it comes."

"Exactly," Emily said, visibly relieved that nobody was asking her to promise something she couldn’t yet deliver.

The team spent the next forty minutes reworking the battery assumptions across every dependent system. That single decision saved weeks of downstream redesign — they would build the first prototype around technology that already existed and worked, rather than a projected improvement that might not arrive on schedule. Adrian had no interest in waiting for perfection before building something. A prototype existed to reveal what the engineers didn’t know yet, not to showcase what they hoped to eventually know.

---

At eleven, the electromagnetic team arrived from Sterling Industrial Works, Miriam at the front carrying a tube of drawings under one arm.

She unrolled them across the main table. James studied the housing schematic.

"This is smaller."

"We redesigned the housing entirely. Fewer individually machined parts, more standardised sections."

"How much lighter?"

"Twenty-seven percent, compared to the version we tested last month."

James looked genuinely impressed. "That’s significant."

"It also reduces cooling requirements, because there’s less thermal mass to manage in the first place."

Emily leaned in over his shoulder. "How much?"

"About fifteen percent."

The room went quiet for a moment while people did the arithmetic in their heads. Those two figures, taken together, affected almost everything downstream. A lighter drive system meant a lighter chassis could carry it. A lighter chassis reduced the demand placed on the battery to move the vehicle at all. Reduced battery demand meant the pack itself could shrink. A smaller battery pack reduced the overall vehicle weight again, which fed back into the drive system requirements a second time.

The improvement wasn’t coming from any single miraculous component. It was coming from the way the pieces were beginning to talk to each other properly for the first time — the exact outcome Adrian had been hoping for when he’d insisted the vehicle be designed around Sterling’s own technology rather than adapted from an existing platform.

He looked at the model rotating on the screen, noticeably more compact than the version from Friday.

"That’s the platform," he said.

James nodded slowly. "For the first time, genuinely, yes."

---

The afternoon was considerably less exciting, which was exactly how good engineering usually went.

The chassis team spent three hours arguing about suspension geometry — specifically whether a double-wishbone arrangement at the front was worth the additional manufacturing complexity given the vehicle’s weight distribution, or whether a simpler MacPherson strut setup would perform close enough for a first prototype without the added cost. James eventually sided with the simpler option, over visible objection from one of the younger chassis engineers, on the grounds that the prototype’s job was to prove the platform, not win a handling award nobody had entered it for yet.

Then they spent another hour on the position of the battery cooling channels, after the thermal team pointed out that the current routing ran directly beneath where the rear passengers’ feet would sit, which was going to be a comfort problem long before it was a performance one.

The software team, midway through the afternoon, discovered that the planned distributed control architecture required considerably more processing power at the edge nodes than their initial estimate had allowed for — a discovery that produced a tense twenty-minute conversation about whether to compromise the redundancy principle Adrian had insisted on the previous week, or simply specify better hardware and absorb the cost. They chose the hardware.

A supplier delayed delivery of a critical pressure sensor by nine days, for reasons nobody could get a straight answer about, which pushed part of the cooling validation work back into the following sprint.

And one of the chassis engineers rejected an early frame design outright, pointing out that the proposed crumple zone geometry would complicate crash testing certification in a way that would cost more time later than it saved now.

Nothing dramatic happened, in the sense that nothing exploded and nobody shouted. But by five o’clock, the prototype had changed considerably from the version they’d started the day with. The vehicle was smaller. Lighter. More structurally integrated across systems that had started the morning as separate problems.

And more expensive.

Robert arrived just before six with the revised budget already printed.

"Two hundred and fourteen million," he said, without preamble.

Adrian looked up. "Wasn’t it one hundred and eighty?"

"That was the original programme, before today’s design changes."

"What changed?"

"Reality," Robert said dryly.

Adrian laughed. "Fair."

Robert pointed at the projected cost curve on the page, which bent upward more steeply than either of them liked. "If we keep adding technology at this rate, this reaches three hundred million before the prototype ever turns a wheel."

"Then we stop adding technology," Adrian said.

Robert blinked, clearly having expected more of a fight.

Adrian looked toward the engineering team, still clustered around the main screen. "We’re not building a showcase vehicle designed to impress a trade show audience. We’re building a working platform." He nodded at the model. "The first version needs to prove the architecture works. It doesn’t need to prove every feature we could theoretically add to it."

Miriam nodded from across the room, clearly agreeing.

"You want the first version to prove the platform," Robert said slowly. "Not showcase every capability at once."

"Exactly."

Robert closed the budget folder. "I’ll hold the programme at two hundred and thirty million. Anything beyond that comes back to me directly for approval."

"Good," Adrian said.

"Agreed," Robert said, and meant it as a boundary rather than a suggestion, which was precisely why Adrian had wanted him running the numbers in the first place.

---

At seven thirty, James took Adrian down to the prototype workshop.

There was nothing there yet. Just an empty floor, freshly poured and still slightly dusty in places. Steel frames stood ready along one wall. Electrical connections had been roughed in along the ceiling, waiting for equipment that hadn’t arrived. A large whiteboard dominated one end of the space, and beside it, a single sheet of paper taped crookedly to the wall.

PROTOTYPE 01.

Adrian stood in front of it for a moment.

"When does construction start?"

"Tomorrow morning."

"First component?"

"Chassis frame."

"Then?"

"Battery enclosure, once the frame’s dimensionally verified. Then the drive units go in."

James walked him through the full sequence, item by item, the specific satisfaction in his voice of someone who had spent months in meetings and diagrams finally reaching the point where actual metal would be cut.

Adrian listened to the whole list without interrupting.

For months, the company had been buying factories, negotiating supplier agreements, acquiring technology piece by piece across half a dozen separate deals that had each felt, at the time, like the entire project. Now there was finally something tangible to build. A single machine that would carry all of it at once — the battery chemistry from Cambridge, the drive system from Sterling Industrial Works, the cooling architecture still being finalised upstairs, the distributed control software, the materials science buried somewhere in Thomas’s original notebook, the manufacturing capability assembled supplier by supplier over the past several weeks.

Every decision the company had made would eventually converge in one place. Four wheels. A steering wheel. A battery. A body.

James looked at him. "Still think twenty months?"

Adrian looked around the empty workshop, at the steel frames waiting to become something. "Yes."

James smiled, tired but genuine. "Then we’ll give you twenty."

---

At eight, Adrian returned to the main office, where Daniel was waiting with a report already open.

"There’s something you should see."

"Meridian?"

"Meridian." Daniel turned the screen toward him. "They’ve bought a British power-electronics company. Supplies several major automotive manufacturers."

"For how much?"

"One hundred and ninety million."

"What was it actually worth?"

"Depending on the valuation method, somewhere between ninety and one hundred and twenty."

"So they overpaid considerably."

"Probably deliberately."

Adrian handed the report back. "Then let them."

Daniel smiled. "That’s becoming your favourite answer to almost everything."

"It’s becoming increasingly accurate, which helps." He glanced up. "What about the power-control supplier Meridian approached last week?"

"They signed."

"With us or with Meridian?"

"With us. Ten years."

Adrian nodded, satisfied. "Good."

Daniel hesitated slightly before continuing. "There’s something else. Their chairman mentioned, almost in passing, that Meridian had offered exactly double our price."

Adrian looked at him. "And they chose us anyway."

"Why do you think?"

"Because money isn’t the only thing a supplier is actually selling when they sign a contract."

"What did we offer instead?"

"Predictability," Adrian said. "Fifteen years of watching Meridian buy and discard companies teaches an owner what happens after the cheque clears. We offered them the version of the future where they still exist in it."

---

Later that night, Adrian walked through the unfinished prototype workshop alone.

The overhead lights were dimmed to their evening setting. The whiteboard still carried the day’s engineering schedule in three different colours of marker, evidence of at least two arguments that had been resolved by simply crossing something out and writing something else above it. Beside it sat the empty stretch of floor where the vehicle would eventually stand — nothing there yet but painted floor markings and a few loose cable runs.

He imagined it there anyway. Not as a rendering on a screen, not as a slide in a presentation deck. An actual machine, built by people he had personally hired, using technologies his companies had developed from scratch or rescued from a notebook older than any of them, manufactured in factories Sterling now controlled or supported through long contracts rather than acquisitions. Eventually sold under a name that, three months into the programme, still hadn’t been settled on.

He found himself smiling at the empty space, which felt slightly foolish and he didn’t particularly mind.

His phone rang. Sophia.

"You’re calling late," he said, answering.

"So are you working late."

"I’m still at the workshop."

"I guessed."

"How?"

"You only answer the phone in that specific voice when you’re looking at something expensive and pretending you’re not thinking about the number."

He laughed. "I’m looking at an empty workshop, actually."

"That’s not very impressive as billionaire activities go."

"It will be."

A short pause on the line, comfortable rather than awkward.

"How’s the car?" she asked.

"Not a car yet."

"You’re still saying that."

"Technically we’re building a vehicle platform. The car comes after the platform proves itself."

"Of course it does," she said, with the specific tone of someone who found his precision about the distinction genuinely funny rather than tedious. "Did anything happen today?"

"We started the prototype programme."

"That’s good, isn’t it?"

"It is."

She sounded pleased on his behalf in a way that still felt slightly unfamiliar to have someone do. "Are you happy about it?"

He looked around the workshop again — the frames, the whiteboard, the empty floor waiting for something real.

"Yes," he said.

It took him a moment to notice how unusual the word felt leaving his mouth in this context. Not satisfied. Not pleased with the numbers. Happy, in the plain sense he hadn’t used casually about work in longer than he could easily remember.

"I’m glad," Sophia said simply, and they talked for a few more minutes about nothing in particular before saying goodnight.

Adrian stayed in the workshop after the call ended. He looked at the whiteboard again, at the schedule written across it in three colours.

Twenty months.

He picked up a marker, crossed the number out, and wrote beneath it: 18 MONTHS.

He looked at it for a moment.

Then laughed quietly at himself. "Let’s see, then."

---

At 11:59, he returned to his office at Calder House.

He didn’t open a list of reports this time. He sat for a moment with the day settling properly, the way it hadn’t during the drive back — the battery decision, the housing redesign, the suspension argument he’d only half-followed, Robert’s budget line, the sensor delay nobody had fully explained yet, James’s twenty months that had just become his own eighteen written in someone else’s marker.

The company was no longer simply expanding through acquisition, the way it had for the first several months of its existence. It was becoming something with an actual circulatory system — technology feeding manufacturing, manufacturing feeding a real product, a product that would eventually feed new markets, and those markets, in time, funding whatever came after this one.

At midnight, the System appeared.

SYSTEM CHECK-IN — DAY 92. REWARD AVAILABLE: £17,000,000 LIQUID CAPITAL. ACCEPT?

He accepted without much ceremony and closed the notification.

Then he opened the prototype schedule one more time, just to look at it. The first physical component would go into machining in the morning — an actual chassis frame, cut from actual steel, in a building he owned, by people who worked for him because they wanted to build something rather than simply because he could pay them to.

For months he had been assembling pieces. Factories. Companies. People. Technology. Capital. Tonight, for the first time, those pieces were finally going to start becoming one single thing.

He turned off the desk lamp and looked out at the dark shape of the city beyond the window.

Tomorrow, Sterling would cut metal for its first vehicle component.

And in eighteen months, if the number on that whiteboard held, the world would find out what happened when a billionaire stopped simply buying the future and started building it with his own hands.

End of Chapter 92