AI Proposal Generator: Preserve the Facts in the Call Notes

The AI draft promises two workshops next week, but the call only discussed a possible session format. Put the source notes beside the proposed scope so the client can see what still needs confirmation.

Separate supplied facts from proposed terms

The fictional Cedar Path Co-op brief asks for two 90-minute staff onboarding workshops and four hours of preparation. An illustrative provider rate is $75 per hour. Delivery dates, participant count and tax treatment are unresolved. These are example assumptions, not a real customer's agreement.

A source-traceable workshop proposal with fee arithmetic, scope boundaries and open decisions
A source-traceable workshop proposal with fee arithmetic, scope boundaries and open decisions
Open the full example ↗

Let the AI organize the offer without inventing the agreement. Source note N1 supplies the workshop count and length. N2 supplies preparation hours and the rate. N3 says dates are not yet agreed. The review proposal carries these IDs into the relevant rows and leaves booking conditions visible instead of filling them with plausible dates.

Atlassian's business proposal guidance separates the problem, solution, scope and pricing. Apply that structure to your actual notes. A benefit can be the intended purpose of the work; it should not become an unsupported percentage improvement or a testimonial you never received.

Recompute the fee before sending the draft

Two 90-minute workshops require 180 delivery minutes, or three hours. Add four preparation hours: seven hours at $75 equals a $525 service fee. This is the sample fee basis, not a final tax-inclusive invoice. Payment timing and tax treatment remain [TO CONFIRM].

The proposed scope includes the two workshops, their agenda and participant handout. It excludes travel, venue hire, recording and ongoing coaching unless separately agreed. The client needs to confirm dates, audience size, delivery setting and the person who can approve the scope. No date is booked and no signature, payment or savings calculation is simulated.

Give the model the actual source constraints

Create a self-contained HTML proposal review copy from these call notes.
Provider, client, problem and source notes with IDs: [PASTE]
Proposed scope, deliverables, exclusions and assumptions: [PASTE]
Quantity, session duration, preparation hours, rates and supplied totals: [PASTE]
Dates, prerequisites, approvals, taxes and payment terms actually agreed: [PASTE]
Open decisions and required official submission/acceptance format: [PASTE]

Use only supplied facts. Mark gaps [TO CONFIRM]; distinguish proposals from commitments and preserve source-note IDs. Do not invent dates, credentials, client outcomes, savings, testimonials, approvals or tax rates. Recompute quantities, minutes-to-hours and fee sums. Retain a conflicting supplied total with [CHECK TOTAL] and withhold affected final pricing until confirmed.
Show the intended work, source-traceable scope, fee basis, exclusions and a short decision request. Use captioned tables with scoped headers, at least 16px body text and labeled rows at 360px without page overflow. Inline CSS only; no scripts, external assets, network, editable fields or fake signature/payment controls. Keep official proposal and acceptance workflows authoritative. Return complete HTML and a list of unresolved terms.

Ask the client to test the boundaries

Send the review draft and ask whether the workshop count, preparation allowance and exclusions match their understanding. If the notes and offer are hard to compare, read them together in the prepared HTML review copy in NOS, then revise the official proposal.

Send the clarified offer with the decisions still needed. Confirm the actual engagement through the normal acceptance process before scheduling work. A readable proposal is not a booking or payment record.

Keep reading