Sales & CRM

How to qualify inbound leads as Construction and Contractor Founders

Sales & CRMFor Construction and Contractor Founders2 apps10 steps~20 min to set up

You get 15 bid inquiries a month across text, email, and referrals. Half of them are tire-kickers who want a number by Friday and disappear. The other half are real jobs you actually want, but by the time you've pulled the scope out of three email threads and a voicemail, you've already spent two hours you don't have. Your current 'CRM' is a sticky note on the monitor and a starred-email folder. Buildertrend has a leads module but you never configured it. HubSpot is overkill and requires someone to babysit it. You need to know which inbound leads are worth a site visit, who still needs a follow-up call, and which ones you already lost to the guy who bid $8k lower.

Build this on Starch → See the apps used

Sales & CRMFor Construction and Contractor Founders2 apps10 steps~20 min to set up

Outcome

What you'll set up

A lead tracking CRM built around how you actually qualify construction jobs — with fields for project type, square footage, budget range, permit status, and how the lead came in — so every inbound inquiry gets scored and followed up on

An email triage system that reads your inbox, flags new bid requests and RFIs, summarizes the key details, and drafts your first response so you're not starting from a blank screen at 9pm

Automated follow-up reminders so no qualified lead goes cold — if you haven't replied to a bid request in 48 hours, Starch tells you

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 Email Agent

Data sources & config

The CRM and Email Agent are wired together: Starch syncs your Gmail data on a schedule so new lead emails surface automatically in your pipeline. If you use Outlook, Starch syncs that instead. QuickBooks is connected directly via scheduled sync so you can see which past clients have open invoices when a repeat lead comes in. Any lead data sitting in Buildertrend or CoConstruct is pulled through browser automation — no API needed — so you're not re-entering job details by hand.

Prompts to copy

Build me a CRM for qualifying inbound construction leads. I need fields for: project type (new build, remodel, addition, commercial TI), estimated budget, square footage, permit status, lead source (referral, website, Houzz, word of mouth), date of first contact, site visit scheduled (yes/no), bid sent date, and current stage (new inquiry, qualifying, site visit done, bid sent, won, lost). Flag any lead where we haven't had contact in more than 5 days. I want a pipeline view sorted by estimated budget so I can see which jobs are worth prioritizing.

Set up email triage for my inbox. Flag any email that looks like a new bid request, a follow-up on an existing estimate, or an RFI from a GC or homeowner. For each flagged email, give me a one-sentence summary of what they're asking for, draft a reply that acknowledges receipt and asks for scope details (project address, timeline, rough budget), and set a reminder if I haven't responded within 48 hours. Don't flag supplier invoices, permit office auto-replies, or subcontractor check-ins unless they mention a new project.

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

Walkthrough

Step-by-step

1 Connect Gmail (or Outlook) — Starch syncs your email on a schedule and starts scanning for inbound bid requests, RFIs, and follow-up threads from the last 60 days.

2 Connect QuickBooks via scheduled sync so the CRM can surface payment history and AR status on any returning client — useful for knowing if that homeowner who called about a kitchen remodel still owes you $4,200 from the bathroom job.

3 Tell Starch to build your lead qualification CRM using the natural-language prompt above. Describe the stages and fields that match how you actually work — not a generic sales pipeline.

4 Set up the Email Agent to monitor your inbox and flag new construction inquiries. The agent reads incoming messages and drafts a response that asks for address, timeline, rough scope, and budget — the four things you need before deciding whether a site visit is worth the drive.

5 For any lead coming in via text, Houzz message, or phone call, manually add a card to the CRM in under 30 seconds — type what you know, Starch fills in the blanks it can.

6 Run the 'qualifying' stage each morning: open your CRM, see every lead where budget is over your minimum job size and a site visit hasn't been scheduled, and decide who gets a call today.

7 After a site visit, update the lead card with actual scope notes. Ask Starch: 'Which leads have had a site visit but no bid sent in the last 7 days?' — it gives you a list with days elapsed so you know which ones are getting cold.

8 When a bid goes out, mark the stage as 'bid sent' and let the Email Agent set a 5-day follow-up reminder. If the prospect hasn't replied by then, Starch drafts a short check-in email you can send in one click.

9 When a lead is won or lost, log the reason. After 90 days, ask Starch: 'What were the most common reasons we lost bids in Q1?' — it reads the loss notes and gives you a plain-English summary.

10 At the end of each week, ask the CRM: 'Show me every open lead, their last contact date, estimated budget, and current stage, sorted by days since last contact' — your 10-minute Friday pipeline review.

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

April 2026 lead week — 11 inbound inquiries, 4 site visits worth scheduling

Sample numbers from a real run

Homeowner remodel (Maplewood) — $85k budget estimate	85,000
Residential addition (Riverside) — $55k budget estimate	55,000
Commercial TI — coffee shop fit-out (Downtown) — $120k budget estimate	120,000
Kitchen remodel (Eastside) — $18k budget estimate (below min)	18,000
Deck addition (referral) — $22k budget estimate	22,000

On Monday, 11 inquiries came in across email and a Houzz message. The Email Agent flagged 7 as bid requests and auto-drafted replies asking for address, timeline, and rough budget. By Wednesday, 5 had responded. The CRM scored them by estimated project size: the $120k coffee shop TI, the $85k remodel, and the $55k addition all cleared the minimum threshold and had permit-ready timelines. The $18k kitchen was below the minimum job size, so it got a polite 'not available until Q4' reply drafted by the Email Agent. The $22k deck was a referral from a past client — when Starch checked QuickBooks, that client had a clean payment history, so it got bumped up the list. Four site visits were scheduled by Thursday. Three bids went out the following week. Without the Email Agent, two of those initial inquiries would have gone unanswered for three days — the Maplewood homeowner later mentioned she had three contractors reach out before lunch.

Measurement

How you'll know it's working

Lead-to-site-visit conversion rate (how many inquiries are worth the drive)

Bid-to-won rate by project type (remodels vs. additions vs. new builds)

Average days from first contact to bid sent

Number of leads gone cold (no contact in 7+ days)

Pipeline value at each stage (total estimated budget of open leads)

Comparison

What this replaces

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

Buildertrend Leads module

Buildertrend has a leads tab, but it's buried inside a PM tool priced for larger shops — you're paying for scheduling, RFIs, and subcontractor portals you may not use just to get a basic inquiry tracker.

HubSpot free tier

Free to start, but the pipeline fields and automations that make it actually useful require configuration time you don't have, and the construction-specific fields don't exist — you'll end up building a workaround for every stage.

Starred-email folder + Excel

Zero setup cost, but no follow-up reminders, no pipeline visibility, and no way to answer 'which bids haven't had a response in 5 days' without reading every email yourself.

Jobber

Strong for quoting and scheduling field crews, but it's built for service businesses (HVAC, plumbing) with recurring jobs — the lead qualification and pipeline view for project-based GC work is thin.

On Starch RECOMMENDED

One platform — crm, email agent 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 connect to Buildertrend or CoConstruct directly?

Buildertrend and CoConstruct don't have open APIs that Starch currently syncs on a schedule, but both are web-based platforms you can log into. Starch automates them through your browser — no API needed — to pull lead data, project details, or contact records into your CRM without re-entering everything by hand.

My leads come in through text message, not email. Can Starch still help?

Starch handles the email side automatically. For leads that come in via text or phone call, you add a card to your CRM manually — it takes about 30 seconds to type the name, number, project type, and rough budget. From there, everything else (follow-up reminders, pipeline tracking, bid status) runs the same way as email-sourced leads.

Will this work with my QuickBooks data to check if a returning client has open invoices?

Yes. Starch connects directly to QuickBooks via scheduled sync, so when a returning client shows up as a new lead, you can ask the CRM 'does this contact have any outstanding invoices?' and get a real answer from your books before you commit to a site visit.

I don't have time to configure a CRM from scratch. How long does this actually take to set up?

You describe your pipeline in plain English — project types, budget thresholds, the stages you use, the fields that matter — and Starch builds the schema. Most operators have a working CRM in under 20 minutes. You don't drag and drop anything or read documentation.

Is my email data stored in Starch? I'm not sure I want all my client communications sitting somewhere else.

Starch is not SOC 2 Type II certified today, so if you're running jobs that require strict data handling standards, that's worth knowing upfront. For most small GC and trade shops, the risk profile is comparable to connecting Gmail to any other business tool — your emails stay in Gmail; Starch reads and syncs them to surface the information you need.

Can Starch tell me which bid I lost and why, over time?

If you log a reason when you mark a lead as lost — 'bid too high,' 'client went with brother-in-law,' 'scope changed,' 'never responded' — Starch can summarize patterns across those notes after 60 or 90 days. Ask it: 'What were the most common reasons we lost bids this quarter?' and it reads your notes and gives you a plain-language answer. The more consistently you log it, the more useful the answer.