Cloud cost intelligence · industrial diagnostics · generative film tools · local AI tooling.A decade of zero-to-one product design, from seed to scale.
Scroll
01 · CloudZero
Scaling from a single user to thirty enterprise clients.
Cloud cost intelligence for engineering teams.
Role
Sole product designer
Timeline
Seed → Series B
Team
Product · engineering · infrastructure
Scope
Platform 0→1 · design system · research
Reach
Workflow integration.
Real-time cost alerts in Slack and CLI. Anomalies surface where engineers already work.
The domain
Co-designing with infrastructure teams.
Learning complex cloud architecture directly from backend engineers. Designing tools for the immediate technical team.
Tagging
Adapting to user taxonomies.
Accepting raw AWS tags as-is to build adjacent structures with minimal UI interference.
Design system
Zero Design System.
Adapting IBM Carbon for rapid engineering execution.
The practice
Full-lifecycle ownership.
Research, interaction models, and execution from seed through two funding rounds. Scaling the platform to market.
One product, five lenses
Interfaces built for context.
Infrastructure cost reads differently depending on who's looking. The same numbers reshape into the view each team already thinks in — and every dollar gets an owner.
total_cost · by feature
Grouped by feature — cost in the shape the product team already thinks in.
Detection → triage
Triage starts in Slack.
A cost anomaly is an incident, not a month-end report. The system detects — the team that owns the resource decides. The alert carries enough to act.
The page as it lands. Resource, delta, baseline, owner — the decision happens in the channel. The buttons are live.
Signal over noise
Routine drift logs quietly. A real departure from baseline pages a human — 33 minutes after spend deviated.
Routed by ownership
Cost allocation names an owning team for every resource. The alert lands in that team's channel and tags the on-call — not a company-wide feed.
Triage before the click
Rate against baseline, start time, projected impact. The engineer knows it's real before opening a dashboard.
Likely causes
Every change from the 24 hours before the spike, ordered by cost correlation. The deploy sits on top — two minutes before the inflection.
Scoped to the actionable
My team's changes is the default view. AWS-initiated noise sits one tab away.
The loop closes
Acknowledge here and the channel shows it. The team sees it's handled without asking.
02 · Cummins · Product, system, process
Accelerating enterprise product cycles.
Synchronizing software design systems with industrial manufacturing cadences.
Product
Guidanz — engine diagnostics
Scope
Design system · delivery process
Pilot
One feature · end to end
Design-to-ship
3 months → 2 weeks
Linear3 months
SpecReviewHandoffBuildQAShip
Isolated specifications, sequential reviews, and rigid engineering handoffs.
Living2 weeks
Design in context → comments → ship.
02 · Cummins
Systemizing product design.
Aligning software component architecture with industrial manufacturing cadences.
The system. Tokens — color, type, spacing, radius — and the components they generate. A design change is a change build already has the name for.
Design in the running product. Engineers build against the live screen, not a spec — what they see is what ships.
The resubmit cycle, collapsed. Days of PDF round-trips become one working session on a living design.
An ask sized to a yes. Months of meetings across teams, managers, and directors — distilled to one pilot feature.
The pilot that shipped. One feature, run end to end on the new cadence — the cadence stuck.
03 · Concept · Sound landscape
An audio landscape shaped by emotion.
A minimalist audio terminal removing cognitive overload through responsive geometry.
An interactive appliance for psychological rest. Sound stripped of choice to match your mind.
The interface
No titles. No queue. No settings.
The geometry responds to you. There is nothing to operate.
04 · Greenlight · Diffusion research
Old photographs in motion.
Two years of diffusion research. The first thing it made was a gift for my father.
Take 01 / 05Play
Direction
The instrument
Greenlight — A still-to-film console.
Designed, built, and deployed solo. Wan 2.2 on serverless GPUs. Output resolution matches the source frame.
The live app runs the session behind the reel. GPU asleep between runs.
05 · Visionary · Local AI tooling
Simplifying the AI dataset pipeline.
Consolidating the entire curation and captioning pipeline into one offline workspace. Free and open source.
Role
Sole designer & engineer
Scope
Product · UX · built in Claude Code
Platform
macOS · Apple Silicon
Release
Alpha 0.1.0 · open source (MIT)
The alpha · live
Six ways to see the same photographs.
Curation is re-seeing one set until the right cut is obvious. Each arrangement surfaces a different structure.
Arrange by
Structure gathers near-duplicates for review before you delete. Color and Person come from the app's own perceptual hashes and on-device face clusters. Select a tile and its real dimensions, color and tags fill the panels.
Rebuilt in the browser from the app's own index — every dimension, color, duplicate and tag here is Visionary's output on a 44-image set. The native app does the same on your folders at a hundred thousand. This is only the demo — the full app is on GitHub.
The hand-off
Packaged for wherever you train.
A curated set only matters if it leaves clean. Visionary writes the caption and packages the folder in the format the trainer already reads.
Caption
JoyCaption's own grammar.
Each caption is built from a type, a length and opt-in extras — no prompt engineering. Taggers and VLMs write to the same .txt.
→
Package
The format the trainer already reads.
Export writes .txt sidecars or one metadata.jsonl. Files renumber in grid order, so your arrangement becomes the training order.
→
Ship
This Mac or a GPU box.
Keep it local, zip it, or scp the set straight to the machine that trains. One way, key auth, nothing stored.
The road to alpha
Five things that didn't survive review.
Good tools are subtractive. Every one of these shipped before it was cut or rebuilt.
Under the surface
Built for speed.
It processes 100,000 photos in under a minute on an 8 GB machine. The heavy analysis runs in the background while you browse.
100K+
images
120fps
sustained scrolling
0
dropped frames in 24 s
Memory footprint against an 8 GB budget.
the rest stays free
08 GB total
267 MB · a 750-photo set~1.5 GB · 100,000 images
The grid decodes only the tiles on screen. Hashes and color read from thumbnails rather than the source files. Duplicate thresholds are computed once so a scroll is just an array lookup. Memory moved from 1497 to 1505 MB across 90 seconds of scrolling at 100,000 images. One file-descriptor leak surfaced at that scale and was closed.
Design philosophy
Less but better. — Dieter Rams
Designed and built end to end in Claude Code — one design review at a time.
Design
One action color. White.
The chrome is dark and neutral so nothing tints how you read a photograph. White is the only color that acts — the primary button, the selection frame. Everything else recedes.
Control
Standard idioms. Ultimate authority.
Finder selection, Quick Look, delete to the Trash — patterns everyone has used for decades. You only notice them when they're gone. The app never overwrites an edit you made. Every destructive step stays reversible until you commit.
Community
Free. Offline. Yours.
MIT-licensed and installed with one command. No account, no telemetry, no bundled weights. The images never leave your machine. It's for the independent researchers that enterprise tools price out.
30+
paying enterprise customers, from one
6×
faster design-to-ship at a Fortune 500
10 yrs
designing AI products, end to end
This is not the negative.
Previously — creative direction, Belladonna Productions (L.I.E. · A Guide to Recognizing Your Saints · Transamerica)campaigns for Dodge & Keds · a decade behind a camerathis site — hand-built in code with an AI pair
