All client stories
Client Story · Insurance · Proposal Document Generation

From Rebuilding Proposals to Reviewing Them

Every new insurance proposal meant revisiting work the team had already done. Employees copied an earlier document, retyped customer and property details, and adjusted tables whenever a property's information changed.

We connected reusable proposal templates to Salesforce so the team could generate proposals using information it already maintained. Employees could spend less time rebuilding documents and more time reviewing the finished proposals before sending them.

The everyday work

Preparing another proposal often meant revisiting work employees had already completed. Changing the properties could mean rebuilding the document by hand. Employees needed a way to handle different property combinations without repeatedly copying information, adjusting tables, and correcting earlier details.

The challenge

The team already had the information. Every new proposal still meant rebuilding the document.

Employees copied an earlier proposal and changed the customer and property details by hand.
Information maintained elsewhere had to be retyped or pasted into the document.
Different property combinations required employees to adjust tables and formatting.
Staff had to find and correct details carried over from earlier proposals.
Why the existing approach wasn't enough A reusable Word and Excel mail-merge template helped, but it couldn't handle every variation in property information and document layout.

The team needed proposal generation connected to Salesforce, templates that could handle single- and multi-property scenarios, and a process that still allowed employees to review the finished proposal.
The work

Understanding the process, then improving how proposals were generated

1
Understand the proposal workflow
We met with the client team to understand how proposals were prepared and how that work fit into its broader operations. We started by converting an existing property proposal into a reusable Word and Excel mail-merge template and trained employees to use it.
2
Address recurring document problems
The initial templates still needed refinement. We corrected problems involving dates, mailing versus property addresses, deductibles, and numerical formatting. These details mattered because employees needed to produce accurate documents without continually making the same manual corrections.
3
Connect proposal generation to Salesforce
We configured Conga Composer to generate proposals using information maintained in Salesforce. The templates were designed to accommodate proposals involving one property or multiple properties, reducing the need to manually rebuild the document whenever the property list changed.
4
Resolve variations and support adoption
The conditional property tables required additional troubleshooting and template revisions. We worked through those issues, configured the solution for production use, and trained employees.

After the property-table issue was resolved, the team used the generation process routinely, with employees reviewing the completed proposals before sending them.
The solution

Generate the proposal instead of rebuilding it

Before
  • Start each new proposal by copying and editing an earlier document.
  • Retype or paste customer, property, and policy information.
  • Add or remove property rows and manually adjust tables and formatting.
  • Find and correct details carried over from earlier proposals.
After
  • Generate a new proposal from a configured, reusable template.
  • Populate proposal information using data maintained in Salesforce.
  • Generate the appropriate property table for one or multiple properties.
  • Review the generated proposal for accuracy before sending it to the customer.
Why it mattered

The problem wasn't that employees needed to work faster. They were repeatedly rebuilding information and document layouts that the business already had.

By connecting reusable templates to Salesforce, the team could generate proposals for different property combinations without starting over each time. Employees retained responsibility for reviewing the finished documents, but they no longer had to assemble and correct every proposal from scratch.

That gave the team more capacity to handle requests, respond to customers sooner, and focus on work that required their attention.

The result

Faster proposals, greater capacity, and more reliable customer documents

Faster preparation
Proposal preparation became significantly faster, helping the team respond to customers and sales opportunities sooner.
More with the same team
Employees handled more proposals without additional proposal-preparation staff and gained time for other responsibilities.
Better accuracy
Standardized, Salesforce-connected templates improved document accuracy and consistency while retaining final employee review.

These are qualitative outcomes based on firsthand project observations and recalled client feedback. Preparation time, throughput, error rates, deal-cycle duration, revenue, and financial savings were not independently measured.

Are employees still rebuilding documents from information your business already has?

If every new proposal means copying an earlier file, re-entering details, or correcting tables and formatting, the problem may be in how information and document templates work together.

Let's talk about where proposal preparation creates extra work and what could make the process easier to manage.