How to Turn Meeting Notes Into a Proposal

Notes are the raw material

After a discovery meeting you hold the ingredients: the client's problem, their goals, the requirements they described, constraints, timing and hints about budget. A proposal is those ingredients arranged so that the client can say yes. The skill is in selecting and organizing, not in writing from scratch.

Step 1: mark each note as confirmed, hinted or assumed

Go through your notes and label each point.

• Confirmed: the client clearly stated or agreed it ("launch on 14 November").
• Hinted: implied or uncertain ("budget somewhere around forty").
• Assumed: something you inferred.

Confirmed items become statements in the proposal. Hinted and assumed items become assumptions or questions.

Step 2: map notes to proposal sections

Step 3: write the executive summary last

Summarize the problem, your approach and the outcome in a few sentences, using the client's words. If they read nothing else, this should be enough.

Step 4: be explicit about scope and exclusions

Scope disputes usually start with something that was never written down as out of scope. List what is not included. For a deeper walk-through see the proposal preparation guide.

Step 5: handle the price with care

Do not guess. If the budget was only hinted at, ask. Check line items, taxes and payment terms. State a validity date. Prices are commitments.

Step 6: review as the client

Read the proposal as if you were the client. Is it what they asked for? Anything missing? Anything that will surprise them? Fix it before it leaves your hands.

Doing it faster with software

If you record the meeting, a tool can draft the first version from the notes. MeetMemo drafts proposals, scopes of work and quotations from meeting notes, marks sections it could not confirm, holds back export until you review them, and exports a branded PDF. You enter and confirm the prices. See meeting notes to proposals. It is in early access, and every draft needs your review. Use the project requirements template when the work is complex.

Common mistakes

• Copying the client's hint as a commitment
• Leaving exclusions out
• Sending a draft with unconfirmed sections
• Pricing before confirming scope

A worked example, from notes to sections

Notes from the call:

"Northwind sells outdoor gear online. Their site is dated and slow on phones. They want it live before the autumn campaign, around 14 November. Five pages: home, shop overview, about, delivery info, contact. Priya supplies the copy by 24 October. Budget: 'let's see the proposal'. Maybe a blog later. Hosting access needs IT."

Proposal sections drawn from them:

• Executive summary: Northwind's current site is dated and slow on phones. We will build a faster, modern five-page site, live by 14 November, ready for the autumn campaign.
• Scope: home, shop overview, about, delivery information and contact pages.
• Timeline: launch on 14 November, subject to the assumptions below.
• Assumptions: Northwind supplies all copy by 24 October. Northwind provides hosting access.
• Exclusions: a blog, which may be added later as a separate piece of work.
• Price: to be completed once scope is confirmed.

Notice that every statement traces back to the notes, and nothing was added that the client did not say.

Choosing how to price

The right pricing model depends on how well the work is defined. These are general patterns, not recommendations for your business.

• Fixed price suits clearly defined scope. Protect yourself with explicit exclusions and a change process.
• Time and materials suits uncertain or evolving scope. Give an estimate range and how you will report hours.
• Retainer suits ongoing work. State what is included each month and what happens when the client needs more.

Whichever you use, say what is included, what is not, how changes are handled, when payment is due, and how long the quote is valid.

How long should a proposal be?

As long as it takes to be clear, and no longer. For a small project, two to four pages is often enough. Long proposals are not more persuasive. They are harder to approve, because the client has to read more to find what they are agreeing to.

Before you send: a final checklist

1. Does the executive summary use the client's own words for their problem?
2. Is every item in scope something they actually asked for?
3. Are exclusions written down?
4. Are dates, names and numbers correct?
5. Are the price, tax and payment terms confirmed by you?
6. Is there a validity date and a clear next step?

Frequently asked questions