Skip to main content

Independent Laravel consultancy for complex applications.

I’m a Laravel consultant for engineering teams whose application has become hard to change. I bring backend and platform architecture experience in multi-tenancy, event-sourced systems, modular design and secure AI-assisted engineering to complex Laravel applications. Start with an architecture review, bring me in hands-on, or keep me on as an adviser.

What I help with

  • Growing coupling

    When a small change touches too much of the application, I help draw clearer domain boundaries and untangle it step by step.

  • Tenancy in an established product

    Adding tenancy to a live product built for a single tenant, while protecting existing behaviour.

  • Architecture rules nobody enforces

    Turning agreed architectural decisions into practices the team can check in code.

  • Safe AI-assisted development

    Helping teams use AI coding tools safely, with shared guidance, careful access boundaries and human review.

  • Security during design

    Considering security while the design is still being shaped, not only in a review at the end.

How I help

I work in three ways, from a one-off review to ongoing advice.

  • Architecture review

    A short, written assessment of your foundations that ends in a prioritised plan your team can run without me.

    How it works (Architecture review)
  • Foundations engagement

    Hands-on work with your team to put the foundations in place: boundaries, quality gates, secure practice and decision records.

    How it works (Foundations engagement)
  • Advisory

    Ongoing design and security reviews and RFC support, for engineering leaders who want a second opinion they can rely on.

    How it works (Advisory)

Selected work

A few anonymised examples of my work.

  1. Making architecture easier to maintain

    I’ve written proposals for clearer domain boundaries and helped turn architectural decisions into practices teams can check in code.

    • Modular design
    • Architecture

How I work

  1. Understand the business constraint.

    I start with what the business needs the system to do next.

  2. Change the system in small, reversible steps.

    Each step can ship on its own and be undone, with no big-bang rewrite.

  3. Write decisions down and prove them in code.

    A written proposal sets out the options, and checks in code keep the decision in place.

Latest writing

Notes on Laravel architecture, platform engineering, security and AI-assisted development.

  1. Strangle, don't rewrite: moving a live system onto a new tenancy model

    4 min read

  2. Baselines that only shrink: freezing technical debt without pretending it's gone

    5 min read

  3. The Dark Side of Caching: Don't Hurt Your Laravel App

    9 min read

Working on a complex Laravel application?

A few lines about your Laravel application and what is slowing your team down are enough to start. I reply within 2 working days.