Accounts and permissions
Proper sign-up, login and roles, so each customer, member or member of staff sees only what they should.
Building a prototype with AI tools is usually the straightforward part. Hosting it, keeping it secure and moving it forward without breaking what already works is where the effort goes.
I take prototypes and proofs of concept and turn them into systems you can run, maintain and grow.
Getting a working prototype out of an AI tool is now quick. Most of the cost and effort of software comes afterwards, once people depend on it.
It needs hosting, security updates, backups and monitoring. Every new feature has to be added without breaking the ones that already work. A prototype is rarely built with any of that in mind, and that is the part I take on.
A prototype proves the idea. These are the parts that tend to be missing or fragile once customers and staff rely on it.
Proper sign-up, login and roles, so each customer, member or member of staff sees only what they should.
Data structured so it stays correct as the number of users, records and features grows.
Inputs checked, secrets kept out of the code and access locked down, before anyone finds the gaps for you.
Billing, email and connections to the other systems you rely on, built to cope when something fails.
Backups, error tracking and updates in place, so problems are caught before your customers notice them.
A codebase that can be changed safely next year, by me or by any other developer.
A working prototype is the best brief I can get. It shows the screens, the flows and the ideas you have already tested, which saves a lot of guesswork.
I start by reviewing what you have. Where the code is sound, I keep it and build on it. Where it is not, I rebuild those parts properly. Sometimes starting the core again is cheaper than patching it, and if that is the case I will tell you before any work begins.
It starts with a free 30-minute call. Show me the prototype and tell me where you want to take it.
If we decide to go ahead, I review the code, data and hosting, and write a plan for what to keep, what to rebuild and what to add, with a fixed price for the first stage. From £1,600 + VAT.
Each stage is agreed and priced before it starts, with a private staging site throughout and a demo and sign-off at the end of each stage.
Hosting, updates, backups and monitoring, plus time each month for changes and improvements. Plans from £250 + VAT a month.
I use AI tools every day. They speed up the routine parts of building software, like boilerplate, tests and first drafts, so more of your budget goes on the parts that matter.
What they do not replace is judgement: how the data should be structured, what needs to be secure, and what will still make sense in five years. Every line I ship is reviewed and tested by me, and I am responsible for it.
It does not matter much which tool built the prototype. Whether it came from Lovable, Bolt, Replit, v0, Cursor or a developer using ChatGPT, what I review is the code, the data and how it is hosted.
It depends on the project. I start with a proper review of what has been built, then build it in the way that makes most sense for where it is going. I usually work in Laravel and Vue, but if a React or Node.js stack genuinely suits the project better, that is what I will recommend.
Not necessarily. Once the idea is proven and customers or important data are on the way, that is a good time to talk. The longer a prototype grows, the more there is to untangle.
Yes. The same approach works for an internal proof of concept, a spreadsheet-driven tool or an early version built by someone who has since moved on.
Send me a link or a short outline of what you have built. The first call is free and there is no obligation.