Work
A closer look at some of the projects I’ve delivered, including a nonprofit and my current project for a gallery. Most of my work is end to end. I start with the user, find the unmet need, and set a North Star, then execute with a program lens: notes, action items, a task list, dependencies, and a critical path. I keep iterating with the client until they’re genuinely happy with what gets launched.
Featured case study · Client engagement
A mobile-first, accessible website for a 501(c)(3) equine-therapy nonprofit. It helps families understand the program, trust the team, join the waitlist, and support the mission. For an org with no IT team, I was the IT team.
Live preview: the real, deployed site, embedded right here and currently in client review.
Before & after
The organization had a thin .com with little for visitors to do. To make their
site more effective, we redesigned it to be inviting, educational, and trustworthy. We added a waitlist and
online giving, and made it mobile-first and accessible.
.org domain.How I approached it
Product lens
Program lens
The discovery trail
Before designing a single screen, I studied how the best therapeutic-riding nonprofits earn trust online. Then I turned the patterns into an information architecture.
The Shea Center, Ride Above Disability, Tara’s Chance, and SD Therapeutic Horsemanship: national names and local peers, to see what families and donors expect.
Emotional hero + one mission line; three CTAs (Donate / Volunteer / Get started); named parent quotes; an accreditation/trust signal; a “what is equine therapy?” explainer for newcomers; meet-the-horses with sponsorship; and impact numbers.
A first-launch sitemap (Home, Services (PT/OT), Meet the Team, Meet the Horses, Waitlist/Inquiry, Donate/Support, Sponsors, Contact), each section mapped to a user need and a conversion.
A polished homepage and core pages first, reviewed together, then refined. Collaborative all the way through.
Implemented as fast, accessible pages wired to the services that run the org; checked on a 375 px phone; deployed to a live, HTTPS URL on Cloudflare Pages.
The full stack, delivered
The user interface is only the part you can see. Because Center X had no IT team, I owned the entire stack, strategy through hosting. They never had to coordinate a registrar, a developer, a forms vendor, and a payments tool on their own.
After weighing Google Forms, Airtable, Tally, and Fillout (generous free tier, unlimited forms from one account), I built the Waitlist Inquiry, Volunteer Interest, and General Contact flows, each routing to a tracked destination (Sheets/Airtable) with category and source tags. I deliberately kept them to basic contact, service interest, and a short inquiry, with explicit “please don’t submit medical details” copy.
Because the public forms collect no protected health information, the marketing and fundraising site shipped now. The form is a swappable module. When Center X needs real clinical intake, it moves to a BAA-signing vendor like Jane App for a PT/OT practice, IntakeQ/PracticeQ, or Jotform HIPAA, separate from the marketing site. (That healthcare instinct carried over from working on FDA-cleared medical devices at Dexcom.)
After comparing PayPal, Zeffy, and Donorbox, I shipped Givebutter, now live on the site. It’s genuinely free on the optional-tip model (tips on = $0 platform + $0 processing; tips off = a flat 3% + standard processing), with a free donor CRM, recurring giving, and campaign notifications. An Amazon Wishlist is an easy in-kind supplement.
Deployed on Cloudflare Pages: free, a fast global CDN, automatic HTTPS, Git-based deploys with preview links for client review, and a password gate that was trivial to toggle before launch.
Kept the domain registered at GoDaddy (no transfer needed) and pointed DNS at Cloudflare
for free DNS, SSL, and CDN, with email records preserved so mail kept working through the cutover.
The site now resolves on its own .org with automatic HTTPS.
Every form lands somewhere with an owner: a shared Sheet or Airtable base per category (waitlist, volunteer, contact) with the tags built into the form structure, so no inquiry goes unanswered.
The outcome
How we worked together matters as much as what shipped. I always try to communicate in the way that’s most comfortable for the client. If email is best, we do that. In this case much of our discussion was on Zoom and over text. It’s so important to have that shared context, capture decisions, and make them together.
Current project · in progress
My next client is a contemporary art gallery in Solana Beach’s Cedros Avenue Design District: four decades of work and 60+ represented artists. The current site makes the art hard to find and is heavy to load. The plan is to put the art and the artists front and center, on a site that feels as contemporary as the work itself.
What we’re aiming for
More work
Personal projects. Each one built to solve a real problem and to learn a new technology in the full stack.
An open-source framework that detects when AI agents skip tool calls or fabricate outputs, the silent failures normal observability misses. Product lens: a category most teams can’t even name yet. Program lens: 310 tests, five framework adapters, and a live dashboard, shipped and in real use.
310 tests · 5 adapters · live dashboard
View projectAn automated analysis agent covering 55+ assets with a 3-layer risk engine, built on Python, Claude, yfinance, and FRED. Product lens: make market risk readable by anyone, not just traders. Program lens: deployed daily via GitHub Actions with cross-source validation so a broken data feed can’t fail silently.
55+ assets · daily auto-deploy
View projectField notes from real builds: how I work with AI agents, what context engineering actually takes, and the failures worth learning from. The thread: thinking out loud, so the craft is visible, not just the polished result.
Field notes · new posts regularly
Read the blogWhether you need something shipped or a clear plan to get there, let’s talk about what an edge looks like for you.
Start a conversation
