Help for owners
The code I paid an outsourced team for is poor quality
Short answer
Bad code shows itself as bugs that keep returning, small changes that take a long time and no tests or notes. Before paying more, get an independent written review of what was delivered, compared with the brief. It tells you whether to repair, rework part of it or rebuild, and gives you a fair basis to talk to the outsourcer.
Does this sound like your situation?
- The same bugs come back after each fix.
- Every small change takes the developer much longer than it should.
- It does not do what the brief and the demo promised.
- A new developer looked at it and said it needs a rewrite.
- There are no notes, no tests and no clear way to build it.
Why does this happen?
The brief was loose, so the result is too
A vague scope lets the outsourcer build the easiest thing that looks right in a demo. It looks finished on the surface and falls apart in real use.
Speed was paid for, quality was not checked
A project run to a deadline with nobody reviewing the code collects shortcuts that surface later as bugs.
Nobody on your side could judge the work
Without a technical person to review it, a delivery is accepted on how it looks, and the problems appear in production.
Libraries and the build were left outdated
A project delivered with old or unsupported parts can break when the platform moves on, and each update then takes longer than it should.
Technical detail: Gradle says deprecated features were used and the build will break on the next major version
What can I do about it today?
- Stop adding scope and money for nowMore features on a weak base make a later repair harder. Pause paid work until you have a review.
- Collect the brief, the quote and what was demonstratedThe review has to compare what was delivered with what was agreed.
- List the problems as users experience themScreens that fail, steps that break, slow places. A list in plain words with dates is enough.
- Keep a copy of the code and the live system as deliveredAsk for the repository, with its history, before relations sour.
- Read your contract on defects and fixesLook for any period in which the outsourcer must repair defects. If money is in dispute, ask a lawyer.
- Get an independent reviewSomeone not paid by the outsourcer should read the code and report in writing.
When should I bring someone in?
- The product is live and failing customers.
- You are about to pay another milestone and doubt the work.
- You need to decide between repair and rewrite.
How do I handle it?
- Review against the briefI read the code, run it and compare it with the agreed scope, and report in plain language what works, what is risky and what is missing.
- Sort the findings by riskProblems that lose money or data come first, then those that slow every change, then style. Parts that work are kept.
- Give you options with reasonsRepair, rework a part or rebuild, each with what it means, so you can talk to the outsourcer with a written basis.
- Do the repair in small, tested stepsEach change is released on its own, with a backup and a way back, so the product keeps running while it improves.
The price depends on what I find, so I quote in writing after a short discovery call. Tell me what is happening and I reply within 24 hours.
What do owners ask about this?
Is it always better to rewrite?
No. A rewrite is a large piece of work and can repeat old mistakes if the brief stays loose. Many products can be repaired in parts.
Can I claim against the outsourcer?
That depends on the contract and your country. A written review is useful evidence, but please ask a lawyer.
Will you review code you did not write?
Yes. A review of someone else's code against your brief is a normal first step.
How was this page made?
I drafted this page with AI assistance. It is general guidance for business owners, not advice for your own system. Found a mistake? Tell me.
For your developer: the technical fixes
Deprecated Gradle features were used in this build, making it incompatible with Gradle 10.Gradle says deprecated features were used and the build will break on the next major versionYour project is configured to compile against Android SDK 35, but the following plugin(s) requireFlutter says plugins need a higher compileSdk or a different NDK