Selected work · Product to production

The visible product and the system beneath it.

Selected examples of how I connect product direction, interface decisions, full-stack engineering, infrastructure, trust, and operating reality.

Discuss your product

01 / 05

Active betaCTO · Product · Platform

Micr

Connecting game discovery, teammate matching, communities, and voice within one social gaming platform.

Role: CTO
Scope: Product direction, UX, architecture, and infrastructure
Stage: Active beta; release stage varies by product surface
Current focus: Reliability, recovery, observability, security, and operating cost

From finding a game to finding your people.

A game directory helps players choose what to play. Micr connects that discovery to compatible teammates, communities, and communication. Matchmaking, events, tournaments, and creator experiences need to feel like parts of the same product.

My contribution

As CTO, I lead product decisions alongside the architecture and operations that support them: how experiences connect, where service boundaries belong, and how the system fails and recovers.

Keep the journey connectedCarry a consistent experience across discovery, matchmaking, communities, and communication.
Make claims measurableDefine workloads, service objectives, and recovery expectations before making scale claims.
Make operations visibleConnect observability, deployment, and access controls to product risk.
Account for the costInclude infrastructure expense and support burden in product decisions.

Available to explore

The public game directory is open to browse. The broader platform remains in beta, with access and readiness varying by feature.

Browse Micr games Explore a platform readiness review

02 / 05

iPhone betaProduct · Mobile · Publishing

Yours

A personal space on the web, made on the phone you already have.

Product: Personal websites made on iPhone
Scope: Composition, local editing, backups, and publishing
Stage: iPhone beta; access by request

A personal website should feel personal.

Photos, words, music, and links rarely fit one fixed profile layout. Yours gives that material a flexible canvas on iPhone, with templates for a starting point and a blank page for a more individual direction.

The product work

The editing and publishing workflow brings composition, local saves, backups, and sharing together. The central decision is to keep the page editable on the phone and let its author choose when it becomes public.

Start with your materialCombine photos, text, music, and links in one composition.
Keep a working copySupport offline editing, saved editions, and editable backup exports.
Publish deliberatelyKeep a private online copy or share a page through a browser link.
Make touch the starting pointBring layout, typography, and color choices into the phone workflow.

Available to explore

The public site introduces the editor, shows example pages, and accepts beta requests. iPhone access is currently through the beta.

Explore Yours and its beta

03 / 05

iPhone betaProduct · UX · Full stack

Leadly

An iPhone beta for matching household items to cited lead records, with source details and uncertainty kept visible.

Role: Product and full-stack engineering
Scope: Product definition, UX, data presentation, and implementation
Stage: iPhone beta by invitation
Constraint: Keep sources, uncertainty, and the limits of identification visible

Help people understand what they found.

Identifying a household item and finding a relevant lead record are different steps. Leadly connects them while preserving the source, date, and limits of the evidence. A camera can help identify an item; it cannot chemically test it for lead.

My contribution

I shaped the product, UX, data presentation, and full-stack implementation around traceable evidence. The interface and data model need to keep an item match distinct from a claim about that individual item's safety.

Keep the source closeShow record context alongside the match, with a path to the evidence.
Preserve uncertaintyMake the limits of identification and source coverage readable.
Design for calmUse plain language and clear hierarchy for sensitive household information.
Support the next stepOrganize records and follow-up information around the item being reviewed.

Available to explore

The public site explains the evidence workflow and accepts iPhone beta requests. App Store release is forthcoming.

Explore Leadly and its beta

04 / 05

Live productProduct · UX · Full stack

ReadmeBio

Turning a link-in-bio page into an authored, living record of what a builder is shipping—without letting live data or deep customization take over the story.

ReadmeBio · Desktop view

Role: Product, UX, and full-stack engineering
Scope: Positioning, editor, integrations, publishing, analytics, billing, and deployment
Stage: Live product with free and Pro publishing paths
Core tension: Deep control and current activity within a clear public profile

A builder's work is more than a list of links.

Repositories, launches, and current projects live in different places. ReadmeBio brings them into a living README that the person can author and arrange.

My contribution

I shaped positioning, editor UX, and the full-stack publishing system around one decision: connected activity should support the person's story. Setup, composition, preview, and publishing follow that hierarchy.

ConnectBring GitHub, X, and Product Hunt activity into profile material.
ComposeArrange blocks, voice, and visual direction in a modular editor.
PublishSeparate drafts from the public profile and custom domain.
LearnUse views, clicks, referrers, and submissions to understand visits.

Author the identityLet the person set the narrative.
Keep drafts separateMake publication an intentional step.
Reveal controls progressivelyIntroduce deeper options as they become useful.
Price the operating layerOffer custom domains, retained analytics, inbox, and exports through Pro.

Available to explore

The public site shows the editor and preview. The example profile uses sample content to demonstrate the published experience.

Visit ReadmeBio Explore the example profile

05 / 05

Live client platformBrand · Web · Operations

Crystal West Cleaning

Connecting the public brand and lead experience to the practical owner workflow that has to support every inquiry.

Role: Brand, web, and operating systems
Scope: Positioning, experience design, implementation, and lead flow
Stage: Live client platform
Constraint: A small operation needs clarity and maintainability more than unnecessary complexity

The context

For a local service business, the website is only the visible end of a larger operating flow. Positioning, service clarity, inquiries, and follow-up all have to fit the way the owner actually works. A polished front end that creates confusion behind the scenes is not a successful system.

My work

I developed the brand and web presence alongside the practical workflow behind it. The work focused on making the offer easier to understand, creating a direct path from interest to contact, and keeping the resulting system manageable for the business operating it.

Start with the offerMake services and customer fit understandable before adding visual or technical complexity.
Design the whole journeyConnect the public site, contact path, and follow-up workflow as one customer experience.
Build for the operatorChoose structure and tooling the business can realistically maintain after launch.
Keep proof honestDescribe the shipped system and responsibilities without inventing conversion or growth numbers.

Visit Crystal West Explore the local business website foundation

Evidence standard

No inflated numbers. No borrowed credit.

A case study should make responsibility and judgment visible. Where an outcome has not been independently measured or approved for publication, I describe the work, the constraint, and the decision instead of manufacturing a metric.

That same standard carries into client work: define the evidence first, build what can change the decision, and verify the critical path before calling it complete.

See how I work

The visible product and the system beneath it.

From finding a game to finding your people.

My contribution

Available to explore

A personal website should feel personal.

The product work

Available to explore

Help people understand what they found.

My contribution

Available to explore

A builder's work is more than a list of links.

My contribution

Available to explore

The context

My work

No inflated numbers. No borrowed credit.

Let’s make the next move clear and make the system hold up underneath it.