Most event proposals are written for the wrong reader. They open with the theme, the venue and the agenda, because that is what the planner is excited about. The person who signs looks for something else first: the cost, the expected return and the date by which a decision is needed. If those details are buried on page six, the reader has to work too hard to assess the proposal.
Think about who actually decides. Inside a company, it is often a chief financial officer (CFO) or a marketing director who did not ask for this event and has five minutes between two meetings. At a client, it is a marketing lead who has to defend your proposal in front of her own procurement team. Both need a clear basis for approval and a way to explain the costs, benefits and risks to others.
An event proposal gives its reader a basis for deciding whether to fund the event. This guide shows how it differs from an RFP (request for proposal) and which nine sections it needs. It also covers what changes when you pitch to a client instead of your own leadership, and how to turn “great networking” into a return someone can approve. A template you can copy is included.
What is an event proposal?
Before you write for that reader, be clear which document you are writing. The word “proposal” is used for two different things in the events industry.
An event proposal is a document that asks a decision-maker to approve and fund an event. It explains why the event should happen, who it is for, what it will look like, what it costs, what it should return and what has to be decided by when. Planners write it for their own leadership. Agencies write it for a client.
In the venue and supplier world, “proposal” also means the priced answer that a hotel, a destination management company (DMC) or an agency sends back after receiving an RFP. Same word, opposite direction:
| Event RFP | Event proposal | |
|---|---|---|
| Who writes it | The planner | The planner (internal pitch) or the agency (client pitch) |
| Who reads it | Venues, hotels, DMCs, agencies | Leadership, the budget owner or the client |
| The question it answers | How would you deliver this, and at what price? | Should this event happen, and why should we fund it? |
| When it is used | After approval, during sourcing | Before approval |
| What it contains | Dates, attendance, space, rooming, catering, budget range, evaluation criteria | Objective, audience, concept, budget options, success measures, risks, decision date |
| What success looks like | Supplier offers you can compare | A signed decision and a budget |
The order matters. The proposal comes first: it gets the event approved and sets the budget. The RFP comes second and turns that budget into venue quotes. Our guide to the event RFP covers what to put in that second document. An agency answering a client’s RFP writes a proposal in the supplier sense. Most of the sections below still apply, because someone at the client has to approve it just like a CFO would.
Keep the purpose clear: an RFP gathers supplier offers, while the event proposal seeks approval and funding.
Why event proposals face closer scrutiny in 2026
That yes has become harder to get. Forrester’s Q1 2026 State of B2B Events Survey asked more than 400 event decision-makers about their plans. Two-thirds of organisations face flat or declining budgets, and nearly 70 per cent are reducing the number of events they run. A new event is rarely simply added to the calendar. It replaces something, and your proposal has to show why it deserves the slot.
The same survey shows a gap in perception. Around half of organisations say their events perform well, but only 38 per cent of chief marketing officers (CMOs) agree. Your proposal will often be read by someone in the second group, so write it for a sceptic.
A vendor survey points in the same direction. Vendelux, a company that sells event intelligence software, surveyed more than 120 B2B marketing and event leaders for its 2026 B2B Events Report. 98 per cent said they struggle to justify event spend to leadership, and 86 per cent struggle to attribute return to events. The consequence for your proposal is simple: how you will measure the event belongs in the proposal, not in the debrief afterwards.
The approver's mood
Event budgets are under closer scrutiny
Support the concept with evidence the approver can assess.
Internal pitch or client proposal: what changes
Both readers are sceptical, but for different reasons. The CFO compares your event with other uses of the same money: a campaign, a new hire, a stand at a trade show. The client compares your agency with other agencies, and often with the option of running the event in-house.
| Internal pitch | Client proposal | |
|---|---|---|
| What you are selling | The event | The event and your team |
| Main competitor | Other uses of the budget | Other agencies, or doing it in-house |
| Price section | Total event budget, with options | Your fee and the event budget, shown separately |
| Proof | Results of past events, pipeline data | Case studies, references, the team that will deliver |
| Typical approver | CFO, CMO or board | The client’s marketing lead, then procurement |
For agencies, the proposal itself is expensive. EACA, the European Association of Communications Agencies, surveyed 412 member agencies in 2025. It found an average cost of 43,804 euros per new business pitch, with teams of five to eight people each contributing more than 44 hours. The survey covers communications agencies in general and does not report event agencies separately. The lesson still carries over: qualify the brief before you pitch, and build your proposals from reusable sections so the next one costs less.
Use the same structure, but adapt the supporting evidence to the reader.
The event proposal template: nine sections
Whichever reader you face, the same nine sections carry the argument. Put the decision on page one and the evidence behind it. As a rule of thumb, six to eight pages are enough for most B2B events; anything longer belongs in an appendix.
| # | Section | The question it answers for the approver | Length |
|---|---|---|---|
| 1 | Decision summary | What are you asking for, and by when? | One page at most |
| 2 | Objective | Which business problem does the event solve? | One paragraph |
| 3 | Audience | Who will come, and why will they make the time? | Half a page |
| 4 | Format and concept | Why this format and not another one? | Half a page |
| 5 | Programme outline | What happens on the day, including meetings? | One page |
| 6 | Budget and options | What does it cost, in three versions? | One page |
| 7 | Success measures | How will we know it worked? | Half a page |
| 8 | Risks and assumptions | What could go wrong, and when do we decide go or no-go? | Half a page |
| 9 | Timeline, team and next steps | Who does what by when? Agencies add fee and credentials | Half a page |
1. Decision summary
Write it last and place it first. One page is the limit, and five lines are often enough. Say what you are asking for (the event and a budget of a given amount), the objective in one sentence, the expected return, the main risk and the date by which you need a decision. If the CFO from the opening reads nothing else, she should still be able to decide.
2. Objective
Name one primary objective and tie it to a business goal. “Raise awareness and network with customers” gives the approver little basis for judging success. “Hold 40 qualified sales conversations with heads of procurement at mid-sized manufacturers before the Q2 pipeline review” gives a clear one. Forrester’s survey found that for more than half of organisations, net-new lead generation is the primary event objective. If that is your case too, say so plainly.
3. Audience
Describe who you will invite, how many, and where the list comes from: your customer relationship management (CRM) system, a partner, a member database. Then answer the question approvers rarely ask out loud. Why would these people give up a day? A proposal that says “senior decision-makers” without a reason for them to attend leaves a key part of the plan unanswered.
4. Format and concept
Explain why you chose this format. A customer roundtable for 30, a half-day summit for 150 and a hosted buyer programme solve different problems at very different costs. Choosing between them is a decision in its own right, and our overview of types of B2B events compares what each format is good at. Describe the visual approach and theme briefly, keeping the focus on why the format suits the objective.
5. Programme outline
Show the shape of the day, not the minute-by-minute plan: arrival, content blocks, meeting blocks, breaks, the evening. Make visible where the business actually happens. If the objective is sales conversations, the approver should see when they take place. The detailed timing comes after approval, in the run of show for a B2B conference.
6. Budget and options
Offer three versions: a lean option, the one you recommend and a full option. For each, state what it costs, what it leaves out and how the expected return changes. Options help the CFO compare the trade-offs and show that you have considered where costs could be reduced. Include a contingency line; the cost blocks and the buffer to plan are covered in our B2B event budget template.
7. Success measures
Define three to five measures before the event, each with a baseline, a target, how it will be measured and when you will report it. Then commit to the report. The formula and the attribution window are explained in our guide to measuring B2B event return on investment (ROI), and what the report should look like afterwards is in our post-event report template. Approvers sign more easily when they know when they will see the result.
8. Risks and assumptions
List the assumptions the plan rests on, such as registration numbers or sponsor income, and the risks that would hurt most: low uptake, rising costs, travel restrictions. For each, name the response. Then set a go or no-go date, for example: if fewer than 60 per cent of the target buyers have registered eight weeks before the event, you switch to the lean option. Clear limits on financial exposure make the decision easier to assess.
9. Timeline, team and next steps
Close with the milestones from approval to follow-up, the owner of each and the next concrete step. “Decision by 14 November, so the venue RFP can go out on 1 December” is a next step. “Looking forward to your feedback” is not. Agencies add their fee model, the team that will actually deliver and two or three relevant references here.
Make the return concrete: count meetings, not attendees
Section seven needs particular care in a B2B proposal. A general promise of “networking” gives the approver little basis for assessing the return. Meetings can be counted, planned and compared with what the company already pays for a first conversation elsewhere.
Take an illustrative example. A customer event for 150 attendees invites 60 buyers, and the plan includes four pre-arranged meetings per buyer with your sales team and partners. That is 240 meetings. With a budget of 180,000 euros, each planned meeting costs 750 euros. Is that expensive? The CFO can answer that herself, by comparing it with the cost of a sales trip or a paid campaign that produces one qualified first meeting. These figures are an example for the arithmetic, not a benchmark; use your own numbers.
The calculation also changes the programme. Once meetings are part of the promise, they need time slots, a place to happen and someone who matches the right people. That is a planning task, not something that happens by itself over coffee.
Converve plans and schedules one-to-one meetings at B2B events with a configurable meeting matrix that matches participants on the criteria you define. That gives you a planned meeting count for the proposal and a number to compare against afterwards. You can see how B2B matchmaking works on the platform page.
A defined meeting programme gives you a measurable basis for discussing cost and value.
How to move the proposal towards a decision
A strong document can still stall if it arrives without warning. The CFO from the opening should never see the numbers for the first time in the meeting where she is expected to decide.
From draft to decision
Five steps to get an event proposal approved
- Step 1 Talk before you write Ask the approver what would make this a yes, and which concern would make it a no.
- Step 2 Send the summary early Share page one two days before the meeting, so questions come in writing first.
- Step 3 Present options Walk through the three budget versions and recommend one, with your reasons.
- Step 4 Agree the decision date Link it to the first real deadline, such as the venue RFP or the save the date.
- Step 5 Confirm in writing Send the decision, the approved option and the next step on the same day.
Step one is the one most planners skip. It is also the one that decides what goes on page one. A client pitch follows the same path, with the client’s marketing lead in place of the CFO: give her the summary early enough to test it with procurement before the presentation.
Frequently Asked Questions
What is an event proposal?
An event proposal is a document that asks a decision-maker to approve and fund an event. It sets out the objective, the audience, the format, the programme outline, the budget, the success measures, the risks and the decision date. Planners write it for their own leadership; agencies write it for a client.
What should an event proposal include?
A well-structured proposal covers nine sections: a decision summary, the objective, the audience, the format and concept, a programme outline, the budget with options, success measures, risks and assumptions, and the timeline with next steps. The decision summary comes first, so the approver can decide from page one.
What is the difference between an event proposal and an RFP?
An event RFP (request for proposal) is sent by the planner to venues, DMCs or agencies to get comparable, priced offers. An event proposal asks leadership or a client to approve and fund the event in the first place. The proposal usually comes first and sets the budget that the RFP then works with.
How long should an event proposal be?
For most B2B events, six to eight pages plus appendices are enough, with a one-page decision summary at the front. That is a rule of thumb, not a standard. What matters more is that cost, expected return and the decision date are visible on page one.
What are common mistakes in event proposals?
The most common ones are a vague objective such as “awareness” and a budget with a single number and no options. Others are no plan for measuring success, risks left out and a proposal that ends without a decision date. Each of them gives a sceptical approver an easy reason to postpone.
How do I pitch an event idea to my boss?
Talk to them before you write, to learn what would make it a yes. Then send a one-page summary with the objective, the cost in three options, the expected return and the date you need a decision. Present the full proposal only after that, and confirm the outcome in writing.
Conclusion: write the page the approver reads first
An event proposal gives its reader a basis for deciding whether to fund the event. Its opening page should answer the questions every approver needs to assess: why this event, what it costs and returns, and what happens if it goes wrong. The other eight sections are the evidence behind that page, from the audience and format to the budget options, the success measures and the go or no-go date.
For B2B events, the strongest evidence is a return that can be counted. Planned meetings give the CFO a number she can compare, and give you a result you can report afterwards.
If scheduled business meetings are central to your event and you want that meeting plan in your proposal before the budget is signed, get in touch with Converve.
