Automation case study

Lead Management

A lead-to-kickoff workflow that acknowledges new enquiries, coordinates follow-up and moves a builder-approved won job into the agreed setup steps.

Self-initiated portfolio buildConstruction coordinationHuman review stays in control

At a glance

Acknowledges

New enquiries receive an immediate reply while the lead is added to the tracking register.

Follows up

A daily Brisbane-time sweep evaluates due leads and sends stamped nudges without doubling up.

Sets up

A lead marked won by the builder can trigger Procore project creation and welcome-pack delivery.

Surfaces failures

Errors are formatted, emailed to the builder and recorded for review or retry.

Client type: Residential builder quoting renovation and new-build work.

The problem

A homeowner enquiry can wait while the builder is on the tools, moving between sites or handling active project decisions. At the other end, winning a job can create a second admin queue: create the project, send the welcome pack and update the register.

The coordination risk is losing visibility at both ends of the pipeline — a lead going quiet at the front, or a confirmed job waiting for setup at the back.

How the system works

The documented build separates instant intake, scheduled follow-up, human-approved won-job setup and centralised error handling. It automates coordination steps without deciding whether a lead should be accepted, quoted or marked won.

Lead Management workflow showing lead intake, daily follow-up, won-job kickoff, Procore setup and error handling.

Explanatory workflow visual based on the documented portfolio build — not a live n8n canvas screenshot.

Inside the build

The build uses a shared lead register, stamped follow-up fields and a won-job gate so each stage can be checked without silently repeating work.

Lead Management build logic showing lead fields, follow-up stamps, won-job gating, Procore setup and error handling.

Explanatory build-detail visual derived from the documented workflow logic.

Actual build evidence

This is an authentic n8n canvas screenshot from the Lead Management build. It shows the four workflow paths, Google Sheets register, Gmail messages, Procore setup, follow-up cadence and error handling; the SVGs remain the clearer client-readable explanations.

Authentic n8n canvas screenshot of the Lead Management build, showing lead intake, follow-up sweeper, won-job kickoff, Procore creation and error handler workflows.

Actual n8n build screenshot supplied for this portfolio case study. Click the image for an in-page larger view.

Controls & exceptions

Follow-up is stamped

Each nudge is recorded so the workflow can distinguish due leads from leads already contacted.

One lead at a time

The documented sweeper processes leads sequentially rather than sending a burst of duplicate messages.

Won-job setup is gated

Procore setup runs only when the lead is marked won and the project has not already been created.

Failures are visible

Workflow and Procore failures are emailed to the builder and preserved in the error record.

What stays human-controlled

Automation supports acknowledgement, follow-up, register updates and agreed setup steps. The builder retains qualification, pricing, scope, availability, negotiation, the decision to mark a lead won and all client commitments.

Tools used

n8nWebhooksGoogle SheetsGmailProcore API
Portfolio disclosure: This is an independently developed portfolio build, not a paid-client case study. It shows how Anna designs reusable workflow systems around recurring construction coordination problems. Builder approvals, commercial decisions, contractual decisions and site actions remain with the builder and responsible project team.