Snap Specs lens development cost: what brands should budget

The short answer, then the useful one

In short: budget $8,000 to $20,000 for a dev-only Specs lens if your team already has the creative concept and just needs it built, and $25,000 to $60,000 if you want a studio to develop the concept and build it from scratch. Those two tiers cover almost every brand brief we see, and the rest of this guide explains what sits inside each number.

Context matters here. Snap Specs launched as a consumer product in June 2026 at $2,195 per unit, shipping from Fall 2026. For brands, that changes the distribution question over time, but right now most Specs activations are event-based: a fleet of devices at a launch, a booth, a festival, or a retail space. That means your budget has two halves that should never be quoted as one figure: the lens development (concept, software, testing) and the activation production (hardware, staffing, logistics). This guide covers the first half in detail and tells you where the second half starts.

One thing that catches brands out: Specs cannot simply run a normal Snapchat lens. It uses a different runtime, built around hand tracking and a head-worn display rather than a phone touchscreen, so even a brand with an existing Snapchat lens is looking at a genuine build for the glasses, not a port. Existing 3D assets and brand direction can carry over; the interaction and spatial design cannot.

The two budget tiers for a Specs lens

Tier 1: dev-only build ($8,000 to $20,000)

This tier is for two kinds of brief. First, agencies and brand teams that already have their own creative direction: a concept, brand assets, and approvals in place, who need a studio that can actually build for Specs hardware. Second, brands that already have an experience on another AR or MR headset, Meta Ray-Ban Display, Vision Pro, or a Quest build, and want it brought to Specs. In both cases the concept and 3D assets already exist; the work is spatial design, interaction design for hand tracking, Lens Studio development, and iterative testing on device, not originating the idea.

The range inside this tier is driven mostly by interaction complexity and how build-ready the supplied assets are: a single clear mechanic with usable 3D files sits near $8,000, while multi-step interactions, assets that need rework, or a cross-platform port with real interaction differences push toward $20,000. Every platform handles hand tracking, gaze, and display differently, so a port is a genuine rebuild of the interaction layer, not a reskin, even when the assets carry straight over. This is the right scope when someone else owns the campaign or the concept, and the brief is a Specs-capable build partner.

Tier 2: full concept-to-build ($25,000 to $60,000)

This is where the studio develops the idea, not just the code. Creative concept, bespoke 3D assets, spatial audio, and an interaction model designed for first-time wearers, then built and tested on hardware. It is the tier that produces a native Specs experience rather than a well-executed brief, and it is where six years of creative direction on AR campaigns actually shows up in the output.

Activation production, device fleet planning, charging rotation, hygiene between users, and staff training so the team on the floor can onboard a guest in under a minute, is scoped alongside the build rather than bolted on after. The production figures here are consistent with what we detail in wearable AR at live events: a spatial guide or simple game sits at the lower end of the range, a spatial reveal with high-fidelity bespoke content sits at the top. Hardware hire, on-site staff, and venue logistics are additional and depend on unit count and event duration.

What pushes the number up

• Interaction complexity. A lens the wearer looks at costs less than a lens the wearer uses. Hand-tracked interactions, multi-step mechanics, and physics all add design and testing time, because every gesture has to work for someone wearing the glasses for the first time.
• Original 3D assets. Asset production is usually the largest single line item. Photorealistic product models, characters, and environment content built from scratch can double a budget. Supplied brand assets in usable formats bring it straight back down.
• Connected and multiplayer features. Shared experiences, where multiple wearers see and interact with the same synchronised content, add networking, session management, and a much heavier testing matrix. Expect the top of the activation range or above.
• Location-anchored content. Experiences locked to a specific physical place require scanning and mapping the venue, and re-testing on site. Powerful for launches and installations, but it adds a site visit and a build dependency on the venue.
• AI features. Voice-driven interaction, live data, and generative content add API integration, prompt design, and latency work. We have shipped this on Spectacles hardware and it is worth the cost when the concept needs it, and padding when it does not.

What brings the number down

Three things reliably reduce a quote. First, existing assets: product models, brand characters, or architectural files in workable formats remove the most expensive part of production. Second, a single focused mechanic: the best Specs experiences do one thing memorably, and a tight concept is cheaper to build and better to use. Third, a second activation: brands that have run one Specs project find the next one faster and cheaper, because the asset pipeline, the operational playbook, and the approval path already exist.

The clearest cost-control lever, though, is the brief itself. A brief that states the audience, the venue, the session length, and the one moment that matters lets a studio scope precisely instead of quoting defensively. We wrote a full preparation guide in how to brief a smart glasses developer.

Timeline and cost move together

A typical Specs lens takes 6 to 10 weeks from brief to tested experience, and a full activation 8 to 12 weeks including operations planning. The phase-by-phase breakdown is in our Snap Spectacles project timeline guide. The budget implication is simple: compressed timelines cost more. Hardware testing cannot be skipped on a head-worn device, so a shorter calendar means parallel workstreams and more people, not fewer steps. If your event date is fixed, brief early; the cheapest week of a Specs project is the one before it starts.

What this looks like in practice

Budget guidance is only useful if the studio quoting it has shipped on the hardware. Our proof: Noodle, a spatial AI workbench for Snap Spectacles that won the Snap category at MIT Reality Hack 2026, built hands-free interaction, voice input, and generative AI into a single lens. And Ice Fishing, a casual spatial game that taught us more about first-time-wearer onboarding than any spec sheet, using a phone as a physical controller for a lens experience. Both were built in Lens Studio on the Spectacles developer platform, and both inform how we scope every quote above.

The wider smart glasses work, including formats and platform strategy beyond Snap, lives on our wearables page, and you can try the studio's browser-based AR work directly at ar.rbkavin.studio. For how Specs pricing sits against WebAR, social lenses, and installations, see the full AR activation cost guide.

Frequently asked questions