Most spatial computing products fail not because the technology is wrong but because the design process never surfaced what users actually need in an immersive context. Winston Francois embeds product design and research operators directly inside your team to close the gap between what your engineers build and what your users will actually adopt. We have done this for companies shipping hardware, software, and platform layers in spatial computing.
The Problem
Immersive UX Has No Established Playbook – Your Team Is Guessing
Spatial computing interaction design does not follow the rules of mobile or desktop. When you apply flat-screen UX conventions to AR/VR, users get motion sickness, disorientation, or simply walk away. Most product teams know something is wrong but cannot diagnose whether the problem is the interaction model, the onboarding flow, or the content itself. Without a structured research process, you burn engineering cycles on features that test well internally and fail in the hands of real users wearing your headset for the first time.
Enterprise Sales Cycles Stall Because Buyers Cannot Evaluate the Product Without Guidance
AR/VR enterprise deals require buyers to imagine a workflow transformation they have never experienced. If your product design does not carry prospects through a scripted, high-confidence evaluation path, your sales team ends up doing product education that should be handled by the product itself. Deals that should close in 60 days stretch to six months or collapse entirely. A weak product design process is costing you pipeline velocity, not just NPS.
Fragmented Research Is Producing Contradictory Signal
Many AR/VR companies run user interviews, beta programs, and analytics in parallel but never synthesize them into a coherent design direction. One team hears users want more freedom of movement; the analytics show users quit when given unstructured mode. Without a research process that integrates qualitative and quantitative signal at the pace your roadmap moves, you are making design decisions on whichever dataset the loudest voice in the room happens to prefer.
Your Roadmap Is Driven by Engineering Constraints, Not User Priorities
In spatial computing startups, the roadmap often defaults to whatever the platform SDK enables next or whatever the founding team finds interesting to build. Research becomes a post-hoc validation exercise rather than an input to prioritization. The result is a product with impressive demos that struggles to generate the repetitive daily use your retention metrics require. Without an embedded design and research function that has standing in roadmap planning, user evidence arrives too late to change direction.
How We Help
The first thing we do is a structured assessment of your current design and research operation. That means reviewing your existing user research artifacts, sitting in on roadmap planning, watching session recordings if they exist, and interviewing your product and engineering leads about where decisions have stalled or reversed.
From the assessment we build a design and research strategy specific to your product stage and target user. If you are pre-launch, the strategy focuses on discovery research and prototype validation. If you are post-launch, it focuses on retention-driving design changes and the research cadence needed to keep pace with your release cycle.
Execution is where Winston Francois works differently from an agency. We embed inside your team. Our operators attend your sprint planning, your design reviews, and your stakeholder presentations.
On the research side, we run the full stack: contextual inquiry with users in the field wearing your device, unmoderated usability testing using remote AR/VR simulation where hardware access is a constraint, and quantitative analysis of the behavioral telemetry your platform already captures.
Measurement is built into the engagement from the start. We define the design quality indicators and behavioral metrics that will tell us whether the design changes we are making are working. Typical indicators include task completion rates in key workflows, session depth, return rate after initial device exposure, and reduction in support tickets tied to navigation or onboarding.
For growth marketing context, our design and research work connects directly to your acquisition and retention metrics. A product that users can evaluate, adopt, and use independently in the first 30 days converts trials to paid and reduces the CAC that your <a href='/services/marketing/'>marketing</a> programs have to absorb.
What we deliver
- Design and Research Audit – current state assessment with gap analysis and prioritized action plan
- User Research Program – contextual inquiry, usability testing, and behavioral analytics synthesis on a quarterly cadence
- Interaction Design Sprints – two-week cycles producing tested interaction patterns for priority workflows
- Research Repository – searchable archive of user insights tagged by persona, workflow, and design question
- Roadmap Influence Reports – monthly synthesis of research findings formatted for engineering and executive planning sessions
- Enterprise Buyer Research – evaluation path design and buyer journey mapping for enterprise AR/VR sales cycles
In AR/VR, a design problem that surfaces in user research at week four costs one sprint to fix. The same problem discovered after launch costs six months of support load and a retention curve that does not recover.
Our Methodology
Winston Francois runs product design and research engagements in 90-day sprints. The first 30 days are an audit and strategy phase: we assess your existing research, map your current design decision process, identify the three or four highest-leverage design problems, and align with your product and engineering leads on what a successful engagement looks like. You end the first month with a prioritized design and research agenda, not a project plan that stretches to the horizon.
Days 31 through 60 are the execution phase. We run the first research cycle, produce interaction design recommendations for the priority workflows we identified in the audit, and begin embedding in your sprint process. Findings from user sessions go directly into your roadmap planning rather than sitting in a research archive that nobody reads. By the end of this phase, your team has seen the embedded model in practice and has an opinion on how to adjust it.
Days 61 through 90 close the first sprint with a measurement review. We compare the behavioral metrics from before and after the design changes, identify what worked and what needs another iteration, and produce a strategy for the next 90-day cycle. What makes this different from traditional consulting is that we are not delivering a report and walking out the door – we are accountable to the same metrics your product team is accountable to, and the next engagement is scoped based on what we learned in the first one. The <a href='/services/measurement/'>measurement</a> framework stays in place after we roll off so your team can continue tracking the indicators we established together.
How We Work
The first 30 days of an engagement are structured around access and alignment. We need to talk to your users, your design and engineering leads, and your go-to-market team. We set up the research infrastructure, run the initial audit, and deliver the strategy document that governs the rest of the engagement. By day 30 your team knows exactly what we are working on and why.
From day 31 through 60 we are running research and producing design output at sprint cadence. We attend your weekly standups, join your design reviews, and produce a bi-weekly research synthesis that feeds directly into your planning process. On the client side, you need a product lead who can make decisions based on research findings and an engineering counterpart who can pull design work into the sprint. We are not effective if research output sits in a queue waiting for a quarterly review.
From day 61 through 90 we run the first measurement review and scope the next cycle. Engagements typically run three to four 90-day cycles. Earlier-stage companies often run two cycles heavily weighted toward discovery research and initial design system work. Later-stage companies often run two or three cycles focused on retention-driving design changes and ongoing research program management.
The Winston Francois team on a standard AR/VR engagement is a lead product design operator who owns the research and design work, a research coordinator who manages logistics and synthesis, and a measurement analyst who owns the behavioral metrics reporting. Larger engagements may add a second designer for parallel sprint work.
- Faster roadmap decisions backed by structured user evidence rather than internal debate
- Improved trial-to-paid conversion driven by a first-use experience that users can navigate without support
- Reduced support load tied to navigation and onboarding as design changes address root cause issues
If your ar / vr / metaverse company needs product design & research leadership, we should talk.
Expand your marketing team output with our experts
Let us take a custom approach to your growth goals by assembling and leading the best-in-class marketing team to support your next stage.
Frequently asked questions
How much does a Product Design & Research engagement cost for AR / VR / Metaverse companies?
A standard Winston Francois product design and research engagement runs between $18,000 and $38,000 per month depending on team size, research volume, and whether the scope includes enterprise buyer research in addition to end-user work. For context, a senior product designer with research skills in the AR/VR market commands $180,000 to $240,000 in base salary plus equity, and takes three to six months to hire and onboard.
How long before we see results from a Product Design & Research engagement?
The first measurable design changes typically ship within 45 to 60 days of engagement start, after the audit phase and the first research cycle produce actionable findings. Behavioral metric movement – task completion rates, return rates, session depth – is visible in your analytics within 30 days of those changes shipping.
How does the Product Design & Research team integrate with our existing staff?
We embed directly into your existing sprint and planning cadence. That means attending your standups, joining your design reviews, and participating in your roadmap planning sessions – not running a parallel process that you have to translate back into your workflow.
What makes Winston Francois different from a traditional Product Design & Research agency?
Traditional agencies run research, produce deliverables, and move on. The person who interviewed your users is rarely the same person who attends your roadmap meeting, and the research findings often arrive too late to change the decisions that matter.
How do you measure ROI from Product Design & Research for AR / VR / Metaverse companies?
We define measurement baselines in the first 30 days before any design changes ship. The primary indicators we track for AR/VR products are task completion rate in priority workflows, return rate after initial device exposure (a leading indicator of adoption), session depth, and reduction in support tickets tied to navigation and onboarding.
What type of AR / VR / Metaverse company is the right fit for this engagement?
Winston Francois works best with companies that have a working product – either in private beta, public launch, or enterprise pilot stage – and a design or product team of at least three people. We are not a fit for pre-prototype stage or for companies that need a founding designer to build the product from scratch.
