Shipped products & platforms

A curated set of fictional case studies in the style of modern product-engineering portfolios — tight narratives, measurable outcomes, and stack callouts. Swap this page in the admin for your real projects.

STACK TypeScript React Next.js Node PostgreSQL Redis AWS Terraform Figma → code

Three builds that show how I work

B2B SaaS · 0 → 1

Northwind Atlas

Operations dashboard for a mid-market logistics company: live fleet map, SLA alerts, and CSV ingest that survived messy enterprise uploads.

Outcome: cut “where is my shipment?” tickets by 38% in Q1 after launch.

ReactMapLibreWebSocketsREST

API platform

Meridian Gateway

Unified API layer in front of three legacy SOAP services — idempotent webhooks, OAuth2 for partners, and request tracing for support.

Outcome: partner onboarding time from 11 days → 2 days.

NodeOpenAPIPostgresKafka

Design system

Campfire UI

Cross-product component library with accessibility baked in (focus rings, reduced motion), Storybook docs, and semantic tokens for theming.

Outcome: design QA cycles dropped ~25% across squads using the kit.

ReactCSS layersa11yStorybook

From discovery to handoff

Shape the problem

User flows, constraints, and risk — written down so engineering and stakeholders share one map.

Vertical slice first

A thin end-to-end path to production early, then widen — fewer surprises at integration time.

Instrument & iterate

Feature flags, structured logs, and dashboards so we improve with evidence, not opinions.

Clean handoff

Runbooks, ADRs, and Loom walkthroughs so your team owns what we built.

This page is demo content: layout and some phrasing were iterated with AI coding assistants (LLM pair-programming), then edited by a human — the same rhythm many teams use now for scaffolds, refactors, and first-draft copy. The skill is still judgment, testing, and knowing what not to ship. When I’m not in the editor, I’m usually tracking Lincoln City FC — Up the Imps.