# What to put in a quote template: the fields that must match your CRM deal https://salesbond.app/blog/quote-template-deal-fields-sales-team-crm/ Published: 2026-10-20 · Updated: 2026-10-26 A good quote template has six blocks (parties, line items, price and tax, validity, terms, acceptance), and each block should map to one field on the CRM deal, so that the amount a customer accepts is the amount the forecast shows. The downloadable templates at the top of the search results cover the customer’s side of the document well. What they skip is the manager’s side: which of those fields have a twin on the deal, who is supposed to fill each one, and how you find out on Monday that the two no longer agree. ## A template is a form. A quote is a promise The distinction matters more than it sounds. A quote is a document a specific customer can accept, and once they do, the number on it is the number you have to deliver at. A template is the blank form your team starts from, so every quote looks the same and can be held up against the deal record without reading it line by line. The template is a management tool. The quote is a sales tool. Most of what ranks for “quote template” is a file. HubSpot’s free price quote template comes as Word or PDF: an itemized costs table, the quote number and date, the expiration date, a customer account number, and an optional terms-and-conditions attachment ( [HubSpot: Price Quote Template](https://www.hubspot.com/resources/templates/price-quote)). Refrens has Word and Excel versions and a list of what a quote must carry, from seller and buyer details and the product, quantity and rate down to terms, accepted payment methods and a signature ( [Refrens: Free Quotation Templates](https://www.refrens.com/en/quote-templates)). Either one is a fine starting point. If someone on your team asks whether Word has a quotation template: yes, plenty. The catch shows up in Refrens’s own comparison of formats, where the downside listed for Word is that it doesn’t add anything up for you. Totals get typed by hand, and a wrong one looks exactly like a right one. That is the whole problem in one sentence. A rep types a total into a document, and separately types a value into the deal. Two people, or one person twice, and nothing checks they agree. One line on terminology, because the search results mix the three: a quote, an estimate and an invoice are different documents that belong to different deal stages, and we cover that in [quote vs invoice vs estimate for a sales team](https://salesbond.app/blog/quote-vs-invoice-vs-estimate-sales-team-crm-stages/). This article is only about what goes inside the quote template. ## What goes in a quote template: six blocks You can build a template with far more fields, and some industries need that. For a sales team the fields fall into six blocks, and every block answers one question a buyer or a manager will ask. 1. **Parties.** Who is selling and who is buying: legal names, addresses, the contact who will sign. Not the buyer’s trading name from the rep’s memory; the legal entity that will pay. 2. **Line items.** What exactly is being sold. Product or service name, description, quantity, unit price. If you sell from a catalogue, use the catalogue names here. 3. **Price and tax.** Subtotal, discount, tax, total, and the currency. One total, stated once, in one currency. 4. **Validity.** The quote number, the issue date and the date the price stops being valid. How long a quote should stay open and what to do when it lapses is its own topic: [quote expiry and validity dates](https://salesbond.app/blog/quote-expiry-validity-date-pipedrive/). 5. **Terms.** Payment terms, delivery or start date, what is and isn’t included, the conditions the buyer accepts by signing. 6. **Acceptance.** Room for the buyer’s name, signature and date, and a way to reference the quote number back to you. That list works as the skeleton of a master template as it stands: paste the six headings into a Word or Google Docs file, fill in your company’s details once, and you have the start of one. The order is the order a buyer reads them. Acceptance goes last because that is where you want them to end up. ## Each block has a twin on the deal Every block on a quote template should map to one field on the CRM deal, with one named person keeping the two equal. Write the pairs down and two things usually jump out: the deal value is the only field most teams actually maintain, and several template fields have no twin at all until you add a custom field. ![Diagram mapping six quote blocks to CRM deal fields, labeled by who fills each: rep, template or customer](https://salesbond.app/wp-content/uploads/2026/10/quote-template-deal-fields-sales-team-crm-2.png) The easiest way to sort the pairs is by who fills them, because there are only three answers and the mix is the point. **The template fills it.** Your own legal entity and address, and the default payment terms. Nobody retypes these. On the deal they are covered by the owner and your company details, and payment terms get their own field (custom, if your CRM has none) that changes only with a reason. **The rep fills it, twice.** This is the big group, and it stays typed twice until your CRM links the quote to the deal: - the buyer’s legal name and address, which go onto the deal’s organization or company, copied from the organization record and not from memory; - the person who will sign, who must already exist as a contact on the deal before the quote goes out; - line items with quantities and unit prices, mirrored as products on the deal, the same products in the same quantities; - the total and its currency, which become the deal value and deal currency, equal to the total on the quote the buyer holds; - the quote number, a quote valid-until date and the discount with its reason, each in a custom field; a discount over your limit also needs an approver; - the quote date, logged as a “Quote sent” activity on the day it leaves. **The customer fills it.** Signature and date. That maps to a stage change rather than a text field: the customer’s signature is what moves the deal to Won, and the rep attaches the signed copy to the deal when it does. If your CRM has a native quotes object, part of the rep’s group collapses. In HubSpot, the deal amount and line items always match the deal’s current primary quote ( [HubSpot: understand how quotes work](https://knowledge.hubspot.com/quotes/understand-how-quotes-work-in-hubspot)). In Salesforce, an opportunity can have several quotes but syncs with only one at a time, and syncing keeps updates flowing between the two records ( [Trailhead: Generate Quotes and Sync Them Easily](https://trailhead.salesforce.com/content/learn/projects/manage-products-prices-quotes-orders/create-multiple-quotes)). That changes the check rather than removing it: now the question is which quote is feeding the record. We go through that for [HubSpot quotes and the deal amount](https://salesbond.app/blog/hubspot-quotes-deal-stage-amount-check/) and for [Salesforce quotes and opportunity sync](https://salesbond.app/blog/salesforce-quotes-opportunity-sync-amount-check/) separately. For Pipedrive teams that sell from a product catalogue, the line items have their own trap, covered in [price match between quote lines and products](https://salesbond.app/blog/price-match-quote-lines-pipedrive/). No quotes object in your CRM? Then the list above is your quotes object. Add the custom fields and make the check manual. ## Fields reps forget Reps don’t forget the total. They forget the fields around it, and those are the ones that turn a won deal into an argument with finance. Currency comes first. A template built for one market gets reused for a customer who pays in another, the rep changes the symbol on the document and leaves the deal in the default currency. The forecast is now adding numbers in two units. We think currency belongs on the template as a visible field, not as a symbol in the total cell, precisely so that it gets noticed and copied. Payment terms are the second. The template says one thing, the rep agreed something else on a call and the deal has no field for it at all. Give it a field. Even a short dropdown beats information that lives only in the rep’s head. Discount reason is the one we would fight for. A discount percentage on its own tells a manager nothing; a reason tells them whether the discount was a decision or a reflex. “Competitor quoted lower” and “end of quarter” are different problems, and you can’t see which one you have if the field does not exist. Pair the reason with the math, because [the discount that looks small and is not](https://salesbond.app/blog/markup-vs-margin-discount-approval-sales-manager/) shows up only when you read it as margin. Approver. If a discount above a threshold needs sign-off, the quote should carry who approved it, and so should the deal. Otherwise the Monday question is “who said yes to this?” and the answer is a Slack thread nobody can find. Version. A revised quote is a new document. If the deal still points at the old one, every field above can be correct and still describe a price the customer no longer holds. Keep a version on the template and a matching field on the deal; the mechanics are in [revised quote versions](https://salesbond.app/blog/revised-quote-versions-pipedrive/), and we won’t repeat them here. ## Quote template hygiene: one master, locked fields The failure we see most is five reps with five personal copies of a template, each slightly edited, each with a different terms block. The customer sees inconsistency and the manager can’t compare anything. So creating a quote template for a team is mostly about what you take away from people. Start with one master file in a shared location, and give it an owner. Personal copies are disposable: a rep opens the master, fills it in, saves the result against the deal and never saves it back over the master. Then lock what shouldn’t change. In Word or Excel that means protecting the sections that belong to the company, which are your legal entity, the terms block and the formula cells, and leaving the rep the line items, the parties and the dates. If a rep needs to change a locked field, that is a conversation, not an edit. Agree a file name pattern and don’t negotiate it per rep. Something like `deal-id_customer_quote_v2_2026-10-20` lets anyone find the right document from the deal record without opening three files. The deal id goes first because its the only part that is unambiguous. And the signed quote lives attached to the deal, not in the rep’s downloads folder and not only in an email thread. If the quote is not on the deal, then for the weekly check it doesn’t exist, and the deal value counts as unverified. None of this is complicated. It’s unpopular, because it takes an edit right away from people who like editing, which is exactly why a manager has to say it out loud. ## Weekly check: does the signed quote match the deal? This is where the template pays for itself. Once a week, before the pipeline review, pull the deals won in the past week and hold each one up against the quote the buyer actually accepted. The first time takes a while. After that it’s quick, because the fields exist. ![Checklist card with five Monday review checks leading to a question for the rep](https://salesbond.app/wp-content/uploads/2026/10/quote-template-deal-fields-sales-team-crm-3.png) 1. Filter deals by status Won and a won date in the last week. 2. Open the attached quote on each one. No attachment? Write the deal down, that is already a finding. 3. Put the quote total next to the deal value, and the quote currency next to the deal currency. If they differ, note the gap and which number the customer signed. 4. Glance at the discount: it needs a reason and, above your threshold, an approver. 5. Take the list to the review as questions for the rep, not as corrections you make yourself. “The customer signed at one number and the deal shows another, which one is right?” is a question a rep can answer on the spot, and the answer tells you whether the template or the habit is the problem. Line-by-line comparison of products, and what happens to the order after the deal is won, belongs to a different check; we walk through it in [ERP vs CRM: where the deal ends and the order starts](https://salesbond.app/blog/erp-vs-crm-quote-to-order-handoff-small-sales-team/). A disclosure, since this is the kind of list people ask us about: we build SalesBond, a sales management layer on top of the CRM a team already uses. It reads deal data from the CRM and finds the deals that need a manager’s attention and explains why. [Check your CRM with SalesBond](https://salesbond.app/) if you want to see that on your own pipeline. The check itself needs no software though. It needs the fields above and a manager who runs it every week. Where the signed quote goes next, through order, delivery and invoice, is covered in [the quote-to-cash process for a small sales team](https://salesbond.app/blog/quote-to-cash-process-crm-handoff-small-sales-team/). Your next step is smaller: open your current template, and for each of the six blocks write down the deal field it should land in. The blanks on that list are the custom fields to add before next week’s check.