Proposal Generation for CPQ
They asked for a proposal. You sent a quote PDF and a cover note. Assemble scope, terms, and configured specs in one customer-ready document.
Proposal · present
Quote data → polished customer document
Source quote
Q-10482
Nordic Process Systems
MX-440 · €84,600
Page 01 · Cover
Nordic Process Systems
MX-440 industrial package · proposal summary for corrosive service duty.
What changes
Full proposal
Scope and narrative sections included
From config
Specs and pricing from validated configuration
Before send
Proposal ready before the customer meeting
The challenge
They asked for a proposal. You sent a quote PDF and a cover note.
A municipal buyer requests a formal proposal for an industrial water treatment skid. Inside sales exports the CPQ price breakdown to PDF, writes scope paragraphs in Word, and pastes boilerplate terms from last year's RFP response. Page three still lists the old membrane option because nobody synced the narrative with the configuration the buyer reviewed online.
Procurement compares three vendors on scope clarity, not line-item price alone. Your quote PDF shows totals and SKUs. Their proposal explains delivery boundaries, service terms, and what is excluded. You lose on format before anyone disputes the number.
Automated quote generation creates records from configuration. PDF quote generation formats branded output. Quote templates control layout blocks. Proposal generation is different: Mercura assembles a customer-facing proposal document with configured product detail, commercial terms, and narrative sections your team approves, not a price list with an email introduction.
Inquiry to config to price to approval to order should produce a proposal that reads like a response to the RFP, not a spreadsheet export with a greeting.
How it works
How Mercura generates sales proposals
Sales ops define proposal templates in Mercura: executive summary, scope of supply, configured equipment sections, commercial terms, exclusions, and optional appendices. When a rep completes a valid configuration, Mercura merges configured BOM lines, pricing, and visuals into the proposal structure. PDF quote pages cover fast branded output; this page is the longer-form document for evaluators who need context. Quote-management tracks pipeline stage; templates control reusable blocks. Someone must maintain approved legal language and which sections appear per product line.
One quote object · four aspects
Q-10482 · Nordic Process Systems · MX-440
Created from
MX-440 configuration
Layout
Approved template
Status · owner
Pending approval · Anna
Document
Proposal
This page · Presented as a multi-section customer document · illustrative record
Two layers
Quote data plus commercial narrative
Proposal merges validated configuration data into approved narrative sections
Layer 1 · Quote data
From the validated configuration
- · Configured BOM lines
- · Options and specs
- · Merged pricing
- · Quote reference Q-10482
Layer 2 · Narrative
From approved proposal sections
- · Executive summary
- · Scope of supply
- · Terms and exclusions
- · Service boundaries
Proposal
One customer document
Specs and pricing stay aligned with what the buyer configured.
Optional section
A section that appears only when the template says so
Illustrative · driven by template section rules, not an automatic content decision
- 01
Cover
- 02
Recommended solution
- 03
Configured scope
- 04
Commercial breakdown
- 05
Terms & next steps
What's included
What proposal generation covers
Tell
- Proposal documents with scope narrative and configured specs
Detail
- Merged pricing and BOM from the validated configuration
- Traceability from proposal sections back to configuration data
Commercial
- Reusable sections for terms, exclusions, and service boundaries
Reach
- Same proposal logic for inside sales, dealers, and key accounts
Next
- Proposal output before approval routing or customer send
- Works with quote templates, PDF generation, and automated quotes
- Updates when configuration, pricing, or approved text changes
The difference
Proposals before and after CPQ
Quote PDF plus Word narrative
- 01 Reps export price PDF and write scope in a separate file
- 02 Terms and exclusions copied from old RFP responses
- 03 Configured options in the proposal disagree with CPQ
- 04 Each bid rebuilds narrative from scratch
- 05 Procurement receives format that looks like a price list
With Mercura
- 01 Configuration merges into a structured proposal document
- 02 Scope and specs stay aligned with what the buyer configured
- 03 Approved terms and sections reused per product line
- 04 Revisions update narrative and pricing together
- 05 Evaluators receive a proposal, not a PDF with a cover email
Real-world example
Example workflow: water treatment skid proposals
A builder of industrial water treatment skids responds to municipal and plant RFPs. Reps used to send CPQ price PDFs with manually written scope in Word. After defining proposal templates in Mercura, a validated skid configuration populates equipment sections, pricing, and standard terms in one document, scope matches the online configuration the buyer saw, and revision rounds update both narrative and line items without rebuilding two files.
Business impact
Why proposal generation is evaluators' document, not a longer quote
Proposal generation is how CPQ answers formal bids with context, not only numbers. It complements automated quote creation, PDF output, templates, pipeline management, versioning, and comparison. Mercura does not replace legal review of contract terms or your CRM opportunity record. Someone must approve template text and train reps when to send a proposal versus a quote. If procurement rejects bids because "this is not a proposal", structured proposal output from configuration aligns inquiry, configuration, price, approval, and order with how buyers actually evaluate.
Business impact
More than a price list
Scope, narrative, and configured specs in one customer document.
Aligned with configuration
Proposal content merges from the same validated session.
Evaluator-ready format
Commercial narrative and terms for formal bids and RFPs.
Compare
Automated quote vs proposal
| Automated Quote Generation | Proposal Generation | |
|---|---|---|
| Answers | Is there a quote record from this configuration? | Does the customer get scope and context, not only numbers? |
| Output | Quote record with lines, options, and pricing | Structured proposal with scope, specs, and terms |
| Depth | Line structure and price | Narrative sections plus configured specs |
| Typical reader | Sales and approvers | Evaluators and procurement |
Both start from the same validated configuration.
Compare
Proposal vs quote templates
| Proposal Generation | Quote Templates | |
|---|---|---|
| Role | The document an evaluator reads | The reusable structure behind documents |
| Controls | Scope, specs, terms, and narrative | Layout, branding, and section rules |
| Maintained as | Approved text per product line | Template library per segment and channel |
| Relationship | Uses template structure | Serves quote, PDF, and proposal output |
Templates decide structure; proposals decide what the customer reads.
Quoting map
How building the offer, creating, controlling, formatting, and presenting a quote connect
Sections merged · proposal ready to present
See a proposal assemble from configuration and approved sections
Book a demo and complete a configuration until scope, terms, and specs appear in one proposal before send.
Let’s build together.
We empower manufacturers to master product modeling, streamline quoting process, reduce errors, and ultimately deliver the tailored solutions that customers demand.