A home-repair company goes digital, part 2: phase one lands — a quote-request form, phone/LINE guidance, and one unified quote record

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.

Why home-repair quoting can’t skip the site visit

Answer one unavoidable question first: why can’t this work like many services, where the customer orders online and pays directly?

Because the problem in home repair is vague at quote time. “The tap is leaking” could be a worn washer, a water-pressure issue, or a cracked pipe — the price can’t be known until a technician sees it on site. That isn’t a lagging process; it’s the nature of this business: problems are judged on site, and quotes are confirmed by a person.

But “must be judged on site” does not mean “every trip is wasted.” Many jobs can be screened in a short phone or video call: if the customer describes clearly enough, the technician can judge whether to visit, what parts to bring, and roughly what range the price is in. And to get there, the company has to get customers to describe the problem the right way first.

What phase one actually did: get the description down

The first website did three things to make “the description” land:

1. Quote-request form. Not an order form — a few fixed questions: what’s the problem, what type (plumbing/AC/appliance/leak), roughly when is convenient, where is the home, how to reach you. The more complete the description, the easier the staff to log and the more prepared the technician.
2. Service-scope and quote-logic page. Says clearly what the company does, how it prices, and what needs a site visit. After reading it, customers ask better questions, and the staff answers one time fewer.
3. Phone/LINE guidance. Every page nudges the same way: describe the problem first, then wait for a human quote. Not self-service ordering — it moves the starting point of the enquiry from “something’s wrong at my house” to “here’s what’s wrong and roughly when I’m free.”

At the same time, the staff logged every quote request into one unified quote record — this is the real lead of the chapter. Every record keeps four things:

1. Source — website form, phone, or LINE;
2. Problem type — plumbing, AC, appliance, or leak;
3. Quote outcome — how much was quoted, whether the customer accepted, dropped it, or cancelled;
4. Technician and hours — who went and how many trips.

The record lives where the staff already works, maybe a shared spreadsheet. What matters is that staff jots one line while taking the order, so the company has data to look at for the first time.

Why technicians and staff would go along

The easiest way for a home-service company to fail here is to make the staff feel the system is “for the boss to watch.” So the design held three lines:

• The record helps the technician, not just the boss. Problem type and hours in the record are references for “what parts should I bring” — the more accurate, the easier next time;
• Only record what drives decisions. No long reports from technicians; four columns are enough. The record is for seeing direction, not for a pretty report;
• The owner actually reads it. Flipping through once a week, and asking the staff with the numbers “which type of job was most this week, how many wasted trips?” — only then does everyone know someone really looks at this, not fill-and-forget.

The technicians’ work itself didn’t change — still going on site, looking, quoting, and doing the job. What changed was being more prepared before leaving, and leaving one line of record when coming back.

What this phase was deliberately not

• No dispatch scheduling system. No route board, no auto-dispatch, no tracking — seven technicians’ work isn’t worth a system yet;
• No native app. No store listing, no download, no accounts — the repeat-customer entry is a phase-two PWA discussion;
• No collecting payment right after an online quote. Quote confirmation, work, and collection stay on existing channels;
• No integration with any platform. No dispatch platforms, no channel integration.

What entering the next phase requires

After the quote record had run for a while, the company could finally answer these questions:

• which problem type is most, which makes money, which loses money;
• how high the wasted-visit rate is, and which jobs could have been judged over the phone;
• what share of repeat customers is, and how customers find their way back;
• where the technicians’ hours go, and which jobs could be combined.

Those numbers are what Part 3 is about — using phase-one data to judge whether a repeat-customer entry is worth investing in.

---

Boundary matters: the shared spreadsheet the staff uses for quote requests is a simple data tool the company maintains itself. 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.