How to Create a Proposal From a HubSpot Deal

The short answer

A HubSpot deal record knows who the buyer is, which stage they're in, and what number you typed into Amount¹. It does not know what you agreed was in scope, what you deliberately left out, or what they will push back on — and that is most of a consulting proposal. HubSpot's own generator covers two pages of it: a quote template can be configured so that HubSpot's AI writes the cover letter and executive summary "using structured data, such as line items, and unstructured data from deal activities, such as meeting transcripts, notes, and emails"¹², on a Revenue Hub Professional or Enterprise account³. For everything past those two modules, generate from the transcript of the call behind the deal, then log the finished document back to the deal timeline. Artiweave does that in under two minutes, every claim traced to a moment in the transcript, anything unsaid flagged rather than invented.

Does HubSpot have a proposal generator?

Not one called that. There is no proposal object in the CRM and no endpoint that turns a deal into a document. What HubSpot ships instead is the quotes tool, which its knowledge base describes as part of "HubSpot's AI-powered CPQ": "Use quotes to share pricing with buyers, record quote acceptance, collect signatures, and receive payments"³. That article was last updated on August 14, 2026, and it is explicit about the gate — quotes are available with Revenue Hub Professional or Enterprise, and "a Revenue Hub seat is required to create and edit quotes"³.

The older surface underneath it is closing. HubSpot's own article on legacy quotes states plainly that it "references the legacy quotes tool, which is no longer available to new users," and that if your account was created after September 3, 2025 — or Sales Hub was added after that date — "legacy quotes aren't available and can't be enabled by a Super Admin, by changing seats, or by assigning partner seats"⁵. The corresponding API reference is now titled "Legacy quotes"⁴. If you are shopping for HubSpot proposal generation in 2026, the Revenue Hub quote is the native answer and the legacy one is a dead end.

What HubSpot's quote generator actually writes for you

More than most write-ups admit, so it is worth being precise. A quote template lets you "configure a layout and pre-filled modules including the cover letter, executive summary, line items, terms, payment options, and acceptance method"¹². Two of those modules are narrative, and HubSpot will generate them: "If the quote template has been configured to generate the cover letter or executive summary using HubSpot's AI, they will be added automatically using structured data, such as line items, and unstructured data from deal activities, such as meeting transcripts, notes, and emails"¹². Inside the editor there is also an AI icon on the modules and in the formatting toolbar to generate text on demand³.

Read that carefully, because it is the one place HubSpot does exactly what this page is about: it reads the call and writes prose from it. You can start that generation from four places — "from deal records, the quotes index page, Breeze Assistant, or workflow actions" — and the workflow route is a named action, "use the Create quote workflow action in a deal-based workflow"³.

Where the quote generator stops

Three hard edges, in order of how quickly you hit them.

The module set is the ceiling. A quote is a header, a parties block, a cover letter, an executive summary, a summary section carrying "the agreement date, term length, discounts, and total contract value," line items, terms, payment options and an acceptance method³ ¹². There is no scope module. No out-of-scope module. No phasing or milestone module, no assumptions module, no dependencies module. HubSpot's answer to that is that "if those modules don't meet your business needs, you can create custom modules to add additional content and customization options to your quote templates"¹² — which is a developer-platform build, not a generator. The document you can produce natively is a priced offer with a covering page in front of it. A consulting proposal is a covering page in front of an argument.

Nothing is traceable. The AI draft is assembled from deal activities in aggregate; nothing tells you which sentence came from which minute of which call, so the check has to be done by a human who was there. HubSpot says as much in the quote editor documentation: "do not include any sensitive information when you interact with our AI. Always remember to double-check AI responses for accuracy"³. On a $60k engagement, "double-check for accuracy" means re-reading the transcript — which is the work you were trying to automate.

The tier gate is real. Quotes need Revenue Hub Professional or Enterprise plus an assigned seat³; creating and managing the templates needs an assigned core seat and a Revenue Hub Professional or Enterprise account¹². If you are a four-person consultancy on a Starter seat, none of the above exists in your portal.

What can a HubSpot deal record actually supply?

HubSpot's knowledge base article on default deal properties, last updated July 31, 2026, is the authoritative list. The ones you would reach for on a proposal are Deal name ("the name you have given this deal"), Deal owner, Deal stage, Pipeline, Close date, Deal type, Deal probability, Amount ("the total value of the deal in the deal's currency"), Deal description ("a brief description of the deal") and Next step ("the next steps that you or another user will take to improve the deal's likelihood to close")¹. Around those sit associations: the Deals API exists so you can "manage this data and sync it between HubSpot and other systems," and it lets you associate a deal with other CRM records or with an activity².

The API makes the minimum viable deal explicit. When creating one, "you should include the following properties in the request: dealname, dealstage, and if you have multiple pipelines, pipeline"². Three fields, none of them prose.

And the shape of the property list matters more than its length. Nearly every default deal property is an enumeration, a date, a currency figure, or something HubSpot calculates for you — Weighted amount is the Amount multiplied by the Deal probability, Deal score is "the predictive deal score calculated by HubSpot AI to score the deal health"¹. Of the entire default set, the fields a human types sentences into are Deal name, Deal description and Next step; even Closed lost reason, which sounds like somewhere to explain yourself, is a set of options you customise¹. One short description field is the whole narrative surface of a deal record.

Deal properties vs. what a proposal needs

Put a consulting proposal next to that list, section by section, and the gap stops being an opinion.

What the proposal section needs	Closest deal field	Verdict
Who the client is, and who signs	Deal name, Deal owner, associated contact and company records¹ ²	Fully covered — merge it and move on
The price	Amount, or Total contract value calculated from associated line items¹	Covered, if the line items are on the deal
Billing schedule and term	Line item Billing frequency, Billing start date, Billing end date¹¹	Covered
Expected timing	Close date¹	Only the date you expect to close — not a delivery schedule
The problem, in the client's words	Deal description¹	One field documented as "a brief description of the deal"
What is in scope	—	No default property. A custom one, typed by hand after the call
What is explicitly out of scope	—	No default property, and the one clients read most closely
Phasing, milestones, deliverables	—	No default property
Assumptions and dependencies	—	No default property
Why this price and not a smaller one	—	Amount is a number with no reason attached¹

A merge template that fills {{amount}} and {{company}} handles the top four rows perfectly and leaves untouched every row that decides whether you win — the same argument we make in our sales-call-to-proposal guide. If you want to see which of those sections carry the weight in a finished document, we have annotated one in the HubSpot consulting proposal example.

Can custom deal properties hold the narrative?

Technically yes, and storage is not the constraint. HubSpot's multi-line text field type "stores multiple strings of alphanumeric characters, such as a paragraph or list of items," with a 65,536-character limit when the value is added through the CRM¹³. You could absolutely create Scope, Out of scope and Assumptions properties on the deal object.

Two things to know before you build that. First, a documented formatting trap: "line breaks included in multi-line text property values are not supported in certain tools, such as marketing emails, quotes, and sequences"¹³ — so the carefully structured scope paragraph you typed arrives in the quote as one unbroken block. Second, and larger: a property is storage, not authorship. Someone still has to sit down after the call and write the scope into it. That is the hour you were trying to remove, and it is the hour during which the deal cools — we have put numbers on that decay in our speed-to-lead statistics.

Where do the numbers on the proposal come from?

This is the part HubSpot models properly, and it is worth knowing exactly how before you build anything. Amount is a single figure someone types¹. Structure lives one level down, in line items: "In HubSpot, line items are individual instances of products. When a product is attached to a deal, it becomes a line item"¹¹. A line item carries name, description ("Full description of the product"), hs_sku, quantity, price ("The cost of the product") and amount ("The total cost of the line item (i.e., the quantity times the unit price)")¹¹.

Those roll up. Total contract value is "the total value of the deal, based on the line items associated to the deal, including any recurring revenue and one-time charges," and HubSpot notes it "does not take into account the value in the Amount property"¹ — so a deal whose typed Amount disagrees with its line items will cheerfully display both figures. On the quote side, "line items are inherited from the associated deal, but line items on quotes have their own record IDs," and where the associated deal uses a default deal setting other than manual entry, publishing a quote copies only the TCV amount back to the deal³.

So: pricing structure, tax rates, billing frequency and term are all genuinely available to a generator. What is not available is the justification. The longest free-text field anywhere in that chain is a product description¹¹, and no product description explains why this client needs three phases rather than two. That reasoning is also what separates a proposal from the document that follows it — see proposal vs. SOW.

How do you actually generate a proposal from a HubSpot deal?

Four routes, in descending order of how native they are. (If what you are answering is an inbound questionnaire rather than a call, that is a different job — see HubSpot RFPs.)

1. Native: a Revenue Hub quote with an AI cover letter

Create the quote from the deal record, pick a template, and let the configured AI populate the cover letter and executive summary from line items and deal activity including meeting transcripts³ ¹². Then send it with e-signature or click-to-accept and payments attached³. Fits: a priced offer to a buyer who already understands the work — renewals, expansions, productised engagements. Doesn't fit: anything where the scope boundary is the negotiation, because there is no module for it. Costs: Revenue Hub Professional or Enterprise, plus seats³ ¹². Delivery mechanics for all of this are in how to send proposals from HubSpot.

2. Manual: open the deal, re-read the call, write in Docs

Still the default outside Revenue Hub. Open the deal, scroll the timeline, listen back to the recording. If your seat supports it — HubSpot requires "an assigned Sales Hub or Service Hub Professional or Enterprise seat" to transcribe and analyze recordings, and only recordings made by users with those seats "will be automatically transcribed" — lift the text directly: on the Transcript tab, click Copy transcript to clipboard⁶. Then paste it into a chatbot, fact-check the output, and rebuild your branding by hand. It works, and it costs one to three hours per proposal while the deal cools.

3. Deal-property merge: a workflow plus a document-generation app

The DIY route: a workflow fires on a deal change and hands the deal's properties to a document-generation app that merges them into a template. Check the tier first — workflows require Professional or Enterprise across Marketing Hub, Sales Hub, Service Hub, Data Hub, Smart CRM or Revenue Hub⁷.

Good at: consistency and triggering. Nothing gets forgotten, and the header block, client name and total are always right. Can't do: write. The merge knows Amount¹; it does not know the buyer said "if the pilot lands, we roll it out to both regions" at minute 31. Feed an AI step the deal summary instead and you get fluent, generic prose with no way to check a figure against what was agreed. Which app you bolt on is its own decision — proposal software that integrates with HubSpot compares what the listings actually document.

4. Transcript-first: Artiweave

Artiweave inverts the input. It reads the finished transcript of the call behind the deal — pasted, uploaded as a .vtt, or pulled from Fireflies or Notion Meeting Notes — extracts pains, goals, scope and every number said out loud, and drafts a complete priced proposal on your own template in under two minutes. Every substantive claim traces back to a moment in the transcript; anything the call didn't cover is flagged rather than quietly filled in. A narrated video walkthrough renders in the background, and the proposal activity writes out to HubSpot against the deal.

One honest caveat: Artiweave is in early access ahead of general availability in 2026, so this is a waitlist, not a download. If you need something in your portal this week, routes 1 to 3 above are the ones that exist today.

Can you auto-generate a proposal when a deal hits a stage?

Partly — and the honest split is between creating an object and writing a document. Every deal stage carries a probability, which HubSpot multiplies by the stage total for the weighted amount in board view, and the default Sales Pipeline runs Appointment scheduled (20%), Qualified to buy (40%), Presentation scheduled (60%), Decision maker bought-in (80%), Contract sent (90%), Closed won (100%) and Closed lost (0%)⁸. Pipeline settings expose an Automate tab for wiring things to those transitions⁸.

What stage-entry automation does natively is narrow: it can "create a task or send an internal notification when a deal's stage changes," and it can rotate the record to an owner — on Sales Hub and Service Hub Starter, Professional and Enterprise, with the full workflow editor recommended for anything more⁹, and workflows themselves gated to Professional or Enterprise⁷. It notifies and assigns.

The one thing HubSpot will genuinely create for you on a trigger is a quote, through the Create quote workflow action in a deal-based workflow³ — the same Revenue Hub object, with the same module ceiling. So the realistic pattern is: fire on entry to a stage where the discovery call is already behind you — Presentation scheduled or Decision maker bought-in in the default pipeline⁸ — and point the resulting task or integration at the transcript, not at a blank template. Triggering earlier just means drafting before you know what goes in it.

What the HubSpot API can and cannot do for you

Can: read the deal, price it, and close the loop. Past the deal sync itself², you can create line items and associate them with a deal in one call¹¹, and the Notes API accepts an associations object targeting a deal, with a note carrying hs_note_body and hs_attachment_ids, where "multiple attachment IDs are separated by a semi-colon"¹⁰ — the supported way a finished proposal PDF ends up on the deal timeline rather than only in someone's sent folder.

Cannot: compose. There is no proposal object and no endpoint that turns properties into an argument. The closest priced-document primitive is the legacy quotes API, which still requires that "for a quote to be publishable, it must have an associated deal and quote template," with hs_status moving through values including DRAFT, APPROVAL_NOT_NEEDED and APPROVED⁴ — and that surface is the one HubSpot has already closed to new accounts⁵. What happens after the document exists is a separate job, covered in how to send proposals from HubSpot.

Native quote vs. manual vs. merge vs. transcript-first

	Native Revenue Hub quote	Manual (deal notes + chatbot + Docs)	Deal-property merge (workflow + doc app)	Transcript-first (Artiweave)
Source material	Line items plus deal activities, including meeting transcripts¹²	Memory, timeline notes, a transcript copied by hand⁶	Structured deal properties only¹	The full call transcript, plus your rate card and template
What it writes	Cover letter and executive summary¹²; no scope or assumptions module	Whatever you write	Nothing — it fills fields	The full document, section by section
Pricing accuracy	Line-item accurate; quote line items inherit from the deal³	You re-check every figure against the call	Right only if Amount was; scope detail absent	Numbers taken from what was said and traced to it; gaps flagged
Branding	Branding set on the quote template, or the default branding used for all quotes¹²	Rebuilt by hand each time	As good as the merge template you maintain	Your template, logo, fonts and boilerplate, applied automatically
What lands on the deal	The quote itself, associated to the deal it was created from³	Whatever you remember to log	Usually nothing, unless you wire extra steps	Proposal activity written via associated notes¹⁰
Tier needed	Revenue Hub Professional or Enterprise, plus seats³ ¹²	Pro/Enterprise seat only for HubSpot's transcript⁶	Professional or Enterprise for workflows⁷	None to draft — the transcript can come from anywhere

What people actually ask about HubSpot proposal generation

Is there a HubSpot proposal generator app?

Nothing HubSpot builds is named that. Natively you get quotes, gated to Revenue Hub Professional or Enterprise with a seat required to create and edit them³, and the legacy quotes tool they replaced is "no longer available to new users"⁵. Everything else marketed as a HubSpot proposal generator is a third-party app connected through the marketplace, a workflow webhook or the API — proposal software that integrates with HubSpot compares what those listings actually document, rather than what their landing pages claim.

Is a HubSpot quote the same as a proposal?

No, though a 2026 Revenue Hub quote is closer than it used to be. A quote is built from the modules HubSpot ships — header, parties, cover letter, executive summary, summary, line items, terms, payment options and acceptance method³ ¹² — which means it can carry a covering argument but has nowhere structured to put scope, out-of-scope, phasing or assumptions. A consulting proposal is mostly those four things. You can extend a template with custom modules on the developer platform¹², which is a project rather than a setting.

Can HubSpot's AI write the proposal from my sales call?

It can write two sections of a quote from it. HubSpot documents that a quote template configured for AI generation will populate the cover letter and executive summary "using structured data, such as line items, and unstructured data from deal activities, such as meeting transcripts, notes, and emails"¹². What it does not give you is claim-level traceability — you cannot ask which sentence came from which minute — and HubSpot's own guidance is to "double-check AI responses for accuracy"³. Artiweave's difference is exactly there: every substantive claim points back at the transcript, and anything the call did not cover is flagged rather than invented.

Can I auto-generate one when a deal hits a stage?

You can automate the trigger, and you can auto-create a quote. Pipeline automation will create a task, send an internal notification, or rotate the record to an owner when a deal enters a stage, on Sales or Service Hub Starter and above⁹; workflows themselves require Professional or Enterprise⁷; and a deal-based workflow can run the Create quote action³. Producing a full narrative proposal is then an app's job or an API integration's job.

Which HubSpot tier do I need?

It depends which piece. Quotes and quote templates need Revenue Hub Professional or Enterprise, with a Revenue Hub seat to create and edit quotes and a core seat to manage templates³ ¹². HubSpot's own call transcription needs an assigned Sales Hub or Service Hub Professional or Enterprise seat⁶. Workflows need Professional or Enterprise⁷, while basic stage automation starts at Starter⁹. Artiweave reads a finished transcript from wherever you already have one, so HubSpot's transcription tier is one option among several rather than a prerequisite.

Where does the generated proposal live?

On the deal, if you put it there. A quote is associated to its deal by design — the legacy API will not publish one without an associated deal and quote template⁴ — and for anything produced outside HubSpot, the Notes API takes an associations object targeting a deal and supports attachments via hs_attachment_ids¹⁰, which is how proposal activity and a PDF surface on the timeline. Artiweave writes that activity out against the deal so pipeline reviews reflect what actually happened after the call — see HubSpot proposal automation for the write-back detail.

Sources

Your deal record has the buyer. The call has the proposal.

Artiweave turns a finished sales call into a polished, on-brand proposal — with a narrated video walkthrough — in minutes. Free while in early access.

Early access rolls out in waves · No card required