Web Developer · Product Builder
From polished web apps to CRM pipelines, I build the tools businesses actually run on.
a few things I've actually shipped ↓
02
Full-stack products
Built with Next.js, TypeScript & Supabase
04
Business systems
CRM, workflows & automation built around real operations
06+
Years in operations
Enough time to learn what software actually needs to do
I spent more than six years as an operations specialist — managing CRM systems, streamlining workflows, and living inside the tools teams depend on every day.
As my responsibilities grew, I wanted to build the tools I was managing, not just operate them. That led me into modern web development — and into GoHighLevel, where operations and engineering meet.
Today I build products end to end: web applications like KATHA, client systems on GoHighLevel, and AI-assisted workflows that change how fast I can design, code, and ship. The operations years are why everything I build survives contact with a real business.
Product Engineering
A premium reading and publishing product built for long-form reading, reader trust, and author workflows — from content discovery and membership to search, progress tracking, and the editorial tools behind a modern publishing experience.
Full-Stack Application
A secure full-stack RSVP system designed to replace spreadsheet and DM tracking with a clear guest flow and a private operational dashboard for the couple — covering authentication, guest status, confirmation workflows, and email updates without adding friction.
CRM architecture, marketing automations, and email workflows — the systems work behind the products. Little workflows that catch a new enquiry, reply, book it in, and let you know, all while you're doing something else.
The guest works through the GHL-connected booking flow.
GoHighLevel logs the guest and the reservation.
Staff update the pipeline as things really happen.
A workflow sends the matching guest email automatically.
A boutique-resort booking flow designed as a real operational system: a calmer customer journey, a structured intake path, and an operational workflow that keeps enquiries moving without losing human review.
It’s one example of how I think about business systems — the whole approach lives here.
The same systems thinking powers client work too, from landing pages with automations behind them to CRM pipelines that catch and route enquiries without spreadsheets.
Real client systems and modern product work built to solve business problems — with the right mix of product thinking, automation, and polished execution.
A production client engagement that moved a wellness practice onto a business-ready GoHighLevel system — public marketing pages, education funnels, CRM pipelines, and automations that fit the way the clinic actually works.
A warm one-page site for a local café — menu, story, and a tap-to-message enquiry form that lands straight in the owner's inbox.
A playful multi-page site for a cat adoption & rescue group — an adoptable-cat gallery, enquiry forms, and friendly auto-replies through GoHighLevel.
The same five steps, whether it's a publishing platform or a booking pipeline.
Understand the problem
Six years in operations come first: how the business actually runs, who touches the system every day, and what breaks when nobody's watching. I build for that — not for the demo.
Design the architecture
Then choose tools for reasons. Next.js App Router for server-rendered speed and honest routing; Supabase when a product needs real auth and Postgres; GoHighLevel when the client lives in their CRM. The problem picks the stack, never the other way around.
Build reusable systems
Design tokens, shared components, pure domain modules with documented seams. The test: the second feature should cost less than the first, and the next developer — often future me — should find the reasoning written down.
Ship
To a URL, not a folder. Real deployments with real users are the only feedback that counts — every project here is live, and the case studies only claim what the repositories can prove.
Refine
Polish is scheduled work, not leftovers: accessibility sweeps, reduced-motion passes, copy edits, print stylesheets. The difference between finished and shipped-and-abandoned is this step.
The direction is set: production-grade applications on Next.js and Supabase, systems that run real businesses, and AI-assisted engineering as a daily practice rather than a novelty. These notes are what's feeding that — things I'm actively studying and already folding into how I build.
Workflows with judgement — agents that plan, call tools, and see a task through.
Model Context Protocol — wiring AI assistants into the tools I already work in.
Shipped for the wedding platform — Postgres, Auth, RLS. KATHA's backend is next.
Server components, caching, and the App Router's deeper corners.
Building with Claude Code every day — much faster, still craft-first.
Whether you need a website, an automation that takes a task off your plate, or a full product built end to end, I'd love to help.
All contact options →
