Start with what the first version must do.
“How much does an app cost?” is a sensible first question. A useful estimate starts with who will use the app and the job it must help them finish. An app for booking one service is different from a marketplace with customers, partners, payments and an admin team.
Write a small, practical brief.
Describe your users, the main task, the features needed on day one and any system the app must connect to. Share reference apps to explain a flow or style, but say which parts you actually need. Keep later ideas in a separate list.
Compare scope, not just the final price.
| Area | Focused first version | Larger product |
|---|---|---|
| Users | One customer journey and basic admin | Customers, partners, staff and admin roles |
| Booking | Choose a service and request a slot | Availability, allocation, rescheduling and notifications |
| Payments | One provider and a defined checkout | Refunds, settlements, wallet rules or subscriptions |
| Integrations | A small set of documented connections | Multiple systems, custom APIs or data migration |
| Release | Agreed devices and a focused test plan | More roles, workflows, devices and operational checks |
This table illustrates differences in scope. It is not a package, quote or delivery-time commitment.
Separate development from running costs.
Ask which costs recur: hosting, messaging, maps, payment charges, model usage, app store accounts, paid services and maintenance. Ask who owns each account and who receives its bills.
Plan for the things outside the code.
Content, product data, provider access, account verification, approvals and feedback can affect dates. List who supplies each item and when it is needed. A delivery plan should make these dependencies visible.
Agree how changes will be handled.
New ideas are normal. Before approving a change, ask how it affects screens, integrations, testing, cost and launch. A short written change record keeps expectations aligned.
Check ownership and handover.
Your contract should explain source-code ownership, transfer timing, third-party licences, repository access, store accounts, documentation and support. Separate fixing agreed defects from building new features.
What to send us for an estimate.
Send a short business description, user roles, essential features, preferred platforms, existing app or website links, required integrations and any target launch dependencies. If the scope is still unclear, start with a discussion to decide what should be explored first.
Explore mobile app development ↗