The Vendor Vetting Ledger: Seven Questions That Separate Real Immersive Studios From Expensive Demos

Every immersive portfolio looks the same: moody renders, a logo wall, a thirty-second sizzle cut. None of it tells you whether the studio can ship on your timeline, inside your budget, without handing you an unmaintainable artifact in month nine. The difference between a capable partner and an expensive disappointment is almost always visible in how they answer a handful of unglamorous questions.

Question One: Who Owns the Source Files When This Ends?

The single most common post-engagement failure is a brand sitting on a compiled application it cannot modify. Insist on a work-for-hire IP assignment covering all source assets, project files, and documentation — not merely the final build. Red flag: any answer involving 'our proprietary pipeline' without a licensing schedule attached.

Question Two: What Happens in Month Fourteen?

Headset OS updates, engine version deprecations, and SDK breaking changes will arrive whether you plan for them or not. Ask for the studio's standard post-launch support model, in writing, with rates. Expect a maintenance retainer in the range of 10 to 18 percent of the original build cost annually. A studio that quotes zero ongoing support is either planning to disappear or planning to charge you emergency rates later.

Question Three: Can You Show Me a Project That Failed, and What It Cost?

This is the six-figure question. Studios that have only successes either lack experience or lack candor — and both are disqualifying. A strong answer names a real project, a real overrun, and a specific process change that resulted. The willingness to discuss failure transparently is the cheapest due diligence available; a single avoided scope-collapse pays for the entire vetting exercise.

Question Four: What Is Your Actual Production Team, by Name?

Many agencies sell senior expertise and staff junior execution. Request the named team, their role, and their committed allocation. Bench-and-bait staffing — a principal on the pitch, a rotating cast on delivery — is the industry's quietest margin play. Your contract should name key personnel with substitution approval rights.

Question Five: How Do You Validate Before You Build?

Realistic studios budget for a paid discovery or prototype phase — typically $25,000 to $75,000 — before committing to full production. A studio that will happily quote a seven-figure build from a one-hour kickoff call is pricing your risk tolerance, not the work. Insist that discovery findings gate the production contract with a defined go/no-go checkpoint.

Question Six: What Are Your Hardware Assumptions, and Who Pays When They Change?

Device fleets, kiosk hardware, and headset logistics are where immersive budgets go to die quietly. A 50-unit deployment carries procurement, provisioning, storage, and replacement costs that some studios quote and others discover. Require a hardware total-cost-of-ownership appendix covering a three-year horizon, including device replacement cycles.

Question Seven: What Does 'Done' Mean, Contractually?

Acceptance criteria for immersive work are notoriously mushy. Define them: target frame rates on specified hardware, load times, accessibility conformance, device test matrix, and a punch-list resolution process with deadlines. Tie final payment milestones to these criteria, not to calendar dates.

Benchmarks to Anchor Your Negotiation

For orientation purposes in the current US market: a proof-of-concept prototype typically lands between $40,000 and $120,000; a production-grade single-platform experience runs $150,000 to $500,000; multi-platform or multi-site enterprise deployments routinely exceed $750,000 before hardware. Quotes dramatically below these ranges usually indicate deferred costs rather than efficiency.

A Closing Word on Process

The studios worth hiring will welcome this line of questioning — the rigorous ones have answered it on every serious engagement they have won. If a prospective partner bristles at the vetting ledger, treat that as data. In immersive work, as in most procurement, the cheapest contract is rarely the one with the lowest number on page one.