Price the complete service
An app usually needs more than screens. Identify the backend, administration, content, payment flow and notifications required to complete the customer journey. Separate launch essentials from later additions, and specify the devices and languages that must be supported. These choices define the work a developer can estimate.
Turn a vague app brief into estimateable work
“An app like a booking marketplace” leaves several projects hidden in one sentence. For an example appointment service, ask for these work packages separately. The table is a scoping worksheet and does not imply a fixed price or delivery time.
| Work package | Details that change the estimate |
|---|---|
| Customer booking | One provider or marketplace; fixed slots or variable duration; rescheduling rules |
| Payments and refunds | Payment provider, test account, partial refunds and reconciliation |
| Staff administration | Roles, branch access, audit history, exports and manual exceptions |
| Launch and operations | Device coverage, translations, monitoring, account setup and support coverage |
Identify expensive uncertainty early
A well-documented integration differs from a system with no test access. Existing data may need cleaning, and store submission may require account setup or content you have not prepared. Ask a proposal to name these dependencies and explain what happens if the assumptions change, instead of hiding uncertainty in a single fixed number.
Include the costs after release
Hosting, domain renewal, store accounts, paid APIs and AI usage can continue after development is paid for. Maintenance and new features require capacity too. At Astera, project development is quoted by scope; ongoing development and maintenance starts from HK$62,000 per month, subject to agreed capacity and coverage.
Before you proceed
- Request separate figures for development and recurring services.
- Agree what acceptance and post-launch defect support include.
- Treat unconfirmed integrations as an estimation dependency.
