One missed job a week.
AI is usually not the first problem.
For a lot of small service businesses, the first problem is simpler and more expensive: the work is already trying to arrive, but the business is leaking it.
The leak comes before the build.
A call comes in while someone is already on another job. A quote gets sent and never gets followed up. A customer asks a question by text, and nobody owns the next step. An after-hours request becomes tomorrow's problem. A service visit happens, but the maintenance or replacement conversation never gets captured clearly.
That is not an AI strategy problem. It is an operating memory problem.
One missed or mishandled job per week can become a real five-figure revenue leak. The exact number depends on the average ticket, close rate, margin, and whether the job was repair, replacement, maintenance, or emergency work. The point is not a fake calculator. The point is that a small leak repeated weekly is not small anymore.
That is why the useful first question is not how to add AI. The useful first question is where money is leaking because the work is not being captured, followed up, handed off, or remembered cleanly.
Sometimes the answer is a better process. Sometimes it is a better form, call flow, or follow-up rhythm. Sometimes a system can help. Sometimes it should stay nowhere near the customer yet.
What part of the business keeps making the same mistake after everyone is already busy?