01
WordPress Development
Custom themes built from a design, not a page builder — and the unglamorous work of making an inherited site behave.
- Custom themes
- ACF
- WooCommerce
- Multisite
Services
Hire the whole skill set, not a specialist per problem.
Most projects need a bit of everything: theme work, a plugin fix, a server that is misconfigured, and someone who can read the code that is already there. That is the job.
Six things I do often
02
Plugin & Add-on Development
Plugins that do one job properly, including commercial add-ons for Gravity Forms and other platforms with real user bases.
- Gravity Forms
- REST API
- Commercial release
- WPML
03
Shopify Development
Storefront work and custom apps for merchants who have outgrown what the theme editor can do.
- Custom apps
- Liquid themes
- Checkout UI
- Integrations
04
Custom PHP Applications
When the job is not a CMS: Laravel and CodeIgniter applications, integrations, dashboards, and long-running back-office tools.
- Laravel
- CodeIgniter
- MySQL
- Third-party APIs
05
Performance & Core Web Vitals
Getting LCP, INP and CLS into the green on sites that were not built with any of them in mind — and keeping them there.
- LCP
- INP
- CLS
- Caching
06
Rescue & Maintenance
Taking over a codebase someone else left behind, fixing what was called unfixable, and keeping it patched afterwards.
- Bug hunting
- Security cleanup
- Legacy code
- Ongoing support
How it works
Four steps, no surprises
-
Scope
You describe the problem. I read the existing code before quoting.
-
Agree
Fixed price for defined work, hourly for open-ended work.
-
Build
Staging first, regular check-ins, nothing lands live unannounced.
-
Hand over
Code, documentation, and support only if you want it.
Questions
Before you write
Can you take over a site someone else built?
Yes — it is a large part of the work. I read the codebase first and tell you honestly whether it is worth keeping, repairing, or replacing. That answer comes before any quote.
Do you work fixed-price or hourly?
Both. Defined work with a clear finish line is quoted fixed. Open-ended work — maintenance, ongoing development, “we will know it when we see it” — is hourly, because a fixed price for undefined work is a guess someone always loses on.
How quickly can you start?
Small fixes usually within a few days. Larger builds depend on what is already booked — ask and I will tell you the real date rather than the one you want to hear.
Do you do ongoing maintenance?
Yes, and several of my Upwork engagements have run for years on that basis. It is optional: you own the code either way, and there is no retainer you have to buy to keep your site working.
Can you make an existing site faster?
Usually, and often substantially. Start with the performance page — it shows this site’s own Core Web Vitals, measured from real visits rather than a lab test.
Describe the problem in a paragraph.
That is genuinely enough to start a useful conversation.