🌁 Home Page 🕶️ Supported Glasses 👓 Even Realities G1 🎙️ Ray-Ban Meta Copilot 🏭 17 Industry Reticles 📱 Mobile iOS/Android App 💻 Desktop Executive HUD 🤝 Partners & Affiliates 🎬 Viral Video Showcase 💎 Pricing & Monetization 📋 Launch Checklist 🎨 Case Study Redesign 🔒 Privacy Policy 🚀 Launch Web App
Case study — how this site actually got built

We used AI coding agents to redesign our own site. Here's exactly what changed.

VisionFlow's marketing site is built the same way the product is: by AI coding agents working directly in this repository's git history, reviewed against what the backend actually does. This page walks through four real, dated changes from that process — no case-study gloss, just the commits.

A note on numbers

Every count on this page (card totals, brand totals, question counts) is taken directly from this repository's own commit messages and diffs — cited inline as a short commit hash you can look up yourself. This page does not claim any change in conversions, signups, traffic, or revenue from this work — none of that has been measured, so none of it is claimed. Where we don't have a real number, we describe what changed in words instead of inventing one.

1. The problem: marketing copy that outran the product

Commits 31a25f6 and e28d394 — Aug 9, 2026

VisionFlow's homepage feature grid had grown to roughly 50 cards, most written to sound finished. An audit that cross-referenced every card against the backend service it claimed to call found that a large share were backed by endpoints that hadn't shipped yet, or that had already been honestly gated to a "not configured" response elsewhere in the codebase — the copy and the code disagreed.

51feature cards marked "Coming Soon" (18 already had a caveat, 33 had none)
4more fabricated backend services found and gated in the same pass
2over-branded cards fixed to say what's actually true

Rather than delete the ambitious cards, the fix reused the .badge-soon pill already established for pricing-tier rows, so the product roadmap stays visible while being honest about what runs today. Two cards (Teleprompter, Orator) had claimed smart-glasses HUD hardware that doesn't exist — their copy was corrected to describe what they really are: real WPM/pacing computation, shown on your phone.

"Marketing copy must match what the backend actually does. If a feature card promises something the backend 501s on, either the backend needs to become real or the card needs an honest 'Coming soon' badge — never leave the two disagreeing." — AGENTS.md, this repository's standing rule for anyone touching website copy

2. Rewriting the smart-glasses hardware page

Commit 0ab926d — Aug 9, 2026 — website/glasses-compatibility.html

The clearest single before/after in this redesign. The page previously listed eight named, trademarked hardware brands — Ray-Ban Meta, Apple Vision Pro, Meta Quest 3, Even Realities G1, Rokid Max, Vuzix Blade 2, XREAL Air 2 Pro, and MentraOS — each tagged 🟢 100% Certified Native Integration against features that, in every case, were backed by services already honestly gated to a "not implemented" response in the backend. That's not just an honesty problem; claiming certified integration with named third-party hardware VisionFlow has no relationship with is a trademark and false-advertising risk.

Before
  • 8 hardware brand cards
  • Every card: 🟢 100% Certified Native Integration
  • Fabricated "key features" per brand (WebXR HoloDesk, Spatial Gauge, Babel Lens — all already 501-gated in the backend)
  • Every card CTA'd straight to the pricing page as if ready to buy on that hardware today
After
  • 2 hardware paths — the only two that are real in any form
  • Ray-Ban Meta Smart Glasses: 🟡 Coming soon — blocked on Meta's partner-approval process, a business gate not a technical one
  • MentraOS-compatible glasses: 🟡 Early / unverified — an alert-viewer built against public SDK docs, never tested on real hardware, no voice output yet
  • Hero copy now points to the phone/desktop app, which is what actually works today

The page's own title changed to match: "Smart Glasses Hardware Compatibility Hub" became "Smart Glasses Hardware Status." Same page, same URL, a completely different relationship to the truth.

3. Two real interactive additions

Commit 073bd7a — Aug 10, 2026

Not every change in this pass was subtractive. Two genuinely new, working pieces of UI shipped the same day — both designed around the same honesty constraint as everything above.

CHAMP Plan eligibility qualifier

Replaced a static bullet-point checklist on champplan.html with a 3-question interactive tool — a headcount slider and two yes/no toggle rows — that tells a visitor in real time whether their company likely qualifies. It deliberately does not compute or show a savings estimate: that number only ever comes from Step 2's licensed-advisor call, on purpose, so nothing generic gets quoted before a qualified person has looked at real payroll data.

Feature-grid search & status filter

Added a search box and "All / Live today / In development" filter chips above the homepage feature grid from Section 1. The "in development" status isn't a second hand-maintained list that copies could drift from — it's computed live by scanning each card's own visible text for the same disclosure phrases ("in development", "not live yet", "coming soon") already established there. If a card's honesty copy changes, the filter follows automatically.

4. Why it happened this way

Multiple AI agents, one shared source of truth

This repository is worked on in parallel by several AI coding agents (including different Claude Code sessions like the one that wrote this page) plus a human — none of them share a live channel to each other. The git history and a running PROJECT_STATUS.md changelog are the only shared state. That's also why this kind of honesty pass keeps recurring: a feature built quickly by one agent can describe itself more confidently than the code underneath it actually behaves, and the next agent's job is often to find and close that gap before it reaches a real visitor.

This page is itself an instance of that convention — it exists because a dated changelog entry pointed back to the commits above, not because a metric proved the redesign "worked." No such metric exists yet.

See the real pages

Every change described above is live on this site today — not a mockup.

Try the feature search & filters Try the CHAMP Plan qualifier Read the glasses status page
🌐