Claude vs ChatGPT for developers: lessons from real ERP builds
Claude or ChatGPT? A working developer's comparison, including how we built X3 Retail ERP with parallel Claude Code agents that learn from their own mistakes.
Read articleSoftware Rescue: We Take Over What Others Left Broken
Abandoned vendors, vibe-coded prototypes and legacy systems past their limit. We take these over, get them stable first and modernise from there.
What's included
- Codebase rescueGetting a prototype ready for production
- Vibe-coded app rescueApps generated with Lovable, Bolt, Replit or Cursor, made safe for real users
- Vendor replacementZero-downtime handover
- Legacy system rewriteModernise without disruption
- Performance remediationDatabase, caching and infrastructure
Read before you write
Rashid Kadura hired us to add a payment gateway to Beyut Libya, his property marketplace. Before writing a line of it, we read the code several earlier teams had left behind. The app and website weren't properly connected to the API, the server was one machine updated by hand, and the code was too tangled to grow. Adding payments on top would have meant decorating a building with a cracked foundation. We told him that first, on a call, in his own code. Then we rebuilt the platform without losing a single listing, and only then connected the payments.
That order, read first, stabilise second, build third, is the whole method. The Gman tailoring ERP came to us as a PHP and Vue app nobody could maintain; after the rebuild it responds about 70% faster, and the client changes business settings without calling a developer. OpenInterview.me arrived as a prototype that couldn't safely take a payment; it now runs Stripe billing in production. And when a hospital's vendor stopped answering, we replaced the system in six weeks without the hospital closing for a day.
Nobody calls us when things are going well. That is fine. Rescue work is a large part of what we do, and the first thing we give you is a straight answer about what you have.
Rescuing a vibe-coded app
Tools like Lovable, Bolt, Replit and Cursor can produce an app that demos well in a weekend. The trouble starts with real users and real money. These are the problems we check for first.
- Security in the browser only. Rules enforced on the screen but not on the server, so anyone with the API address can skip them.
- Secrets in the frontend. API keys and database credentials shipped to every visitor's browser.
- Open database rules. Tables any signed-in user can read or edit, including other customers' data.
- Payments that can double-charge. No idempotency, so a retry or a repeated webhook charges twice.
- No tests, no logs. Nothing tells you what broke or when, until a customer does.
Most of these apps don't need to be thrown away. They need the foundations a prototype skips.
How a rescue runs
The same five steps, whether the code came from an agency, a freelancer or an AI tool.
- AccessSource code, servers, domains, store accounts and payment dashboards handed over and secured.
- Written auditWhat works, what is risky and what is broken, walked through on a call in plain language.
- StabiliseBackups, monitoring, and the fixes that stop data loss or lost money, before anything new.
- Fix or rebuild, decided togetherPart by part, with the reasons written down. Often it is a mix.
- Build forwardNew features on a base that can carry them, with a working demo every week.
Fix it or rebuild it?
The question every rescue comes down to. These signs usually decide it.
| What we find | Usually means |
|---|---|
| The core data model is sound, the code around it is messy | Fix and refactor in place |
| Each fix breaks something unrelated | Rebuild the worst parts first, keep the rest |
| The framework or language is no longer supported | Planned rewrite, moved over module by module |
| Nobody can deploy it safely | Fix deployment first, then decide on the code |
Built and running
Beyut Libya: Real Estate Marketplace Rescue
0 listings lost in the rebuildRead case study
EHMS: Hospital Management System
95% faster core workflowsRead case study
OpenInterview.me: Hiring Platform
Rescued from prototype to productionRead case study
Gman Stitching Platform
70% faster response timeRead case studyCommon questions
Can you take over a project someone else started?
Yes. We have turned unstable prototypes into dependable payment platforms and replaced a hospital's system after its vendor would neither update it nor fix its issues. We assess first, stabilise, then build.
How do you avoid disrupting a system people use daily?
We plan the switch around how people actually work, move and check the live data ourselves, and stay on site when it goes live. At the trust hospital in Chishtian we moved the data and the staff onto the new system in person, and the hospital did not close for a single day.
Can you rescue an app built with Lovable, Bolt or Replit?
Yes. The method is the same as for any inherited code: get access, audit, secure the data and payments, then decide part by part what to keep. Many of these apps need their foundations fixed, not a full rebuild.
What if we don't have all the source code or accounts?
Getting access back comes first: the code repository, servers, domain, app store and payment accounts. The written audit lists anything missing and the safest way to recover it.
What does a rescue cost?
It starts with a written audit, so the price of the work is based on what is actually there instead of a guess. After the audit you get a plan with options to fix, rebuild or mix the two.
Ready to scope your rescue & modernization project?
Answer three quick questions and we'll send a written plan covering scope, team, timeline and estimate.
Articles on this
AI-native software development: how our AI agents build and senior engineers check
AI-native software development, from real projects: specialised AI agents write the repetitive code, and senior engineers own architecture and every release.
Read article
The Vibe Coding Doom Loop: Why Your Lovable or Replit App Breaks Every Time You Fix It
Fix one bug in your Lovable or Replit app and ten more appear? Why the vibe coding doom loop happens, the prompts that prevent it, and when to call an engineer.
Read article