The red flags are a firm price before any assessment, a rush to rebuild everything, vagueness about what you will own, casual handling of your data and keys, defensiveness when questioned, and pressure to pay it all up front. Any one warrants caution. Several together are a clear signal to keep looking, however appealing the price.
Information current as at 5 July 2026
Most developers are honest and capable, but the stakes of getting it wrong are high enough that knowing the warning signs is worth your time. None of these on its own proves bad intent, but each is a reason to slow down and ask more, and several together are usually your instinct telling you something true.
The most common red flag is a confident, fixed price for finishing your app before anyone has properly assessed it. As covered elsewhere, an honest quote needs a look under the hood, because the true cost depends on things you cannot see from outside. A firm number offered too early is either a guess that will drift upward or a lure to get you committed. It is not reassuring, it is a warning. The reassuring version sounds like "let me assess it first, then I can price it accurately", which puts your interests ahead of a quick close and shows the partner respects how the work actually gets scoped.
Be wary of anyone whose first instinct is to declare your entire build worthless and start again. Sometimes a rebuild genuinely is right, but it is also the most profitable and least demanding path for the person quoting, so it should be argued for with specific reasons, not reached for by default. A partner who cannot point to which exact parts are salvageable and which are not, and why, is either being lazy or is not looking closely. Your existing work has value. Dismissing all of it wholesale, without engaging with what actually works, is a sign they are pricing their convenience rather than your need.
If you have made something and it needs to become real, send it over. We will tell you honestly what it needs to be live, safe and yours, whether that is a quick fix you can do or a proper build. No obligation.
Watch closely when you ask what you will own and how your data will be handled. A trustworthy partner answers these plainly and even volunteers reassurance. Vagueness, deflection, or an implication that you would never want to leave them is the sound of lock-in being built in. The same goes for security: if they are casual about your secret keys, happy to have passwords pasted into a chat, or wave away the question of exposed data, that carelessness is exactly the problem you are hiring them to solve. How someone treats your ownership and your data before payment predicts how they will treat both after.
The behavioural flags matter as much as the technical ones. Pressure to decide quickly, irritation when you ask reasonable questions, and a demand for full payment before any work is delivered all point the same way. A confident, fair partner is comfortable being questioned, works in stages with checkpoints, and is open to structures like staged payments or escrow that protect you if things go wrong. Someone who resists all of that, who wants your trust and your full fee before proving anything, is asking you to carry all the risk. When the manner is off, believe the manner, because it rarely improves once the money has changed hands. The way a person treats you while they are still trying to win your business is very often the best version of how they will treat you, so if that version already includes pressure or defensiveness, take it as a preview rather than a first impression to be argued past.
If you have made something and it needs to become real, send it over. We will tell you honestly what it needs to be live, safe and yours, whether that is a quick fix you can do or a proper build. No obligation.
Whether you can name exactly what you want built, or you just know something is leaking, the next step is the same conversation.