There is no useful fixed price for a custom web application without context. The right budget depends on what the product must do, who will use it, what systems it needs to connect to, and how much risk needs to be removed before launch.
The main cost drivers
Most cost sits in complexity rather than screen count. A simple customer portal with a few forms and dashboards is very different from a workflow platform with permissions, approvals, payments, reporting and integrations.
- Discovery, requirements and technical planning
- UX, prototyping and interface design
- User roles, permissions and workflows
- Third-party integrations and APIs
- Data migration and reporting
- Security, testing and support
Why discovery matters
A discovery phase protects the budget. It turns assumptions into a roadmap, identifies dependencies, and helps decide what should be built first. For many organisations, the best first release is smaller than the original idea but much more likely to launch successfully.
How to control cost
Start with the business outcome, not a feature list. Prioritise the workflows that create value, reduce admin or improve customer experience. Build the smallest useful version first, then use real feedback to guide future releases.
What to ask an agency
Ask how they handle discovery, risk, technical architecture, testing, security, documentation and support. The cheapest estimate is rarely the lowest total cost if the platform has to be rebuilt later.
Ready to talk about the project?
Tell us what you are trying to build, what is blocking progress, and what the business needs to change. Armour by Granite will come back with a practical next step.
