Questions to ask your agency before commissioning an immersive website
An attractive demonstration is not enough to define an immersive website project. Before commissioning the work, clarify what the experience should explain, which media it needs and how people will use it. These questions help you compare concrete proposals and prepare for delivery as well as the changes that follow.

Before commissioning an immersive website, ask your agency to explain the proposed journey, required content and conditions in which the experience will work. An attractive demonstration shows an intention; it does not always establish what will be delivered, how the site will adapt to a phone or what your team can edit. These points need to become concrete parts of the conversation before the scope is agreed.
You do not need to master the tools to ask useful questions. Your role is to connect the experience with your offer, audience and available resources. The agency’s role is to make its choices understandable. The following questions help structure that discussion and obtain a proposal whose boundaries can be examined before you commit. They also provide a record of what has been decided and what still needs clarification.
Establish what immersion should help people understand
Ask: “Which information becomes clearer through the proposed experience?” The answer should name a subject: the organisation of a place, how an object works, stages of a method or the relationship between offers. If the discussion concerns only spectacular effects, return to the content. Animation can support a business presentation, but its value depends on what it contributes to a visit and to a prospective client’s understanding.
Continue with a real situation: “Does someone looking for this service need to cross the entire sequence?” This reveals the role of direct routes. Immersion can accompany discovery without becoming a compulsory gateway for every need. Ask where services, practical details and contacts are located, including for someone arriving directly on an internal page. A useful experience needs to accommodate those visits as well as the guided introduction shown in a demonstration.
Define exactly how the sequence behaves
“What happens when I scroll, stop and move backwards?” This is more useful than simply requesting a video effect. Establish what the gesture controls, when each scene begins and how the next one appears. You can then distinguish a video that starts playing from a presentation whose progress follows the visitor’s scrolling. Similar-looking references may involve very different interactions, content preparation and conditions for using the finished page.
Request a short account of the journey, naming scenes and their purposes. A list of five pictures does not necessarily explain intermediate stages or continuity. If the project involves an object coming apart, confirm what will actually be produced and supplied. Do not infer from one reference image that the complete movement already exists or can be obtained without additional work on the media needed to create the proposed sequence.
Inventory the media required
Ask directly: “Which files do we provide, and which are included in the proposal?” Distinguish photography, video, sequence images and any specific visual elements. Identify their status: available, needing adaptation or requiring production. The list reveals whether the demonstration uses actual business content or references that need replacement. It also helps the team identify missing material before design decisions depend on assets that nobody has yet arranged to produce.
Ask how framing will be prepared for different screens. An image suited to a large format may not retain its subject in a narrow composition. Who approves quality and factual accuracy? Who checks the conditions for using each asset? Responsibilities should be clear, particularly where several suppliers or teams contribute content before integration. Discuss the handover between those contributors and the people responsible for building the final website pages.
Examine phone use during design
“Can you show the journey with our content on a phone-sized screen?” This prevents mobile use becoming merely a promise of later adaptation. Examine headings, framing, buttons and the ability to reach another page. The presentation may differ from a large screen while retaining its subject, identity and necessary information. Ask the team to explain those choices rather than assume that every desktop movement must be reproduced unchanged.
Discuss less favourable conditions too: arriving before media finishes loading, interrupting a visit or returning from another page. What does the person see and what can they do? A useful answer describes expected behaviour instead of simply promising smoothness. Ask which devices and situations will be examined before delivery and how difficulties found during that review will be addressed. The agreed checks should correspond to the experience being commissioned.
Plan reading that does not depend on every effect
Ask for a usable presentation without motion. W3C reference.
Examine headings, pictures, explanations and links in that presentation. Stopping movement is insufficient if essential information becomes unreachable. Ask about keyboard navigation and readability too. You are establishing what the project includes and what will be checked. Avoid turning a general accessibility statement into an undefined guarantee or a claim whose scope nobody can explain. The discussion should lead to observable behaviours and agreed responsibilities within the proposed work.
Clarify what your team can change
“Can you show us how to replace a heading, a photograph and a project?” These changes do not always involve the same work. A practical demonstration distinguishes editable information, media requiring preparation and changes needing assistance. It also shows what happens with a longer heading or an image whose proportions differ from the initial example. These cases tell you more about routine management than simply seeing an administration screen.
Ask how the sequences connect. Does replacing one part require revising every transition? Does adding an activity change the overall organisation? Independence should be described through possible operations and explicit limits. It is not established solely by the presence of an editing area, particularly when an experience relies on media produced for one subject or one precise visual scenario. Agree what the team can do and what requires a separate assessment.
Make budget and timing comparable
Ask a scope question: “Which stages, content and checks are included?” Distinguish design, writing where planned, visual production, implementation, adaptations, languages and delivery. Proposals become comparable when deliverables are explicit. A total alone does not show whether media already exists, whether creating it is included or whether certain pages and variants require further work. Establish these differences before deciding that two proposals describe the same level of service.
Clarify timing dependencies. Which decisions are required from you, when, and what happens if content arrives later? Ask about the number and nature of revision exchanges and how changes of direction will be treated. These questions help prepare your own organisation without attributing a deadline or service to the agency that it has not confirmed. The schedule should reflect the responsibilities and decisions needed from both sides of the project.
Describe delivery and expected checks
“How will we know the website matches the approved project?” Ask for observable criteria: pages present, approved copy, working links, enquiry routes, sequence behaviour and presentations adapted to agreed formats. Criteria should extend beyond a visual impression. They provide a framework for identifying a necessary correction and distinguishing it from a new request arising after scope approval. That distinction supports a more precise discussion when the site is ready for review.
Clarify handover: access, content, media and working files where included in the agreement, alongside information needed for management. Who controls the domain name and accounts? How can another authorised person take over the agreed tasks? Answers should be concrete and suited to your organisation. Do not assume that a deliverable is included simply because it would be useful to have; establish what is provided and what remains outside the agreement.
Prepare the first changes after publication
Ask: “What happens if we change an offer or add a project after launch?” Use a likely example from your activity. The agency can explain the stages, required content and what would need assessment at that point. This helps distinguish correction, editorial update and a development that transforms the story or site structure. It also reveals how much of the original presentation depends on a particular set of images or information.
Discuss responsibility after delivery. Who receives a problem report? What support is actually included? Which interventions need a separate agreement? Avoid filling gaps with assumptions. A clear working relationship depends on arrangements both parties understand, including when the business changes content or decides to develop its communication in the following months. It is better to describe those boundaries explicitly than to discover different expectations when an update becomes urgent.
Use the answers to reach a decision
Collect answers in a short document. For each point, distinguish what is confirmed, what depends on your content and what remains open. If two proposals use the same terms, compare operations and deliverables rather than wording. “Immersive”, “bespoke” or “editable” do not by themselves describe an identical project across agencies. A practical comparison identifies what those terms mean for the pages, content and management tasks you are actually commissioning.
Choose according to fit, clarity of explanation and coherent scope. A visually ambitious proposal may require content you are not ready to produce. A more focused approach may better suit the planned launch. These questions make that decision explicit, without reducing the choice to the quantity of animation or the immediate impact of a demonstration. The project needs to work with your offer and resources as well as your visual ambitions.
To prepare a discussion with MV Design, bring your offer, available media and one journey you would like to make clearer. Use these questions to examine possibilities, production conditions and project stages. You will have a concrete starting point for defining an experience that suits your business and for understanding what needs to be agreed before the work begins.