I build AI operating systems for businesses.
One system for an operation that used to live across tools that never talked to each other.
Until one question.
“How do we stop typing every reminder by hand?”
The first module. Everything after it grew from the same data.
Four modules, four before-and-afters, four numbers.
Each one measured on its own, in minutes per task, on this operator’s production data. The screens are recorded in the demo tenant.
The messages write themselves. Sending stays one tap.
The schedule stopped being a picture and became data.
A last-minute tour used to mean five phone calls.

The balance settles as each tour closes.
The areas talk to each other.
Nothing is typed twice. Every booking is read once, and the same data runs the day.











In her wordsJeff’s work had a very significant impact on our operation. The tools he developed let us raise productivity, cut the time spent on operational tasks considerably, and have far more control over the company’s different processes. They also brought more organisation and alignment between the different areas, making day-to-day communication and management much more efficient.
Beyond the technical quality of the work, I would also highlight his professionalism, his ability to understand the needs of the business and, above all, his readiness and availability to find solutions and answer the challenges that came up along the project.
I recommend Jeff without hesitation to any company looking for someone competent, responsible and focused on creating solutions that truly generate value for the business.
The numbers, with their source.
Where AI does not touch.
Writing this list with the client is part of the delivery, not an appendix. A team that does not know where the machine stops distrusts it entirely. The default:
- 01Decisions about peopleHiring, letting go, evaluating, changing someone’s shift.
- 02Money going outPayments, the final price, discounts, credit.
- 03Messages that leave with the company’s name, unreviewedWhen the subject is a complaint, a cancellation, money, or something that already went wrong.
- 04Clinical, legal or tax judgmentA model can draft. It does not sign.
- 05Any output whose data source cannot be tracedIf a number has no source, it does not go out. Missing data pauses the flow and tells a person.
- 06What the team already does well and fastAutomating that does not pay for its own upkeep.
In this system that line is the whole design. The schedule is built by the managers because it is a judgment about people. The balances are plain code because they must be right. The customer send is a human decision because the cost of being wrong is the channel the business runs on.
The map and the first module.
Fixed price, one to two weeks, quoted after the call. You keep the map of your operation and one module running, whether or not we continue.
Map the operation. Time the costliest jump.
Every tool the operation lives in, and every copy between them. Minutes per task, ten real runs, before anything changes.
Draw the line. Build the first module.
What the AI will do and what it will never do, approved before the build. The first module is built so the second one fits.
Measure again, same unit.
Same task, same method. If the hours did not come back, that gets written down too.
Tell me which jump between your tools costs the most.
Full disclosure: I work at that company. I built the system that runs the operation where I work, so I live with my own decisions.