A home-repair company goes digital, part 3: use phase-one data to judge whether a repeat-customer entry is worth it

This series follows a home-repair company in Chonburi, step by step, into digital. The story comes from our real implementation experience in the home-services industry — if you run a small service company living off repeat customers, you should see your own vans in every chapter. Each chapter explains: what was built, what was deliberately not built, and what evidence earned the right to move on.

After phase one ran, what the company saw

The unified quote record ran for about two months, and for the first time the company saw its business in numbers, not feelings:

• The business composition became clear. AC service and leak waterproofing were the profit engines; small-appliance jobs were many but thin, and a few types lost money after fuel and hours. Which looked busy and which actually made money finally had numbers.
• The wasted-visit rate surfaced. Roughly one trip in five could have been judged over the phone with two more questions. Those trips — fuel, hours, and a technician spinning idle — were the most direct waste.
• Repeat customers were a bigger share than anyone thought. Repeat calls were above thirty percent — AC service especially, because a home’s problems aren’t one-time, they come back year after year. This made the owner seriously ask for the first time: should this group be served specially?
• The technician-hours distribution was obvious. In AC season, technicians couldn’t keep up; the small-appliance technician sometimes had no jobs in a day. The room to combine assignments and cross-team support became visible for the first time.

These numbers aren’t a fancy report. But they answered the key question: the most worthwhile investment might not be dispatch — it might be repeat customers.

The owner’s judgment: invest in what, and why not dispatch first

Many people would read the uneven-hours data and say “of course, get a dispatch system.” The owner paused and checked the phase-one data point by point:

• A dispatch system’s value rests on “volume is big and scheduling is complex enough.” At seven technicians and a dozen orders a day, the staff with the record plus phone coordination still turns the wheel — the marginal gain of a system is small;
• But losing repeat customers happens every single day. The AC customer needs service every summer — but if they can’t find your number, they call the shop on the corner instead. The neighborhood pool is only so big; every repeat customer you lose is hard to replace;
• Repeat-customer maintenance is cheap and fast. No new technician, no new process — just make sure the customer can “find you next time,” and you keep one more order.

The conclusion: worth investing in a repeat-customer entry, and it can be small and cheap. So phase two started — not a native app, but a PWA as the repeat-customer re-discovery entry, plus a feedback loop after service.

What this phase was deliberately not

• Not buying a Field Service Management (FSM) system. Phase two doesn’t solve “who goes where” — it solves “does the customer find you next time”;
• Not building a native app. Listing, review, and dual-platform maintenance are ongoing costs — too heavy an investment for a regional small company; PWA is more than enough;
• Not building a full CRM at once. No full customer profiles, no loyalty points, no automated marketing — just the repeat-customer entry and feedback;
• Not throwing away phase one. The website, quote requests, and unified record all stay; the PWA is a repeat-customer-specific re-discovery entry, not a replacement for new-customer acquisition.

What entering phase two requires

Before phase two, the company held three lines: the data was clear enough to see the business composition and wasted-visit rate, the repeat share confirmed it was worth serving specially, and the owner himself had learned to read those numbers. If any one of the three doesn’t hold, phase two becomes a shell that customers don’t use and technicians don’t care about.

Part 4 is about how phase two landed: why a PWA instead of a native app, and how the post-service notification triggers the first feedback.

---

Boundary matters: the phase-one website, quote-request form, and unified quote record form a complete loop from a new customer describing a problem to a human quote. The PWA repeat-customer entry, dispatch scheduling, online payment, customer accounts, and CRM in this series are separate projects with their own scope — they are not part of a standard website package, and entering phase two is not building a full service-management system.