He began building a model using historical delivery information.
At first, the system was simple.
Then he added predictive traffic analysis.
Warehouse capacity forecasting.
Dynamic route optimization.
Automated dispatch recommendations.
He spent almost a year working on it during evenings and weekends.
When he presented the idea to his employer, the director of technology listened for twelve minutes and then leaned back in his chair.
“Brandon, this is ambitious.”
“That's the point.”
“We have existing vendors.”
“I know. Their systems aren't solving this.”
“Maybe they solve enough.”
“Enough is costing you millions.”
The director folded his hands.
“I'm not sure you're the right person to lead a project of this scale.”
Brandon stared at him.
“Why?”
“Experience.”
“I designed the prototype.”
“Designing a prototype and managing an enterprise product are different things.”
“Then evaluate the product.”
The director smiled.
“We appreciate your initiative.”
Two months later, Brandon resigned.
People told him he was making a mistake.
He had a daughter.
A mortgage.
A reliable salary.
Health insurance.
A career path.
Leaving a stable engineering position to start a software company with no investors looked unreasonable.
His friend Marcus Bell said exactly that over lunch.
“You have completely lost your mind.”
“Possibly.”
“You're thirty-one. You have a family.”
“I know.”
“You don't have enough money.”
“I have savings.”
“That's not what I said.”
Brandon pushed a stack of printed diagrams toward him.
“Look at the model.”
Marcus sighed.
He looked.
Twenty minutes later, he stopped complaining.
“This actually works?”
“The early version does.”
“How much could it save a midsize fleet?”
“Depending on operations, maybe eight to fourteen percent in route-related costs.”
Marcus stared at the pages again.
“You sure?”
“That's why I need pilot customers.”
Marcus leaned back.
“Then find them.”
That sounded simple.
It was not.
Brandon sent seventy-three proposals during the first six months.
Nine companies responded.
Four agreed to meetings.
Two listened to full presentations.
None signed contracts.
One executive spent the entire meeting addressing questions to the white consultant Brandon had hired to help prepare the financial projections.
Even after Brandon introduced himself as founder and chief engineer, the executive continued treating the consultant as the decision-maker.
Afterward, the consultant looked embarrassed.
“I'm sorry.”
“For what?”
“He kept asking me questions you should've been answering.”
Brandon packed his laptop.
“I'm used to it.”
“That doesn't make it okay.”
“No,” Brandon said. “It doesn't.”
The first client finally came from a family-owned shipping company in New Jersey.
The owner, an older woman named Evelyn Brooks, gave him fifteen minutes.
Brandon needed twelve.
She studied his projected savings.
“If you're wrong?”
“You pay only the agreed pilot fee.”
“And if you're right?”
“Your delivery costs fall, and you become my first long-term customer.”
She smiled.
“Confident.”
“Prepared.”
Evelyn laughed.
“Fine. Thirty-day pilot.”
The trial saved her company enough money that she extended the contract before the original month ended.
She then introduced Brandon to two other logistics businesses.
By the end of the first year, he had six customers.
By the end of the second, eighteen.
By the third, Coleman Software had employees in Philadelphia, New Jersey, and Delaware.
The company moved into a small office.
Brandon hired engineers, customer-service representatives, an operations manager, and eventually a finance director.
He insisted on paying people properly.
When investors suggested reducing employee benefits to improve margins, he refused.
“We're not building this company by making the people who build it miserable.”
One investor laughed.
“That's sentimental.”
“It's operational.”
“Meaning?”
“People who trust their employer stay longer. They learn the product. They solve problems faster. Retention is cheaper than replacement.”