WordPress is my core — but custom WordPress development means writing real code. PHP, MySQL, JavaScript, CSS, REST APIs. I'm not configuring plugins; I'm engineering solutions from scratch. That foundation means I can take on projects that go beyond WordPress when the situation calls for it — Laravel backends, custom PHP systems, API integrations with external platforms. I've done it. I just won't tell you I can build anything. What I can tell you is that if your project is rooted in WordPress or PHP, I can handle more than most developers you'll talk to.

Mostly marketing agencies that need a senior developer they can trust with complex work — someone who doesn't need hand-holding and won't disappear. And startups that need something built properly the first time, not patched together and rebuilt six months later. If you have a real problem that needs real engineering, we'll probably work well together.

Yes — and at a deeper level than most. I've built custom modules and extensions for Elementor, Divi, and Beaver Builder, not just used them. I know how they work under the hood. That said, for new projects I consistently recommend building with native Gutenberg and custom blocks instead. It's faster, lighter, doesn't add third-party dependencies that can break or disappear, and produces code that any developer can maintain. I'll always walk you through the tradeoffs — but that's usually my recommendation.

Both. I work from Figma files, design systems, or rough wireframes. If you don't have designs yet, I can help you find the right designer or work from functional wireframes to get started. I don't need everything perfect to begin — just clear on what the goal is.

You own it completely. Everything ships with documentation covering what was built and how to extend it. Your team, your next developer, or any agency can pick it up without calling me. That said, most clients do keep me on for ongoing work — not because they have to, but because continuity has value.