Contents
A beautiful proposal and a believable proposal are easy to confuse, especially from the side that writes them. One makes the reader admire the agency for a few minutes. The other makes the reader willing to hand over their event, and in my experience the two overlap much less than agencies hope. Clients usually read an event proposal from the total outwards: they open the cost table, check the line items and the scope against whatever can be verified, and only then return to the concept to decide whether the people behind it can be trusted with the day.
I have spent time on both sides of this. In my operations years with Global Tourism Forum and, later, INFLOW Network I received proposals, put them next to each other and argued about them with colleagues; as a co-founder of Flex Event, I now write them, often against a deadline that arrived with a late brief. An event proposal, for the record, is the document in which a company describes how it would deliver a specific event: what it would do, with which suppliers and which team, on what timeline and at what cost. Its job is to win the work. For the person reading it, though, it is a promise about a day that hasn’t happened yet, and reading it means judging how far that promise can be trusted. Speaking for myself, that is how I have always read proposals, from either chair, and it has very little to do with the order in which the pages were arranged.
The cost table gets opened first
Agencies build a proposal like a story. The opening pages carry the understanding of the brief, then the concept with its own name and logo, the moodboard, the flow of the day, the technical plan, the team, the references, and at the very end, the total. The structure climbs towards the number.
Most readers start at the number. That is not greed, and it is not a lack of interest in ideas. The total tells them how to read everything else. If it sits far above what they had in mind, the concept pages will be read sceptically, in search of what could be cut. If it is suspiciously low, the reader goes straight to the line items looking for what is missing. Only when the total lands inside the expected range does the file get read roughly in the way the agency intended, from front to back with some goodwill.
Agencies that accept this write the cost section with more care than the cover. A short summary at the top of the table, saying in a few lines what is included, what is assumed and what is not covered, does more for the reception of the whole file than another two pages of concept. It also signals something readers notice immediately: that the company is comfortable being checked.
Each desk in the client’s office reads a different page
A proposal for one of a company’s corporate events or for a congress almost never has a single reader. The marketing or events manager who wrote the brief reads it closely, page by page. In larger companies, procurement reads the commercial terms and lines the numbers up against the other files. The general manager or board member who signs off may look at three pages at most: the idea, the total and perhaps the team. Someone in finance reads the payment schedule and nothing else. In associations, a committee often sees only a summary prepared by one of its members, which means the agency’s file is being retold by someone else before it is judged. For companies with a foreign head office, the proposal may also be summarised in English and forwarded abroad, where someone who has never been to the venue reads a page of it on a screen between meetings.
Each of them is reading a different document, in effect. A file written for one of them, usually the creative audience, loses the others; the cost page full of jargon puzzles the general manager, and the concept pages full of adjectives irritate procurement. The best proposals I have read seemed to know who would be holding which page and wrote each section in the language of its most likely reader, plainly where it needed to be plain and with some colour where colour helped.
The line items carry the trust
A proposal is judged by its most checkable page, and in event work that is almost always the list of line items.
Concepts cannot be verified before the event; line items can. An experienced reader looks at a row reading “sound and light system” and asks how many speakers, what class of equipment, how many technicians, whether setup and rehearsal days are included. Rows for event technology get the same treatment, since a registration app or a live voting tool often appears as a single word and a price, with nothing about who operates it on the day. A row that answers those questions in the file builds trust, and a row that leaves them open looks cheap, because it can be filled in later however suits the supplier. Phrases like “or equivalent” next to equipment brands, staff numbers without hours, transfers without vehicle types and venue costs that quietly leave out the setup day are the rows that get read twice by anyone who has run an event.
Agency fees belong in the same conversation. Some companies show the fee on a separate line, as a percentage of the total, while others spread it across the items. Both are legitimate, but readers notice which approach is used, and a file that is open about its fee tends to earn more trust than one that buries it, even when it looks more expensive at first sight.
Concept pages are read in their own particular way, for recognition rather than inspiration. Readers aren’t hoping to be surprised; they want to see their own event. That is why moodboards built from images found online so often fall flat, since the reader has met the same glowing tunnel and the same floral arch in other files that month. What lands is an idea that clearly grew out of this client’s audience, product, venue or something said in the briefing meeting. A concept that follows the attendee journey from the invitation to the ride home reads as thought through, because the reader can picture their own guests inside it. Since so many proposals are produced in a week or less, the concept is frequently the most rushed section, and it shows. One modest idea that fits will always read better than three ambitious ones that could belong to anybody.
A concept also reads as more honest when it says which parts are still pictures. The distinctions I look for are simple ones:
- a stage rendering is not a structural drawing
- a guest flow sketch is not an approved crowd safety assessment
- a proposed speaker is not a confirmed booking
- a venue on option is not a signed venue contract
Marking these takes a line each, and it makes everything else in the file easier to believe.
Four PDFs often describe four different events
The hardest part of reading is comparison. On paper it looks easy: four files, four totals, choose the best value. In practice the files frequently describe four different events, particularly when the brief gave no budget range or a vague audience. One agency imagines a simple program in a hotel ballroom, another an outdoor stage with a show, a third adds flights and accommodation the others left out, and a fourth quietly turns the whole thing into a hybrid event with a streaming crew nobody asked for. Setting those numbers side by side means nothing, and the reader ends up building a spreadsheet to translate every file into the same scope. That spreadsheet, more than the proposals themselves, often decides who wins. Procurement teams with long experience fix their evaluation criteria before any offer arrives, and any client can borrow that habit without the paperwork, simply by deciding what will be compared before the brief goes out.
Agencies can make this much easier, and the sharp ones do. A short paragraph near the front that restates the scope as the agency understood it, with the number of guests, the days, whether any part of the program runs as a virtual event, what is included and what has been assumed, lets the reader see at once whether the files are comparable. It protects the agency too, because a client who chose a proposal knowing its exact scope is far less likely to feel surprised by an invoice later. I would go further and say that when a brief is genuinely unclear, a quick call to ask, before writing anything, is a better investment than a polished file built on a guess.
The meeting room after the PDF
Many proposals are decided not on paper but in the meeting that follows, when two or three companies are invited to present and answer questions. What the client is really testing there is whether the people at the table understand the file they sent. Can the project manager explain why setup needs two days? Can someone say, without searching through the deck, what happens if the opening speaker cancels? Does anyone know who will write the survey questions sent to guests afterwards, and what the client will do with the answers? Does the team know which of the client’s people will make the final call? These answers reveal far more than any page.
From the agency side, I have come to treat that meeting as a second brief. The client’s questions show what worried them while reading, and those worries are rarely the ones the agency expected, so a revision sent afterwards that answers them directly, instead of repeating the presentation, is often what wins. For larger events, that conversation sometimes ends in a staged decision, with the agency appointed first for a planning phase and production approved later, once the site visit and the real budget are done, which is a sensible arrangement for both sides when the scope is still moving. From the client side, the meeting is the place to ask about the rows that looked thin and the assumptions hiding in the scope. It is also where the client sees, sometimes for the first time, whether the person who would run the event was even involved in writing the file. A project manager who can talk through the timeline without looking at the slides has usually built it, and one who keeps deferring to the sales director usually has not, which is worth knowing long before the contract is signed.
The meeting is also where the agency learns whether it is being taken seriously or simply used as a price reference. Clients who already know whom they will choose sometimes invite others to justify the decision internally, and experienced agencies can usually tell from the questions. A client who asks nothing about the team, the timeline or the risks, and only about the discount, has often made up its mind already.
Admiration fades by the time the file reaches the second reader, while trust survives being forwarded, summarised and compared line by line. That is the whole difference between the beautiful proposal and the believable one, and the contracts I have seen signed almost always went to the second kind.