Services

What I Build

These are the full stack engineering services I offer. I build PHP and Laravel backends and Vue or React front ends, along with custom WordPress builds, LAMP deployment and maintenance, and landing pages built around the form.

I've split these into five because people come looking for them separately. A team that needs a Laravel API has a different problem from a business that needs its WordPress theme rebuilt. In practice most projects use more than one of them. That's why it can make sense to hire one person who covers the whole stack, instead of bringing in three specialists and managing the gaps between them yourself.

PHP & Laravel Development

I build the server side in PHP and Laravel. That covers REST APIs and MySQL schema design, and I plan third-party integrations into the architecture early so they don't get bolted on at the end.

• PHP / Laravel
• REST APIs
• MySQL schema design
• Third-party integrations

Vue & React Front End Development

Front end development in Vue, React and TypeScript. I build components that fit together cleanly and data tables that cope with production volumes, and I use GSAP for motion that's worth what it costs in frames.

• Vue
• React / TypeScript
• GSAP / ScrollTrigger
• Responsive UI

Custom WordPress Development

I build custom WordPress themes from scratch. Advanced Custom Fields sits behind every editable region, so your marketing team can run the site without opening a template file.

• Custom themes
• ACF
• WooCommerce
• Custom plugins

Deployment & Ongoing Maintenance

This is the work that comes after launch. I set up LAMP environments on DigitalOcean and track down slow queries. I also keep existing applications running with patches and new features.

• LAMP / DigitalOcean
• Query tuning
• Speed & SEO
• Code review

Landing Page & Lead Capture Development

I build landing pages around the form instead of the hero image. The form validates on the server and hands leads straight to your CRM, and once there's enough traffic for the results to mean something, I split-test it.

• Landing pages
• Lead capture forms
• CRM handoff
• A/B variants

How a project runs

Scoping, before I quote anything

In the first conversation I want to know what the thing has to do. The framework comes later. I'll ask what already exists and what has to keep working while it changes. I'll also ask who edits the content after launch, and what it costs you when something goes wrong. Then I write up a scope and mark the parts I'm unsure about, so you can see what the estimate assumes.

Building it in your own repository

Work shows up in branches you can review, against your staging environment, as it happens. I settle the schema before building an interface on it. Fixing a data model in week one takes an afternoon, but in week six it means redoing the interface too. Because you can watch it come together, you can change direction while that's still cheap.

Handing over a deploy you can run without me

I document the environment and make the migrations repeatable. Every editable region gets wired to an admin screen someone who isn't a developer can use. If you keep me on for maintenance afterwards, that's your call. The build itself won't depend on me, and none of the code is written so that only I can work on it.

Ways to work together

• Fixed-scope project. A set build with a written scope and a fixed price. This works best when you can already describe what you want on a single page.
• Monthly retainer. A block of hours each month for maintenance, new features and the odd emergency. It suits a live application that keeps growing after launch.
• Hourly. For work I can't honestly scope up front, like an audit, a performance investigation or a codebase nobody documented.

Who this tends to suit

• Teams without a backend engineer who need one for a set stretch of work
• Agencies that want a build partner who'll talk to the client directly when that saves a round trip
• Businesses that inherited a codebase nobody maintained and need it stable before it grows
• Founders who have a validated idea and a spec, and need a first version built from it