Sales & CRM

How to qualify inbound leads as Local Service Business Founders

Sales & CRMFor Local Service Business Founders2 apps10 steps~20 min to set up

You're a plumbing or HVAC owner and your 'lead qualification process' is whoever answers the phone first writes the job on a sticky note. Google Voice messages pile up, web form submissions land in an inbox you check every other day, and by the time you call back, the homeowner already booked someone else. Jobber and Housecall Pro log the jobs you win — they don't help you work the ones still in the maybes pile. You have no idea which leads came from Google Ads vs. the Home Depot flyer vs. word-of-mouth, and you can't remember if that Oakdale apartment complex ever got a callback after the free estimate you drove 45 minutes to do.

Build this on Starch → See the apps used

Sales & CRMFor Local Service Business Founders2 apps10 steps~20 min to set up

Outcome

What you'll set up

A custom lead-qualification CRM built around how your business actually stages jobs — from first call to booked, with fields for job type, property type, estimated ticket size, and source — so nothing falls through the cracks between inquiry and dispatch

An inbox triage layer that reads your Gmail, surfaces unread quote requests and callback promises, drafts replies for you to send in one tap, and sets follow-up reminders when you go quiet on a lead for more than 48 hours

A browser-automated pipeline that pulls new form submissions or messages out of your field service platform (Jobber, Housecall Pro, or ServiceTitan — no API needed) and drops them into your Starch CRM so you're working one list, not three

The Starch recipe

Apps, data, and prompts

The combination of Starch apps, the data sources they pull from, and the prompts you use to drive them.

Apps used

CRM

Data sources & config

The CRM and Email Triage apps use Gmail as a scheduled-sync provider — Starch syncs your Gmail messages on a schedule so email threads stay attached to each lead automatically. Housecall Pro, Jobber, and ServiceTitan are reached through browser automation — Starch logs into your account through your browser, no API needed. Google Calendar is a scheduled-sync provider used to flag estimate appointments already on the books.

Prompts to copy

Build me a CRM for qualifying inbound service leads. Stages are: New Inquiry, Estimate Scheduled, Estimate Sent, Follow-Up Needed, Booked, Lost. Fields I need: customer name, address, job type (plumbing / HVAC / electrical), property type (residential / commercial / rental), how they found us, estimated ticket size, and the last thing I promised them. Flag any lead that's been sitting in Estimate Sent for more than 5 days without moving.

Set up email triage on my Gmail. Every morning at 7am, surface any emails that look like new service requests or follow-ups on estimates. Summarize each thread in one sentence, draft a reply I can send from my phone, and create a reminder if I haven't responded within 48 hours.

Every weekday at 8am, go into my Housecall Pro account through the browser, pull any new requests that came in overnight, and add them as leads in my Starch CRM with the customer name, address, job type, and the notes they left. No API needed — just log in and get the data.

Run these in Starch → or paste them into your favorite agent

Walkthrough

Step-by-step

1 Start with the CRM app from Starch's App Store and describe your qualification stages out loud: 'New Inquiry, Estimate Scheduled, Estimate Sent, Follow-Up Needed, Booked, Lost' — the AI builds the pipeline around those exact labels, not a generic sales funnel.

2 Add the fields that matter for service work: job type, property type, lead source, estimated ticket size, and a 'last promise' field where you log things like 'said I'd call Thursday with the parts price.' These are the fields you'd otherwise keep in your head.

3 Connect Gmail as a scheduled-sync provider so every email thread tied to a customer is automatically attached to their CRM record — no copy-pasting from your inbox into a spreadsheet.

4 Set up the Email Agent app to triage your inbox every morning at 7am. Tell it: 'Flag anything that looks like a new service request, an estimate follow-up, or an unhappy customer, summarize it in one line, and draft a reply I can approve from my phone.'

5 Build a browser automation that logs into Housecall Pro (or Jobber or ServiceTitan — no API needed) each morning, pulls new request forms from the previous 24 hours, and creates a matching lead in your Starch CRM with name, address, job type, and any notes the customer left.

6 Set a staleness rule on the CRM: 'Flag any lead in Estimate Sent that hasn't moved in 5 days and add it to my daily follow-up list.' This replaces the mental overhead of remembering who you quoted last week.

7 Ask the CRM a plain-English question each Friday: 'Which leads did I lose this month, and where did they come from?' Use that answer to stop paying for the ad source that's bringing in tire-kickers.

8 When a lead moves to Booked, have Starch check Google Calendar (scheduled-sync provider) and confirm there's an appointment on the books. If there's no event in the next 14 days, flag it so dispatch doesn't fall off.

9 For leads that go cold after an estimate, set an automated follow-up: 'Three days after an estimate is sent with no reply, draft a follow-up email referencing the job address and estimated price and put it in my drafts for review before sending.'

10 At the end of each week, ask the CRM: 'What's my close rate on HVAC estimates vs. plumbing estimates, and which zip codes are converting best?' No pivot table required — type the question, get the answer.

See this running on Starch

Connect your tools, describe what you want, and the agent builds it. Closed beta is free.

Try it on Starch →

Worked example

Week of March 10, 2026 — HVAC tune-up season push

Sample numbers from a real run

New inbound leads (Mon–Fri)	23
Leads surfaced from Gmail triage	11
Leads pulled from Housecall Pro via browser automation	12
Estimates sent by Thursday	14
Leads flagged as stale (>5 days, no reply)	4
Booked jobs from that week's leads	9
Average ticket size (booked)	380
Revenue recovered from stale-flag follow-ups	1,520

It's spring tune-up week and 23 leads came in across Monday through Friday — 11 from Gmail (a mix of website contact forms and direct emails) and 12 that submitted through Housecall Pro's booking widget overnight. Without Starch, four of those would have sat unread until Wednesday. With the browser automation running at 8am daily, every Housecall Pro request was in the CRM before the first technician left the yard. The Email Agent flagged three Gmail threads as 'estimate follow-up, no reply in 72 hours,' drafted a two-line check-in message for each, and the owner approved all three from his phone while waiting at a supply house. Two of those four stale-flagged leads converted — one was a $680 compressor swap, one a $840 mini-split install — totaling $1,520 that would have gone to the competitor who called back first. Close rate that week: 9 out of 14 estimates sent, vs. a historical average closer to 5 out of 14 when working off sticky notes and memory.

Measurement

How you'll know it's working

Lead response time (target: under 2 hours from first contact to callback attempt)

Estimate-to-book rate by job type (HVAC vs. plumbing vs. electrical) so you know which estimates are worth driving across town for

Stale lead count — how many estimates have been sitting more than 5 days with no follow-up

Lead source close rate — which channel (Google Ads, referral, Nextdoor, door hanger) actually turns into booked revenue

Revenue recovered from follow-up sequences — dollars booked on leads that required a second or third touch

Comparison

What this replaces

The other ways teams handle this today, and how the Starch version compares.

Jobber / Housecall Pro built-in CRM

Good for tracking booked jobs; almost no support for working leads that aren't booked yet, and you can't customize the pipeline stages or add fields like 'last promise made to customer.'

HubSpot free tier

More pipeline flexibility than field service tools, but takes real admin time to configure, has no knowledge of your Housecall Pro or Jobber data, and becomes expensive fast once you want automation.

Spreadsheet (Google Sheets)

Free and flexible, but it doesn't draft your follow-up emails, it doesn't flag stale leads automatically, and it doesn't pull new requests out of Housecall Pro while you're in a crawl space.

ServiceTitan + built-in reporting

Powerful if you're a larger operation, but expensive, rigid on customization, and still won't write your follow-up emails or triage your Gmail inbox.

On Starch RECOMMENDED

One platform — crm, founder inbox all running on connected data. Setup in plain English; numbers stay current via scheduled syncs and live agent queries.

Try it on Starch →

FAQ

Frequently asked questions

Does Starch replace Jobber or Housecall Pro?

No — and it's not trying to. Your field service platform handles work orders, dispatch, and invoicing. Starch sits on top of it and handles the qualification and follow-up work that happens before a job is booked and after an estimate goes cold. The browser automation pulls data out of Jobber or Housecall Pro without requiring an API, so both tools keep doing what they do.

Jobber and Housecall Pro don't have public APIs. How does Starch connect to them?

Through browser automation — Starch logs into your Housecall Pro or Jobber account through the browser, exactly like you would, and pulls the data it needs. No API required. This is how Starch handles any tool that's web-based but doesn't have an API connector available.

I run a very small shop — 3 techs, maybe 15-20 leads a week. Is this overkill?

15-20 leads a week is actually the sweet spot where a missed follow-up really hurts. If you're closing 7 out of 15 and a better follow-up process gets you to 9 out of 15, that's two extra jobs a week at whatever your average ticket is. The setup is a few hours, not a full IT project.

What happens when Gmail shows the OAuth consent screen? Will my customers see something weird?

When you connect Gmail, the OAuth consent screen currently shows the underlying connector's name rather than 'Starch.' This is a known issue and a Starch-verified client is on the roadmap. It only affects the one-time connection setup on your end — your customers never see it.

Can I see which leads came from Google Ads vs. word of mouth vs. my truck wrap?

Yes, if you capture the source when the lead comes in. Tell Starch to add a 'how did you hear about us' field to the CRM, and then ask it at the end of each month: 'What's my close rate and average ticket size broken down by lead source?' You'll get a plain-English answer, not a chart you have to interpret.

Is Starch SOC 2 certified? I'm cautious about giving software access to my customer data.

Starch is not currently SOC 2 Type II certified, and there's no on-premises or self-hosted option. If your business has strict data compliance requirements — for example, government contracts or healthcare clients — that's worth factoring in. For most residential and commercial service businesses, the data involved (names, addresses, job types, email threads) is lower sensitivity.

What if I want to track leads from Nextdoor or Google Local Services Ads, not just email?

If those leads land in your Gmail inbox (most LSA leads do), the Email Agent picks them up automatically. For Nextdoor or other platforms where leads come in as browser notifications or direct messages, you can build a browser automation that checks those inboxes and drops new messages into your CRM. Describe it to Starch and it will build the workflow.