Apps & Software
Application Development Cost Components: What Sets the Budget
The cost of building an application is not set by the number of pages, but by the number of modules, user roles, integrations, data migration, security level, and costs after release. This guide maps the components so a budget can be read.
SEO and Content Specialist
7 min read
Short answer: the cost of building an application is set by the number of modules and workflows, the number of user roles and their permission rules, integrations with other systems, migration of legacy data, the security level aimed for, and costs after release (infrastructure, licenses, upkeep). The number of screens is not the main driver. That is why a figure you can rely on only exists after the needs are mapped, not from a single rate per application.
The question of application cost almost always comes first, yet it can only be answered once several things are clear. Two quotes for a “request application” can differ widely because one counts three modules and one role, while the other counts six modules, five roles, and an integration with the finance system. This guide maps the components that make up a budget, with no rupiah figures, so incoming quotes can be compared fairly. Writing down the requirements is covered in How to Write a Requirements Document Before Building an Application, and time estimates in How Long Does It Take to Build a Web Application?.
Application cost components in one table
| Component | What sets its size | Question to ask yourself |
|---|---|---|
| Scope | Number of modules, workflows, and business rules | Which processes must truly exist in the first version? |
| User roles | Number of roles and permission rules per role | Who sees and changes what? |
| Integrations | Number of systems that must connect | Which existing systems is the data used from? |
| Legacy data | Volume and cleanliness of the data moved | Where is the data now, and how tidy is it? |
| Security | Data sensitivity and level of controls | What data is processed, and who will check it? |
| Testing and launch | Test coverage, training, support | Who tries it, and who is trained? |
| Infrastructure and licenses | Server or cloud usage, third-party services | Where does the application run, and who pays the bill? |
| After release | Fixes, upkeep, further development | Who maintains it once it is done? |
Scope: modules and workflows
Scope is the largest component, and it is counted from modules and the business rules inside them, not from the number of pages. One request form with three approval stages, notifications, and status tracking is heavier than ten information pages. A requirements document that writes the workflow step by step makes modules countable. Without it, a quote has to guess, and guesses are usually rounded up or end in revisions midway.
How to keep this component down: set a first version containing only the processes that hurt most when done manually, then add other modules in later stages. Building in stages lets the budget be split per stage.
User roles and access rules
Every role brings rules: what may be seen, changed, approved, or deleted. An application with one role is far simpler than one with five roles whose rights cross between units. These rules are also the ones most often missed when requirements are collected, and only appear during trials when an officer finds they cannot open the data they need. Login patterns and activity logging are covered in Role-Based Login and Activity Logs.
Integrations with other systems
Integrations add work because the new application has to adapt to systems the build team does not control: data formats, access methods, and the other party’s change schedule. Count how many systems must connect and whether they have documented interfaces. Integration with finance, warehouse, or HR systems is common, and each is counted separately. If the main job is actually connecting systems that already exist, the scope needs to be assessed separately.
Migrating legacy data
Data already in spreadsheets or an old system can rarely be moved as is. It usually needs cleaning, mapping to the new structure, and checking with the people who know the data. Volume and tidiness decide how long this takes. Ask from the start: how many records, where are they stored, and who can confirm they are correct.
Security and data protection
The security level aimed for affects the amount of work. The OWASP Application Security Verification Standard (ASVS) 5.0 describes it with three levels: Level 1 holds about 20% of the requirements as a starting point, meeting Level 2 means implementing about 70% of the requirements, and Level 3 is for applications that want to show the highest security. ASVS itself advises organizations to choose a level according to the sensitivity of the application and the expectations of its users.
When an application processes personal data, Article 35 of Law Number 27 of 2022 requires the data controller to protect and ensure the security of the data it processes, including setting the security level with regard to the nature and risk of the data. That means security is not an optional extra for such an application, and should go into the budget from the requirements mapping. This summary is for technical planning, not legal advice.
Testing, training, and launch
Limited trials, final data migration, training, and an early support period are often left out of the count even though they take real time. Ask whether the quote includes them, and how long support lasts after the application goes live.
Infrastructure and licenses: costs that run separately
The cost of building an application differs from the cost of running it. Cloud providers bill by usage: AWS, for example, states a pay-for-what-you-use principle, with discounts for commitment or high volume. So infrastructure bills rise and fall with the number of users and the amount of data, and are best paid directly in your company’s name. Third-party services the application uses, such as email delivery or maps, also have their own bills. A comparison of on-site and cloud placement is in Office Server, Cloud, or Shared Hosting.
Costs after release
An application is used for years, and its needs change. Count from the start: the warranty period for fixing errors in the work, a regular maintenance plan, and who develops the next features. Source code ownership also decides how easily you can switch maintainers, covered in Source Code Ownership in Application Development Contracts.
How to keep the budget in check
- Start from requirements mapping, and take that stage separately if needed, so you hold a scope document before being tied to a full project.
- Build in stages. Versions that can be tried regularly let direction be corrected before it goes too far.
- Record every change as its own request with its impact on time and cost, agreed before it is done.
- Ask for quotes that state their assumptions: number of modules, roles, integrations, and data moved.
- Consider alternatives. If the need fits ready-made software, that may suit better; the comparison is in Custom Application, Ready-Made Software, or Spreadsheet?.
Checklist for comparing quotes
- Is the number of modules and workflows counted the same in every quote?
- Are user roles and their permission rules mentioned?
- Are integrations and data migration counted, or excluded?
- Do testing, training, and support come included?
- Are the security level and its checks explained?
- Who owns the source code and the infrastructure accounts?
- What applies after handover: warranty and maintenance?
How Legia works
In the Web Application Development service, cost is counted from the number of modules and business rules, the number of user roles and their permission rules, integrations with systems already running, legacy data migration needs, and the user load to be carried. The exact figure is given after the requirements mapping stage (1-2 weeks), which can be taken separately so you receive a scope document and a cost estimate without being tied to a full project. The system is built in stages and can be tried every two to three weeks. Changes in requirements are recorded as separate requests, assessed for impact, then agreed before being done. Source code is kept in a repository in your company’s name from day one. Legia covers fixes for errors in its work for 30 days after handover, after which a subscription maintenance plan is available. Other services in this pillar are on the Applications & Software page.
Frequently asked questions
Is application cost counted per page?
Generally not. What is counted is modules, workflows, business rules, user roles, and integrations. One page with complex approval logic can be heavier than many static pages.
Does the build cost include servers and licenses?
Usually these are separate. Server or cloud bills and third-party licenses are paid to the provider, and preferably in your company’s name so you can monitor usage.
Can the budget be split by stage?
It can when the system is built in stages. Each stage produces a part already in use, so the decision on the next stage rests on results already seen.
Why can quotes differ so much for needs that look the same?
Because the assumptions differ: number of modules, roles, integrations, security level, and test coverage. Ask each quote to write down its assumptions, and compare those before the final figure.


