Skip to content

What we build

Explore Vendrato

For enterprise teams

Book a free call

Based in the Philippines. Working worldwide.

All insights

A CRM Pipeline for Australian Builders: From Enquiry to Accepted Job

Define enquiry, site visit, quote and handover stages with clear owners and exit rules, using an illustrative small-builder workflow.

A builder’s CRM pipeline should show what needs to happen before a job is accepted, who owns that action and when it is due. Use stages with observable entry and exit rules. Keep the sales pipeline separate from the schedule for work already underway.

The goal is to answer a practical question: which enquiries need attention today? A board full of coloured cards is not helpful if “quoted” means several different things to different people.

Separate customer history from job delivery

A customer relationship management system holds contacts and their interactions. A job-management system organises the work itself. These may be features of one product, but they remain different responsibilities. The Australian Government’s digital-tools guide describes both categories.

In a small building business, one customer might request two separate projects. Keep the customer record connected to two opportunities rather than combining all discussions into one status. After acceptance, hand the agreed scope to the delivery process; do not make the sales board carry every construction task.

If your team is still deciding whether a CRM is necessary, start with our spreadsheet-versus-CRM decision guide.

Start with a small set of stages

The following is an illustrative pipeline for a small renovation builder, not a claim about a particular company’s practice.

Stage Evidence required before moving on
New enquiry A person has been assigned and the first response is due
Scope check Job type, actual service area and the next information needed are recorded
Site visit arranged The customer and responsible staff member have agreed the visit
Quote preparation Required measurements and assumptions are available, with a quote owner and due date
Quote sent The exact version and send date are recorded, with a next action
Accepted for handover The business’s acceptance requirements are checked and delivery has received the record
Closed or deferred A reason and, where appropriate, a genuine revisit date are recorded

Do not advance a card because someone intended to send a quote. Advance it when the quote was actually sent. Similarly, a customer’s request for a start date is not automatically acceptance.

The table is an operational model. Contract formation, deposits and domestic-building obligations require rules appropriate to your state, work and circumstances; a CRM status cannot establish compliance.

Give every open opportunity a next action

For each active enquiry, keep these fields visible:

  • Responsible person and a backup during absence.
  • Last meaningful customer contact.
  • The next action, stated as something someone can do.
  • A due date and the information blocking progress.
  • Current quote version, if one exists.

“Waiting” is not a complete next action. “Estimator to confirm access details with the customer on Thursday” makes the responsibility explicit. If the customer has asked for a pause, record that request and an appropriate revisit date rather than running repeated reminders.

In the illustrative renovation business, a site visit cannot be arranged until access is confirmed. The enquiry remains in scope check with a named owner. This is more useful than moving it into a stage that suggests a visit is already booked.

Keep quote versions traceable

Link the actual quote document to the opportunity. Record revisions separately so staff can identify which scope and price were discussed. Business.gov.au’s quote-preparation guidance recommends clear written descriptions, costs, terms and relevant revisions.

Do not let an automated follow-up refer to an obsolete version. If the scope changes, pause the old follow-up and assign the revision. Our quote follow-up guide explains how to connect reminders to the current owner and next action.

Trial the pipeline with five difficult records

Before importing the whole enquiry history, use synthetic examples:

  1. Two enquiries from the same customer for different properties.
  2. A request outside the builder’s actual service area.
  3. A site visit that needs rescheduling.
  4. A quote revised after a scope change.
  5. An accepted job handed to someone other than the salesperson.

For each, ask a staff member who did not create the record to find the owner, current status and next action. If they need an explanation from the record’s creator, change the fields or stage rules.

Finally, check that the delivery team receives the accepted scope and unresolved questions without retyping them. The handover should preserve context, not merely move a card to a green column.

Review the queue before adding automation

A short weekly review can identify overdue actions, quotes with no follow-up decision and records with no owner. Start with those operational gaps. Automate only the steps whose rules are stable enough for another person to follow consistently.

Use the CRM setup checklist to plan permissions, migration and training. Vendrato’s CRM setup service can help turn your enquiry process into a system your team can maintain.

Your next chapter

Planning a digital project?

Show us your current website or workflow. We will discuss where to focus and what a project could involve.

Let’s talk about ithello@vendrato.com