Working with Claude Code and other AI Agents (there are plenty of them!), I turn an idea into a deployed, working tool in days. The part that takes longer to learn is what to do before, around, and after the code: the business risk, the data, the legal edges. I do both.
React, Vite, Airtable, Vercel, Render. Real deployments at live domains, not prototypes that stall in a folder.
Speed is useful only if the thing it produces can be trusted with real users and real data on day one.
Email capture, onboarding flows, anything that takes information from a person and stores it somewhere.
If you handle personal data in the UK you likely need to register with the ICO and pay the data protection fee. I check this before launch, not after a complaint.
Resend, Stripe, calendar and automation integrations wired in so the app actually does its job end to end.
Lawful basis, consent where it is needed, data minimisation, retention, and a clear answer to where every record lives and who can reach it.
DNS, environment variables, CORS, deploy pipelines. The unglamorous plumbing that decides whether a thing stays up.
Secrets kept out of the client, origins locked down, cookie and tracking choices made on purpose rather than by default.
Most people who can wire up an app cannot tell you whether you are allowed to launch it. Most people who understand the legal and commercial side cannot build the thing. The gap between those two is where projects get expensive, slow, or quietly exposed.
I have run the business side for years: governance, committees, contracts, risk. I know how to read a situation and ask the question nobody else in the room is asking. Does this collect data we are responsible for. Who is liable if it breaks. What happens to this information in two years.
When I build something for you, those questions are already answered, because I was the one building it. You get one person accountable for the whole picture, instead of a developer who hands you a working app and a problem you did not know you had.
What personal data does this touch, where does it sit, and who can get to it.
Whether registration and the data protection fee apply, and getting it in place if so.
A privacy policy that matches what the app actually does, with consent handled where the law asks for it.
Secrets, origins, and permissions reviewed so the easy mistakes are closed off.
How long data is kept, how it gets deleted, and how someone hands the project on.
A written record of the choices made, in language you can read without me in the room.
Tell me what you want it to do and who it is for. I will tell you what it takes to build it, and what it takes to launch it without leaving a mess behind.
Email me