Develop · Build
How it came together.
- 01
Checking the vision against what the tooling does
The useful contribution to someone else's idea is finding where it breaks. Vendors are strong on individual phases and weak at the seams: the handoffs between capture, render, display and customisation are manual, and the tooling behind them assumes a headset or a desktop, so a room-scale LED wall falls through every gap. Naming that early costs a paragraph; discovering it mid-build costs the schedule.
3D & Spatial - 02
Arguing it in sales terms, not specification terms
A developer does not buy a refresh rate. The case that landed was behavioural: projection forces the lights down, puts visitors in a safe zone to avoid casting shadows, and leaves them watching rather than exploring, which is the opposite of the conditions under which someone commits to a purchase. Screens keep the room lit and social.
Marketing & BD - 03
Saying which parts are not solved yet
The straightforward way to win a client meeting is to let the demo imply the whole thing already works. The research named the gaps plainly instead, because a client who commits on an overstatement finds out later, and by then the credibility is spent.
Research