One path, three stages

I take on ageing PHP and Laravel platforms and get them back under control. It happens in three stages, in order.
You do not have to commit to the whole journey. You just have to start it.

Three stages, not a menu

Every ageing platform goes through the same journey: first find out how bad it is and stop the bleeding, then rebuild what needs rebuilding, then keep it healthy. These are not three services to choose between. They are the stages, in order. Each one sells the next: the audit scopes the modernisation, the modernisation ends with a platform worth maintaining, and the retainer is the relationship that keeps it that way. You do not have to commit to the whole journey. You just have to start it.

1
Secure — the Platform Audit
Stage 1 of 3

Secure — the Platform Audit

The smallest safe first step. A fixed-price, fixed-scope review of your codebase, security, and server, delivered as a plain-English report with a prioritised, costed action plan. £1,950, within two weeks. Even if you never hire me again, you walk away knowing exactly what you own and what it needs.

Start with a Platform Audit
2
Modernise — legacy PHP to Laravel
Stage 2 of 3

Modernise — legacy PHP to Laravel

Scoped from the audit, never guessed at from a distance. Using the Strangler Fig pattern, old and new run side by side, so your users see no disruption. Zero-downtime deployment with automated rollback. You end up with a modern Laravel codebase, tests, documentation, and no vendor lock-in. The result is confidence, not fear.

See Modernise
3
Maintain — the ongoing retainer
Stage 3 of 3

Maintain — the ongoing retainer

Where the journey lands. A dedicated technical partner who monitors your infrastructure and deals with issues before they become outages. Proactive monitoring, dependency and security updates, monthly reporting, and named response times. £500 a month.

See Maintain

Common questions

Answers to what people usually ask before they start.

What happens after launch? Do you offer ongoing support?
Yes. Most clients move onto a monthly support arrangement after their project goes live. This covers ongoing development, updates, security monitoring, and someone to call when something needs attention. For WordPress sites, this includes testing all core, plugin, and theme updates in a local environment before applying them to your live site. For Laravel and PHP platforms, it means a dedicated block of time each month for bug fixes, small improvements, and proactive maintenance. You're not left to fend for yourself after handover.
What is your development process?
What's the difference between WordPress and Laravel? Which is right for my project?
WordPress is a content management system built for websites. It's ideal if you need your team to manage pages, blog posts, and media without technical help. It has strong SEO tooling, a familiar admin interface, and a huge ecosystem of plugins. Laravel is a PHP framework for building custom web applications. It's the right choice when you have specific business logic, complex data relationships, or workflows that off-the-shelf software can't handle. If you're not sure which fits your situation, tell me what you're trying to achieve and I'll give you an honest recommendation. I build both, so I have no reason to push you towards one over the other.
Where are you based, and do you work with clients outside Sheffield?
I'm based in Sheffield, South Yorkshire, but work with clients across the UK, and most of my work is done remotely. I've built and supported platforms for businesses in London, Edinburgh, and throughout the North of England. Location is rarely a barrier. If you'd prefer a face-to-face meeting, I'm happy to travel for the right project.