The Estimate Writes Itself

Every service business that sends a person to look at a job runs on this moment. Somebody stands in a yard, a kitchen, a crawlspace or a roof valley and has a real conversation with a homeowner. Then, hours later and miles away, somebody else has to turn that conversation into a document with line items and a total. Usually the somebody else is the same person, tired.

The quote that goes out is never the conversation. It is a copy of a copy. And the gap between the two is where jobs are lost: the measurement that drifted, the material the homeowner asked for that never made it onto the page, the deadline that got forgotten, and above all the two days it took to send, during which the homeowner called somebody else.

Memory is a leaky bucket, and every hand-off is a hole

In 1885 a German psychologist named Hermann Ebbinghaus spent months memorizing nonsense syllables and testing himself at intervals, and he drew the first forgetting curve. Its lesson fits in a sentence: most of what you will forget, you forget fast. The hours between the backyard and the kitchen table are exactly the hours where the curve is steepest.

Now stack the hand-offs on top of the decay. The homeowner says it. You hear it. You write a fragment of it. You carry the fragment home. You reconstruct it from memory. You type the reconstruction into a CRM. You price what you typed. Each step keeps most of what mattered, and none of them keeps all of it. Multiply a number a little below one by itself six times and you get a number a lot below one. I wrote about this shape yesterday as the arithmetic of seams: an intention that has to survive n hand-offs succeeds with p to the n. The estimate is that arithmetic with a truck parked outside.

Nothing about this is new as a wish. Estimators have carried voice recorders for decades. What is new is the second step. Until recently a recording was just a longer, more annoying version of the legal pad: somebody still had to listen to it and type. Now the recording can be read by something that never gets tired, never forgets which side the soft boards were on, and does its reading while you drive to the next job.

How the system works

There are three pieces and a short prompt. None of them requires writing code.

1. The recorder. A Plaud Note Pro rides magnetically on the back of the phone. It has four microphones and picks up a conversation from across a deck, labels who is speaking, and has a button that marks the moment you press it. That button matters more than it sounds: when the homeowner says the thing that will decide the job, you press it, and the agent later knows that line is the one to get right.
2. The bridge. Plaud publishes an official MCP connector. In Claude you open Customize, then Connectors, add Plaud Web MCP and authorize it with your Plaud login. From then on Claude can list your recordings, read a full transcript with timestamps and speaker labels, and read Plaud’s own summary and action items.
3. The schedule. A Claude scheduled task runs a saved prompt on a cadence you pick, with your connectors attached, and it runs in the cloud, so your laptop can be closed in the truck. I set the demo to weekdays at 6 p.m., which means the drafts are waiting when the estimator opens the CRM the next morning.
4. The destination. The CRM. The demo uses Jobber because so many home-service shops live in it. There is no first-party Jobber connector for Claude yet, so you connect it through one of the community or hosted MCP servers, each of which you authorize through Jobber’s own login. Housecall Pro, ServiceTitan and the others follow the same pattern with their own connectors.

The prompt is where the judgment lives. It tells Claude which recordings count as walkthroughs, how to avoid quoting the same one twice, what to pull from the conversation, how to price, and what it is never allowed to do. The full text is below; you can paste it into a scheduled task and replace the price book with your own rates.

PLAUD WALKTHROUGHS TO JOBBER DRAFT QUOTES
Scheduled task prompt for a local service estimator
Schedule: weekdays at 6:00 PM. Connectors: Plaud and Jobber.

Setup, once:
1. In Claude, open Customize, then Connectors. Add "Plaud Web MCP" and authorize with the Plaud login.
2. Add a Jobber MCP connector (there is no first-party Jobber connector yet; community servers and Composio's hosted connector both work -- pick one and authorize through Jobber's own login).
3. Create a scheduled task, paste everything below the line, set it to weekdays at 6:00 PM, and attach both connectors.
4. Fill in the PRICE BOOK section with your real rates before the first run.

------------------------------------------------------------

You are the estimating assistant for [COMPANY NAME], a [deck / fence / roofing / remodeling] contractor. Every run, turn today's homeowner walkthrough recordings into draft quotes in Jobber.

STEP 1 -- Find new walkthroughs
Use Plaud list_files with date_from set to today's date (and yesterday's, in case a recording synced late). A walkthrough is any recording whose name contains "walkthrough", "estimate", or "site visit". Ignore everything else.

STEP 2 -- Skip what is already quoted
For each walkthrough, search Jobber quotes for its Plaud recording ID in the quote notes. If you find one, skip that recording. Never create a second quote for the same recording.

STEP 3 -- Read the conversation
Use get_transcript for the full speaker-labeled text, and get_note for Plaud's summary. Pull out:
- Homeowner name, phone, email, and property address
- Every piece of scope the estimator committed to, with measurements and quantities
- Materials, colors, and brands the homeowner asked for
- What the homeowner wants kept as-is
- Timing, budget, access, pets, gate codes, HOA rules
Pay extra attention to any highlighted moment in the recording -- the estimator pressed Highlight because it mattered.

STEP 4 -- Price it
Use only the PRICE BOOK below. Quantity comes from the transcript, rate comes from the price book. Do the arithmetic yourself and double-check it.
If the transcript gives a range ("five or six joists"), use the higher number and flag it.
If something has no price-book entry, use the closest entry and flag it.
Never invent a price.

STEP 5 -- Build the draft in Jobber
- Find the client by phone or email. If none exists, create the client and property.
- Create the quote as a DRAFT with one line item per scope item: name, description, quantity, unit price.
- In the quote notes, write: what stays as-is, timing, any homeowner preferences, and the line "Source: Plaud recording [recording name], ID [recording ID], [date]."
- Do NOT send the quote, email the homeowner, or text anyone. Drafts only.

STEP 6 -- Report
Finish with a short plain-text summary for the estimator:
- Each draft created: client, job, subtotal, Jobber quote number
- Each flag that needs a human decision
- Each recording skipped and why

PRICE BOOK (replace with your real rates)
Demo and haul-off, existing decking ....... $4.00 per sq ft
Replace joist, 2x10 pressure treated ...... $85.00 each
Composite decking, installed .............. $28.00 per sq ft
Composite railing, installed .............. $65.00 per linear ft
Pressure-treated decking, installed ....... $16.00 per sq ft
Stairs, rebuild ........................... $110.00 per step
Permit handling ........................... $250.00 flat

Three rules in that prompt carry most of the weight.

• Drafts only, never sent
• Every quote tagged with its recording ID
• Price only from the price book
• Flag ranges and gaps

Drafts only, because the estimator is still the person who promised the homeowner a number, and a quote should never reach a customer without that person reading it. The recording ID, because a scheduled task that runs every evening will see yesterday’s recordings again, and the ID is how it knows a job is already quoted. The price book, because the most dangerous thing an AI can do on an estimate is invent a reasonable-sounding rate. When the transcript says five or six joists, the prompt says use six and flag it. When the homeowner asks for a color the price book does not carry, it says use the nearest rate and flag it. The flags are the estimator’s morning reading.

One more rule lives outside the prompt. Tell the homeowner you are recording. It costs one sentence at the start of the walkthrough, it is the right thing to do everywhere, and it turns the recording into part of the service instead of a secret.

The CRM stops being the place where an estimate is written. It becomes the place where an estimate arrives.

What changes when the conversation is the record

1. Speed to quote becomes the sale.

   Homeowners collect bids, and the first credible number sets the frame for every one after it. When one contractor’s quote arrives the same evening and the others arrive in two days, the evening quote is not just faster. It is the anchor.

2. Estimators start narrating.

   Once saying is writing, good estimators will say the measurements out loud, repeat the homeowner’s requests back to them, and name the materials as they look at them. It will sound like good customer service. It is also dictation.

3. The price book becomes the company.

   When the drafting is automatic, the thing that makes one contractor’s quotes better than another’s is the rates, the line items and the rules behind them. The price book stops being a spreadsheet nobody updates and becomes the most valuable document in the business.

4. The highlight button replaces the clipboard.

   The one physical gesture left in estimating is marking the moment that matters. That press tells the agent what to get exactly right, and it tells the office, later, what the customer actually cared about.

5. The kitchen table goes back to being for dinner.

   The evening hour of retyping disappears from the trade, the same way the evening hour of balancing a checkbook disappeared from households. People will not miss it, and in ten years they will not believe it was normal.

Why I build things this way

At Charleston AI we do not sell people tools and training. We deliver finished work. This system is that idea in its plainest form: the estimator does the part only a person can do, which is standing in the yard and earning the homeowner’s trust, and the paperwork arrives finished. I have been living a version of it myself. I asked for the video at the top of this page before dawn on a Sunday, said what I wanted, and the finished thing came back. The notification everyone wants is Done. For an estimator, Done is a draft quote with a total on it.

The obvious next question is where those drafts should land. Wiring Claude into a rented CRM works today, and it is the right first step. But there is a second path that I think more owners will take: build your own CRM, keep the rented one running as a mirror for a year, and then leave. That is Part 2.

The ledger

Already true

A recorder can capture a walkthrough with speakers labeled. Plaud’s connector gives Claude the recordings, transcripts and summaries. Claude scheduled tasks run on a cadence in the cloud with connectors attached. Jobber’s API can create quotes with line items. Every piece in the video exists today.

What has to happen

The contractor has to write down a real price book, attach a CRM connector they trust, and keep the drafts-only rule for long enough to learn where the agent is right and where it needs a flag. And the crew has to get comfortable saying the job out loud.

Where I am probably wrong

Plenty of estimates are not decided by talking. On a roof, in a crawlspace, behind a wall, the estimator’s eyes know things that never get said, and a transcript cannot price what nobody spoke. For those trades the recorder captures the homeowner’s wishes and the estimator still writes the scope. If that turns out to be most jobs, this saves an hour of typing, not a day of waiting, and the speed-to-quote prediction is the first one to fall.

Back at the kitchen table, the legal pad still says five or six joists, question mark. In the new version of that evening there is no legal pad. There is a draft that says six, with a flag that says the homeowner said “five or six,” and a recording of her saying it.

The estimate was written in the backyard. You were there when it happened.