What happens after I send a studio my half-built app?

Sending your half-built app off can feel like dropping it into a black box and hoping. It should not be. A good studio follows a fairly predictable path between receiving your app and starting real work, and most of that path is about understanding before doing. Knowing the steps helps you tell a considered process from a rushed one.

First, they understand what you sent

The opening stage is assessment, and it should come before anything is changed. A good studio reads through your code, works out where your data lives, checks what is connected and what is exposed, and forms a real picture of what you have. This is careful, unglamorous work, and it is the foundation of every honest decision that follows. You should expect questions during this phase, because your context fills gaps the code alone cannot. What you should not expect is large-scale rebuilding before anyone has understood the whole. If work begins changing things immediately, without a survey first, the process is skipping its most important step.

They deal with anything urgent

If the assessment uncovers something dangerous, an exposed secret, an open database, an unsafe payment path, the right response is to flag it plainly and, with your agreement, close it quickly. This triage is a good sign, because it shows the studio is separating "this could hurt you today" from "this would improve things eventually" and treating your live risk as the priority. You should be told clearly what was found, in terms you understand, and what the urgency is. A studio that surfaces the scary things early, rather than quietly folding them into a long invoice, is one treating your interests as the point of the exercise.

They report back in plain language

Once they understand your app, a good studio comes back with findings you can actually follow: what works, what is risky, what is salvageable, and what is not. This report should be in plain terms, not a wall of jargon meant to impress or obscure. It is your chance to understand your own system, often better than you did when you built it. A studio that cannot explain what it found in language you follow is either not communicating or not as clear on it as it should be. The quality of this report is a strong preview of what the whole engagement will be like to live through.

They give options, and wait for your yes

Finally, they present options rather than a single take-it-or-leave-it verdict: what to keep, what to fix, what to rebuild, with reasons and rough costs for each path. The good version lays out trade-offs so you can choose with your budget and stakes in mind, perhaps a lean fix now and more later, or a fuller job at once. Crucially, no large work should begin until you understand and agree the plan. You are meant to be a partner in the decision, not a spectator handed a bill. If the process reaches real work without your informed agreement, something has gone wrong, however good the intentions. The healthiest sign at this stage is that you feel like a decision-maker who has been given a clear map and real choices, rather than a client being steered toward the largest possible invoice, and a studio genuinely on your side will make sure the choice feels like yours.