Questions to ask before paying anyone to fix your app

You do not need to be technical to vet someone well. You need a short list of pointed questions and the patience to listen to how they answer. The content of the answer matters, but so does the manner: a good partner welcomes these questions, because they are the questions a careful client should ask.

Questions about how they start

Ask what they will do before they quote a fixed price. A good answer involves assessing your actual app: reading the code, checking the data, finding the risks. Ask how they arrived at their estimate, and whether it could change. Anyone willing to name a firm price for finishing your app without looking at it is either guessing or planning to revise it upward later. You want a partner who treats the assessment as a real step, priced modestly or even free, and who can then explain the fuller quote in terms of what they actually found. How they begin tells you how they will continue.

Questions about ownership and lock-in

Ask, plainly, what you will own at the end. Will the code sit in your accounts? Will the data be under your control? If you and this partner parted ways in six months, could someone else pick it up? The answers reveal whether they build to hand over or build to keep you dependent. A confident, ownership-first partner answers these easily and even volunteers reassurance. Hesitation, or an implication that you would not want to leave, is the sound of lock-in. This is the question people most often forget to ask before paying, and the one they most often regret skipping. If you take only one question from this list into your next conversation, make it this one, and do not accept a vague answer, because vagueness about ownership almost never resolves in your favour later.

Questions about your data and security

Ask how they will handle your secret keys and your customers' data during the work, and what they will do about anything they find exposed. A serious partner has a clear answer: they use proper, revocable access, they never need your raw passwords pasted into a chat, and they treat an exposed key as urgent. If security seems to be an afterthought in their answer, or they wave it away, that is telling, because casual handling of data is exactly the problem you are hiring them to fix. How they talk about your data before they are paid predicts how they will treat it after.

Questions about what could go wrong

Ask the uncomfortable ones. What happens if the work runs over? What if a fix does not hold? What if you are unhappy partway through? How do payments work, and would they use staged payments or escrow so you are not paying everything up front for an unproven result? A trustworthy partner has thought about these and answers without defensiveness, because they have been asked before by good clients. Evasiveness or irritation here is worth more than any glowing promise, because it shows you how they behave when things are not going smoothly, which is exactly when you will need them to behave well. It is also worth asking who will actually do the work, and whether the person you are talking to is the person who will be typing, because a warm sales conversation followed by unfamiliar hands on your system is a common and avoidable disappointment.