Workflow Teardown

Teardown: From Quote Request
to Paid Invoice

This is an illustration of a workflow many small service businesses run by hand, not a client project. Follow one job from the first request to the payment, see where the minutes and the mistakes pile up, and compare it with an automated version that keeps people in charge of the decisions.

Published September 14, 2026 · 7 minute read

The business in this example

A home services company with an office manager, two estimators and several crews. Requests arrive by phone, email and a website form. The company uses a scheduling app, accounting software and a document template for quotes. Nothing is connected, so people move the information between them.

The times below are illustrative estimates for one job, chosen to be modest.

Step 1: The request arrives (about 5 minutes)

The office manager copies the caller’s details, or the form email, into the scheduling app.

  • Form requests sit in an inbox until someone checks it
  • A returning customer gets created a second time under a slightly different name

Step 2: The site visit is scheduled (about 10 minutes)

Several texts go back and forth between the customer, the office and the estimator to find a time.

  • The agreed time lives in a text thread, not the calendar
  • The estimator arrives without the notes from the original request

Step 3: The quote is written (about 15 minutes)

The estimator fills in a document template from site notes, prices it from memory or a price sheet, saves it as a PDF and emails it.

  • An outdated price sheet produces a quote below cost
  • Line items and totals are typed separately and do not always agree

Step 4: Chasing the quote (about 5 minutes)

Someone is supposed to follow up on quotes that get no answer. When the week gets busy, nobody does.

  • Quotes that would have been accepted with a reminder quietly expire
  • There is no list of which quotes are still open

Step 5: The job is booked (about 5 minutes)

When the customer says yes by email, the office manager retypes the job, the address and the quoted items into the scheduling app.

  • A changed scope agreed on the phone never reaches the crew

Step 6: The invoice is created (about 5 minutes)

After the job, the office manager creates the customer again in the accounting software and copies the line items from the quote.

  • Extra work done on site is left off the invoice
  • Invoices go out days after the job, so payment arrives later too

Step 7: Getting paid (about 5 minutes)

Payments are matched to invoices by hand, and overdue ones are chased when someone remembers.

  • Overdue invoices are noticed only at month end

What that adds up to

About 50 minutes of office and estimator time per job, before any of the failures above. At 30 jobs a week, that is about 25 hours a week spent moving information between tools, plus the cost of expired quotes, missed extras and slow payments.

Put your own numbers into our guide to sizing a manual process to see what the equivalent figure is for your business.

The automated version

The same tools, connected, with people making the decisions:

  • Every request creates or matches the customer automatically and appears in one queue, with duplicates flagged
  • The customer picks a visit time from the estimator’s real availability, and the request notes travel with the appointment
  • The quote is built from a current price list, with totals calculated, and the estimator reviews it before it is sent
  • Unanswered quotes get a reminder on a schedule, and the office sees a list of open quotes
  • An accepted quote creates the job with its line items, and scope changes are added to the job, not to a text thread
  • Completing the job drafts the invoice from the job’s final items for the office to approve and send
  • Payments are matched automatically where possible, and overdue invoices trigger reminders and a weekly list

What stays with people

Pricing judgment, approving each quote and invoice, handling unhappy customers and deciding what to do about unusual jobs. The automation removes the copying and the forgetting, not the decisions.

Not every business needs all seven steps automated. Often the right start is the one or two steps that lose the most money, such as quote follow-up or invoicing after the job.

Where It Starts

Typical Starting Points

Work is priced by scope, not by the hour. You get a written scope with a fixed price before anything starts, and larger builds are split into milestones. The ranges below show where engagements typically start.

See Starting Prices
EngagementWhen it fitsInvestment
Automation Opportunity ReviewYou know the workflow hurts, but not yet what, if anything, to build: one workflow reviewed, with the smallest worthwhile fix in a written action plan.$495 fixed fee
Quick Win AutomationOne tightly bounded problem with a clear finish line.From $1,500
Core Automation or Integration BuildWorkflows and system connections the business runs on, priced in a written scope.From $5,000
Operations Automation PartnershipAfter a build: monitoring, maintenance, vendor and API changes, and small improvements.From $750 / month

See all pricing

Questions

Common Questions

Is this based on a real client?
No. It is an illustration of a common pattern, with modest time estimates. Your workflow will differ, which is why the first step is mapping your own.
Do we have to replace our software to do this?
Usually not. Most of the steps can be connected between tools you already use, if they offer an API, import or export. Replacing a tool is only worth discussing when one has no way to exchange data.
Where would you start?
With the step that loses the most money or time for you. For many service businesses that is quote follow-up or invoicing, because both affect revenue directly.
What does a person still approve?
Anything that reaches a customer or involves money: quotes, invoices and unusual changes. The automation prepares the work and a person approves it.
Next Step

Does This Look Like Your Week?

Walk us through your version of this workflow. We will tell you which steps are worth automating first and what the automated version would look like.