Find revenue leaks by tracking the stages between discovery, inquiry, estimate, and completed work. Repair the first consequential handoff failure before buying additional traffic or software.
Look for leakage across the whole journey
A trades business can lose suitable opportunities at several points: customers cannot understand the service, calls go unanswered, requests lack an owner, estimates arrive late, or replies sit unnoticed. AI may help with some of these problems, but calling all of them an AI gap obscures the cause. Map the customer journey from discovery to completed work and write the evidence available at each stage. The first measurable break in that chain is usually a better starting point than the most fashionable tool.
Distinguish discovery from conversion
If few suitable people find the business, inspect service descriptions, listings, referrals, and marketing targeting. If people arrive but do not make contact, test the mobile website, phone links, and inquiry form. If inquiries are healthy but estimates are scarce, inspect qualification and response ownership. These are different problems with different remedies. Sample AI search answers only as one part of discovery research, recording factual errors and cited sources. An absent recommendation alone cannot tell you how many potential jobs were lost.
Follow a real inquiry through the records
Choose a recent customer request and reconstruct the timeline: first contact, useful response, qualification, appointment, estimate, follow-up, decision, and completion. A hypothetical painting inquiry might receive an immediate automated acknowledgment but wait three days for anyone to offer an assessment. The acknowledgment improved the appearance of speed without moving the job forward. Define useful response as a relevant action or answer, then identify the employee or system responsible for making it happen at each step.
Repair the smallest consequential break
If requests lack structure, improve intake fields and callback assignment. If open estimates are forgotten, implement status-based reminders that stop on a customer decision. The estimate follow-up workflow addresses that specific handoff. If source information is wrong, correct it before connecting more automation. Introduce a shared exception queue so staff can see incomplete records and failed transfers. A small repair that restores ownership can have more operational value than adding another customer-facing channel.
Use a funnel the team can explain
Track suitable inquiries, assessments, issued estimates, accepted estimates, and completed jobs using consistent definitions. Break out spam and duplicates so the numbers reflect actual opportunity. Add elapsed time between stages and the most common reason work stops. Compare contribution margin with the cost of each improvement, including review effort. The U.S. Small Business Administration's financial management guidance offers general context for maintaining useful business records. Keep the dashboard small enough that the office can act on it every week.
Keep building your understanding
Start with one useful workflow.
Tell us what happens today and where it gets stuck. We’ll help define a practical next step.