HubSpot
Custom themes, modules, and HubL templates that marketers actually enjoy editing.
About me
The complex modules, the migrations that can't lose rankings, the integrations that have to just work — seven years of HubSpot, end to end.
How I got here
I didn't plan to become a HubSpot developer. I planned to be a generalist. The HubSpot work just turned out to be the thing I was good at and other people kept paying for — so I stopped fighting it.
Where I first met HubSpot. From apprentice to shipping real client builds — and figuring out this was the work I was good at.
Deeper into custom modules, themes, and HubL — building for clients who had to live in the editor every day, which is where my obsession with editor-friendly work started.
Complex modules, migrations that can't lose rankings, and CRM integrations wired through the API. The hard, end-to-end work other developers tend to hand off.
How I work
Custom themes, modules, and HubL templates that marketers actually enjoy editing.
Next.js, React, and serverless when HubSpot isn't the right tool for the job.
Core Web Vitals audits and the unsexy work that fixes them — image pipelines, render-blocking JS, Lighthouse scores that don't lie under load.
Schema, sitemaps, and WCAG-conscious markup — built in from the start, not bolted on before launch.
Tech Stack
Boring on purpose. I pick tools that other developers can pick up without a week of onboarding.
Send a few lines about the project. I read everything personally and reply within one business day — even if it's to say no.
Start a conversation