Sub-contracting smart glasses development: what agencies need to know before the first call

When to sub-contract vs build in-house

Building for Snap Spectacles requires Lens Studio, Spectacles SDK knowledge, hand tracking APIs, and regular access to the hardware for testing. Most integrated agencies, production companies, and experiential studios do not maintain this capability in-house because the work volume does not justify a full-time Spectacles developer on the payroll.

Sub-contracting is the right call when:

• The smart glasses component is one part of a larger campaign that the agency is leading
• The agency does not have a Lens Studio developer with Spectacles credits
• The build timeline is tight and there is no room for a team to learn the platform on the job
• The activation is event-based and the specialist studio needs to be on-site

Building in-house is worth exploring when the agency has an existing Lens Studio team with phone lens experience and a three-month runway to develop Spectacles fluency, or when the client brief calls for ongoing smart glasses work across multiple projects that would justify the training investment.

What to hand over

A sub-contracting engagement works cleanly when the handoff is clear from the start. What the specialist studio needs:

• The creative brief for the smart glasses component (not the full campaign deck, just the scope they are building)
• The desired user journey described in plain language (what the person wearing the glasses does, sees, and feels)
• Platform and hardware confirmation (Snap Spectacles, Meta Ray-Ban, or both)
• Event date and activation context (indoor/outdoor, how many devices, how many simultaneous users)
• A named point of contact at the agency who owns the relationship

What to keep

The client relationship stays with the agency. The specialist studio builds; the agency presents, manages feedback, and owns sign-off with the client. This is standard sub-contracting practice and it works the same way in smart glasses builds as it does in any other specialist discipline.

Creative direction stays with the agency. The specialist studio is fluent in what the platform can do, but the creative concept, the brand fit, and the campaign narrative are the agency's to own. A good specialist studio will flag when a creative direction is technically unachievable on the hardware and offer alternatives, but the direction itself comes from above.

Final sign-off on deliverables stays with the agency. The specialist studio delivers a working Lens; the agency validates it against the brief and approves before it goes to the client.

IP and NDA: what to clarify upfront

Most smart glasses builds involve 3D assets, custom scripts, and sometimes novel interaction patterns. Clarify ownership before development begins: who owns the Lens file, the 3D models, and the TypeScript scripts after delivery? For most brand commissions, IP transfers to the brand via the agency on final payment. Confirm this is reflected in the sub-contractor agreement.

On NDAs: the specialist studio will have access to the campaign concept before it is public. A standard NDA covering campaign creative and client identity for the duration of the project and a defined period after is normal practice. Most specialist studios expect this and have their own template if the agency does not.

On usage rights: if the Lens is published to Snapchat under a brand account, confirm who manages the Snap developer account credentials, who has publishing rights, and what happens to the Lens after the campaign window closes.

QA and hardware testing: who owns what

The specialist studio owns the technical QA: does the Lens run at the target frame rate, does hand tracking respond correctly, does the experience work on the number of devices the activation requires. This is not something the agency can delegate to the client or to an in-house QA team that has not used Spectacles before.

The agency owns the creative QA: does the Lens look and feel right, does it match the brand guidelines, does the user journey play out as briefed. This requires someone at the agency to put on the Spectacles and experience it. Remote review of screen recordings is not a substitute for hardware testing on the actual device.

On event day: how on-site support works

For event activations, on-site support from the specialist studio is strongly advisable for the first activation, especially if the agency team has not run a smart glasses activation before. On-site support covers:

• Hardware setup and device pairing before the event opens
• Testing in the live environment (lighting conditions, space dimensions, and crowd density all affect AR performance)
• Troubleshooting during the activation
• Reset procedures if a device needs to be rebooted between sessions

Clarify on-site support scope in the sub-contractor agreement: how many days, start and end time, what is included and what is extra. On-site support is typically a day rate on top of the build fee, not included by default.

If the agency is running the activation without specialist on-site support, require a handover session before the event where the agency team learns the hardware setup, the reset procedure, and the common failure modes. This session should include documentation the team can reference on the day.

What to ask in a first call with a specialist studio

Four questions that tell you whether the studio is the right fit:

• What have you shipped on Snap Spectacles specifically (not on Lens Studio generally, not on mobile AR)?
• What is your testing workflow on device?
• Can you be on-site for the activation?
• What does your handover documentation look like?

A studio that has shipped real Spectacles work will answer the first question with specific project names and what the build involved. A studio that answers with general Lens Studio experience and "we can figure out Spectacles" is not the right sub-contractor for a time-critical brand activation.

Frequently asked questions