The map and the first module.
The first piece of an AI operating system: a map of where your operation lives today, and the costliest jump between those tools moved into one system and running. You keep both, whether or not we continue.
Three things, on paper and in production.
Not a report. Not a slide deck. The map, one module running in your operation, and a number measured on your own data.
The map of your operation
Every tool the operation lives in, and every copy between them: who copies what, from where to where, how many times a day. Drawn on one page. It is also the order of everything that could come next.
The first module, running
The costliest jump, moved into one system and running in your operation: the AI prepares, a person dispatches. Built so the second module fits, if there is ever a second one.
The number, with its source
Minutes per task before anything changes, ten real runs. The same measure on day 30, written down with where it came from. If the hours did not come back, that gets written down too.
Bookings or jobs, a team in the field, money that has to reconcile.
Tours and activities, transfers and small fleets, field services, property management, equipment rental, small logistics. Fifteen to seventy-five people, with two to four of them coordinating the rest. The signs I look for on the call:
- 01You name three or more tools without noticing.
- 02Someone has “operations” or “coordination” in their title.
- 03The month-end close takes a day.
- 04The owner answers messages at night.
- 05You already paid for software that “didn’t fit”.
Not for: a task that changes its rules every month, or one the team already does well and fast. Automating that does not pay for its own upkeep, and I will say so on the call.
What it looks like when it works.
One operator in Lisbon. It started with one module, the messages, and grew module by module until the whole day ran in one system.
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.
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.
Two weeks of work. One number at the end.
Remote, on your own tools. A screen-share while someone does the task once, end to end; what your tools already record; two people timing the same task for three days. Then the build. Then the same measure, thirty days later.
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 by you 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.