← portal
Confidential · Directional
Use ← → or scroll · N = notes
KLICKby Lucyd
See it. Say it. Saved.

Governed, AI-agnostic capture-and-act on the safety eyewear workers already wear.

Vision DeckDirectional · MNPI-safeNASDAQ: LUCY
01 / KLICK

The Category Is Real, and the Window Is Now

  • Smart glasses are no longer a concept: the market grows from ~$0.9B (2024) to ~$4.1B (2030), a ~29% CAGR.
  • AI glasses shipped ~8.7M units in 2025 — and one player (Meta) owns ~85% of that volume (Omdia).
  • The industrial segment already holds the largest revenue share (~27%+ of its tracked smart-glasses universe in 2025, per Grand View — a separate dataset from the headline figure above).
  • Translation: the consumer race is crowded and concentrated; the governed-enterprise lane is contested but wide open to a differentiated entrant.
  • KLICK is Lucyd's entry into that lane — governed multimodal capture, built on hardware we already ship, that works free-and-open for consumers and fully IT-controlled for the enterprise.
Lead with category momentum, then immediately narrow to where we can actually win — industrial, not consumer scale.
02 / KLICK

The Problem: Ungoverned Capture Scares the Enterprise

  • The glasses winning consumer share are built around always-on capture with no controls — no IT in the loop, no policy, no audit.
  • In regulated and security-conscious workplaces, ungoverned capture is a liability, not a feature — regardless of whether it's photo or video.
  • Legal frameworks restrict capture itself — wearable monitoring creates exposure regardless of who's wearing it.
  • IT and security teams default to "no" on any camera they can't see, govern, and audit.
  • Result: the workers most likely to benefit are the workers most likely to be blocked.
The incumbent's biggest gap isn't that they shoot video — it's that capture is ungoverned. That gap is our opening: governed capture, IT-controlled.
03 / KLICK

KLICK's Position: Governed Multimodal Capture, Two Ways

  • KLICK captures both photos and short, governed video clips — voice-triggered, hands-free. The difference isn't what it captures; it's who controls the capture.
  • It rides on our existing ANSI Z87.1 safety-eyewear platform — the glasses workers are already mandated to wear.
  • Say "KLICK" → photo or short clip → phone → cloud → available on every device. Hands-free, frictionless.
  • It works two ways from one device: open — free and uncontrolled for any consumer or prosumer who owns it — or fully IT-controlled for the enterprise. (Detailed on the next slide.)
  • Positioning: "the camera glasses your security team approves." Not because it can't capture video — because IT decides what, when, and where it captures.
  • We win the governed middle — construction, utilities, field service, insurance, logistics, large industrials.
The pivot here: the moat is GOVERNANCE, not "no video." Same device serves consumer upside and the enterprise sell — capture is full and free in open mode, IT-controlled in enterprise mode.
04 / KLICK

Dual-Mode: One Device, Open or Controlled

  • Governance isn't always-on — it's a toggleable enterprise tier layered on the same device. The mode is set when the device is provisioned.
Open mode Controlled / Enterprise mode
Who owns it The consumer / prosumer owns the device and the data IT-governed, org-owned
AI Bring your own AI keys and data IT-sanctioned model + allowed skills
Capture Full, free, uncontrolled Policy-driven: what / when / where, photo-vs-clip enabled by IT
Audit None Capture audit logs (adoption, not content)
Data Yours Zero-data-retention options, retention / redaction
IT in the loop No Yes — enrollment, identity, provisioning
  • Open mode captures the consumer / long-tail upside no enterprise-only player pursues.
  • Controlled mode is the margin engine — the governed sell that re-rates the business.
  • One device, one SDK, governance layered on for enterprise: we don't choose between the consumer market and the enterprise market — we serve both.
This is the core architecture decision. Don't position governance as a constraint — it's an optional tier that unlocks the enterprise sell without sacrificing the consumer upside. Keep directional: no MDM/endpoint specifics here, those live in the partner/integrator scope.
05 / KLICK

Capture → Ask → Act: The Hands-Free Agent Loop

  • KLICK is not just a camera — it's a hands-free capture-and-act terminal on safety eyewear.
  • Two voice triggers, both within our existing wake-word/command budget:
    • "KLICK" → capture a photo or short clip (governed multimodal capture, shipping first).
    • "Lucy, …" (or a temple tap) → dictate a prompt; the answer is spoken back through the open-ear speakers.
  • A third step closes the loop: "Lucy, email this to the foreman" → an agent skill fires the action (email, log to inspection report, create a ticket, post to chat).
  • Dumb glasses, off-board intelligence — the AI runs on the phone/cloud, not the frame. The glasses are an efficient sensor + audio shell: capture cheaply, hand off, drop to near-sleep while the model thinks, then speak the answer back.
  • Why this fits Lucyd: we already make audio eyewear. "Speak the answer back" is native — the camera is just a new input into the same audio + wake-word + SDK platform.
  • Vertical example — field inspector: "KLICK. Lucy, does this corrosion exceed spec? Log it to the report and flag for review." Hands stay on the work; the glasses see, reason, and act.
This is the elevation from "voice-triggered camera" to "multimodal agent terminal for the frontline." The power efficiency point matters — we don't burn battery making the glasses compute; we hand off, sleep, and answer in audio. Photo and short clips fit the v1 envelope; capture ships on the hardware timeline, and the ask/act layer is a software fast-follow.
06 / KLICK

AI-Agnostic & Governed: Bring Your Own Model

  • KLICK is AI-agnostic by design — route each request to whatever model the user or enterprise already pays for: ChatGPT, Claude, Gemini, or a Lucyd default.
  • Enterprise-safe: capture + prompt go to their sanctioned endpoint under their governance. IT controls which model, which data, and which skills are allowed — plus redaction and retention.
  • This is the inverse of consumer-AI lock-in. The giants want you on their model, their cloud, their terms. We hand control back to the customer.
  • Consumer-safe too: use an AI subscription you already have — no new-subscription friction.
  • The governance moat extends to the AI layer: it's no longer just admin controls and audit logs, it now covers models, endpoints, and the skills/workflows themselves — each integration becomes switching cost.
  • Ties straight to recurring software: a skills/actions framework + open SDK lets enterprises and third parties build their own integrations — latent platform/network effects on top of the per-seat governance annuity.
This is the strategic unlock and it deepens the moat without new silicon — value shifts to software. AI-agnostic + governed is exactly what consumer-AI players won't do, because their whole model depends on owning the AI relationship. Keep this directional: no model-routing specifics or partner terms here — those live in the partner/integrator scope, not this deck.
07 / KLICK

The Trojan Horse: Adoption Without the Adoption Battle

  • The hardest part of any wearable is getting people to wear it. We skip that fight.
  • ~$4.4B+ of protective eyewear is already on workers' faces today, growing toward ~$8B by 2035 (Future Market Insights).
  • KLICK is an upgrade to mandated PPE — not a new gadget asking for permission.
  • Vendors (Vuzix, Samsung) report 30%+ reductions in inspection/repair time and more first-visit resolutions in AR field-service deployments — a vendor-reported claim we'll validate against our own pilots.
  • Lowest adoption barrier in the category, on hardware we already manufacture.
This is the single most underrated advantage — distribution into a captive, already-equipped workforce.
08 / KLICK

The Moat (7 Powers, Simplified)

The moat is governance + AI-agnostic control + an ANSI normal-PPE form factor + speed + IP — won inside a real but time-boxed first-mover window, not by assuming incumbents can't follow.

Power Our position
Cornered Resource (core) ANSI Z87.1 certified normal-PPE frame + established manufacturing relationships + safety channel — the differentiated asset incumbents can't easily replicate
Switching Costs The governance layer — capture policy, admin controls, audit logs, identity/SSO, data-retention enforcement — extended to the AI layer: which models, endpoints, and skills/workflows are sanctioned
Counter-Positioning (time-boxed, marketing frame) A consumer-brand trust frame vs. ungoverned consumer-surveillance optics — a real but ~12-24 month first-mover window, not a hardware moat. The enterprise flank is contested; the lead is won by moving fast and filing IP now
Branding "The camera glasses security approves" — a trust brand, not a surveillance brand; reinforced by AI-agnostic + governed
Network / Platform (latent) A skills/actions framework + open SDK lets enterprises and third parties build their own integrations — each one a new switching cost and a path to platform effects
Process/Scale (building) Moving toward owning more of our own hardware source over time
The moat is governance, AI-agnostic control, the ANSI form factor, and speed + IP — NOT "no video." Counter-positioning demotes to a consumer-brand marketing frame, not a structural moat. This is a time-boxed ~12-24 month first-mover window; we win it by moving fast and filing now, not by claiming the giants can't follow.
09 / KLICK

Our Wedge vs. the Field

  • The segment is contested, not empty — enterprise smart-glasses players already serve these verticals (Vuzix: Intune-certified, MDM, capture + device management; RealWear: rugged ANSI headsets, high-res, device management).
  • Our four-point wedge against them:
    1. ANSI Z87.1 normal-PPE form factor — at a fraction of the weight and price of rugged enterprise headsets; the glasses workers already wear, not a headset they have to adopt.
    2. Dual-mode governance — one device that is free-and-open for consumers or fully IT-controlled for the enterprise; capture policy, audit, and retention are toggleable, not bolted on.
    3. AI-agnostic, bring-your-own-model governance — route to the customer's own sanctioned model under their controls, instead of locking them to a vendor stack.
    4. Consumer / long-tail optionality — the same hardware carries downstream upside the enterprise-only players don't pursue.
  • On the giant side: Meta, Google/Samsung, and Apple are committed to ungoverned consumer scale — and the more invasive consumer glasses get, the harder enterprise IT and legal recoil, which widens our lane.
  • Honest boundary: we don't claim the absolute-secure tier (defense/pharma/cleanroom want zero camera, physically absent).
Don't claim the segment is unserved — Vuzix and RealWear are there. Our differentiation is the four-point wedge: normal-PPE form factor + price, dual-mode governance, AI-agnostic control, and consumer optionality. We differentiate on form factor + price + governance, NOT on "no video." Naming the boundary we don't win makes the win we do claim believable.
10 / KLICK

Market Size (Directional, Bottom-Up)

  • We don't anchor on a vague "TAM." We size the workforces already wearing safety eyewear.
  • US construction alone is ~7-8M workers; add utilities, logistics/warehouse (millions), and ~50K insurance adjusters.
  • Each seat is a hardware sale plus recurring governance software — so revenue compounds per user, per year.
  • Even modest penetration of mandated-PPE workforces is a multi-hundred-million-dollar opportunity.
  • The point isn't the headline number — it's that every unit carries a software annuity behind it.
Directional only. The strategic insight is the recurring-per-seat layer on top of hardware, not a single TAM figure.
11 / KLICK

Business Model: Hardware + Recurring Governance Software

  • Hardware: the glasses — a durable, channel-ready product on our existing platform.
  • Software, two tiers: a free consumer tier and a paid Pro tier for individuals.
  • Enterprise SKU: the margin engine — per-user/month governance bundling admin controls, audit, identity, and data-retention enforcement.
  • Proof point: the leading dictation player monetizes enterprise governance at a strong per-user/month rate and sits inside 270 Fortune 500 companies.
  • Hardware gets us in the door; the governance subscription is what re-rates the business.
This is the shift from selling glasses to selling a governed platform — recurring, sticky, high-margin. That's the multiple.
12 / KLICK

Roadmap: Governed Multimodal Now, Live-Streaming "Pro" Later

Phase What it unlocks
Phase 1 (v1) Voice-triggered photo + short governed video clips → cloud → every device (the trust beachhead)
Phase 2 Voice dictation + the ask/act agent loop — hands-free reason-and-act
Phase 3 Universal cross-device clipboard + desktop — "Klick-to-clipboard"
Phase 4 Deeper governance + skills depth, and the "Pro" follow-on
  • v1 is already multimodal — photo and short clips fit the v1 form-factor envelope.
  • What's deferred is continuous live-streaming / remote-assist — a market-pulled "Pro" follow-on on a heavier form factor. For remote-assist we integrate TeamViewer / Teams rather than build a video-collaboration stack.
  • Same hardware carries the consumer upside ("Klick-to-clipboard," screenshot-to-clipboard) as long-tail growth; the software, cloud, and governance carry forward 100% into any Pro follow-on.
Sequence is the strategy. v1 ships governed multimodal capture (photo + clips) — that's the beachhead, not image-only. The deferred piece is continuous live-streaming, which is a heavier-form-factor Pro SKU; for collaboration we integrate, not build.
13 / KLICK

Two Games: Cash Engine vs. The Multiple

Retail Armor (Walmart/Costco) KLICK / Armor Pro
Role Cash engine The moat + the multiple
Nature Commodity volume Defensible IP + recurring software
What it does Funds operations Re-rates the company
Acquirer view Bought for inventory Bought for IP + platform
  • The fiduciary case: a public company raises to build moats and shareholder value — not to sell more commodity glasses.
  • A small team can run this moonshot through partners — no internal hardware org required — so it doesn't steal focus from retail.
Frame KLICK as the value-creation engine that sits alongside, not instead of, the cash business.
14 / KLICK

Why This Creates Shareholder Value

  • Re-rating: moves Lucyd from commodity re-brander toward owner of recurring software + candidate IP (claims pending a prior-art / freedom-to-operate search) around the novel combination — governed multimodal capture on an ANSI-certified safety frame with a governance/audit method.
  • Strategic optionality: positions us as an acquisition target valued for platform + governance software, with IP optionality once the prior-art search and counsel filings land.
  • Supply-chain independence: the path to owning more of our own hardware source — durable cost and process power.
  • Cost of inaction: stay a commodity reseller → zero acquisition premium, margin compression, and the counter-positioning window closes the moment a giant or a safety incumbent ships governed capture.
  • Asymmetric bet: small, partner-run program; large, durable upside.
The risk isn't doing this — it's not doing it and watching the window close while we stay a re-brander.
15 / KLICK

The Ask (Directional)

  • Endorse the two-game strategy: protect the retail cash engine; fund KLICK as the moat and the multiple.
  • Greenlight the partner-led model — run the moonshot through partners, keep the internal team small and focused.
  • Authorize the path to a funded pilot + software v1 at directional scope (figures handled separately, internal).
  • Back the supply-chain-independence goal — owning more of our own hardware source is the real long-term prize.
  • Next step: convert this vision into a funded pilot decision on the directional timeline.
Keep the ask directional and strategic. Specific figures, instruments, and timing live in the internal financial model — not here.