Most software projects that stall do not fail for technical reasons. They fail because expectations were never clear. These questions reveal a company's level and protect you from disputes that surface two months in.
1. Do I receive the source code after delivery?
If the answer is no, or evasive, that is a strong warning. Without the source code you are tied to that company forever and every small change becomes a negotiation. Ask for this in writing in the contract.
2. Which account will the app be published under?
The app must be published to Google Play and the App Store under your company name. Some companies publish under their own account to retain control. If that happens and you leave, you lose the app, its reviews and its users.
3. Can I see apps you have actually shipped?
Not screenshots on a website — real store links you can install and try. Read the reviews too: they tell you about stability and post-launch support.
4. Who exactly will work on my project?
Some companies meet you with a strong team and then subcontract the work. Ask about the names and level of the people who will build it, and whether they are employees or external contractors.
5. What exactly is included in the price?
Ask for an itemised breakdown: design, development, dashboard, payment integration, store publishing, testing, training. Quotes arriving as a single number without detail hide surprises.
6. What is not included in the price?
A more important question than the previous one. Hosting, annual store subscriptions, payment gateway fees, maintenance, changes after sign-off — all must be written down clearly.
7. What is the warranty period and what does it cover?
The warranty should cover free bug fixes for a defined period after delivery. The distinction between "a bug" (free) and "a new change request" (billed) must be explicit.
8. How will I follow progress?
A serious company gives you regular builds showing real progress, not written reports. Ask for a testable version at least every two weeks. Projects where the company disappears for two months and returns with a finished product are the ones that stall most often.
9. Is the design custom or a template?
A simple question that changes both price and outcome. Ask to see and approve the screen designs before any code is written; that saves expensive revision rounds later.
10. What happens if I stop the project?
A clause many people ignore. It must be clear what you receive if the project halts midway and how outstanding amounts are calculated. The presence of this clause is itself a sign of transparency.
Warning signs
- An instant quote without asking anything about your project.
- A price implausibly below every other offer — usually recovered during delivery, or gone after the first payment.
- Promises of very short delivery times without staged detail.
- Refusal to put clear terms in the contract on the grounds that "we work on trust".
- A guarantee of first place on Google or guaranteed marketing results.
Summary
A good company is not the one that says yes to everything. It is the one that explains the risks and alternatives and writes down what you agreed. If you have a project and want a frank opinion before you start, send us the details.