Services
Events & Experiences
Enterprise & Training
Gaming & Education
A practical planning guide for anyone about to approach a technology partner. The ten questions that decide the outcome, the technical and commercial details most briefs leave out, and a complete brief template you can copy and use.
.png)
.png)
This article is the document I wish every client had before the first meeting. It is not a sales tool. A better brief makes our job easier, but it also makes you a harder client to overcharge, because a clear brief is the thing that lets you compare proposals honestly.
Work through the ten questions below and you will have a brief stronger than most of what reaches us. Section 6 is a complete template you can copy straight into a document.
QUICK ANSWER: Unclear requirements at the start are the single most common cause of scope creep, and scope creep is expensive. Industry research puts scope creep at 52% of projects with an average budget overrun of 27%, and complex projects fail to deliver their intended benefits far more often than simple ones. The brief is where that risk is either contained or created.
Those numbers are worth sitting with. Roughly half of projects experience scope creep, and when it happens it adds something like a quarter to the budget. The most frequently cited cause is not indecision later — it is vague or incomplete requirements at the beginning, which leaves a space that everyone involved fills with their own interpretation.
Immersive projects are unusually exposed to this because the deliverable is subjective. "Impressive," "premium," "world-class" and "wow factor" appear in almost every brief we receive and mean nothing that can be priced, designed against, or verified on handover. Two suppliers reading the same brief will quote entirely different things, and you will have no fair basis on which to compare them.
The remedy is not a longer brief. It is a more specific one. A good brief can be three pages.
QUICK ANSWER: Answer these ten before approaching anyone: who is the audience; what should they understand; what should they feel; what should they do; what should they remember; how many visitors per hour; how long should each interaction last; is it temporary or permanent; how will content be updated; and what does success look like.
If you can answer all ten in a paragraph each, you have a brief. If you cannot answer questions 1, 5 and 10, the project is not ready to be designed yet — and that is a useful thing to discover now rather than three months in.
QUICK ANSWER: The difference between a weak brief and a strong one is specificity. Weak answers describe a mood; strong answers describe a measurable outcome, a named audience, and a number.
1. Who is the audience? Weak: "The general public." Strong: "Primarily Emirati and expatriate families with children aged 6–14, visiting at weekends in groups of four to six, plus weekday school groups of 25–30 and occasional VIP delegations requiring a separate fast-track route." Audience segments move through space differently and need different pacing. Naming them changes the design.
2. What should they understand? Weak: "Our sustainability story." Strong: "That our water desalination process uses 40% less energy than the regional average, and why that matters for the country's 2050 targets. One idea, explained so a fourteen-year-old could repeat it." If you cannot reduce it to one or two sentences, the experience will try to say everything and land nothing.
3. What should they feel? Weak: "Wowed." Strong: "Curious at entry, slightly awed at the central moment, and quietly proud by the exit." Emotion is designable, but only when it is specific enough to sequence.
4. What should they do? Weak: "Interact with the technology." Strong: "Physically choose between three energy scenarios and see the consequence of their choice play out at scale." This answer alone determines whether you need sensors, touch surfaces, or nothing at all.
5. What should they remember? Weak: "Our brand." Strong: "One number, and the feeling of having personally caused something large to happen." Design for one memory. Visitors will not retain five.
6. How many visitors per hour? Weak: "As many as possible." Strong: "Peak 300 per hour on weekends, 80 per hour midweek, with school groups arriving in blocks of 30." This is the number that most often forces a redesign when it arrives late. Give it early.
7. How long should each interaction last? Weak: "Not too long." Strong: "Eight minutes for the main experience, with two optional deep-dive stations of 90 seconds each." Duration multiplied by capacity is throughput, and throughput determines the whole layout.
8. Temporary or permanent? Weak: "Permanent, but we might move it." Strong: "Permanent, operating daily for a minimum of five years, in a location that will not change." Half-answers here are expensive. Event-grade and year-round-grade are different products at different prices.
9. How will content be updated? Weak: "We'll deal with that later." Strong: "Quarterly content refreshes managed by our in-house marketing team, plus annual data updates, without requiring the integrator to return on site." This answer alone determines whether a content management system is built.
10. What does success look like? Weak: "Positive feedback." Strong: "Average dwell of six minutes or more, 60% of visitors able to recall the core message at 30 days, and 200 qualified enquiries in the first quarter." Agree the target and the failure threshold in writing before anyone designs anything.
QUICK ANSWER: Space, power, structure, flow, accessibility, ambient light and connectivity determine what is physically possible. Discovering a constraint after design is complete is the most common cause of avoidable cost, so put whatever you know into the brief, even if it is incomplete.
You are not expected to answer these as an engineer. You are expected to flag what you know and what you do not.
Available space. Floor dimensions, and critically, ceiling height. For 360-degree immersive setups a minimum around 3 metres is generally advisable, and lower ceilings meaningfully constrain what can be done. Include the plan if you have it.
Power. Available supply, phase, and whether an upgrade is possible. Power limitations are discovered late far too often and can reshape a whole design.
Structural requirements. Anything heavy or mounted at height needs structural assessment — as a general rule of thumb, elements over roughly 25 kg or mounted above about 2 metres will need checking. If the building has load limits or you are in a heritage or leased space, say so in the brief
Audience flow. Entry and exit points, where queues will form, and whether the route is one-way. If the space has fixed architecture you cannot change, that is a design input, not a detail.
Accessibility. Wheelchair access is a regulatory requirement, not a nice-to-have, and sensory accessibility increasingly matters too. Raise it in the brief so it is designed in rather than retrofitted.
Ambient light. Projection and ambient light are in direct conflict. If the space has windows or skylights, say so — it may determine whether you use projection or LED, which is one of the largest cost decisions in the project.
Connectivity. Network availability, whether the system must reach the internet, and any IT or security policy that applies. Government and semi-government projects frequently carry requirements that need designing around from the start.
Maintenance access. Rarely considered at brief stage and genuinely important: equipment mounted where it cannot be reached quickly becomes a recurring operational cost. A reasonable standard is that serviceable components should be reachable within about fifteen minutes without heavy equipment.
QUICK ANSWER: Content ownership, data capture, ongoing maintenance and operating manpower decide what the experience costs to run, not just to build. Settle them in the brief and the proposals you receive will be comparable.
Content ownership. Who owns the content when the project ends you, the integrator, or a third party? Who holds the source files? This becomes urgent the first time you want to change something, and by then your negotiating position is weaker.
Data capture. Will the experience collect visitor data? If so, what, how is consent handled, where is it stored, and who is accountable for it? This has design consequences and compliance consequences, and it is far easier to build in than bolt on.
Maintenance and support. Who maintains the system after handover, what response time do you need, and what spares are held? For a permanent installation, budget this from the start rather than discovering it in year two.
Operating manpower. Does the experience need staff to run it? How many, with what training, and are they yours or provided? An experience that needs three hosts per shift has a very different operating cost from one that runs itself.
Budget. Include a range. Clients often withhold budget believing it strengthens their position; in practice it produces proposals that cannot be compared and wastes everyone's time. A range lets a good partner tell you honestly what is achievable within it, and what is not.
Timeline. The opening date, and whether it is fixed. If it is tied to an event, a royal visit or a public announcement, say so immovable deadlines change sequencing, procurement and cost.
QUICK ANSWER: Copy the structure below into a document and fill it in. Three to five pages is enough. A brief this complete will get you materially better and more comparable proposals.
PROJECT BRIEF - [PROJECT NAME]
1. Overview Organisation, contact, one-paragraph description of what you want to create and why now.
2. Objective What this experience must achieve for the organisation. One or two sentences.
3. Audience Primary and secondary segments, group sizes, languages, any VIP or protocol requirements.
4. The Ten Questions A short paragraph against each: understand / feel / do / remember / visitors per hour / interaction duration / temporary or permanent / content updates / success definition.
5. Space and Site Location, floor area, ceiling height, existing architecture, ambient light conditions, plans attached if available. Note anything fixed or immovable.
6. Technical Context Power availability, structural constraints, network and IT policy, existing AV or building systems that must integrate, access and delivery constraints.
7. Accessibility Physical and sensory accessibility requirements.
8. Content Who provides content, who owns it on completion, expected update frequency, languages required.
9. Operations Operating hours, staffing model, maintenance expectations, data capture requirements.
10. Commercial Budget range, procurement process, decision-makers and approval stages.
11. Timeline Key dates, whether the opening date is fixed, and what it is tied to.
12. Success Measures Two to four measures with targets, and what would count as failure.
13. References Anything you have seen and liked or disliked with a note on why. Two or three examples are worth several paragraphs of description.
QUICK ANSWER: The common failures are leading with technology instead of outcome, withholding budget, omitting throughput, describing mood instead of objective, and involving the technology partner too late to influence anything.
Leading with a hardware wish list. A brief that opens with "we want a 12-metre LED wall and a hologram" has pre-decided the answer without establishing the question. It is also the fastest route to overspending, because it removes the partner's ability to propose something cheaper that works better.
Withholding the budget. This rarely produces a better price. It produces proposals at wildly different scales, none of which can be fairly compared, and a second round of work for everyone.
Omitting throughput. Visitors per hour arrives late in more briefs than any other critical number, and it is the one most likely to force a redesign.
Describing a mood instead of an objective. "Premium," "wow," "world-class" cannot be designed against or verified. Replace each with something observable.
Briefing too late. By far the most expensive mistake. If the architecture is finished, the ceiling heights are fixed and the power is allocated before the technology partner is involved, you have removed most of the options and will pay more for a worse result.
Not naming the decision-maker. Projects where approval authority is unclear accumulate changes from every direction. Name who signs off, at brief stage.
QUICK ANSWER: A capable partner should respond with questions before a proposal, conduct a site survey, challenge parts of the brief, and give you a breakdown by category rather than a single number. If you get a quotation with no questions asked, treat that as information.
Expect questions first. Any partner who can quote an immersive project without asking anything is quoting a room, not an outcome.
Expect a site survey. Power, structure, light and access need to be seen. A proposal built entirely from a floor plan carries risk that will surface later as variation.
Expect to be challenged. If everything in your brief is accepted without comment, you are working with an order-taker. Useful partners will tell you when an ambition does not fit a budget, when a requested technology is the wrong choice, and when a smaller intervention would achieve more.
Expect a category breakdown. Hardware, content, software, infrastructure, engineering, installation, commissioning, support. A single figure tells you nothing and cannot be compared against another supplier's single figure.
Expect a definition of success in the proposal. It should reflect back the measures you set out, with the partner's view of whether they are realistic.
QUICK ANSWER: We would rather help shape a brief than receive a finished one, because the decisions that matter most are made before the specification is written. Across more than 800 delivered projects, early involvement is the clearest predictor of a project that lands on budget and performs afterwards.
Some of the most useful work we do happens before there is a project to sell. A client describes an ambition, we walk the space, and the conversation establishes what is actually achievable, sometimes larger than they imagined, frequently smaller and sharper.
We will review a brief before you issue it. Including briefs going out to competitive tender where we may not win. A better brief produces better proposals from everyone, and we would rather compete on a clear one.
We survey before we quote. Power, structure, ceiling height, light and access get verified rather than assumed, because assumptions become variations.
We tell you when the answer is less. If the objective can be met with a smaller intervention, that is the recommendation, even when it reduces the value of the project to us. It is the reason clients come back.
We price by category. So you can see where the money goes, challenge it, and compare us honestly against anyone else.
The experience behind the advice. More than 800 delivered projects since 2018 across the UAE, Saudi Arabia, Oman and the wider GCC, for clients including DEWA, the Government of Dubai, Atlantis The Royal, Emaar, Dubai Future Foundation, PwC and Louis Vuitton, which means the guidance above comes from what these projects actually required, not from theory.
Author: Fahad Javaid is Founder and CEO of Power Interactive, a Dubai-based immersive technology studio. This article is written from more than 800 experiential technology projects designed, engineered and delivered across the UAE, Saudi Arabia, Oman and the wider GCC since 2018.
At minimum: the objective, the audience, what visitors should understand, feel, do and remember, visitors per hour, interaction duration, whether the installation is temporary or permanent, how content will be updated, and how success will be measured. Add space and technical context, accessibility requirements, content ownership, operating model, budget range and timeline. Three to five pages is usually enough.
Shorter than most people assume. Three to five pages of specific answers beats twenty pages of description. Specificity matters far more than length one precise sentence about throughput is worth several paragraphs about ambition.
Yes, as a range. Withholding budget tends to produce proposals at incomparable scales and an extra round of revisions. Sharing a range lets a partner tell you honestly what is achievable within it and what is not, which is the more useful conversation.
As early as possible, ideally while the space, architecture and objectives are still open to influence. Briefing after ceiling heights, power allocation and layout are fixed removes most of the options and usually increases cost for a worse outcome.
That is genuinely useful information. If you cannot answer who the audience is, what they should remember, or what success looks like, the project is not ready to be designed and finding that out at brief stage costs nothing, whereas finding it out mid-build is expensive. A good partner will help you work through the gaps.
Whatever you know, flagged honestly. Floor dimensions, ceiling height, whether the space has windows, what power is available, and whether the building has any structural or heritage constraints. You are not expected to specify systems, you are expected to describe the space and say what you are unsure about.
Insist every supplier breaks their price down across the same categories: hardware, content, software, AV infrastructure, engineering, installation, commissioning and ongoing support. Differences usually sit in the less visible categories, and a single headline figure hides exactly the things you need to compare.
It reduces the risk of cost increases, which is usually where budgets are lost. Industry research attributes scope creep to around half of projects with average overruns near a quarter of budget, and unclear initial requirements are the most cited cause. A specific brief is the cheapest risk control available on a project.
We design and build immersive experiences that engage, excite and transform audience interaction combining art, engineering, and next-gen technology to bring brands and spaces to life.
