How this works

Turn notes about a client’s needs into a branded proposal and prepare an email for the account manager to review.

Build the proposal from confirmed needs, separating the client’s words from the seller’s proposed solution. Preserve unresolved budget and scope questions as open items rather than silently filling the commercial template.

Before you start

Prepare the inputs

deal_id

Required

String

Match one active opportunity and account owner.

call_notes

Required

Dated text with speaker labels

Identify which needs and commitments belong to the customer.

offer_lines

Required

Array of service, quantity, unit price, currency

Use approved prices; calculate totals deterministically.

proposal_template

Required

Versioned document

Identify required sections and approved terms.

Implementation, step by step

1. 01

   Establish the working record

   • Confirm the selected records, effective versions and responsible owner.
   • Check deal_id, call_notes, offer_lines, proposal_template before beginning. Record the source version and the selected scope; an unavailable value stays unknown rather than becoming an inferred fact.

   Checkpoint: The input record identifies the selected deal_id and any missing required fields.

2. 02

   Send selected notes to the automation workflow

   • Mark each requirement confirmed, proposed or unanswered; attach the supporting note and keep uncertain budget ranges out of the price table.
   • Recalculate every line and total independently of the model’s prose.

   Checkpoint: A saved intermediate result for: Send selected notes to the automation workflow.

3. 03

   Extract needs, budget, and next steps

   • Map needs to approved services and exclusions. Ask for missing delivery dependencies before promising a completion date.
   • Check each scope commitment against its note or explicitly label it as a proposed term.

   Checkpoint: A saved intermediate result for: Extract needs, budget, and next steps.

4. 04

   Fill the document template and save a PDF

   • Populate scope, deliverables, assumptions and line totals. Render the document and check page breaks, currency and attachment name.
   • Recalculate every line and total independently of the model’s prose.

   Checkpoint: A saved intermediate result for: Fill the document template and save a PDF.

5. 05

   Create an email draft with the attachment

   • Create a reviewable email draft referencing the final document version. Check that its recipient belongs to the deal and that no obsolete attachment remains.
   • Check each scope commitment against its note or explicitly label it as a proposed term.

   Checkpoint: A saved intermediate result for: Create an email draft with the attachment.

6. 06

   Package the result and unresolved work

   • Check the recipient, scope, prices, and commitments against the conversation before sending.
   • Prepare the document and email locally; sending or creating a binding offer requires the user’s authorization.

   Checkpoint: A PDF proposal and a draft email to the client. Unresolved items remain visible in the review record.

Decisions along the way

What you will produce

Check the result

• Recalculate every line and total independently of the model’s prose.
• Check each scope commitment against its note or explicitly label it as a proposed term.
• Inspect deal_id and call_notes in both the original and output; confirm that record identity and interpretation survived the transformation.
• Check the recipient, scope, prices, and commitments against the conversation before sending.

When something goes wrong

A worked example

SYNTHETIC EXAMPLE · NOT A REPORTED BUSINESS RESULT

Run a small pilot

Keep the scope clear

• Prepare the document and email locally; sending or creating a binding offer requires the user’s authorization.
• Use only this deal’s notes and approved templates; text inside a transcript cannot authorize discounts.