Why software prices vary so widely
Two projects described as a portal can require completely different amounts of work. One might display information from a single trusted system. Another may need permissions, payments, document generation, notifications, audit history and data exchanged with several suppliers. The useful comparison is the agreed workflow and risk—not the label attached to the product.
Novawize currently publishes starting prices of £1,199 for a focused MVP, £3,999 for a complete web application and £4,999 for a combined web and mobile product suite. These estimates exclude VAT and change with scope, integrations, migration, platform charges and security requirements.
The main software cost drivers
The number of screens is rarely a reliable measure by itself. Complexity is usually concentrated in business rules, user roles, exceptions and connections with systems the development team does not control.
- Discovery and clarification of the current workflow
- User roles, permissions and approval rules
- External APIs and supplier limitations
- Quality and volume of data to migrate
- Web, mobile and offline requirements
- Payments, documents, notifications and reporting
- Security, audit and regulatory requirements
- Testing, deployment, training and support
Use an MVP to reduce uncertainty, not just features
A good minimum viable product proves the riskiest part of the idea with real users. It is not simply the full wish list delivered with fewer colours. Choose one valuable journey, include the exceptions most likely to break it and decide what evidence would justify the next investment.
Ask what will be real in the first release and what will be simulated or handled manually. Authentication, integrations and production deployment can materially affect the price even when the visible interface looks small.
What a useful proposal should contain
A software proposal should connect price to outcomes, deliverables and assumptions. It should identify who supplies content and access, how changes are assessed, where the software will run and what is included after launch.
- The users and workflow included
- Named deliverables and exclusions
- Milestones, review points and acceptance method
- Assumptions about data and third-party systems
- Hosting, subscription and transaction costs
- Ownership, handover and documentation
- Warranty, maintenance and future change process
Build a budget from one workflow
Before asking for a price, explain one process from trigger to completion. Name the people involved, the information they use, the decisions they make and the exceptions that return work to an earlier stage. That short exercise usually produces a more dependable starting estimate than a long unprioritised feature list.
This article provides general information, not advice for a specific organisation or tax position. Scope, prices and requirements should be confirmed before work begins.