Ravi and the Brief That Saved His Product Launch

Ravi joined one of my Module 1 groups in early autumn. He worked in marketing for a small hardware company and had been told, in one meeting, that he would run the unveiling of a new product. He had a date, a rented room and a lot of enthusiasm. What he did not have was a written description of what the event needed to achieve.

I asked him the question I ask every learner on the first evening: if a producer called you tomorrow to quote this job, what would you tell them? Ravi listed the date and the venue name and then stopped. He laughed, a little embarrassed, and said that was the whole list.

That honest pause is where the module begins. A launch project has stages, and each stage depends on information gathered in the one before it. Ravi had skipped straight to the end of the line, and he was about to ask strangers for prices on a job nobody had defined.

We spent the first session mapping a launch project from first conversation to the day after the event. Ravi drew it on a whiteboard: enquiry, brief, quotation, planning, rehearsal, event day, delivery. Seeing it laid out, he noticed that his company had decided on the venue before anyone had decided how many guests the room had to hold.

That is a common order of events, and it is not a disaster, but it narrows choices. We talked about which decisions are cheap to change early and expensive to change late. Guest numbers, stage size and whether the event is filmed all belong in the cheap column at the start of a project.

I encouraged him to treat the stages as a conversation order rather than a rulebook. Each stage gives you a reason to ask the next set of questions, and none of them is wasted if the brief is honest.

• Enquiry: who is asking and why now
• Brief: goals, audience, tone
• Quotation: scope the producer can price
• Delivery: what the client receives afterwards

For the practice exercise, each learner writes a one-page brief for an imagined launch. Ravi chose his own, which made it the most useful brief in the room. He had to decide what a successful evening looked like: press attending, a recorded reveal for the website, a short live segment for people who could not travel.

Once those goals were written down, other details followed naturally. A recording meant thinking about camera positions and the sight lines from the audience. A live segment meant asking about internet at the venue. A reveal moment meant talking to the presenter about timing.

I read his draft in the break and marked the gaps with a pencil. Not many were missing, but the ones that were would have changed the price: nobody had asked whether the room had a loading entrance, or how long the team could access it before doors opened.

The module's central lesson is that a quotation is only as good as the information behind it. Producers price what they can see in the brief. Where the brief is silent, they either guess high to protect themselves or guess low and discover the gap later, usually on the day.

We practised the list of details a producer will want before writing a number: event date and any flexibility, venue and access times, expected audience, running order in rough form, number of presenters, filming and streaming needs, and what should be delivered afterwards.

Ravi copied the list into his notebook and said he would send it to his managers before the next planning meeting. I told him that was the real exercise. The skill is not only knowing what to ask a producer but knowing what your own team has not yet decided.

• Date, flexibility and venue access times
• Audience size and running order in outline
• Filming, streaming and delivery expectations

A few weeks later Ravi told the group how the enquiry went. He sent a one-page brief to three producers instead of a vague email. The replies came back faster, and the questions they asked were sharper, because they were responding to a plan rather than trying to build one from nothing.

One producer pointed out that the rented room had limited load-in time, something Ravi had not considered. Because it surfaced at the brief stage, he moved the event setup to the evening before. A discovery like that on the day itself would have cost him a morning and a lot of nerves.

He did not end up with a perfect event, and he would be the first to say so. What he gained was a calmer sense of where each decision sat in the project, and a habit of writing things down before asking anyone to price them.

You do not need a launch on the calendar to practise this. Pick any gathering you have been part of, a team away day or a small product demonstration, and write the one-page brief that should have existed before it. Notice which answers you would have had to chase.

The exercise is deliberately plain. A brief is a page of decisions, not a document designed to impress. If a question has no answer yet, write that down too, because an honest gap is far more useful to a producer than a confident guess.

Module 1 gives you a structure for this, and the later modules build on it. Cue sheets, rehearsals and venue plans all draw on what the brief says. Ravi found that the earlier the page was written, the less he had to rework later.