AI-generatedLaravel upgrades
I’m DC, a freelance Laravel developer in the UK. An application on Laravel 10 goes to 11, then 12, then 13, and each step can surface a package that hasn’t kept up. Automated tools handle much of the framework’s own changes; the time goes on your dependencies and your own code, which is why an upgrade is priced after reading the dependency list.
13
March 2026 · latest
12
February 2025
11
March 2024
10
February 2023
Dates follow Laravel’s published support policy. Symfony and Drupal projects are extended where they already run rather than rewritten, and Django and FastAPI cover the Python side.
In his words
Four lines from the quote library. It moves on by itself and stops while you read.
So now it’s just me. No politics, because there’s nobody to play them with. No selling you hours you don’t need.
Bespoke work, by job
Software that fits no platform: written for the job, by a freelance Laravel and Django developer who designs it and then builds it.
Freelance Laravel developer
Customer portals, admin systems, booking and ordering tools, and the back end of SaaS products. Laravel is where most of my bespoke work happens, with Filament for admin screens so staff get a working interface early, and tests on the parts that move money or data.
Django developer
Django earns its place when a business needs a data-heavy application with a proper admin: back-office systems, customer portals, reporting, and APIs other systems call. Its built-in admin gives staff a working interface to the data from day one. On the Python side I also build with Django REST Framework and FastAPI, and bring older Django projects up to a supported release.
Freelance WordPress developer
WordPress sites built properly: a custom theme without a heavy page builder, custom post types and fields for the content the business actually has, and bespoke plugins for the features no plugin offers, written to WordPress’s own standards so they survive updates. Headless WordPress with a Next.js front end where speed and security matter most.
Laravel upgrades and support
An application on an unsupported Laravel version stops getting security fixes. Upgrades go one major version at a time, and the time goes on your packages and your own code rather than the framework, so the work is priced after reading the dependency list. Ongoing support keeps an application patched and its PHP version current.
APIs
An API so a store, a mobile app or a partner can use data that is currently locked in a spreadsheet or an old system. Built in Laravel, Django REST Framework or FastAPI, with authentication, rate limits and documentation someone else can follow.
Symfony and Drupal
Where a project already runs on Symfony, or on Drupal which is built on it, I work within it rather than rewriting it: new features, upgrades, and the integrations around it.
Internal tools
The spreadsheet that runs the business, emailed round and edited by three people, turned into a small application with a proper database, permissions and a history of who changed what. Often the quickest return of anything on this page.
Yes. The first step is reading what exists and telling you honestly what state it is in, before anything is changed.
It depends on the packages you use more than the framework. I read the dependency list first, then price and plan it one version at a time.
Either can build most applications well. It usually comes down to what your team already knows, and whether the product leans on Python’s data libraries.
You do, from the first commit, in repositories and hosting registered to you.
UK based · PHP · Python · JS · TS. Every first call is free.