I build systems that ship and stay up.
8 years of server crashes, 3 AM alerts, and scaling problems — that's what makes my code different.
Started with servers, not code
My first job was managing cPanel and WHM servers for a UK hosting reseller. Every time a server went down at 3 AM, I was the one fixing it. That shaped how I think about every system I build — reliability isn't a feature, it's the baseline.
After years of keeping servers running, I started building the tooling around them: custom WHMCS themes, client portals in WordPress, then full headless setups with Next.js. That's when I realised software could eliminate most of the firefighting entirely.
The shift into AI automation happened naturally. The same clients who needed reliability also needed their support queues automated, their WHMCS connected to WhatsApp, and their onboarding streamlined. So I built those systems too.
Three things I'm built for
AI & Automation
WhatsApp bots, n8n workflows, LLM agents. I automate the repetitive work that burns your team out.
Custom SaaS
Multi-tenant platforms, billing systems, admin dashboards. Production-grade from day one.
Hosting Systems
cPanel, WHM, WHMCS — if it runs a hosting business, I've built, broken, and fixed it.
My working philosophy
“Ship it, don't perfect it”
I favour working software over architecture debates. You can always refactor; you can't recover a missed market window.
“Production means real constraints”
Shared hosting CPU limits, mobile-first performance, 3 AM incident scenarios. I design for reality, not demos.
“Boring tech wins”
Next.js, MySQL, pm2, Tailwind. I choose proven tools over trendy ones. Your business depends on it not breaking.
Proof I mean it
I don't just build for clients — I build and run my own products. No mockups. Live systems.
Let's build something that lasts.
If you need a system that ships on time and stays up under pressure — not a mockup that looks nice in Figma — let's talk.