When a project needs more than a content site, I build the whole thing: database, business logic, APIs and the interface on top. Usually Laravel or Node on the server, React or Vue on the front, chosen to fit the problem rather than out of habit.

What's included

  • Database design that reflects how the business actually works.
  • REST APIs, or Inertia where the only consumer is your own frontend and a separate API would be pure overhead.
  • React or Vue interfaces built as components rather than pages.
  • Third-party integrations: payments, CRMs, ERPs, AI APIs.
  • Authentication, roles and permissions done properly.
  • Deployment and CI so releases are routine rather than an event.

How it works

01

Model the domain

Get the data model right first. Almost every painful web app is one with a data model that did not match reality.

02

Build in slices

End-to-end vertical slices you can actually use, rather than a backend that works in theory for three months.

03

Ship and iterate

Deploy early to a staging environment so feedback arrives while changes are still cheap.

Recent work

Frequently asked questions

Should I build a web app or use WordPress?

If the core of what you need is content with some functionality attached, WordPress is usually the cheaper answer and I will say so. If the core is behaviour, workflow and data, forcing that into WordPress costs more than building it properly.

Laravel or Node?

Both are fine. Laravel if the work is data and business logic heavy with a conventional web frontend, Node if you are already in a JavaScript ecosystem or need heavy realtime. The wrong reason to choose either is fashion.

Get in touch

Want to know more about me, tell me about your project, or just say hello?

Drop me a line and I'll get back to you as soon as possible.