He kept detailed records.
Explained repairs before performing them.
And refused to replace a functioning component simply because a customer didn't understand what was wrong with the vehicle.
When his daughter was eleven, he began teaching her how to organize his invoices.
She sat behind the counter with a pencil, a calculator, and a stack of receipts.
At first, she hated the work.
She wanted to play outside.
Her father insisted that she finish organizing the papers before leaving.
One afternoon, she discovered that a supplier had charged the workshop twice for the same part.
She showed him.
He examined the invoices.
Then smiled.
“Good catch.”
She grinned.
“Does that mean I can go?”
“Almost.”
He placed another receipt on the desk.
“Tell me what you learned.”
She sighed.
“That suppliers make mistakes.”
He shook his head.
“Sometimes.”
She frowned.
“What else?”
He tapped the paper.
“A number in a computer isn't automatically the truth.”
She looked toward him.
He continued.
“Somebody has to be willing to check.”
That lesson stayed with her.
Years later, when her father's garage became involved in a dispute over a municipal towing fee, she saw how important accurate records could become.
One of his customer vehicles had been removed during a street-clearing operation.
The paperwork associated with the tow was incorrect.
Her father spent weeks contacting offices and correcting the error.
Eventually, the situation was resolved.
But he lost work hours.
His customer lost time.
And both were treated as though their questions were an inconvenience.
The CEO was seventeen then.
She remembered her father's frustration.
More importantly, she remembered how little power he seemed to have when the official records were wrong.
He could explain what had happened.
Show invoices.
Provide photographs.
But the people behind the counter kept pointing toward their computer screens.
The system said something different.
Therefore, they assumed the system was right.
Her father eventually proved otherwise.
But the experience changed the way she understood authority.
A database could contain a mistake.
A government employee could misinterpret a record.
And a person with little money could suffer enormous consequences while trying to prove that something simple hadn't happened the way the paperwork claimed.
When she founded Lattice Integrity, she built the company around a straightforward principle.
Records should be verifiable.
Not because technology was inherently honest.
But because trustworthy systems made it harder for any one person to change the story without leaving evidence.