Wes · Product Engineer / Frontend Developer

I turn operational friction into clear, tested, shippable products.

I work from the workflow outward: find the repeated workaround, define the product, build the interface and system around it, test the risky paths, and stay accountable for what actually ships.

Review the proof View résumé GitHub

Product strategyInterface designFrontend engineeringDeployment

Featured Work

Three products. Clear proof.

Each summary separates implementation from estimates, demos from production behavior, and public proof from protected product access.

Working public demoDealership operations

PrepFlow Dashboard

A role-based workflow for the handoffs between Sales, Inventory, Business Office, Service, Admin, and shared TV boards.

Ownership: Product definition, workflow model, UX, React frontend, demo packaging, and portfolio deployment.
Architecture: React 19 + Vite PWA; shared client state drives role-specific views. The public build uses seeded local demo data; the service-backed architecture is separate.
Tests: 175 Vitest tests across 21 files cover role switching, requests, ownership, holds, finance, service, TV boards, auth, and KPI logic.
Tradeoff: The public demo removes backend setup and real customer data, so it proves workflow behavior—not multi-user production load.
Validated outcome: Buildable, installable demo with six connected operating views and repeatable seeded handoffs.

Estimate label: The ~$27K annual labor value in the full summary is modeled, not a measured customer result.

Behind the Build Open live demo →

Working public demoLayout optimization

Lot Control

A standalone browser app for blueprint-backed planning, constraint-aware stall generation, live vehicle placement, and bounded reorganization.

Ownership: Product concept, operating model, interaction design, geometry engine, SVG interface, test suite, and static deployment.
Architecture: Zero-dependency ES modules with one shared lot/vehicle model, SVG rendering, local persistence, and GeoJSON import/export.
Tests: 106 Node tests cover lot operations, optimizer geometry, gate reachability, tessellation seams, mixed angles, circulation, and browser-safe behavior.
Tradeoff: Local-first portability avoids account and backend setup; collaboration and cross-device sync are intentionally out of scope.
Validated outcome: Applied layouts preserve the vehicle census, reject invalid circulation, and keep displaced cars in an explicit off-lot yard.

Behind the Build Open live demo →

Live production · access gatedVehicle identity platform

Garage‑Pass

A production-facing platform that gives each real car a digital home for identity, ownership history, records, events, awards, and community context.

Ownership: Founder/product owner and hands-on engineer across product direction, frontend, backend, data contracts, release tooling, and operations.
Architecture: SvelteKit 2/Svelte 5 static frontend on Firebase Hosting; Express 5 API on Cloud Run; Firestore in production with a SQLite adapter for local development and tests.
Tests: Jest + Supertest backend/integration coverage, Vitest frontend tests, Firestore emulator/rules suites, and Playwright authenticated E2E in the release gate.
Tradeoff: The public launch gate protects production work and user flows; the case summary is public so architecture and engineering decisions can still be evaluated.
Validated outcome: The production domain returns HTTP 200 and intentionally routes guests through the current access gate while member surfaces remain authenticated.

Behind the Build Visit production gate →

The Work

Active projects

Explore by category

Swipe to explore categories

Showing all 7 active projects

Production Platform

Garage‑Pass

A production-facing vehicle identity platform spanning digital garages, records, ownership context, events, awards, and community.

SvelteKit Express Firestore

Production gated Behind the Build Public Gate →

Marketplace Prototype

Pock-IT

An invite-only everyday-carry prototype connecting community, collections, simulated transactions, carry logs, and demo lineage records.

EDC Marketplace Private Beta Demo Lineage

Private beta Behind the Build Open Preview →

Workflow UI

PrepFlow Dashboard

Every vehicle. Every handoff. One dashboard. From check-in to admin sign-off — nothing falls through the cracks.

React Workflow UI Dealership Ops

Live Behind the Build Live Demo →

Dealership Operations

Lot Control

Merge site planning, constraint-aware layout generation, live vehicle placement, and bounded morning reorganization into one portable app.

Lot Operations Constraint Aware Capacity Planning Lot Planning

Live Behind the Build Live Demo →

Commerce + Brand UI

Teal Leopard

A boutique storefront where brand-led merchandising, product discovery, cart flow, and customer-care details work as one shopping experience.

Storefront Commerce UX Brand UI

Live Behind the Build Live Demo →

Game Lab

A hands-on lab for proving one interaction or complete gameplay loop before a game earns full scope. Midnight Circuit, a native racing build, is the first game in development here.

Interactive Gameplay Racing

In development Behind the Build

Read-only Market Planning

Trader

An NQ planning workspace that makes daily bias, confluence, entry, a 20-point target, and invalidation explicit, with manual fallback and a conditional read-only data bridge.

Fintech Manual Fallback Read-only Feed

Working demo Behind the Build Open Planner →

Status language is literal: production means a deployed product; working demo means runnable demo behavior; private beta means access-controlled; completed and parked means preserved without planned development; prototype and concept mean incomplete; estimates are labeled as modeled; conditional integrations are not described as active without live verification.

About Wes

Product thinking, frontend craft, and ownership through release.

I am a product engineer and frontend developer focused on operational software: the places where unclear status, repeated questions, or a fragile workaround cost people time.

My work spans product definition, interface architecture, implementation, testing, deployment, and iteration. I use demos to make behavior reviewable, tests to make the risky paths explicit, and candid status labels so the portfolio never asks a reviewer to confuse potential with production proof.

Read the résumé View GitHub Email Wes

My Process

Start with the workaround. It usually points to the real problem.

The extra spreadsheet, the repeated question, the step everyone warns you about — these are clues. Following them back to the source reveals what people actually need and where a better way can make the greatest difference.

01
Watch the work
See where people pause, repeat themselves, switch tools, or invent a workaround just to keep moving.
02
Trace the friction
Look past the obvious symptom to find the missing information, constraint, or decision creating it.
03
Design a better path
Remove unnecessary steps and shape a practical solution around how people actually think and work.
04
Prove it in practice
Put a working version in real hands, watch what changes, and refine it until the improvement holds.

Get In Touch

Let’s build
something.

Have a project idea, a problem worth solving, or just want to see how something gets built? Drop a message — I read everything.

Contact@BuiltByWes.App

new‑message

I turn operational friction into clear, tested, shippable products.

Three products. Clear proof.

PrepFlow Dashboard

Lot Control

Garage‑Pass

Active projects

Garage‑Pass

Pock-IT

PrepFlow Dashboard

Lot Control

Teal Leopard

Game Lab

Trader

Product thinking, frontend craft, and ownership through release.

Start with the workaround. It usually points to the real problem.

Let’s buildsomething.

Message sent.

Let’s build
something.