Insights · guide
How to decide whether visionOS belongs in a client proposal
Drafted with Insight · edited by The WE ARE VR team
business

Use three gates before adding visionOS to a proposal: audience, budget and deployment.
What's the problem?
Apple Vision Pro can make a proposal feel current before anyone tests the fit.
That creates a familiar mistake. The platform becomes the idea, while the client’s actual need sits underneath it. A beautiful spatial prototype is still the wrong choice if guests cannot access it, the budget cannot support it, or the team cannot run it reliably.
Start by asking what people must do.
A small group of decision-makers might need to inspect a building model, review product options or understand a complex space. visionOS could suit that focused, high-detail experience.
A busy public activation has different needs. Guests may arrive in groups, wear glasses, have limited time and need help fitting the headset. If the experience depends on rapid turnover, every fitting and explanation affects the queue.
The platform is one line in the proposal. Its operating conditions fill the rest of the page.
What's the solution?
Run the proposal through three gates. If any gate fails, remove visionOS or price the work needed to fix the gap.
First, check the audience.
Ask who will use the experience, how many people need access and how long each session lasts. Also ask whether they are comfortable wearing a headset. A private property review for six executives has different demands from an exhibition stand serving walk-up visitors.
Second, check the full budget.
Do not price only the application. Include the headset, development hardware, protective cases, transport, testing time, cleaning supplies and a trained facilitator. Add a spare plan if the event depends on one device. Imported specialist hardware can also be difficult to replace quickly in Johannesburg.
Third, check deployment reality.
Confirm where the experience will run, who controls the devices and how updates will be handled. Test the room, lighting, network access, audio and guest flow. Decide what happens when tracking fails or an app refuses to launch. “Restart everything” is a recovery plan, although not a very impressive one.
Consider a Jozi architecture studio proposing an immersive apartment review. The audience is a small client team, sessions are scheduled, and detailed spatial inspection supports the decision. visionOS may pass all three gates.
Now move the same experience to a shopping-centre activation. There are walk-up guests, short sessions and pressure for steady throughput. A simpler headset fleet, mobile augmented reality or a large interactive display may fit better.
If visionOS passes, test the complete experience on one labelled device before updating every headset. This canary device catches software, tracking and account problems without risking the whole deployment.
What's next?
- Take one current proposal and write down the audience size, session length and required outcome.
- Add a separate deployment line covering hardware, facilitation, transport, testing, cleaning and recovery.
- Run the experience on one device in the real venue, then record clear pass conditions before expanding.
Share what you test with the Jozi XR community, or send us the proposal question blocking your next step.
The WE ARE VR team
