Proposal Tools
Proposal generation turns reviewed Salesforce Opportunity line items into customer-facing documents. The goal is an editable DOCX when needed and a polished PDF that matches company branding and contract language requirements. This section exists because proposal formatting, template selection, photo appendices, contract language, and Salesforce attachments are operationally sensitive and need repeatable rules.
Document outputs
| Output | Purpose |
|---|---|
| Primary customer proposal attachment and print/export format | |
| DOCX | Editable version for manual adjustment where required |
| Inspection report | Internal-facing report with inspection findings and photos |
Rendering model
Reviewed line items ── become ── proposal table
Company template ── supplies ── header, footer, brand, typography
Photo appendix ── appears before ── contract language
Final document ── attaches to ── Salesforce OpportunityTemplate direction
The proposal renderer should use company-specific template assets where available. American Pool, Continental, and SCMG templates differ mainly by header, footer, branding, and typography. Contract language should appear behind any selected photo appendix.
Trackability
SaleID should appear on generated customer proposals and in the footer where required so each quote can be traced back to the Salesforce Opportunity.
Common pitfalls
- Do not treat DOCX output as a pixel-perfect PDF clone; it should be editable while staying visually close.
- Do not include raw uploaded file names under customer-facing photos unless the proposal explicitly requires them.
- Do not generate customer-facing proposals before the review workflow has produced the final Salesforce line-item state.
Related pages
- Standard Workflow explains where proposal generation belongs in the guided process.
- Expert Mode explains proposal generation when no field inspection is used.