Open to interviews nowBen MorrosNew York

Builds the productsthat businessesrun on.

Came to engineering from years in operations and business. Now leading the build of EyeBrowse — AR commerce, in-store kiosks, and an operator admin built to run a multi-store chain — and translating between exec priorities and the engineering.

Flagship system

EyeBrowse

Browser-native AR over a native SDK, so independent retailers ship without app-store friction or vendor lock-in. Storefront, offline-first kiosk, and a multi-location operator admin share one Postgres + Realtime backbone.

Platform scale

135k+
retail SKUs integrated
610+
brands in catalog
26
admin pages
3
production surfaces

Storefront

Built

Competitor AR requires an app download — the #1 conversion killer in retail.

Browser-native AR try-on. No app, no vendor lock-in, works on any phone.

Kiosk

Built

Retail WiFi fails 3-4 times per shift. Transactions can't depend on connectivity.

Encrypted offline checkout with background sync when WiFi returns.

Admin

Built

Franchise owners need one view across every location. Store managers see only theirs.

26-page editorial admin with role-based access, ⌘K palette, real-time inventory.

Dashboard demo

The admin is the proof surface.

Switch roles, move between operating pages, and ask the admin architecture questions in the AI tab. This is not a static screenshot wall.

Operator Admin · live demo · synthetic data

Editorial weekly briefing for the super admin. Hero MRR, 12-week trajectory annotated with launches, three operational signals, practice constellation, leaderboard. The page is a recurring artifact — the same shape ships every Monday.

Role
EyeBrowse admin dashboard preview

Built for desktop: 26 operating pages, role-based access, and a ⌘K command palette. Open it full-screen to explore the real thing.

Open full-screen admin
live

Ask the admin anything in the Ask AI tab — real Claude Sonnet, streams in real time.

Fast hiring signal

Scope ready to own next.

Strongest where product ambiguity, technical architecture, and business execution overlap. Evidence below — case studies, live demos, and a public resume.

Best role fit

  • Founding / early-stage engineer — build the whole product
  • Full-stack / product engineer across AI, healthcare, commerce
  • Solutions / forward-deployed engineer — customer-facing technical depth

Immediate ownership

  • Convert messy business requirements into a production roadmap
  • Design the architecture and ship the first durable version
  • Translate risk, cost, and tradeoffs for non-technical leadership

Proof to inspect

  • EyeBrowse — case study, screenshots, and a live operator admin demo
  • CareFlow — running real clinical operations for a medical practice today
  • Everything is inspectable end to end: architecture, tradeoffs, runbooks
How I lead

Operations first.
Engineering second. Both, in service of the business.

Years in operations and business — sourcing, executive support, and chief-of-staff work — before writing production code. The combination is the differentiator: someone who understands the business a product serves, then writes the migration that ships it.

The track record

Now

Head of Engineering · CTrue Vision

Leads engineering on EyeBrowse — AI-powered virtual try-on, AI prescription analysis, in-store kiosks, two integrated payment systems, and an operator admin built to run a multi-location chain. Owns the technical roadmap, launch sequencing, and the executive narrative for the platform.

Before

Operations & business · Haddad Brands, Medrite, Q4 Designs

Sourcing, production, and buying for the Nike Kids line at Haddad Brands; executive support to the EVP at Medrite Urgent Care; chief-of-staff work at Q4 Designs. The business-side grounding behind the engineering.

Foundation

MBA · Johns Hopkins Carey Business School

Finance, strategy, and the analytical framework for translating engineering tradeoffs into business decisions. Comfortable in a boardroom. Comfortable in a code review.

Operating principles

Lead with business constraints

The best architecture is the one the business can sustain. Margin, headcount, and timeline are first-class inputs — not friction to engineer around.

Translate in both directions

Executives need cost and risk; engineers need latency and coupling. Same system, two languages — written and spoken in either fluently.

Set priorities, not preferences

A technical goal is a measurable bet on a business outcome. Roadmaps tied to revenue, retention, and risk ship; roadmaps that read as preference lists do not.

Ship the durable v1

A focused first version that survives real load is worth more than a perfect third version that hasn't been tested. Iterate on what real users hit, not what slides predicted.

Same system.
Two lenses.

Every technical decision has a business dimension. Toggle between lenses to see how the same EyeBrowse architecture reads from an engineering perspective versus an executive one.

EyeBrowse architecture

Business lens: what changes for customers, managers, and revenue.

Executive view

Customers see frames on their face instantly — no app download, no special hardware, works on any phone. The same AR technology Warby Parker uses, but accessible to independent retailers.

Executive view

When a frame sells in one store, every screen in every location updates in under a second. No stale inventory, no overselling, no embarrassing "sorry, that's actually sold out" moments.

Executive view

Store managers see only their location's data. Franchise owners see everything. Nobody sees what they shouldn't. Every change is tracked and auditable.

Live demos · running on this page

Move your cursor.
See real-time sync the way a store chain would.

The same Supabase Realtime infrastructure EyeBrowse uses to keep inventory and pricing in sync across store locations is running on this page. Every visitor sees every other cursor live — open a second tab to test the broadcast across sessions.

One pipeline. Six components. Every kiosk and storefront in sync.

eyebrowse-architecture.svg
Client
Browser Storefront

Browser-native webcam capture — no app or extension

Runs natively in the browser — zero app downloads, zero friction. Customers try on eyewear from any product page without leaving the retailer's site.

Processing
MediaPipe

468 facial landmarks detected in <16ms

Google's ML framework maps 468 facial landmarks per frame at 60fps. This precision is what makes virtual try-on feel real — glasses sit on your face, not float near it.

Processing
Edge Functions

Serverless compute for AI orchestration

Runs auth, validation, and AI orchestration close to users so the browser stays fast without a dedicated app server.

Intelligence
AI Layer

Claude API + Gemini for product recommendations

Routes recommendation requests across providers with fallback so style guidance keeps working even when one model is slow.

Data
Supabase Realtime

WebSocket pub/sub for live updates

Built to sync inventory in real time across every store location. A product marked 'sold' in-store disappears from the try-on experience within 200ms.

Data
Admin Dashboard

Real-time inventory and analytics

Store managers see live try-on analytics — which frames are trending, conversion rates, and inventory levels updating in real time without page refreshes.

Business value is shown inline for each componentEyeBrowse — Production Architecture

Let's
talk.

Hiring for an AI, commerce, operations, or platform problem? Send the role, timeline, and what success looks like. Replies come back the same day.

Send role context

Short is fine. A role link, team context, timeline, and the problem you are hiring around is enough.