Build an AI Agent That Turns a Sales Call Into a Finished Quote

Quick answer

To automate quotes with AI, give an agent like Claude a folder holding your pricing rules, your services list, and a few past quotes, then drop in the sales call transcript and ask it to draft the quote. In a public demo, this turned an hour-long task into roughly a two-minute one, and it works for any business that sends quotes, proposals, or estimates, anywhere in the world.

Every quote you send says the same thing twice. Once in the sales call. Once in the price you type up afterward, from memory.

Quoting Is the Job Nobody Automates First

Marisol runs a four-person marketing agency in Austin. Every week she takes two or three discovery calls with new clients. Every week she does the same thing after each one.

She opens last month's proposal. She copies the format. She scrolls back through her notes to remember what the prospect actually asked for. She checks the rate card in her head. She writes it up in her own words, in her own template, hoping she did not forget the add-on the client mentioned at minute forty of the call.

An hour later, she has a quote. Sometimes two.

Nobody starts a business because they love writing quotes. And yet quoting is often the first real thing a prospect sees from you: the moment they decide whether you are organized enough to trust with real money.

Here is how quoting usually works, on repeat, at agencies, contractors, consultancies, and service shops everywhere:

  • A sales call happens. Nobody writes it down cleanly.
  • Whoever owns the relationship remembers the details, or they do not.
  • The quote gets built from memory, an old file, and pricing rules that live in someone's head.
  • Every quote reads slightly differently, because every quote was handwritten under time pressure.

You are not slow. Your quoting process has no memory. It resets to zero after every call, and you rebuild it from scratch, every single time.

What an AI Agent Actually Needs to Write a Quote

A chatbot answers a question. An agent finishes a job.

Ask ChatGPT or Claude, cold, to write you a quote for an IT support contract, and you get a generic template. It has no idea what you charge, what you offer, or how you phrase things. That is the chatbot experience, and it is why most owners try AI for this once and give up.

An agent is the same model, with your business sitting next to it in a folder.

That is the whole trick, and it is simpler than it sounds. IT consultant Curtis Branum demonstrated it on his channel in June: he opened a plain folder on his computer, named after the client project, and inside it were four things.

  1. A short instructions file (in his case, a CLAUDE.md) stating the agent's one job: turn a discovery call into a clean, accurate, client-ready quote.
  2. A company file with his pricing rules, in his own words.
  3. A services file listing his packages and what is included in each.
  4. A folder of past quotes, so the agent matches his tone and formatting instead of inventing its own.
Flow diagram showing a sales call transcript feeding into a context folder of pricing, services and past quotes, which an AI agent reads and reasons over to produce a finished client quote
The flow: transcript in, context folder consulted, agent reasons, finished quote out.

Drop the call transcript into a "calls" folder, type one sentence asking for a proposal, and the agent reads all of it: the transcript, the pricing rules, the old examples, and writes a finished quote that already matches how the business prices and talks.

Why This Works Now, and Not Two Years Ago

~2 minutesHow long it took Claude Code to turn one recorded discovery call into a full, priced client quote, in a public demo by IT consultant Curtis Branum. One demo, not a universal benchmark, but the mechanism behind it is real and repeatable.

Two years ago, giving an AI model your pricing meant pasting it into a chat window every single time and hoping it remembered by the next message. It did not. Every conversation started over.

What changed is memory that persists in files instead of a chat window. Anthropic's Claude Code reads a project folder the way a new hire reads an onboarding binder, every time it opens, without you retyping anything. Feed it your business once. It reuses that context for every quote after.

This is not limited to construction or IT services. Agencies, consultants, contractors, studios, anyone who turns a conversation into a priced proposal, can run the same setup. One founder posted on X that he was using a similar agent, built on GPT-5.6, to handle quoting, scheduling, insurance, and compliance for an entire company he was launching. Take that as one person's early account, not a proven system, but it points at where this is heading.

Isn't This Just a Fancy Proposal Template?

No, and the difference is the part that matters.

A template is static. You fill in blanks, and it has no idea whether what you typed makes sense against your margins or your past deals.

An agent reads the actual conversation. It notices the prospect has 25 users, not 15. It notices the compliance requirement mentioned once, at the seven-minute mark, that changes which package applies. It prices against your real rate card and explains why it chose that tier, the way a sharp account manager would, not the way a mail-merge would.

The output still needs your eyes on it before it goes out. This is a draft that is 90 percent done in two minutes, not a system that replaces your judgment on price.

How Do I Automate Quotes for My Small Business With AI?

There are two honest paths here, depending on how comfortable you are with a folder full of text files.

Path one: the agent-folder method, no CRM required.

  1. Create one folder per client project, or one shared folder if you quote similar work repeatedly.
  2. Write a short instructions file that states the agent's one job: turn a call transcript into a client-ready quote in your voice.
  3. Add a company file: your pricing logic, margins, and any rules about discounts or minimums.
  4. Add a services file: your packages, what's included, and what costs extra.
  5. Drop two or three of your best past quotes into an examples folder, so tone and formatting carry over automatically.
  6. After each sales call, save the transcript, or a recording's auto-transcript, into a calls folder.
  7. Ask the agent, in one sentence, to build the quote from the last call.
  8. Read it, adjust the number if it needs adjusting, and send it.

Path two: the no-code stack. If you would rather not touch a folder of text files, the same idea runs through connected tools instead of a coding assistant: a form or a shared inbox captures the request, a workflow tool like Make.com or Relay.app routes it to an AI model, the model matches it against your price list, and a template in Canva or your CRM turns it into a branded document. Quote-specific platforms such as DealHub and Jinba package this whole flow for teams already running on HubSpot or Salesforce. Either path lands you in the same place: a business that remembers its own pricing so a person does not have to, every single time.

Three Ways to Quote, Compared

ApproachSetup effortWhat it costs youBest for
Manual, from memoryNoneAn hour or more per quote, every timeBusinesses sending fewer than one quote a month
No-code stack (Make.com, Relay.app, Lindy, DealHub)A few hours to wire up forms and templatesMonthly subscriptions, some setup complexityTeams already running a CRM like HubSpot or Salesforce
Agent folder (Claude Code or similar)An afternoon to write your context files onceUsage-based AI costs, no new subscriptionOwner-operators and small teams quoting straight from calls

What This Looks Like at Marisol's Agency

Marisol takes a call from a local bakery chain wanting social media management and a website refresh. She used to block ninety minutes the next morning to build the proposal.

Instead, the call recording's transcript lands in her calls folder the moment the meeting ends. Marisol types one line: build the quote from today's call with the bakery.

The agent reads the transcript. It sees three locations, a request for weekly content plus one paid campaign a month, and a mention that the client's last agency was slow to reply. It checks her services file, prices the retainer tier that matches three locations, adds the one-time website line item from her rate card, and writes a cover note promising a same-day response window, because that objection came up on the call.

Two minutes later, Marisol has a draft that already sounds like her. She tightens one sentence, checks the total against her margin floor, and sends it before lunch.

What You Have After This

A week in, you have one working example: a real quote that came out of the agent instead of out of your memory.

A month in, you have a folder that knows your business better than a new hire would on day one, and every quote reads like the same person wrote it, because in a sense, one system did.

Six months in, quoting stops being the thing you dread after every good call. It becomes the fastest step in your sales process instead of the slowest one.

Same pricing. Same services. A completely different quoting machine.

How do I automate quotes for my small business with AI?

Put your pricing rules, your services list, and two or three past quotes into one folder, then feed an AI agent a sales call transcript and ask it to draft the quote against that context. Tools like Claude Code do this with plain text files; no-code platforms like Make.com, Relay.app, or Lindy do the same thing through connected forms and workflows if you would rather not touch a folder directly.

Do I need to know how to code to set this up?

No. The agent-folder method is just text files in a folder, named clearly, with no programming involved. If that still feels like too much, the no-code path (Make.com, Relay.app, Lindy, or a CPQ tool like DealHub) gets you a similar result through forms and templates instead.

Is it safe to let AI decide my prices?

The agent applies pricing rules you wrote yourself; it does not invent numbers. Treat every output as a draft, not an autopilot: read it, check the total against your margin floor, then send it. That review step is what keeps this safe.

What if I don't use Claude Code?

The same idea works with a ChatGPT project, a similarly configured agent, or a no-code stack built on Make.com, Relay.app, or Lindy. The tool matters less than giving the AI your pricing, your services, and real examples to work from.

How is this different from a normal quote template?

A template fills in blanks you type yourself; it has no idea if the numbers make sense. An agent reads the actual sales call, catches details you might forget, prices against your real rate card, and explains its reasoning, closer to what a sharp account manager does than what a mail-merge does.

Find your first high-payback workflow.

See the Sprint

Sources

HN

Editorial responsibility
Notma Intelligence publishes practical guidance using named sources and visible dates. AI tools may assist research or drafting; a named human remains responsible for factual review before publication.
Read the editorial policy → · Meet founder Hammton Ndeke →

Find your first high-payback workflow.

Book a free conversation or start with the fixed-fee Sprint.

See the Sprint

Keep reading