Custom software development for companies
T-NEX develops business applications and extends existing systems, from clickable prototypes and integrations to agreed handover and support.
Explore serviceGuides for companies
How much does it cost to have an app developed?
Application costs follow the usable scope and the conditions for development and operation. Screen count or hourly rate alone cannot support a reliable estimate. A useful comparison includes preparation, implementation, integration, acceptance, your own effort and the period after launch.
In daily work
1. Describe a first usable version
For companies and startups commissioning a web application, mobile application or custom business system.
Define an end-to-end workflow: who starts with which information, what processing is required and what outcome is produced? A job management application might connect scheduling, mobile capture and completion. That sequence describes scope better than general labels such as dashboard, login and AI.
Separate essential functions from later extensions. For each main function, specify how completion will be recognised. Include missing information, unauthorised users and failures in connected systems. A small first scope should still allow a real task to be completed.
Overview
2. Identify cost drivers for each function
An interface can appear simple while supporting complex rules. Roles, approvals, data migration, offline behaviour and integrations influence effort. Use the same level of detail when requesting proposals from multiple suppliers.
| Dimension | Planning question |
|---|---|
| Users and roles | Who may view, change or approve which data? |
| Platforms | Does a responsive web application suffice, or are additional mobile capabilities needed? |
| Integrations | Which specific data and actions must other systems provide? |
| Data migration | Which existing data needs cleanup, mapping and import? |
| Exceptions | What happens without connectivity, with duplicates or without permission? |
| Operation | Which availability, backup, support and recovery arrangements are agreed? |
Overview
3. Calculate total cost for the same period
A clear model is: total effort = external implementation + internal preparation and coordination + integration and data work + acceptance and rework + operation and development + handover or exit. Each item needs a stated scope and a quantity assumption.
Record internal work explicitly: answering domain questions, making decisions, preparing tests and accepting results take the customer’s time. Check whether external proposals already include project management and quality assurance to avoid counting the same work twice. Explain any risk allowance rather than adopting an allegedly standard percentage.
Overview
4. Compare freelancers, agencies and external teams fairly
A freelancer, an agency and an ongoing external team may take on different responsibilities. Establish who actually owns specification, coordination, architecture, tests and operation. The sourcing label alone says little about total costs.
Ask about cover, onboarding and knowledge transfer. International collaboration also needs reachable contacts, shared working windows and an agreed access model. A lower nominal rate does not prove a lower total cost, and a higher rate does not guarantee an easier handover.
Overview
5. Budget for operation before launch
After the first release, applications may require hosting, monitoring, security updates, support and functional changes. Agree what is included, how urgent incidents are handled and how ordinary development is commissioned.
Handover involves more than source code: repository access, documentation, configuration, account control, data export and a reproducible deployment belong in the agreed scope. Plan a future handover to an internal team or another supplier from the beginning.
Overview
6. Evaluate proposals against outcomes
Ask suppliers to separate fixed scope, assumptions and points that still need investigation. If technology or data is uncertain, a bounded preliminary phase can be useful. Its result should enable a better decision, for example through a tested integration or a validated workflow.
Compare the same acceptance cases and operating period, not just the final amount. A cheaper proposal leaving data cleanup, testing or support unspecified covers a different scope. Record changes to scope, cost and timing together.
- Deliverable and acceptance criterion for each main function.
- One-off and recurring services with clear quantities.
- Customer responsibilities and available test data.
- Change procedure, handover and operating responsibilities.
FAQ
Frequently asked questions
How much does a simple app cost?
Simple is not a defined scope. Roles, integrations, migration and operating requirements can be substantial even with few screens. A concrete proposal needs a first workflow and acceptance criteria.
Is a web application cheaper than a mobile app?
That depends on the functions and operating conditions. First establish whether a responsive web application meets the task or whether device capabilities and offline behaviour add requirements.
Should I choose fixed price or time and materials?
A clearly bounded and testable scope can support a fixed-price agreement. Open requirements need a transparent process for ongoing prioritisation and cost control. The contract model does not replace specification or acceptance.
How can I prevent important costs from being omitted?
Use the same scope matrix for every supplier. Explicitly cover data work, customer effort, testing, integration, operation and handover. Record assumptions and exclusions.
What helps prepare an initial discussion?
A process example, key user roles, existing systems and a list of essential outcomes. Current forms or anonymised data samples help explain the real workflow.
Related options
You may also be interested in these.
Outsourcing software development
Commission external software development with clear goals, data responsibilities, roles, acceptance criteria, handover and ongoing operational support.
First version: Updated:
Read articleOffshore software development with T-NEX
Distributed software development with T-NEX: agree scope, collaboration and handover in advance, with costs considered across the full engagement.
Explore serviceWhich task would you like to solve next?
Bring a concrete task. Together, we will define what the application needs to do.
Discuss your application scope