Speed-to-Lead for Builders: What Should Happen in the First 30 Minutes
When a new enquiry lands, the first 30 minutes should follow a set sequence. In the first two minutes, the alert reaches a named person (not just an inbox). By minute five, that person has called, and if nobody answers, sent a short text. Between minutes five and fifteen, the qualifying call covers scope, location, budget and timeframe. By minute thirty, the next step is booked and the enquiry is logged with every detail captured. If the owner is on site, a named backup runs the same steps. The point is simple: the process catches the lead, not someone's memory.
Two quick illustrative examples (not clients) of what that looks like in practice:
- A renovation builder on a roof at 10:15am gets a form enquiry. The office manager receives the alert, calls at 10:17, gets voicemail, texts at 10:18, and books a call-back for 12:30 when the owner is off the tools.
- A custom home builder at a Saturday open home gets a web enquiry. Nobody is at a desk, so the after-hours text goes out automatically and the Monday morning roster picks it up first thing.
We covered why response time matters in 19 Hours and 1.6 Attempts, where one builder we work with was averaging 19.1 hours to first response, with 1.6 attempts before a lead was dropped. This article is the "how". It is a playbook you can print, stick on the office wall and hand to whoever answers your phone.
The 30-minute sequence at a glance
| Window | What happens | Who owns it | Done when |
|---|---|---|---|
| Minute 0 to 2 | Alert reaches a human | System, then named responder | Someone has seen it and claimed it |
| Minute 2 to 5 | First touch: call, then text if no answer | Named responder | Call made and text sent (if needed) |
| Minute 5 to 15 | Qualifying conversation | Named responder or owner | Core details captured |
| Minute 15 to 30 | Next step booked, enquiry logged | Named responder | Appointment in the calendar, record complete |
These are working targets to aim for during business hours, not promises. Some days you will miss them. The goal is that missing them becomes the exception instead of the norm.
Minute 0 to 2: does the alert actually reach a human?
This is the step most builders assume is working and rarely check. An enquiry that sits in an inbox nobody opens until Friday has a response time of three days, no matter how keen you are.
What good looks like:
- Every enquiry source sends an alert to at least two places: the named responder's phone and a shared record (a CRM, a shared inbox, or even a shared spreadsheet if you are small)
- Alerts arrive as something people notice, like a text or push notification, not only an email
- Someone claims it. A simple reply like "got it" in a team chat, or assigning it in your CRM, stops two people calling the same person or, worse, nobody calling because each assumed the other had
If you are not sure your alerts are reliable, that is its own problem, and a common one. Forms going to spam, alerts going to an ex-staff member's phone, messages sitting unread on Facebook. We will cover those in a separate article on why builder enquiries go missing.
Minute 2 to 5: call first, then text
Call first. A phone call does more in 30 seconds than three emails, and it tells the homeowner a real person is on the other end.
If they do not answer, leave a short voicemail, then send a text straight away. Many people will not pick up an unknown number but will read a text within minutes.
Voicemail script
"Hi [name], it's [your name] from [business]. You just sent through an enquiry about [project type] in [suburb]. Keen to have a quick chat. I'll send you a text now as well, so you've got my number. Talk soon."
Keep it under 20 seconds. Say the project and suburb so they know it is not a cold call.
Follow-up text script
"Hi [name], [your name] from [business] here. Just tried to call about your [project type] enquiry. Is now a good time for a quick chat, or would later today suit better?"
Two things make this work: it references their enquiry, and it gives them an easy yes. Avoid links, long paragraphs or anything that looks automated.
Email (only as the third touch)
Email is useful for sending information, but it is a weak first touch. If you have their email and have not reached them by phone or text, send a short note with the same message and your direct number.
Minute 5 to 15: the qualifying conversation
When you get them on the phone, the goal is not to sell. It is to understand what they want, check it is a fit, and agree a next step. Ten minutes is usually enough.
What to capture on every enquiry
| Field | Why it matters |
|---|---|
| Name, phone, email | Obvious, but often incomplete |
| Site address or suburb | Confirms it is inside your service area |
| Project type and rough scope | New build, extension, renovation, what rooms, size |
| Budget range | Checks the job is viable before anyone spends time on it |
| Timeframe | Starting next month and starting in two years need different handling |
| Plans or drawings | Tells you where they are in the process |
| Council or consent status | Affects timing and what you can quote |
| How they found you | So you know which channels produce real work |
| Decision makers | Who else needs to be at the site visit or meeting |
A simple call flow
- Thank them and confirm the basics. "Thanks for getting in touch. You're looking at a [project] in [suburb], is that right?"
- Ask about the project. "Tell me a bit about what you have in mind." Then listen. Most of the fields above come out naturally.
- Ask about budget early and without awkwardness. "Have you got a rough budget range in mind? It helps me point you in the right direction." If they do not know, give a typical market range for similar work in your area and ask if that sits comfortably.
- Ask about timing. "When are you hoping to get started?"
- Agree the next step. Site visit, design meeting, or a call with the owner.
If it is clearly not a fit (wrong area, wrong type of work, budget well below what the job needs), say so kindly and, if you can, point them somewhere useful. A helpful no protects your reputation and your time.
Minute 15 to 30: book the next step and log everything
The call is not finished until two things have happened.
The next step is in the calendar. Not "I'll get back to you". An actual time for a site visit or meeting, with a calendar invite or confirmation text sent while it is fresh:
"Great to chat, [name]. Confirming [day] at [time] at [address] for a look at the site. Any questions before then, text me on this number."
The record is complete. Every field above, logged in the same place, with a note on what was agreed. If you use a CRM, move the enquiry to the right stage. If you use a spreadsheet, fill in the row. If something was missing, note it for the site visit.
This matters more than it sounds. Without the record, the next person who touches the enquiry (you, in two weeks) starts from scratch, and good enquiries quietly fade.
What if they don't answer at all?
Many enquiries will not pick up on the first try. That is normal. What is not normal is giving up after one or two attempts, which is exactly what that 1.6 attempts figure looked like in practice.
A sensible follow-up pattern for enquiries you have not reached:
| When | Touch |
|---|---|
| First 5 minutes | Call, voicemail, text |
| Same day, afternoon | Second call |
| Next day, morning | Call and text |
| Day 3 | Email with your number and a helpful resource |
| Day 5 to 7 | Final call and a text that leaves the door open |
The last text might be: "Hi [name], just checking in once more about your [project]. No pressure at all. If the timing's not right, feel free to reach out whenever you're ready." That tone keeps you on their list without being pushy.
Who covers when the owner is on site?
This is the real sticking point for most builders. The owner is the best person to talk to a new client, and also the person least likely to be near a phone at 10am on a Tuesday.
The answer is a cover roster. It does not need to be complicated.
A simple cover roster
| Time | First responder | Backup |
|---|---|---|
| Weekday business hours | Office manager or admin | Owner (call-back window at lunch and end of day) |
| Weekday evenings | Owner or on-call team member | Automated text, then first thing next morning |
| Saturday | Rotating team member | Automated text, Monday 8am call |
| Sunday and public holidays | Automated text | Monday 8am call |
| Leave and holidays | Named stand-in, written down | Owner |
A few rules that make a roster actually work:
- Write it down and share it. A roster only in someone's head is not a roster.
- Give the first responder a script and a calendar. They should be able to book a site visit without asking the owner.
- Set call-back windows for the owner. For example, 12:30 and 4:30. The first responder can promise those times with confidence.
- Check the handover. Once a week, look at every new enquiry and confirm each one got a first touch and a logged next step.
If you are a very small team and the owner is the only option, the same logic applies: set two fixed call-back windows a day, have an automatic text go out immediately, and treat those windows like a site meeting you cannot miss.
Do automated replies count?
An automated text or email is a good safety net, especially after hours. It tells the homeowner their enquiry arrived and when to expect a call. It is not a replacement for a person. A homeowner planning a large build wants to speak to someone who knows what they are talking about.
Keep automated replies short, honest and specific: "Thanks for your enquiry. We're on site today, and [name] will call you before 5pm." Only promise what your roster can deliver.
"An auto-reply buys you a few hours of goodwill. Spend them wisely."
If the alert never reaches the right person, response time is beside the point. Use the builder enquiry leak checklist to test forms, inboxes, phones and social alerts first.
Frequently asked questions
What is a good lead response time for builders?
As a working target, aim to make the first call within minutes during business hours, and certainly the same day. In the builder we looked at in our 19 Hours article, the average first response was 19.1 hours. Under 24 hours is the baseline, same-day is better, and minutes is better again.
How many times should you try to contact a new lead?
More than most builders do. A pattern of five or six touches over about a week (calls, texts and one email) is reasonable and not pushy, as long as each message is polite and relevant.
Should I text or call a new enquiry first?
Call first. If there is no answer, leave a short voicemail and follow up with a text straight away. The text often gets the reply the call did not.
What if I'm on site when an enquiry comes in?
Have a named backup who receives the same alert and can make the first call and book the next step. If there is no backup, send an automatic text and call back at a fixed time you have committed to.
Do I need a CRM to follow up leads properly?
Not to start with. What you need is one place where every enquiry is logged with the same fields and a clear next step. A CRM makes that easier as volume grows, but a shared spreadsheet used consistently beats a CRM nobody updates.
What should I ask on the first call?
Location, project type and scope, budget range, timeframe, whether they have plans, consent status, how they found you, and who else is involved in the decision. Then book the next step before you hang up.
Make the process catch the lead
Fast follow-up is not about working harder or answering the phone on a ladder. It is about a simple, written process: the alert goes to a named person, the first touch happens quickly, the details get captured, and the next step is booked before the call ends. Our Builder OS overview shows how this fits with capture, qualifying and handover.
If you want to see how your own response process stacks up, take the two-minute Builder Growth Assessment. It shows which system to fix first, including follow-up. For general enquiries, get in touch. You can also find more on how we work from the Contractor Scale homepage.