Henry Mayo Asheville, NC

Solutions architect programming since 2013

Software that fits the way people actually work.

The real problem is rarely the stated one. It hides in the handoff nobody trusts, the spreadsheet behind the spreadsheet, the “five-minute” task that eats an afternoon. I sit with the people closest to the work, trace the whole system, and build the fix end to end. Web, mobile, data, AI — whichever the job calls for.

What that looks like in practice

01

Start with the real workflow

Pricing, planning, dashboards, awkward handoffs — I sit with the people doing the work before I decide what the software should be.

Workflow appsOperations toolsPricing systemsDemand analyticsForecasting
02

Make AI earn its keep

Retrieval, fine-tuning, agents, vision — and the judgment to use ordinary code when it will be faster, cheaper, and easier to trust.

RAGFine-tuningAgentsMCPComputer visionOn-device ML
03

Follow the feature end to end

From the first interaction through APIs, queues, data models, and deployment. Fewer handoffs keep the idea intact and the edge cases owned.

TypeScriptPythonSwiftReactRemixNext.jsShopifyNode.js
04

Build the quiet machinery

Event pipelines, caches, ranking systems, and cloud infrastructure designed to stay boring while the product does interesting things.

PostgreSQLFirestoreRedisWebhooksQueuesAWSGCPObservability
05

Design trust into the model

Sensitive health, education, customer, and payment data handled with explicit boundaries, careful access, and no surprises.

HIPAAFERPASOC 2Secure authPermissionsAudit trails
06

Get the room unstuck

Turn a grower’s hunch into a spec, a technical constraint into a clear choice, and competing asks into the next useful thing. This part is my favorite.

DiscoverySystems thinkingPrototypingMentorshipPlain English
Collector platform

Garden

A purchase becomes the start of a collection, not the end of checkout. Garden turns new orders, opted-in order history, and custom plants into a living catalog; tracks cultivar-aware collection gaps and loyalty; supports permissioned sharing; and sends alerts only after a real zero-to-stock transition. Underneath: verified, idempotent Shopify webhooks, linked identities, Firestore, image processing, caches, and repairable imports.

Order syncCultivar-aware progressPermissioned sharingImage pipelineInventory-triggered alerts
Operations system

Garden Admin

The control room behind it: recommendation weights and demand velocity; collection and reward tooling; a customer view spanning orders, plants, loyalty, alerts, and linked identities; plus a campaign studio with live send progress. Events are deduplicated and time-decayed, writes are rate-limited, summaries cached, and staff actions recorded.

Demand analyticsRecommendation tuningCustomer 360Collection opsEmail studioStaff action history
Commerce system

MrMaple storefront

A Shopify Empire theme rebuilt to behave like a zone-aware plant-shopping app: fixed mobile navigation, swipe-and-zoom product pages, climate-specific care, recent history, and product rails backed by Garden’s demand snapshots and feedback events. The interface stays tactile; the backend keeps the context.

Shopify LiquidMobile PDPUSDA zonesCare guidanceDemand feedback
Use the storefront →
Shipped & published

Ventful

A fully built event social platform for iOS — discovery feeds, ticketing, and a personalized recommendation engine balancing taste, friends, and what’s happening tonight. Co-founded, architected, and published end-to-end. I’ve loved making mobile apps ever since — a phone is where software meets someone’s day.

iOSCross-platformTicketingSocial feedsRecommendation engineApp Store