Nobody googles "customer relationship management" at 9pm. They google why the quote went quiet, why the phone goes to voicemail on jobs, and why the money is three weeks behind the work. Each page below answers one of those directly, then shows the fix.
A customer who goes silent after a quote has usually not rejected it; they have been interrupted by life, are waiting on a second price, or feel awkward about questions they have not asked. Silence is the default outcome of a quote with no follow-up, and nearly half of home-service estimates never receive one.
THE FULL ANSWER →Follow-up reads as pushy when it is vague and about you ("just checking in"); it reads as helpful when it is specific and about them. Send three short messages: day 2, a question that is easy to answer ("did the quote come through, and is this a June job or sooner?"); day 5, something useful such as lead times or a photo of similar work; day 10, a polite close-the-file note that gives them an easy out.
THE FULL ANSWER →You are usually not losing on price; you are losing on follow-through. When two quotes are within 10–15% of each other, the job goes to whichever company responded faster, explained the number better, and checked in while the customer was deciding.
THE FULL ANSWER →Callbacks get forgotten because the promise lives in someone's head or on a sticky note instead of attached to the customer. The fix is to make every "I'll call you back" a task on the customer record with a time on it, created in the same motion as the promise, and to surface those tasks on one daily list.
THE FULL ANSWER →The software-category page for this leak: Follow-Up Automation Software for service businesses →
You are losing leads to competitors because they respond first, not because they are better or cheaper. A customer with a leak or a dead AC calls two or three companies and books whichever one answers; the others never hear about the job.
THE FULL ANSWER →You cannot answer every call while working, so stop trying to and fix what happens next instead. The caller who hits voicemail is already dialing the next company; a text that reaches them within seconds ("Sorry we missed you, is this about a repair or a quote?") catches most of them mid-list.
THE FULL ANSWER →Paid leads usually fail to convert because of what happens after they arrive, not because the leads are bad. A lead that waits hours for a reply has already booked a competitor; one followed up once and never again goes cold by default.
THE FULL ANSWER →Quotes take days because pricing happens at a desk, after the visit, from notes and memory, in the evening when there is no evening left. Every day between the visit and the quote lowers the close rate: the customer cools, a competitor sets the price frame first, and the quote arrives as a document rather than a continuation of the conversation.
THE FULL ANSWER →You cannot tell which marketing works because the lead's source gets lost between the first contact and the paid job: the ad platform knows the click, the phone knows the call, the scheduling tool knows the job, and the accounting package knows the invoice, and none of them share a customer. The fix is to record the source on the customer record at first contact, as one of a few fixed categories, and carry it through quote, job, and invoice, so cost per booked job by channel becomes a report.
THE FULL ANSWER →The software-category page for this leak: Lead Response Software for service businesses →
Customer history ends up in text threads because texting is the fastest way to talk to customers and nothing captures what gets said. The risk is that the business's memory now lives on one device: lose the phone, lose the employee, or simply scroll past the message, and the gate code, the agreed price, and the photo of the problem are gone.
THE FULL ANSWER →When an employee leaves, the customer relationships leave with them if the history lived in their memory, their phone, or their notebook. The protection is not a contract; it is a customer record the business owns, where every call, text, quote, job, photo, and note lands as a matter of course.
THE FULL ANSWER →You cannot take a day off because the business's memory is in your head rather than in a system. Who is owed a callback, what was quoted, which customer has the tricky gate, and which job is first tomorrow all live with you, so when you leave, the knowledge leaves.
THE FULL ANSWER →Technicians do not write job notes because the current way of writing them is slower than the job it describes, happens after the moment, and never visibly helps the person writing. The fix is not more asking; it is making capture part of closing the job on the phone: a photo, a tap for parts used, a two-line note, done in the driveway in under a minute.
THE FULL ANSWER →You cannot see what is outstanding because quotes, jobs, and invoices live in different tools and nothing joins them. The fix is a single pipeline where every customer moves through one path, from lead to quote to scheduled job to completed to invoiced to paid, and each stage shows a count, a value, and how long each item has sat there.
THE FULL ANSWER →The admin eating your evenings is mostly the same job typed into different tools: the quote re-keyed into the schedule, the job re-keyed into the invoice, the customer details re-keyed into each. Most of it disappears when one record carries the job from quote to payment, and the routine follow-through (reminders, follow-ups, review requests, payment nudges) sends itself on schedule.
THE FULL ANSWER →A business that gets busier without getting more profitable is usually leaking in four places that only show up at volume: jobs that are finished but not invoiced, quotes that are sent but never chased, customers who are served once and never asked back, and work that was priced without knowing what it cost. None of these are visible in a bank balance.
THE FULL ANSWER →The software-category page for this leak: Customer Database Software for service businesses →
The software-category page for this leak: Appointment Reminder Software for service businesses →
Invoicing falls behind because it lives in a separate tool from the job, so it depends on someone re-entering the details at a desk after a long day, and anything that depends on end-of-day data entry loses to fatigue. The fix is to build the invoice from the job record itself: the customer, the work, and the price already exist, so the invoice is one tap when the job closes, sent from the driveway.
THE FULL ANSWER →Customers pay late mostly because paying is inconvenient and nothing reminds them: the invoice arrived days after the work as a PDF, paying it means finding a chequebook or logging in somewhere, and the only follow-up is an awkward call the business keeps postponing. The fix is to invoice at completion with a one-tap payment link, keep a card on file for repeat customers, and let the system send polite reminders on a schedule.
THE FULL ANSWER →The software-category page for this leak: Invoicing & Payment Software for service businesses →
Customers do not come back because nothing reminds them to. Satisfaction is not memory: a delighted customer eighteen months later has forgotten your name and googles the job again, and whoever answers first gets it.
THE FULL ANSWER →Feast or famine happens because the work that fills next quarter (follow-ups, rebooks, referral asks, renewals) is the first thing dropped when this quarter is busy, so the quiet season arrives with an empty pipeline. The weather sets the shape; the pipeline sets the depth.
THE FULL ANSWER →The software-category page for this leak: Customer Retention Software for service businesses →
The software-category page for this leak: Review Automation Software for service businesses →
Booking takes four calls because the calendar lives where the customer cannot see it and every change has to pass through the office. The fix is to let customers pick from slots you actually offer, by text or from your site, and to confirm and reschedule by text in one exchange.
THE FULL ANSWER →Double-booking happens when more than one calendar exists: the office's, the owner's phone, the technician's memory, and the paper diary. Any booking made in one and not the others is a conflict waiting for the morning.
THE FULL ANSWER →Customers call for updates because nothing else tells them. A four-hour window with silence inside it forces the customer to chase, and every chase is a call the office has to answer.
THE FULL ANSWER →The software-category page for this leak: Job Scheduling Software for service businesses →
Thirty minutes with Mel, using scenarios from your trade. Not a feature tour: the one leak costing you most, closed live.