The sales conversation with a mobile app development company is designed to build confidence. Polished case studies. Smooth handoffs. A proposal that arrives within 24 hours that somehow covers everything you mentioned and prices it reassuringly. It is very easy to feel good about a company that is good at selling.
It is harder to know whether they are good at building. And the difference between those two things is only visible once you are mid-project and the invoice has cleared.
These 20 questions are the filter. Ask them before you sign anything. The answers — and the confidence, specificity, and transparency with which those answers are given — will tell you more about the right partner than any portfolio ever will.
Questions About Portfolio and Delivery History
1. Can you show me three apps you built from scratch in the last 24 months that are currently live?
This is not negotiable. Not mockups. Not screenshots. Live apps on the App Store or Google Play that you can download, open, and use right now. A development company that cannot produce three live references has not delivered three products worth referencing.
2. What is the current daily active user count for each of those apps?
This question matters because it separates apps that launched from apps that worked. A startup app with 200 daily active users six months after launch tells a different story from one with 15,000. Ask the question. Listen to whether they answer it directly or pivot to the download count.
3. What was the biggest technical challenge on one of those projects, and how did you resolve it?
Vague answers — ‘we overcame some integration challenges’ — reveal companies that have not thought deeply about their own work. Specific answers — naming the specific integration, the failure mode, the architectural decision that resolved it — reveal genuine engineering depth.
4. Have any of your startup clients raised funding after launching their app?
Investors fund apps that work. A development company whose clients have raised funding after launch is one that builds products good enough to pass investor scrutiny. It is one of the most meaningful portfolio signals available.
Questions About Process and Methodology
5. Walk me through your development process from our first brief to App Store submission.
You want to hear: discovery workshop, UI/UX design and prototype, iterative development sprints with demos at the end of each sprint, QA across device matrix, App Store submission preparation, and post-launch support handover. If any of those phases is missing or vague, ask why.
6. How long is a typical development sprint, and what deliverables do I see at the end of each one?
Two-week sprints with working features demonstrated at sprint demos is the standard for competent agile delivery. One-month sprints with ‘progress reports’ instead of working features is a warning sign. You should see real, functioning code at the end of every sprint — not a status update.
7. How do you handle scope changes mid-project?
The answer should be: a documented change request process, with each scope change assessed for time and cost impact, presented for approval before implementation. ‘We are flexible’ without a structured change process is how budgets double between the proposal and the final invoice.
8. What does your QA process look like specifically?
They should describe: manual testing across a defined device matrix, automated regression testing for core user flows, performance testing under simulated load, and accessibility testing. ‘We test everything before delivery’ is not a QA process. It is a reassurance that tells you nothing.
Questions About Technology and Architecture
9. What would you recommend for my app — native, React Native, or Flutter — and why?
The answer should be specific to your use case. If they ask clarifying questions before answering — what features are you building, do you need deep hardware integration, what is your iOS/Android priority — that is the right behaviour. If they immediately recommend their preferred framework regardless of your product, the recommendation is serving them, not you.
10. How do you approach state management in React Native (or Flutter) at scale?
For React Native, you want to hear a specific opinion: Redux for complex state, Zustand for lighter-weight applications, React Query for server state management. For Flutter, you want to hear: Provider, Riverpod, or Bloc. A developer who says ‘it depends’ without elaborating is telling you they have not formed a considered opinion — which is fine for junior engineers and concerning for senior architects.
11. How do you handle app performance across Android’s 24,000+ device configurations?
This should include: a defined test device matrix covering the most common screen sizes and OS versions in your target market, performance profiling tools (Flipper, Android Profiler, Instruments for iOS), and a specific process for identifying and resolving scroll performance issues and memory leaks.
Questions About Legal and Business Terms
12. Who owns the source code when the project is complete?
The answer should be: you do. Completely. With no conditions, no ongoing licensing fees, and no dependency on the agency for future access to your own codebase. Any other answer is a non-starter.
13. Will you sign an NDA before we discuss our product in detail?
Yes — immediately and without hesitation. Any development company that hesitates, qualifies this, or asks you to wait until after an initial call before signing an NDA is not a company you should be sharing your product idea with.
14. How is pricing structured — fixed-price milestones or open-ended time-and-materials?
Milestone-based pricing tied to accepted deliverables protects your budget and creates shared accountability for scope. Open-ended time-and-materials billing with no defined scope ceiling puts all the financial risk on you.
Questions About Communication and Ongoing Support
15. Who is my single point of contact throughout the project?
It should be a dedicated project manager — not a rotating cast of developers who are also managing other clients. A PM who knows your product, owns your timeline, and can make decisions without escalating every question is the difference between a smooth engagement and a frustrating one.
16. How many other projects will my development team be working on simultaneously?
Dedicated teams produce better outcomes than shared resource pools. An honest answer here — whether it is ‘fully dedicated to your project’ or ‘shared across two concurrent projects’ — helps you calibrate expectations about availability and response time.
17. What does post-launch support look like, and what does it cost?
You should hear: a defined warranty period (typically 30 to 90 days) for bug fixes, followed by a structured maintenance retainer priced at 15 to 20 percent of the annual build cost. Vague ‘we will be here if you need us’ commitments are not support models.
Questions That Reveal Partnership Quality
18. What would you push back on in my current brief?
A good development partner challenges bad ideas, flags scope that is too ambitious for the stated timeline, and raises architectural concerns before they become development problems. A company that agrees with everything in your brief is not giving you their honest assessment — they are selling you.
19. Can we do a two-week paid pilot sprint before committing to the full project?
Any credible mobile app development company welcomes a paid pilot sprint. It demonstrates capability rather than describing it. A company that resists, deflects, or tries to substitute the pilot with a longer sales process is a company less confident in their process standing up to real scrutiny.
20. What is the most common reason your client relationships fail to meet expectations?
This question is unusual enough to be disarming. A company that answers it honestly — ‘scope creep from clients who add features mid-sprint’ or ‘clients who do not have a technical stakeholder available for weekly reviews’ — is a company operating from self-awareness. A company that says ‘our client relationships always succeed’ has told you they are not willing to be honest with you.
Conclusion
Twenty questions is a lot to ask. But you are about to hand over a significant amount of money to a company you probably met online two weeks ago, and trust them to build something that could define your startup’s first year. The companies that answer these questions with specificity, transparency, and genuine honesty are the ones worth hiring. The ones that dodge, deflect, or give you polished non-answers have told you everything you need to know.