The founder's checklist before hiring a mobile app development studio

Most bad studio engagements aren't obvious until months in — a codebase you can't move, a "senior team" that turns out to be one person you never talk to, a scope that quietly grew. Here's what to check before you sign anything, not after.

Ownership — check this first, in writing

• Repository access. Ask for it to be under your GitHub/GitLab org from day one, not transferred "at the end." A studio that resists this is telling you something.
• Accounts. Domain, hosting, app-store developer accounts, Firebase/cloud projects — all in your name, with you as owner, even if the studio manages them day to day.
• Designs. Figma files (or equivalent) shared to a workspace you control, not one you'll lose access to when the engagement ends.

If any of these are "we'll hand it over once the invoice is paid" — that's leverage being held over you, not standard practice.

Who's actually doing the work

• Ask directly: who will write the code, by name? Not "our team" — the actual people.
• Ask whether the person who scoped the project is the person who'll build it. A lot of friction comes from a senior person selling the engagement and a junior team executing it.
• If seniority matters to you (it should, for a first product), ask what "senior" means concretely — years shipping production apps, not years the company has existed.

Scope and pricing

• Is the quote fixed-scope or time-and-materials? Make sure you know which, and that the definition of "done" is written down, not implied.
• Ask what happens when scope changes mid-build. A studio with no answer to this will either eat unbounded scope creep (and rush your product) or bill you for it without warning.
• Get milestones with concrete, checkable deliverables — not just percentages of a total price.

Process signals worth asking about

• How do they handle a disagreement about a technical decision? You want a studio that pushes back with reasoning, not one that just says yes to keep you happy.
• What's their release process? "We'll figure it out" is a red flag for anything going to an app store, where review cycles and versioning mistakes cost real time.
• Can they show something they actually shipped — not a mockup, not a case study written in the passive voice about a client who can't be named, but something live you can install or visit.

The one-line test

If you can't get a straight answer to "who owns the code when this ends, who's writing it, and what does done mean" — keep looking. Those three answers tell you more than a portfolio deck.

Want to run your own situation past someone who isn't trying to sell you anything in the next 15 minutes? Book a build-readiness call — you'll leave with a rough scope, the likely risks, and the next sensible step, even if we're not the right studio.