OOmnistu

Blog / Startup Guides

Startup Guides

20 questions to ask an app development company before you sign

Ask specific questions about scope, ownership, testing, delivery and maintenance before choosing an app development company.

OOmnistu
Reviewed 2026-11-16 · 2 min read

Use these in a call or in writing. Keep the answers in one table so you can compare vendors. Good answers are specific. Vague answers are a reason to ask a follow-up, not proof of a problem.

About the work

  1. Which parts of my brief are unclear or risky, in your view?
  2. What is included in your estimate, feature by feature? What is excluded?
  3. Which platforms and OS versions will you support?
  4. Which third-party services will the app depend on, and who owns those accounts?
  5. How will you test the app, and with what devices and test data?

About the team

  1. Who will work on my project and in what role? Are any parts subcontracted?
  2. Who is my single point of contact, and how quickly do you respond?
  3. What happens if someone on the team leaves mid-project?

About process and money

  1. How do you show progress, and how often?
  2. How are changes requested, estimated and approved?
  3. Is the price fixed or time-based, and what happens if the estimate proves too low?
  4. How is payment linked to delivered work?

About ownership and exit

  1. Who owns the code, designs and data when I have paid?
  2. Will source code, cloud accounts and app store accounts be in my name?
  3. What documentation do you hand over?
  4. If I leave, how do you support the handover to another team?

About launch and after

  1. Who submits the app to the stores, and what happens if it is rejected?
  2. What support is included after launch and for how long?
  3. How do you handle security issues found after release?
  4. Can I speak to a past client about a project that had difficulties?

How to use the answers

Make a table with the questions down the side and vendors across the top. Mark each answer as clear, partial or missing. Weigh missing answers on ownership, payment and team more heavily than missing answers on style or tools, since they are harder to fix later. That weighting is our advice, not a rule.

This list is not legal advice. Have a lawyer review the contract.

By Omnistu.

Sources

Previous
MVP vs prototype vs proof of concept: choose the next experiment