Services
I take over web apps that are stuck and ship the next release.
The developer left, the prototype won't hold up with real users, or the team can't keep up. I read the code, tell you what is solid and what is risky, then ship the next release.
Get in touch
Is this for you?
You built the first version with an AI tool such as Lovable, Bolt or Cursor. It works in the demo, but sign-in, payments or data break once real customers use it.
The developer who built your app stopped replying, or left, and nobody else knows how it runs.
You have a working product with real users and a backlog that keeps growing.
An agency handed over a repository and you can't tell whether it is in good shape.
You have one in-house developer and need a second pair of hands who can start without a long handover.
Not what you need if you want a brand-new product built from nothing. MVP development covers that.
What you get
A one-page audit first
I read the code, the deployment and the data model, and I run the app. You get one page in plain words. It says what works, what could hurt your customers, whether I'd keep, fix or rebuild, and the fixes in order with a price for each. You can forward it to a co-founder or investor as it is.
You can stop after the audit
The audit has a fixed price. If you stop there, the note is yours to keep and to give to any developer.
Access stays in your name
The repository, hosting, domain and other accounts stay yours. I'm added as a guest.
Nothing goes live without your OK
Fixes go in as pull requests you can read, or have someone read for you. If the deployment isn't safe yet, they go to a staging copy first.
A short update every working day
A few lines at the end of each day on what I did and what comes next.
Notes as I go
How the app runs, how to deploy it and what I changed, so the next developer can start fast.
What the first two weeks look like
Week 1
Access, audit and a plan
Read access, a local copy, the audit and a short call to go through the note. We agree what to fix first, or you stop there.
Week 2
First fixes and first feature
The first fixes and the first small feature, shipped to production if the deployment is safe to use, or to a staging copy if it isn't.
Relevant experience
Since 2022 most of my work has been in codebases other people set up. The largest was caisy's CMS editor, a repository with more than 5,000 commits. I read the data model first, then traced one feature from the screen through the API to the database before I changed anything. At caisy I also built features on Next.js, tRPC and Drizzle codebases, including schema and migrations for Stripe billing and subscriptions.
On an AI platform for real-estate investors, I audited the live frontend, ranked the problems by how much they hurt users and fixed them in that order. Users whose login had expired used to land on an empty page with no way back to sign-in. One shared handler now catches that on every page. The audit case study has the rest.
On ScriptBee's Next.js app, agent runs took two to ten minutes and were lost if a user refreshed the page. I moved them to background tasks that keep going after the tab closes. The ScriptBee case study has the details.
How we work and what it costs
Most of the apps I have taken on were TypeScript, React and Next.js, with Node.js and PostgreSQL behind them.
The audit has a fixed price, and you can stop after it. If you want me to carry on, I price the first fixes per phase. After that we agree a monthly retainer or a price per task, depending on how much you need me.
Tell me what the app does, which stack it uses and what has gone wrong, and I'll reply with next steps.
Questions people ask
The developer who built our app left with no documentation. Can you take it over?
Yes. I start with read access to the repository and the hosting, run the app locally, and write the missing documentation as I go: how it runs, how it deploys and where the risks are. The audit tells you what is solid before anything changes.
Can you fix an app built with Lovable, Bolt, Replit or Cursor?
Yes, if the code can live in a repository you own. I treat it like any app someone handed over. I read it and check sign-in, data access, payments and deployment against what real customers will do, then fix the riskiest parts first. Sometimes keeping the code is right and sometimes a partial rebuild is cheaper. The audit tells you which before you pay for either.
How long does the first audit take?
It depends on the size of the app. I look at the repository and the deployment first, then tell you how long the audit will take before I start. For a small app it's a few days.
Do I need to give you access to everything on day one?
No. I start with read access to the repository and the hosting dashboard. Production data, payment keys and admin accounts stay with you until we agree what I need and why.
Will you break the app for our current users?
Nothing goes to production without your OK. If the deployment isn't safe to use yet, I fix that first and ship to a staging copy until it is.
What if the code is a mess?
Messy code isn't always broken code. The audit lists what is actually broken and says what to keep and what to fix. Nothing gets rewritten until we agree on it. Fix or rebuild covers how I decide.
Can you work next to my other developer?
Yes. I work in the same repository through pull requests, follow the conventions already there and write down what I change. Your developer or CTO decides what I work on.
We're an agency. Can you take over a client's app for us?
Yes. I work under your brand and in your tools, and I never contact your client. The audit has a fixed price, so you know your margin before you quote.
What do I own at the end?
Everything. The code, the repository, the hosting accounts and the notes stay in your accounts. I work in them as a guest.
Related articles
What an app audit should tell you before you pay for fixes
What a short audit of a stuck web app should give you. One page in plain words, the risks to your customers, keep, fix or rebuild, and the fixes in order.
Fix or rebuild? How to decide on an inherited web app
A way to decide whether an inherited web app should be repaired or rewritten, with the signs that point each way and a safer middle path.
How to take over a codebase from a developer who left
A checklist for taking over a website or web app from a previous developer, from getting access to shipping a first change without breaking production.
Other services
Build AI features and agents
Chat interfaces, agent tools and background tasks that call a model, built into a real product with accounts, data and deployment.
Build an MVP
One developer from first commit to launch. A small, working first version of your product that real users can try.
Build your web app or website
A site or app with a real back end, with accounts, a database, forms, payments and an admin side. Built, deployed and explained.
Arabic and bilingual web apps
Real right-to-left layouts, Arabic and English together, forms and numbers that behave. Built by a native Arabic speaker.