A quote template is the connective tissue between what sales promised and what finance can actually book. Set up poorly, it leaks margin, confuses legal, and produces proposals that look nothing like each other. Set up well, it generates a signed-ready document in under four minutes with margins protected, approvals triggered automatically, and every line item traceable back to the catalog. This guide walks you through the full build: structuring the product catalog, writing pricing rules that survive edge cases, designing the approval chain, and locking in the review cadence that keeps the whole system honest.
Time: 120 minutes
Before you build anything in the CRM, pull the last twenty quotes your team sent and lay them side by side. You will find three things, and all three matter. First, structural drift: some reps break out setup fees, others bury them in year-one subtotals, and a few forget them entirely. Second, naming inconsistency: the same SKU appears as four different product names depending on who typed the proposal. Third, discount sprawl: discounts show up as percentages, dollar amounts, free months, and sometimes as unlabeled line-item reductions that nobody can reconcile against the price book. Catalog every variation. Those variations are your real requirements, not the clean spec a finance partner might hand you in isolation. A template built from the clean spec breaks the moment a rep tries to replicate a deal they closed last quarter. A template built from the audit absorbs the messy reality while still enforcing structure. Share the audit findings with sales leadership and finance before you touch the CRM. You want everyone agreeing on what the template needs to handle before you start making trade-offs about what it will not.
The product catalog is the backbone of every quote your team will ever send. Build it like infrastructure, not like a spreadsheet. Each product gets a stable SKU, a canonical name, a product family, a unit of measure, a list price, a floor price, and a default term length if applicable. The stable SKU is non-negotiable. If a rep can create a product on the fly during a quote, your catalog is a suggestion rather than a system, and finance will spend the next three quarters reconciling line items that do not match anything in the price book. Lock product creation to admins and route all new-product requests through a lightweight intake form. Yes, this will frustrate the first few reps who want to invent a line item mid-call. It will save you from the invoicing meltdown that follows uncontrolled catalog growth. Group products into families so you can apply pricing rules at the family level instead of maintaining per-SKU overrides for everything. Keep the family taxonomy flat. Two levels is usually enough: product family and product type. Three levels and reps spend five minutes clicking through hierarchies to find what they want. Four levels and they give up and type the price manually.
One price book cannot serve a motion that sells to both SMB and enterprise, or that runs promotional pricing alongside standard pricing. Build one price book per combination of motion, segment, and currency. Each price book is a thin overlay on top of the catalog that specifies list price, floor price, and any segment-specific adjustments for the SKUs in scope. Keep the number of price books down to what you can actually maintain. Three to six is healthy for most mid-market software businesses. If you have fifteen, you have a maintenance problem disguised as flexibility, and reps will routinely attach the wrong price book to a deal because the names stopped meaning anything. Make the default price book obvious at quote creation and tie it to opportunity type or segment so reps are not making the choice by hand. The handful of exceptions where a different price book applies should require an explicit override with a logged reason. If overrides happen often, the default rule is wrong, not the override process.
Pricing rules are the layer that keeps reps from quoting prices your business cannot support. There are three rules every quote template needs. First, floor-price enforcement: no line item below the per-SKU floor without an approval. Second, discount-tier logic: a discount of a certain percentage triggers a certain level of approval, and the system blocks submission until the approval is granted. Third, bundle protection: if a rep removes one SKU from a bundled offering, the price of the remaining SKUs reverts to standalone list, not the bundle discount. Each rule should be enforceable at the CRM level, not left to rep judgment or manager vigilance. Reps will discount to close deals. That is their job. Your job is to make sure the discount hits the right threshold and the right approver. Write the rules in plain language first and share with sales leadership for sign-off. Then translate them into CRM logic. A rule nobody can explain in a sentence will not survive its first edge case. Keep the rule set small. Four or five rules that always fire are worth more than fifteen rules that reps have learned to work around.
The approval chain is where the template proves it is a business system, not a document generator. Map discount percentages to approvers. A standard mid-market structure has rep-level authority up to a modest discount, manager approval through a middle band, director approval beyond that, and CFO or VP of sales for anything that threatens margin targets. Keep the number of tiers to three or four. Five tiers and the approval chain becomes a bottleneck that reps route around by asking for verbal approval and backfilling the record. Attach each tier to a named role in the CRM, not to specific individuals. People change jobs. Roles persist. For each tier, define a maximum response time, an escalation path if the approver is out, and an auto-approve fallback if the sales-ops team decides a window has elapsed and the deal needs to move. Approval chains that stall break deals. Approval chains that fire without record erode trust. The template needs both the discipline to enforce the chain and the pragmatism to keep deals moving when a human is on vacation.
With the catalog, price books, pricing rules, and approval chain in place, you can finally build the quote document. Keep the output clean. Cover page, executive summary, line-item table, totals block, terms section, signature block. Resist the urge to include a marketing pitch inside the quote. Buyers in the signature stage want to confirm numbers, not read copy they already read in the pre-sales deck. The line-item table is the heart of the document. Include SKU, product name, quantity, unit price, discount applied, extended price, and term. Hide SKU from the customer-facing render if your audit says buyers find it noisy, but keep it available for internal verification. The totals block should break out subtotal, discount applied, taxes if applicable, and the single number the customer will pay this period. Terms language comes from legal and should be a merge field driven by the deal type, not a text block reps edit per quote. If a rep is editing terms language, the template is wrong or the deal is non-standard, and non-standard deals route through legal, not through the template.
Every quote the template produces should carry structured metadata that lets you report on it later. Fields the template should populate automatically or require at creation: deal type, price book used, total contract value, annualized contract value, discount applied in percent and dollars, term length, start date, approvers who signed off, and quote status. Status should move through a short, well-defined lifecycle: draft, in approval, approved, sent, signed, lost. Make transitions auditable. A quote that jumps from draft to sent without passing through approved is a red flag your rule enforcement is leaking. Store the generated PDF against the opportunity, versioned, so you can trace what was sent and when. Reps will revise quotes. Buyers will counter. The template should treat each revision as a new version, not a silent overwrite. Version history is the artifact that resolves the inevitable "but I thought we agreed on" conversation three months into the contract.
Do not launch the template to the full sales team on day one. Pick two reps who regularly deal with messy edge cases. Give them the template, a two-page quick-reference, and permission to break it. Watch them use it on three real deals each. You will find bugs in the pricing rules, naming conflicts in the catalog, and approval tiers that fire at the wrong thresholds. Fix those before anyone else sees the template. Launching to the whole team with hidden bugs trains reps to work around the system from day one, and that habit never fully fades even after the bugs are gone. After the pilot pass, invite the pilot reps to walk the rest of the team through the template in a live session. Peer-led onboarding beats admin-led onboarding every time because the pilot reps have already answered the questions the rest of the team is about to ask. Publish the quick-reference, the recorded walkthrough, and a short changelog of what differs from the old process.
A quote system is a living artifact. Every quarter, pull the last ninety days of generated quotes and look at four numbers: average time from quote creation to send, average discount applied, percentage of quotes that triggered an approval, and win rate on quotes that triggered approvals above the middle tier. If time-to-send is climbing, the template has acquired friction, usually from a well-meaning field someone added that nobody fills in cleanly. If average discount is drifting up, your pricing floors need revisiting or your enablement needs refreshing. If approval triggers are firing on more than roughly a third of quotes, your tiers are too tight and you are creating queue pressure for no gain. If win rate on heavily discounted quotes is not meaningfully higher than win rate on standard quotes, your discount strategy is not buying you anything and the margin is leaking without a return. Share findings with sales leadership and finance before changing anything. Changes to a quote template ripple into every open deal that references the current configuration, so time changes to the start of a quarter whenever possible.
Three to six is healthy for most mid-market businesses. Build one price book per combination of motion, segment, and currency, then stop. If you find yourself at ten or more, you have a maintenance problem disguised as flexibility, and reps will routinely attach the wrong price book because the names stop meaning anything. Consolidate wherever two price books differ by only a line or two.
Automated routing with manual approvals. The system should block submission until the right approver signs off and route the quote to that approver without a rep having to find them. Approvals themselves stay human because the judgment call that justifies a discount above the standard tier is exactly what you want a manager to make deliberately, not what you want a rule to rubber-stamp.
Route them off-template to a legal and finance review before the quote is generated. The template is designed to handle the common cases cleanly; forcing it to handle every edge creates clutter that slows the common case down. Keep a short, documented list of what qualifies as non-standard, such as deals above a dollar threshold, deals with custom indemnity language, or multi-entity contracts, and build a clear intake path for them.
The catalog needs a single named owner, usually in revenue operations or finance. Shared ownership is no ownership. The owner reviews catalog changes, enforces the SKU convention, maintains the quarterly review cadence, and signs off before any new SKU goes live. Without a named owner, the catalog drifts within six months and the quote template starts producing line items nobody can reconcile.
Review quarterly, revise when the numbers tell you to. Minor fixes such as a typo in terms language or a missing SKU can ship anytime. Structural changes to pricing rules, approval tiers, or document layout should land at the start of a quarter so you are not changing the rules under open deals. Avoid mid-quarter changes except for genuine bugs; the churn costs more than waiting.
In most cases yes, because renewal line items, terms language, and approval triggers diverge enough from new-business quotes to justify their own template. Share the catalog and price books across both templates to avoid duplicating maintenance. The renewal template typically needs fewer approval tiers, additional fields such as prior ACV and expansion delta, and simpler terms language because the master agreement already exists.
Strkr gives you the product catalog, price books, pricing rules, and approval workflows you need to run this playbook end to end. Build once, enforce automatically, close with confidence.
No sales call, no migration consultant, no four-month implementation. Enter your card, get 14 days of the full Pro tier, cancel any time before day 14 with zero charge. Spin up a workspace, import your CSV, and have something useful before lunch.
