Chapter 95: The Supplier Who Said No

The meeting in Wales began with a cup of tea and a refusal.

Adrian had expected the refusal.

He simply hadn't expected it to come before they sat down.

Gareth Morgan stood beside the entrance of his factory, hands tucked into the pockets of his jacket, while rain tapped against the corrugated roof behind him.

"You want too much capacity," he said.

Adrian looked at the building.

"How much do you think we need?"

"Enough that I wouldn't be able to serve my existing customers."

Daniel glanced at the figures on his tablet.

"We're offering minimum-volume guarantees."

"Guarantees don't create machines overnight."

Gareth opened the door.

"Come inside."

The factory was older than Sterling Industrial Works by several decades.

There were no polished floors. No enormous glass offices. The machinery had been maintained rather than replaced, and some of the equipment looked old enough to have survived several generations of engineers.

But everything was clean.

Everything had a purpose.

And the workers knew the machines.

Adrian noticed that immediately.

A machinist stopped beside one of the forging presses and adjusted something with a spanner without consulting a manual.

Gareth saw him watching.

"That machine is thirty-one years old."

"Still works."

"Better than some newer ones."

Adrian smiled.

"That's dangerous to say around a billionaire."

Gareth laughed.

"You're not going to buy it?"

"No."

"Good."

They continued walking.

At the far end of the factory stood an empty section.

Gareth pointed toward it.

"That's where the expansion goes."

"How much?"

"New forging line, heat-treatment equipment, inspection systems, automated handling. About twenty-two million pounds."

"Timeline?"

"Fourteen to eighteen months."

Adrian looked at Daniel.

"Can we accelerate?"

Daniel checked the figures.

"Maybe twelve."

Gareth shook his head.

"Twelve if nothing goes wrong."

Adrian looked at him.

"And something always goes wrong."

"Now you're learning."

They walked into a small conference room.

Gareth poured tea.

Adrian sat opposite him.

"I'll finance the expansion."

Gareth didn't answer.

"Equipment financing," Adrian continued. "Not cash into your company."

"Why?"

"Because I don't want you spending money on anything unrelated to the capability we're building."

Gareth studied him.

"And in return?"

"Ten-year supply agreement."

"Exclusive?"

"No."

That surprised him.

"No?"

"I don't want exclusivity."

"Why not?"

"Because if your entire business depends on us, you become fragile. If we become your only customer, we become fragile."

Gareth leaned back.

"You've thought about this."

"I've had to."

Daniel placed a draft agreement on the table.

Gareth didn't touch it.

Instead, he asked, "What happens if your vehicle programme fails?"

Adrian looked directly at him.

"Then you still have the machines."

"And the financing?"

"Still yours to repay under the agreed schedule."

"And if Sterling cancels the programme?"

"Your other customers remain."

Gareth stared at him for several seconds.

"Meridian offered me more money."

"I know."

"They offered to buy seventy percent."

"I know."

"They would have funded the expansion."

"I know."

"Why should I take your deal?"

Adrian looked around the room.

"Because you're not looking for someone to buy your company."

Gareth said nothing.

"You're looking for someone who will help you build the next twenty years."

The older man lowered his eyes.

For the first time since Adrian had arrived, he looked less like a businessman negotiating a contract and more like a man deciding what he wanted his life's work to become.

Finally, he picked up the agreement.

"I'll have my lawyers review it."

Adrian smiled.

"That's all I'm asking."

The agreement wasn't signed that day.

Adrian didn't mind.

He had learned that speed and urgency weren't the same thing.

Some decisions needed pressure.

Others needed room.

By the time they left the factory, the rain had become heavier.

Daniel climbed into the car beside Adrian.

"Do you think he'll accept?"

"I think he wants to."

"That's not the same thing."

"No."

Adrian looked through the window at the factory disappearing behind them.

"But that's enough for today."

Daniel checked his tablet.

"We have another problem."

"Of course we do."

"The battery cooling redesign."

Adrian looked at him.

"Emily?"

"She sent preliminary numbers."

"How bad?"

"Not bad."

"Then why do you look worried?"

"Because the redesign is changing the battery enclosure."

Adrian sighed.

"How much?"

"Eight millimetres."

"That's nothing."

"It is when the chassis is already fixed."

Adrian leaned back.

"Can we accommodate it?"

"James thinks so."

"Then let them."

Daniel nodded.

"There is another issue."

Adrian turned toward him.

"Go on."

"The cooling system is becoming more complicated."

"How?"

"Additional channels. More sensors. More control valves."

"How many?"

"Thirty-six."

Adrian frowned.

"Thirty-six additional components?"

"Yes."

"That's too much."

Daniel nodded.

"That's what James thinks."

Adrian looked outside.

"Arrange a meeting."

The engineering team gathered at Sterling Industrial Works the following morning.

Emily joined remotely from Cambridge.

James stood beside the vehicle architecture model.

Miriam had the electromagnetic system displayed on the opposite screen.

Adrian looked at the assembled team.

"Explain the problem."

Emily began.

"The battery performs better than our original model predicted, but heat distribution isn't uniform under prolonged high-load operation."

"Cause?"

"The new cell architecture changes internal resistance."

"Solution?"

"More cooling."

Miriam shook her head.

"That's not the solution."

Emily looked at her.

"What do you mean?"

"We're treating the battery as if the only answer is more cooling capacity."

"Because it needs more cooling capacity."

"Or it needs less heat concentration."

Silence.

Miriam pulled up the thermal model.

"Look at this section."

A cluster of cells highlighted on the screen.

"The hottest region isn't evenly distributed. Most of the pack remains significantly cooler."

Emily leaned closer to the screen.

"So you're suggesting we change the cell arrangement."

"Partly."

"That affects energy density."

"Yes."

Emily thought about it.

"How much?"

"Maybe two percent."

Adrian looked at both women.

"Two percent loss in energy density?"

"Potentially."

"And what do we gain?"

Miriam pointed at the thermal map.

"Much more uniform temperature distribution."

Emily studied it.

"Which means less cooling demand."

"Exactly."

Adrian looked at Emily.

"Would the battery still beat the original baseline?"

"Yes."

"By how much?"

"Approximately twelve percent."

Adrian nodded.

"Then do it."

Emily smiled.

"You're choosing the less efficient cell layout."

"I'm choosing the one that works."

She nodded.

"Fair."

Adrian looked around the room.

"This is the prototype rule."

Everyone listened.

"We are not building the most impressive machine on paper."

He pointed toward the vehicle model.

"We're building the machine that can actually exist."

James nodded.

Miriam smiled faintly.

The meeting moved on.

The next problem was software.

Sterling's software team had designed the vehicle around distributed control.

It was one of Adrian's earliest requirements.

If the central computer failed, the vehicle couldn't simply become a very expensive piece of furniture.

But distributed systems created their own problems.

James brought up the latest architecture.

"We have twelve control domains."

"Too many?"

"No. But communication between them is becoming complicated."

"Latency?"

"Partly."

"Security?"

"Also."

"Power?"

"Yes."

Adrian looked at him.

"How many problems are there?"

James smiled.

"Enough."

Adrian waited.

"The problem is that every system wants priority."

"The battery management system wants priority. Drive control wants priority. Thermal management wants priority. Safety systems want priority."

"Which one gets it?"

"Safety."

"Always?"

"Yes."

Adrian nodded.

"Then design around that."

James looked at him.

"That's easier to say than implement."

"Then implement it."

James laughed.

"You really enjoy making simple statements about complicated problems."

"I pay people to solve complicated problems."

The room laughed.

For the first time that morning, the tension eased.

Then James looked back at the screen.

"We'll need a physical fail-safe."

"Explain."

"If software fails, some safety functions need to remain operational without relying on the main network."

Adrian nodded.

"Build it."

"That adds cost."

"How much?"

"Maybe £4 million."

"Build it."

Robert, sitting at the back of the room, wrote something down.

Adrian noticed.

"What?"

"I'm keeping track."

"Of?"

"How many times you've said 'build it' this week."

Adrian smiled.

"How many?"

"Thirty-seven."

"Only?"

The room laughed again.

That afternoon, the first real disagreement between Adrian and Robert came.

They were reviewing the programme finances.

The controlled budget remained £230 million.

Current commitments had reached £171 million.

Robert pointed toward the projected expenses.

"If we approve everything currently requested, we reach £226 million."

Adrian looked at the screen.

"What's missing?"

"Contingency."

"How much?"

"Almost nothing."

Adrian leaned back.

"What's the largest remaining uncertainty?"

"Tooling."

"How much?"

"Potentially £12 to £18 million."

Adrian was silent.

Robert continued.

"We either reduce the programme scope or increase the budget."

"No."

Robert looked up.

"No to which?"

"Both."

Robert frowned.

"Then what?"

Adrian pointed at the programme.

"We find another way."

"That's not financial planning."

"It's exactly financial planning."

Robert shook his head.

"We're not short of money."

"I know."

"Then why refuse to increase the budget?"

"Because if we increase it every time something becomes difficult, the budget stops meaning anything."

Robert nodded slowly.

That was the answer he had expected.

Adrian continued.

"The prototype doesn't need every feature."

"What gets removed?"

"Nothing that affects the core platform."

"Everything else?"

"Delay it."

Robert looked at the list.

"Luxury interior?"

"Later."

"Advanced entertainment?"

"Later."

"Autonomous driving features?"

"Later."

"Premium materials?"

"Later."

Robert smiled.

"That saves us."

"It also keeps the project honest."

Adrian stood.

"We're building the first Sterling vehicle."

He looked at the projected model.

"Not the final Sterling vehicle."

That evening, the manufacturing team made another breakthrough.

The revised near-net forging design reduced the amount of material removed from the drive-unit housing by sixty-three percent.

Machining time dropped from fifty-three minutes to twenty-eight.

Tool wear fell significantly.

The cost of each housing dropped by almost forty percent.

Miriam walked into Adrian's office holding the report.

"It worked."

Adrian looked up.

"How much?"

"Forty percent cheaper per unit."

He smiled.

"That's better."

"There's more."

"What?"

"We can use the same process for two other structural components."

Adrian leaned back.

"Then do it."

Miriam shook her head.

"You've said that already."

"And?"

"Nothing."

She placed the report on his desk.

Then she paused.

"You know what the strange part is?"

"What?"

"We're starting to design the factory around the product."

Adrian looked at her.

"Shouldn't we?"

"Most companies do the opposite."

"Why?"

"Because factories already exist."

Adrian looked through the glass wall toward the production floor.

"Then we shouldn't be most companies."

Miriam smiled.

"No."

She walked away.

At 9:15 p.m., Adrian finally left the factory.

His phone showed one unread message.

Sophia.

7:30 tomorrow. Don't forget.

He replied.

I won't.

Another message arrived.

And Adrian?

Yes?

You owe me a dinner without talking about batteries, factories, suppliers, cars, money, or Meridian.

He smiled.

That's most of my vocabulary.

Her response came almost immediately.

Then learn new words.

Adrian laughed.

He put the phone away.

For the first time in several days, he wasn't thinking about the factory.

Not immediately.

At 11:59 p.m., the System appeared.

[Daily Check-In Available.]

Adrian tapped the notification.

[Day 95 Check-In Complete.]

[Reward: £19,000,000 Liquid Capital.]

The transfer completed.

Adrian looked at the number briefly.

Then he closed the System.

The important numbers tonight were elsewhere.

Fourteen percent battery improvement.

Sixty-three percent less machining waste.

Forty percent reduction in drive-unit housing cost.

Two hundred and thirty million pounds remained the programme ceiling.

Eighteen months remained the target.

And for the first time, Prototype 01 was beginning to look less like an expensive experiment and more like the beginning of a manufacturing system.

Adrian stood by the window of his bedroom.

The city was quiet beneath him.

He had money.

He had companies.

He had factories.

But the thing that mattered most was becoming increasingly clear.

The real advantage wasn't how much he could afford to buy.

It was how quickly Sterling could learn.

Every mistake became data.

Every failed design became knowledge.

Every supplier problem became a reason to build another capability.

The company wasn't simply developing a vehicle anymore.

It was learning how to manufacture one.

And that was a much bigger achievement.

Tomorrow, Adrian had dinner with Sophia.

For one evening, he intended to leave the future of Sterling alone.

But tonight, before sleeping, he opened the prototype schedule one last time.

The eighteen-month target remained untouched.

For now.