Fixed quote after a free call

A home service CRM that follows every lead to a paid job

Leads for a service business arrive from calls, website forms, Google, directories, Facebook and word of mouth, and most get tracked on a whiteboard or not at all. We connect every source to one pipeline in your field service software or a CRM such as HubSpot, send a fast first reply, create call-back tasks, move each lead through request, quote, booked, done and paid, and send a weekly report on which sources bring paying customers. A typical build costs $1,000 to $2,500 per workflow and takes about four weeks.

The problem

Why service businesses lose leads between the van and the office

The owner of a small service business is usually on a ladder, under a sink or driving between jobs when a new lead arrives. A form submission waits until evening, a directory lead goes to an inbox nobody checks and a voicemail gets returned the next day, after the customer has booked someone else.

Even when leads are captured, the trail breaks between systems. The lead lives in email, the quote in Jobber or a spreadsheet, the invoice in QuickBooks, so nobody can say which advert or listing actually produces paying work.

What we build

What our home service CRM automation includes

Every lead source captured

Website forms, missed calls, directory and Google leads, Facebook lead forms and referral emails flow into one pipeline.

Fast first reply

An approved text or email within minutes acknowledging the request and asking for photos or the address if needed.

Pipeline stages that match the work

New request, site visit booked, quote sent, job booked, completed and paid, linked to your field service software.

Call-back and visit tasks

Tasks with due dates for the office or owner, so no lead waits until the weekend.

Duplicate and repeat customer matching

Returning customers recognised by phone, email or address and linked to their history.

Source-to-revenue report

A weekly email showing leads, quotes, booked jobs and paid revenue by source.

Who does what

Automation does the chasing, people make the calls.

Every step is marked: what runs on its own, what a member of staff reviews and what stays with a person who decides.
  1. 01 Automated

    Lead arrives

    A call, form, directory lead or referral creates or updates the customer record.

  2. 02 Automated

    First reply sent

    The customer gets an approved acknowledgement and any questions about photos or access.

  3. 03 Automated

    Stages update

    Quotes, bookings and payments in your field service software move the lead along.

  4. 04 Office review

    Office follows up

    The office manager calls back, books site visits and records outcomes.

  5. 05 Owner or office manager decides

    Pricing and scheduling

    Prices, crew allocation and which jobs to take are decided by the owner.

How it behaves

How the field service CRM pipeline behaves

What each person sees and what runs in the background, including what happens when something goes wrong.

What the customer sees

  • A quick reply after they call or fill in a form
  • A clear next step, such as a site visit or a quote
  • A call back when they asked for one

What the office sees

  • One pipeline with every lead and its stage
  • Call-back and site visit tasks with due dates
  • A weekly report by source

What the automation does

  • Captures and matches leads from every source
  • Moves stages as quotes, jobs and invoices change
  • Logs every step and alerts on failures

Edge cases and fallbacks

Same customer calls and fills in a form
Matched by phone or email and merged into one request.
Lead is outside your service area
Flagged to the office with a polite decline template ready to send.
Spam or sales call submits a form
Filtered by rules and kept out of the pipeline, with a log to check.
Field service software API outage
Leads queue and retry, and the office gets an alert with the details.

Architecture

A lead-to-job pipeline for a service business at a glance.

The setup we usually start from. We adapt it to the phone system and practice software you already use.
Calls Answered and missed Web forms Site and Google Directory leads Email and apps n8n Capture and match Field service CRM Jobber, HCP, CRM First replies Text and email Office manager Call-backs, visits Weekly report Source to revenue
  • Input
  • Logic and services
  • Data
  • Output
  • People

How it flows

  1. 1 Calls, website and Google forms and directory leads arrive from every source.
  2. 2 n8n captures each one, matches returning customers and creates the request in your field service CRM.
  3. 3 The customer gets a quick reply and the office gets a call-back or site visit task.
  4. 4 A weekly report shows leads, quotes, jobs and paid revenue by source.

Project planner

How the project runs, phase by phase.

Typical durations for a first version. Your proposal lists the exact phases, dates and what you sign off at each step.

Home service CRM & lead-to-job pipeline project plan

Typical time to launch: about 4 weeks, then support

  1. 01

    Discovery

    2 to 3 days

    Lead sources, field service software, current tracking and how quotes and jobs flow.

  2. 02

    Design

    2 to 3 days

    Stages, first-reply wording, matching rules, consent and the weekly report.

  3. 03

    Build

    1 to 2 weeks

    Source connections, pipeline sync, replies, tasks and reporting.

  4. 04

    Shadow run

    About 1 week

    Leads flow into the pipeline while the office keeps its old process, and we compare.

  5. 05

    Launch

    1 to 2 days

    Switch over and walk the office through the pipeline.

  6. 06

    Support

    Ongoing

    New lead sources, stage tweaks and monitoring.

What it runs on

Real products only, connected through the access each vendor provides. See all integrations

n8n Jobber, Housecall Pro or ServiceM8 (route confirmed per project) HubSpot CRM API Website forms and Facebook lead forms Twilio SMS Gmail or Microsoft 365

Cost estimate

What it costs, line by line.

Estimates to plan with. Your fixed quote follows a free call, once we have seen your systems and volumes.
  • Discovery and design

    Lead sources, stages, wording and reporting.

    $200 – $400

  • Build

    Capture, matching, pipeline sync, replies and tasks.

    $500 – $1,300

  • Integrations

    Field service software, CRM, forms and messaging.

    $150 – $400

  • Testing and shadow run

    Side-by-side run with your current process.

    $100 – $250

  • Launch and training

    Switch-over and office walkthrough.

    $50 – $150

  • Total project estimate

    $1,000 – $2,500

Optional monthly care after launch is quoted with your proposal. Fixed quote after a free call. Field service software, CRM, Twilio and n8n are billed to you directly. Many lead sources or a two-way accounting link may need a second workflow.

Monthly running costs you pay directly

Estimates from the vendors' published pricing, checked November 2026. Billed to you by each vendor, never marked up.

  • Field service software or CRM: Your vendor's own plan.
  • Twilio SMS (US): About $0.0083 per message segment each way plus carrier fees, and about $1.15 a month per local number (Twilio's published US pricing).
  • n8n: Free self-hosted Community edition, or n8n Cloud from about €20 a month (Starter, billed annually).

What pushes cost up

  • Systems without an API, or with integration access that must be requested from the vendor
  • Writing data back into your core system rather than only reading from it
  • Several locations, brands or very different processes to support
  • Custom apps, dashboards or a voice line on top of the workflows

What keeps cost down

  • One location and one clear process to start with
  • Cloud software with a documented API
  • Using tools you already pay for instead of adding new ones
  • Approved wording and sample data ready at the start
Get a fixed quote

Privacy and consent

Rules we design for, with the sources.

General information to plan with, not legal advice. Your counsel or data protection adviser confirms what applies to your practice.

US: marketing texts need consent

Texts that promote services sent with automated systems need prior express written consent; a reply to a customer's own enquiry is treated differently.

Source: www.law.cornell.edu

US: A2P 10DLC registration

Anyone sending application texts from a 10-digit long code to US numbers must register for A2P 10DLC.

Source: www.twilio.com

UK: marketing by text and email

PECR requires consent, or the soft opt-in for existing customers, for marketing by electronic mail, with an easy way to refuse.

Source: www.legislation.gov.uk

How we deliver

Agile delivery, in 1 to 2 week sprints.

We deliver in short Agile sprints using Scrum, so you see working software every one or two weeks instead of waiting for a big reveal at the end.

Every sprint

  1. 1 Sprint planning. At the start of each sprint we agree which backlog items we will finish, each with written acceptance criteria you can check.
  2. 2 Daily stand-up. A short internal check-in on progress and blockers. You get a written update in your Slack or Teams channel, not another meeting.
  3. 3 Sprint review and demo. At the end of each sprint we demo what was built on test data or in a shadow run, and you accept it or ask for changes.
  4. 4 Retrospective. The team looks at what went well and what to change in the next sprint, and we share anything that affects you.

How scope stays under control

Product backlog
Every feature, fix and question in one prioritised list you can see at any time.
Acceptance criteria
Plain-language conditions for "done" on each item, agreed before work starts.
Change requests
New ideas go into the backlog with an estimate. Nothing changes scope or price without your written approval.
User acceptance testing (UAT)
Before launch your team tests the real workflow against the acceptance criteria and signs off.

Tools we use

Jira, ClickUp or Trello for the backlogSlack or Microsoft Teams for updatesGitHub for code and version historyLoom or a live call for demos

Project manager / Scrum master

Runs the sprints, keeps the backlog and timeline honest, and is your single point of contact.

Business analyst

Maps how the work runs today, writes the workflow specification and acceptance criteria with your team.

Automation engineer

Builds the n8n workflows, integrations, AI steps and error handling.

Backend developer

Writes custom code where a no-code step is not enough: APIs, data sync, secure storage.

Frontend / mobile developer

Builds forms, booking pages, dashboards, web apps or Android apps when the project needs them.

QA engineer

Tests every workflow against the acceptance criteria, including edge cases and failure paths.

DevOps engineer

Sets up hosting, access, backups, monitoring and alerts, and the deployment pipeline.

Who does what at each phase

Free call
Project manager, business analyst
Understand the problem, check it is worth automating and outline a rough range.
Discovery
Business analyst, automation engineer
Map the current process, systems and data, and agree success measures.
Design
Business analyst, automation engineer, backend developer
Write the workflow specification, data flows, compliance notes and backlog with acceptance criteria.
Sprints
Automation engineer, developers, QA
Build, test and demo in 1 to 2 week sprints; you accept or adjust after each demo.
UAT and launch
QA, DevOps, project manager
Your team tests and signs off, we switch on, monitor closely and train the team.
Support
Automation engineer, DevOps
Stabilisation window, then optional monthly care with monitoring and changes.

A point of contact

One person who can answer questions and approve decisions, with about an hour a week during the project.

Access

Admin or API access to the systems involved, created as separate accounts with the least access needed.

Sample data

Real but non-sensitive records (or de-identified ones) so we can design and test against reality.

Approved wording

Message templates, policies and consent wording (for SMS, your opt-in and opt-out text) reviewed by you.

Vendor agreements

Signed agreements with the software vendors that will handle personal data, such as a BAA or processor contract.

Time for testing

A few hours from the people who will use the system, for the demos and user acceptance testing.

Working system

Workflows, integrations and any apps running in your accounts, under your keys.

Documentation

Workflow specification, data-flow map, run book and exported workflow files.

Training

A walkthrough for the team and a short recorded video for new starters.

Handover

All access, credentials and code handed over; you can keep us or take it in-house.

Stabilisation window

Fixes for anything that does not meet the agreed acceptance criteria after launch.

Support options after launch

  • No plan

    You run it yourselves after the stabilisation window and contact us when you need a change.

  • Monthly care

    Monitoring, error alerts, small changes and updates each month, with an agreed response time.

  • Priority care

    Faster response times for business-critical workflows and a monthly review call.

How a project moves through our team

Free call PM and analyst Discovery Process and data Design Spec and backlog Sprints Build, test, demo Your review Accept or adjust UAT and launch Sign-off, go live Support Monitor and improve
  • Input
  • Logic and services
  • People
  • Output
  • Data

How it flows

  1. 1 A free call with the project manager and business analyst to understand the problem and whether it is worth building.
  2. 2 Discovery and design produce a written specification, data-flow map and a backlog with acceptance criteria.
  3. 3 The team builds in 1 to 2 week sprints; you review a demo at the end of each and accept or adjust.
  4. 4 Your team runs user acceptance testing, we launch, then monitor and improve under a support plan.

FAQ

Home service CRM & lead-to-job pipeline questions, answered.

Most service businesses are best served by the CRM inside their field service software (Jobber, Housecall Pro, ServiceM8 or ServiceTitan), because quotes, jobs and invoices already live there. A general CRM such as HubSpot helps when you run longer sales cycles or several brands. We work with what you have.

Both include CRM features: client records, requests, quotes, jobs and invoices. What they often miss is capture from every lead source and reporting by source, which is what we add.

Leads that arrive by email or through an API or webhook can be captured. Each directory differs, so we confirm the route for the ones you use before quoting.

It sends an approved acknowledgement within minutes and asks for anything you need, such as photos or the address. Prices and booking times come from a person or your own online booking.

Yes. Many of our builds are for owner-operators. Tasks go to your phone, and the weekly report fits on one screen.

Leads by source, time to first reply, share of leads quoted, quotes accepted, jobs completed and paid revenue by source.

Free 20-minute call

Want this for your local service?

Book a free 20-minute call. We will look at how the work runs today, tell you honestly whether it is worth building and give you a fixed quote if it is.

Book a free 20-minute call