Price landscaping jobs and draft customer quotes from site-visit voice notes
Have Claude price a landscaping job and draft the customer quote from your site-visit voice notes, using your own cost catalog and last year's quotes, then check every number before the quote goes out.
What the agent did
Source-reported example · as described by Quinten O'Dea (founder/owner, Q&A Landscaping, Pittsburgh, PA), interviewed by Todd Saunders (co-founder, Dalton Mills)
The owner of Q&A Landscaping (Pittsburgh, PA; higher-end landscape and hardscape install work, about 20 crew members), who handles all of the company's sales and quoting, described his workflow in a video interview.
Per the interview, he fed Claude his cost structure (labor at different levels such as owner and foreman with fully burdened costs, materials, equipment and overhead recovery, plus rules such as lawn repair always needing topsoil, seed and straw) and uploaded every quote he wrote the previous year so it would follow his writing voice, ordering and quote sequencing.
After walking a client's yard he records voice notes on his phone; an AI note-taker transcribes them; he uploads the notes into Claude. Claude asks a few follow-up questions, writes customer-facing quote copy in his style and prices the job broken down into labor, equipment and materials with overhead applied.
In the interview he shows two examples (4 yards of brown mulch with a couple of plant replacements; replacing a railroad-tie wall with a Versa-Lok wall with takeaway and lawn repair). He reviews every quote, questions assumptions Claude makes, corrects numbers, and enters the quote into his own quoting software for the customer.
Reported: the owner says the process is "a significant reduction in the time", though "it's not instant" and "on most quotes, there's a slight tweaking one way or another." Reported: Claude's output is "a note that looks just like my quote" from the previous year.
Reported: his goal was to stop doing quotes on Fridays and Saturdays after a week of appointments, to have more time with his new child. No time or money figures are given.
Limitations
Details are thin: this is a 16-minute interview, not a written walkthrough. No prompt, project instructions, cost catalog or full finished quote is published; the on-screen demo is brief. The voice note-taker app and the quoting/CRM software are not named.
No time saved, quote volume, accuracy or win-rate figures are given; the time reduction is the owner's own description. The owner says Claude sometimes makes up assumptions or skips calculations, so every price needs checking against real costs; the owner checks every quote.
The video title ("built his own AI voice quoting platform" that "frees up his entire weekend") overstates what the interview shows: the owner uses Claude with uploaded documents, not a separate platform he built.
The publisher sells software to trades businesses (see Commercial interest). Auto-generated captions were used for quotes; they render "Claude" as "Quad" in places and spell the owner's name as "Quentin".
Try it in your business
What you'll need
Claude; an organized cost catalog (labor rates with burden, materials, equipment, overhead recovery) and job rules; a set of past quotes to show writing style and quote structure; a phone voice note-taker that produces transcripts; the owner's review of every price and quote before it goes into the quoting software
The owner works in Claude with uploaded documents (his cost catalog and last year's quotes) and pastes in transcribed voice notes; the note-taker is a separate app and nothing is connected to Claude; no custom code is described.
Starting prompt
The author didn't publish their prompt (checked the full auto-generated transcript and the YouTube description of the video, and the Dalton Mills show page https://daltonmills.com/resources/videos/blue-collar-builders-episode-8, on 2026-10-19; the owner describes his inputs and corrections, e.g. "please don't just guess", but no prompt or project instructions are shown or linked), so this is our adaptation.
How ours differs from the original setup: Same Claude execution agent.
Written as a single reusable instruction rather than the owner's built-up project; adds an explicit rule to show calculations and list assumptions instead of guessing (the owner says he had to tell Claude this), and keeps the quote as a draft for the owner to review and enter into his own software.
Assumes the owner supplies the cost catalog and past quotes.
You help me price landscaping jobs and draft customer quotes. Use only the attached files: my cost catalog [labor rates by role with burden, materials, equipment, overhead recovery] and my past quotes [examples]. I'll paste a transcript of my site-visit voice notes. First, ask me about anything missing (quantities, access, disposal, number of days, equipment). Then give me: 1) customer-facing quote text in the same style, order and wording as my past quotes; 2) an internal cost breakdown by labor, equipment and materials with overhead applied, showing each quantity, unit cost and calculation. Never guess a cost, quantity or rate: if it isn't in my files or notes, mark it as an open question. List every assumption separately so I can check it. This is a draft for my review; don't send anything to the customer.
Replace the [bracketed] parts with your own files and tools.
Get examples like this every Tuesday and Friday
Practical ways to put AI agents to work in your business. We check the original sources, explain the setup and point out the limits. Free.
Unsubscribe any time. Privacy policy
Related use cases
Onboard a new client end to end: draft the contract, set up their Slack channel and podcast feed, and build website mockups for your review
Have Claude run a client-onboarding skill that drafts the client's contract, creates their shared Slack channel, adds them to your client database, and prepares samples, website mockups and a podcast feed for your review, while you send the invites, grant access and write the client messages yourself.
Our suggested starting prompt — not the author's original · untested
You'll need: Claude with skills (or saved instructions) describing your onboarding process; your internal docs, past contracts and the client's correspondence; access to your documents (for example Google Drive and Docs) and, if you let it do setup steps, to your team chat (the author used Slack via Claude's browser use) and client database; your own review of the contract, every account, channel or access change, and every client message. Building the skills was a one-off investment of about a day of the author's time, by his estimate.
Help me onboard a new client for my [type of service] business. Work in stages and stop for my approval at the end of each one. Stage 0 (first time only): Read my internal docs and past client notes in [folder]. Write a short overview of what my business does and how it works, then draft a step-by-step client onboarding checklist. I'll correct it. Once I approve it, save it as reusable instructions I can run for future clients. Stage 1, contract: Using the client emails and call notes I've attached and my past contracts in [folder], draft a service contract for [client] as a document. Look up their public details (legal name, registered address, registration number) and list where you found each one. Highlight anything that differs from my usual contract or that you're unsure about. Don't send it or upload it to a signing service. I'll review it and send it myself. Stage 2, setup: List every channel, record and account this client needs (for example a shared [Slack] channel that follows my naming pattern, or an entry in my client database), and wait for my OK before you create each one. Don't invite the client, grant access, change permissions, or enter any password or payment details. Give me the invite link or the exact page to open, and I'll do those steps. Stage 3, tailoring and samples: Review [the client's website or materials], list the special cases my service needs to handle for them, and propose a rule for each. After I approve the rules, prepare [sample deliverables] for me to check, and flag anything you're unsure about. Stage 4, mockups and delivery setup: Make mockups of [how my deliverable would look on their website], using their public branding, and draft [the feed, page or other delivery setup] privately. Don't publish anything until I approve it. Stage 5, client update: Don't write or send messages to the client. Give me a bullet list of points to cover in my update, then check my draft for clarity and for anything I've missed. Finish with a checklist of what's done, what's waiting for my approval, and what I need to do myself.
Draft sales-call recap emails from your notes
Have the follow-up email after a sales call drafted from your notes, ready for you to check and send.
Author's example instructions
You'll need: Claude Code on a paid Claude plan, a plain-English rules (skill) file, and call notes saved as files. How the notes reach the agent is not disclosed.
1. Read the call notes first. Use only names, numbers and dates that appear in them. 2. Write in my voice: short sentences, first person, no buzzwords, no exclamation marks. 3. Open with the one problem the prospect cared about most. 4. List the next steps, each with an owner and a date. 5. Never send the email. Save a draft and tell me where it is. 6. If the notes are missing or unclear, stop and ask me instead of guessing.
Categorize bank transactions, number vouchers, match payments to invoices and draft year-end accounts
Have Claude Cowork do the bookkeeping from a bank statement and spreadsheet, match payments to invoices and draft year-end accounts, as the author describes in a LinkedIn post that he says Claude wrote.
Our suggested starting prompt — not the author's original · untested
You'll need: Claude Cowork with access to your bookkeeping spreadsheet (and a backup copy), your bank statement export and your sales invoices; last year's accounts prepared by your accountant, for the format; a rules file kept alongside the spreadsheet; your own answers to its questions; your accountant's review.
You are helping me with bookkeeping in Cowork. Files: bank statement [file], bookkeeping spreadsheet [file], sales invoices [folder], last year's accounts from my accountant [file]. Step 1: make a backup copy of the spreadsheet before changing anything and tell me where it is. Step 2: read the spreadsheet and describe my categories, how voucher numbers run and which kinds of transaction never get a number; wait for me to confirm. Step 3: fill in only blank rows where the category and voucher number are clear from the history; for anything new or ambiguous, list a question for me instead of guessing, and never overwrite a filled row. Step 4: check your work against the backup: row counts, and gaps or duplicates in the numbering; report what you find. Step 5: match each client payment to a sales invoice and list any invoices still outstanding and any matches you are unsure about. Step 6: save the rules we agreed, and my answers, to [rules file] and show me what was added. Then, only after I have reviewed all this, draft this year's accounts in the same layout as last year's, section by section, from the categorised data, and flag anything that needs my accountant's judgement (for example depreciation, tax and opening balances) instead of filling it in. Do not send anything to my accountant or anyone else.

