Quote follow up automation that wins back quiet estimates
Most service quotes are not lost to a cheaper competitor; they are lost to silence. We build a workflow that collects the details and photos you need before quoting, drafts an estimate from your own price list for you to check and send, then follows up unanswered quotes with a short, polite sequence and hands warm replies back to you. A typical build costs $1,000 to $2,500 per workflow and takes about four weeks.
The problem
Why service quotes go quiet
Quoting eats evenings. Requests arrive with no measurements, no photos and a vague description, so the first step is always a back-and-forth to find out what the job is. By the time the quote goes out, the customer has had two others.
Then nothing happens. The customer meant to reply, a partner wanted to think about it, a question about timing went unasked. Without a consistent follow-up, a good share of quotes simply expire in the field service software.
What we build
What our estimate follow up automation includes
Smart request form
Questions that change with the service, with photo upload, so you get measurements and access details up front.
Draft estimates
Line items drafted from your price list and the answers given, created as a draft quote for you to adjust.
Quote delivery tracking
Sent, viewed and approved status read from your field service software where available.
Polite follow-up sequence
Two or three short messages over a couple of weeks, stopping the moment the customer replies, books or declines.
Reply hand-off
Questions about price, timing or scope go to the owner with the quote attached.
Win and loss reasons
A one-tap reason when a quote is declined, and a monthly report on acceptance by service.
Who does what
Automation does the chasing, people make the calls.
-
01
Automated
Request submitted
The customer answers service-specific questions and uploads photos.
-
02
Automated
Draft estimate created
Line items are drafted from your price list as a draft quote.
-
03
Office review
Owner checks and sends
The owner or estimator adjusts and sends the quote.
-
04
Automated
Follow-ups sent
Unanswered quotes get a short sequence that stops on any reply.
-
05
Owner or office manager decides
Pricing decisions
Final prices, discounts and whether to re-quote are decided by the owner.
How it behaves
How quote follow ups behave
What the customer sees
- A form that asks the right questions for their job
- A clear quote from the business
- Two or three friendly check-ins at most
What the owner sees
- Draft estimates ready to check
- Replies with questions flagged
- Monthly acceptance by service
What the automation does
- Drafts estimates from the price list
- Tracks quote status and sends follow-ups
- Stops on any reply and logs everything
Edge cases and fallbacks
- Photos do not show enough
- The owner gets a one-tap request for more photos or a site visit.
- Customer asks for a cheaper option
- Routed to the owner; the workflow never discounts.
- Quote approved online mid-sequence
- The next status check stops the sequence and moves the lead to booked.
- Field service software outage
- Follow-ups pause rather than run on stale status, and the office is alerted.
Architecture
Quote intake and follow-up at a glance.
- Input
- Logic and services
- Data
- People
- Output
- AI step
How it flows
- 1 The customer fills in a request form that asks the right questions for the service, with photos.
- 2 n8n applies your price list rules and creates a draft estimate in your field service software.
- 3 The owner adjusts and sends it; unanswered quotes get a short follow-up sequence.
- 4 Accepted and declined quotes feed a monthly report with reasons by service.
Project planner
How the project runs, phase by phase.
Quote request intake & estimate follow-up project plan
Typical time to launch: about 4 weeks, then support
-
01
Discovery
2 to 3 days
Services, price list, current quote process, acceptance patterns and wording.
-
02
Design
2 to 3 days
Form questions per service, estimate rules, follow-up timing and stop rules.
-
03
Build
1 to 2 weeks
Form, estimate drafting, quote status reads, follow-ups and reporting.
-
04
Shadow run
About 1 week
Draft estimates compared with your own quotes; follow-ups sent to a test inbox.
-
05
Launch
1 to 2 days
Switch on the form and follow-ups for live quotes.
-
06
Support
Ongoing
Price list changes, new services and wording updates.
What it runs on
Real products only, connected through the access each vendor provides. See all integrations
Cost estimate
What it costs, line by line.
-
Discovery and design
Services, price list rules and sequence design.
$200 – $400
-
Build
Form, estimate drafting, follow-ups and reporting.
$500 – $1,300
-
Integrations
Field service software, form tool and messaging.
$150 – $400
-
Testing and shadow run
Draft estimates compared with real quotes.
$100 – $250
-
Launch and training
Switch-on and owner 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. Draft estimates need a price list with clear rules; jobs that always need a site visit get intake and follow-up only.
Monthly running costs you pay directly
Estimates from the vendors' published pricing, checked November 2026. Billed to you by each vendor, never marked up.
- Form tool: Your form provider's own plan, if not built into the website.
- n8n: Free self-hosted Community edition, or n8n Cloud from about €20 a month (Starter, billed annually).
- Twilio SMS (US): About $0.0083 per message segment plus carrier fees (Twilio's published US pricing).
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
Privacy and consent
Rules we design for, with the sources.
EU: 14-day cancellation for services
Most services bought at a distance can be cancelled within 14 days of the contract being agreed; urgent repairs and maintenance are an exception.
Source: europa.euUS: follow-up texts and consent
Follow-ups relate to a quote the customer asked for; promotional texts beyond that need prior express written consent.
Source: www.law.cornell.eduUK: follow-up messages
Under PECR, marketing by text or email needs consent or the soft opt-in, with an easy way to refuse in every message.
Source: www.legislation.gov.ukFree tools
Try these first, free.
Guides to read first
How we deliver
Agile delivery, in 1 to 2 week sprints.
Every sprint
- 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 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 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 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
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
- Input
- Logic and services
- People
- Output
- Data
How it flows
- 1 A free call with the project manager and business analyst to understand the problem and whether it is worth building.
- 2 Discovery and design produce a written specification, data-flow map and a backlog with acceptance criteria.
- 3 The team builds in 1 to 2 week sprints; you review a demo at the end of each and accept or adjust.
- 4 Your team runs user acceptance testing, we launch, then monitor and improve under a support plan.
FAQ
Quote request intake & estimate follow-up questions, answered.
It is a set of automatic, polite reminders sent after you send a quote, so customers who meant to reply do. It stops as soon as they book, decline or reply, and hands real questions back to you.
Usually two or three over one to two weeks: a check that the quote arrived, an offer to answer questions and a final note before it expires. We set the timing with you.
It drafts line items from your price list and the customer's answers. You always check and send it; nothing goes to a customer without your approval.
Where the software exposes quotes through its API or an integration platform, yes. We confirm the route for your plan before quoting.
The form collects details and books the visit, and follow-ups start after you send the quote from the visit.
Time from request to quote sent, quote acceptance rate by service, replies to follow-ups and decline reasons.
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.
More for local services
All servicesHome service CRM & lead-to-job pipeline
Every call, form, directory lead and referral lands in one pipeline linked to your field service software, with fast first replies, call-back tasks and a weekly report on which sources turn into paid jobs.
From $1,000 · About 4 weeks Details
Missed-call text-back for service businesses
When you cannot pick up on a job, every missed caller gets a text within seconds asking what they need, with photos welcome, and emergencies such as leaks or no heat are flagged to you first.
From $1,000 · About 3 to 4 weeks Details
AI receptionist & answering service
An AI receptionist on your phone line, website and text that answers service, area and pricing-guide questions from your own answers, takes job details and booking requests and hands emergencies to the on-call tech.
From $2,500 · About 5 to 8 weeks Details