Django Developer, UK Based
Software development for founders who need it running, not just written.
Most of my work happens in the final 20% of a project. The part where software becomes a product. I take systems from wherever they are and get them into production. Properly.
Tell me about your project
The problem I solve
There's a gap between code that works and software that runs.
Ideally, I'm involved from the start — taking an idea from first conversation through to a live, working product. Those are my favourite projects. But it doesn't always happen that way, and that's fine. A lot of my work starts somewhere in the middle.
You hired a developer and got a repository.
The code might even be good. But it's not live, it's not monitored, and every time you ask about deployment you get a different answer. You've paid for something you can't use yet.
You built it yourself with AI tools and it's "nearly ready."
It demos well. You can show people. But when you try to deploy it, or hand it to someone technical, things start unravelling. Missing migrations. Secrets stored in code. Incomplete error handling. Authentication that works in testing but struggles in production. The gap between 80% and production-ready turns out to be most of the work.
You inherited something messy.
Maybe you bought a business, maybe a co-founder left, maybe a contractor disappeared. You've got a system that sort of works and no real understanding of what's holding it together.
All three of these are solvable. They're also exactly the kind of problem I work on.
What I bring
Before becoming a developer, I spent 15 years running a heavily regulated business, and I've been running businesses of one kind or another since 2008. I care about reliability, auditability, compliance, and systems that still make sense six months after launch.
I came to Django development after watching what happens when software meets reality. Real users, real pressure, real consequences when things break. That means I think about your system the way you do: what breaks under load, what an auditor will ask for, what happens when a user does something unexpected, and what you'll need to change in 18 months.
I take projects from conception to deployed, and I specialise in the part most developers skip. All of my work is done remotely, and I use the right tools to make sure communication and progress tracking are clear throughout.
- Django systems built for production from day one
- Assessing and rescuing AI-assisted or rapidly-built MVPs
- Taking over stalled or abandoned work and getting it over the line
- Compliance, audit trails, and regulated environments
- Subscription platforms, community platforms, and anything with real users doing real things
- Deployment, monitoring, and the operational reality of running software
Recent Projects
Work that's built, deployed, and running.
Community Platform • Live
High Mile Heroes
A community platform for high-mileage car enthusiasts, with active entries and real users. Built around engagement and community ownership, reducing reliance on social media platforms. The hard part was building something the community would actually use.
Visit site →
Subscription Platform • Live
Cosmic Lessons
A subscription platform built from scratch: authentication, payments, content delivery, and deployment. The difficult part wasn't any single feature. It was making them work as a coherent system that a non-technical founder could actually operate.
Visit site →
Personal Platform • Live
LJ Talks
A personal content and writing platform. Built, deployed, and maintained independently. Demonstrates the full stack from design to production hosting.
Visit site →Regulated Environment • Private
Building Safety Platform
A compliance and audit system for building management. Required careful thinking about data integrity, audit trails, and what "done" actually means when inspectors and insurers are involved. Happy to discuss the work if you're building something in a similar space.
How I Work
A straightforward process.
Most projects start with a conversation. Sometimes you have a working system that's stuck. Sometimes you have a folder of code and a list of unanswered questions. Sometimes you're not entirely sure what's wrong. All of that is fine.
1. Initial conversation
You tell me what you're building, where you're stuck, and what success looks like. I'll ask questions, and I'll be straight with you about whether I think I can help.
2. Technical review
I look at the code, infrastructure, deployment setup, and operational risks. The goal is understanding reality rather than assumptions.
3. Plan and proposal
You'll get a clear explanation of what's needed, what's risky, what's already working, and what it'll take to get where you want to go.
4. Build, fix, deploy
This is where the work happens. Features, infrastructure, deployment, monitoring, testing, documentation. Whatever the project actually needs.
5. Handover and support
The goal isn't just working software. It's software you understand, can operate, and aren't afraid of six months later.
About
I'm Laura.
I've been running businesses since 2008 and building Django systems seriously for the last several years. I'm based in the UK.
I work with founders and small teams who need someone who can own a difficult technical problem end to end. Not just write code to a spec, but think about what the system actually needs to do and make sure it does it properly.
I like the kind of work that requires real thinking. Messy starting points, unclear requirements, systems that need unpicking before they can move forward. That's usually where I do my best work.
If something's stuck, broken, or never quite made it to launch, let's talk.
FAQ
Questions I get asked.
Why Django?
Django is what Instagram, Pinterest, and Spotify are built with. It's a mature, battle-tested framework that comes with user authentication, an admin dashboard, and security protections built in — so you're not paying me to reinvent things that already work.
For you, that means a faster build, fewer security risks, and a system that can grow with your business. You fully own the code, it runs on standard hosting, and any competent Python developer can pick it up if we stop working together. No vendor lock-in, no proprietary platform you're stuck with.
What can you build?
Anything that needs users, data, or business logic behind it. That includes booking and scheduling systems, customer portals, payment integrations, internal admin tools, compliance platforms, and membership sites. If your project needs a database, authentication, or an API, it's likely a good fit.
For simpler needs — a marketing site, a landing page, a blog — I'll use WordPress where it's the right fit, or clean HTML and CSS when it isn't. No unnecessary frameworks, no bloat. Everything works on mobile, loads fast, and is built with security in mind from the start.
Do you use AI in your development work?
Yes, daily — it helps me work faster and catch things I might miss. But I treat it as an assistant, not a replacement for knowing what the code does and why.
The reason this matters to you: a lot of systems are being built right now with no-code and AI tools by people who can't debug them when something goes wrong. That's fine for a prototype, but if real users, real payments, or real data are involved, you need someone who understands what's underneath. I use AI where it genuinely helps, and I always stand behind the code it produces.
Can you rescue a project that's stuck or broken?
That's a large part of what I do. Whether it's an MVP that was never finished, a deployment that keeps failing, or a codebase that the previous developer left in a state, I'm comfortable picking up other people's work and getting it to a place where it actually runs and can be maintained.
The first step is always an honest assessment — sometimes it's fixable, sometimes it's faster to rebuild parts of it, and I'll tell you which.
What happens after launch?
You're not left on your own. I make sure you understand how to operate what I've built — what to monitor, how updates work, and where to find things. If you want ongoing support, I'm available for that. If you'd rather bring someone else in, the code is clean, documented, and built on standard tools that any experienced developer can work with.
The goal is software you're confident running six months later, not something you're afraid to touch.
How much does a project cost?
It depends on the scope. A small fix or deployment might be a few hours of work. A full build or rescue project could be several weeks. I'll always give you a clear idea of cost before any work starts, and I won't let a bill grow without talking to you first.
If the budget doesn't stretch to everything at once, I'll be upfront about that — and I'll help you work out which steps to take first so you're making real progress with what you have. Not every project needs to be done all at once to move forward.
The best way to get a realistic answer is to describe your project and I'll come back with an honest estimate.
Hire me
Tell me about your project.
I take on a small number of projects at a time. If you've got something that sounds like the work above, including if you're not sure whether it's salvageable, the best thing to do is describe it. I'll give you an honest answer.
I'll respond within a couple of days. If it sounds like a fit, we'll find a time to talk.
This form sends your name, email address, and project summary to my inbox so I can reply. See the privacy policy.