“Ethan, people want something they can understand in ten seconds.”
“They’ll understand it when it saves them money.”
Claire looked between them.
“We need both.”
Ethan nodded.
“I agree. But the system has to work first.”
As the competition approached, Brandon became increasingly impatient.
He wanted to simplify the project.
Remove the complicated operational details.
Concentrate on a presentation that would impress the judges.
Ethan refused to present savings estimates they hadn’t verified.
One afternoon, Brandon closed his laptop and looked across the library table.
“I don’t think this is going to work with you leading the technical side.”
Ethan stared at him.
“Why?”
“Because you keep slowing everything down.”
“I’m checking whether the assumptions are accurate.”
“We need something investors will trust.”
Ethan looked at him.
“And you don’t think they’ll trust the numbers?”
Brandon hesitated.
Then he said something Ethan would remember for years.
“We need someone people will take seriously.”
The room became quiet.
Claire looked down.
Trevor avoided Ethan’s eyes.
Ethan slowly closed his notebook.
“All right.”
Brandon seemed surprised.
“All right?”
“I’ll work on my own version.”
He gathered his papers.
Then he left.
He walked home that evening carrying a backpack full of notes and a disappointment he didn’t know how to explain.
When Diane asked what happened, he told her.
She listened carefully.
Then she said, “Are you quitting?”
Ethan looked up.
“No.”
“Good.”
He frowned.
“That’s all?”
She smiled.
“You’re not quitting. Then we have work to do.”
Ethan laughed.
And for the first time that day, he felt like he could breathe.
He began rebuilding the project from the beginning.
He needed a way to simulate delivery routes using realistic data.
He knew the mathematics.
He understood the problem.
But he wasn’t yet skilled enough to build the complete software on his own.
That’s when Marcus Bell became involved.
Marcus was nineteen, a former student from Ethan’s school who worked part-time at an auto parts store while taking community college programming classes.
He was quiet, practical, and unusually patient with technical problems.
The two had known each other for years.
Marcus never cared what Ethan wore.
He cared whether an idea worked.
When Ethan explained the project, Marcus listened.
Then he asked, “Can you prove the savings?”
“With a working model, I think so.”
Marcus nodded.
“Then let’s build one.”
They worked at Ethan’s kitchen table.
Marcus wrote code.
Ethan created routing models and entered sample delivery data.
They tested different schedules.
Adjusted vehicle availability.
Added delivery windows and warehouse loading times.
The first version didn’t work.
Neither did the second.
By the third week, the program could calculate routes, but it couldn’t adjust properly when a delivery took longer than expected.
Ethan became frustrated.
One evening, he sat staring at the screen while Marcus reviewed an error message.
“This isn’t going to work,” Ethan muttered.
Marcus looked up.
“Not yet.”
Ethan sighed.
“We’ve been at this for hours.”
Marcus smiled.
“Then we’ve learned several ways not to do it.”
Ethan laughed despite himself.
They kept working.
Eventually, they developed a basic model that could reduce wasted miles by considering loading delays, delivery windows, and vehicle capacity.
It wasn’t elegant.
It didn’t have beautiful graphics.
But it worked.
When competition day arrived, Ethan wore his repaired jacket.
Diane had pressed his shirt the night before.
Marcus carried the laptop.
They set up their presentation at a small table near the back of the exhibition hall.
Brandon’s group had a polished display, professionally printed graphics, and an impressive slide presentation.
Ethan noticed them across the room.
Brandon looked surprised.
“You actually entered?”
Ethan nodded.
“Yes.”
Brandon glanced at the laptop.
“Well, good luck.”
Ethan smiled.
“You too.”
He turned back toward his project.
He didn’t want another argument.
He wanted to show what he’d built.
During the preliminary judging, one of the evaluators asked Ethan to demonstrate how the system would respond if a vehicle were delayed.
Marcus entered a new delivery time.
The program froze.
For a moment, nobody spoke.
Ethan felt heat rise in his face.
The evaluator looked at the screen.
“Is something wrong?”
Ethan took a breath.
“Yes. There’s an error in how we update the route.”
He didn’t pretend otherwise.
He asked for a moment to check the calculation.
Marcus opened the relevant code.
They found the problem.
A delivery window had been counted twice.
They corrected it.
Then the system recalculated the routes.
The evaluator watched the results.
The new schedule reduced unnecessary travel and avoided the loading bottleneck.
She leaned closer.
“How much would this cost a small company to implement?”
Ethan explained that the early version could run on existing computers and wouldn’t require businesses to replace their vehicles or purchase expensive equipment.
The evaluator nodded.
“Interesting.”
Then she asked, “What makes your approach different?”
Ethan looked at the screen.