Short answer
The cost of custom software is driven by business rules, integrations, data migration, testing and operations, not by the number of screens. Without a validated scope no reliable figure can be given, but separating the cost items and comparing quotes on the same scope reduces uncertainty considerably.
Screen count is not enough
The same screen can require very different effort depending on permissions, pricing rules and external services. Business logic and data movements belong at the centre of estimation.
An order list, for example, is a small job if it is a simple table with filters and export. The same list is a much bigger job if it shows different fields by role, syncs with a stock system and writes every change to an audit log. When asking for a quote, describe workflows, roles and integrations rather than a list of screens.
Separate three cost areas
Estimate product development, migration and integration, and ongoing operations separately. Licences, external services, data cleaning and training can add less visible work.
Product development is usually the most visible item. Migration and integration cover cleaning existing data, running in parallel with the old system and dealing with the limits of external services. Operations and maintenance cover error monitoring, security updates, backups and small changes after launch; this item does not end at go-live.
An example of reducing uncertainty
For a customer portal, clarify roles, file types, approval steps and the existing CRM connection. Separate the first release from later stages and explicitly flag integration work that remains unknown.
Flagging an unknown item instead of hiding it makes quotes easier to compare: a note such as "to be priced once the CRM interface is confirmed" is better than a surprise item later.
Compare equivalent proposals
Use the same scope, acceptance criteria and maintenance period. A low initial price can be offset by missing delivery or higher operating costs. Exposing cost drivers is more useful than inventing a general price range without scope.
Add these rows to your comparison table: included test types, acceptance criteria, handover documents, bug-fix period, go-live support and maintenance terms. An empty row can mean the quote does not include that work.
Scope tiers: an example classification
The classification below is not a price or duration estimate; it is an example distinction showing how scope differs and which factors determine time and cost.
A practical evaluation exercise
Use a quotation form as an exercise. Collecting fields, calculating role-dependent prices and creating CRM records are different scopes. List data, rules, integrations and acceptance tests for each version. Estimate the essential workflow first and keep later ideas separate from the first-release commitment.
You should end up with a three-part list: the mandatory flow, a second phase and the unknowns. The price discussion should start with the first list only.
Frequently asked questions
The questions we hear most often when budgeting for custom software.
Why does every company quote a different price?
When the scope is not written down, every team makes different assumptions. One includes testing and handover, another does not; one prices screens, another prices business rules and integrations. Asking for quotes on the same written scope makes the reason for the difference visible.
Is a fixed price or time-based pricing safer?
If the scope is clear and no changes are expected, a fixed price gives predictability. If the scope will be discovered along the way, a time-based or phased model can be more honest. Either way, how change requests will be priced should be in writing.
What costs appear after go-live?
Hosting and licences, error monitoring, security and dependency updates, backup checks and small improvements create recurring cost. Ask about it as a separate line from the development quote.
Is off-the-shelf software always cheaper?
Often at the start, but you need to consider adaptation, licences, integration and exit costs. See our guide Off-the-shelf or custom software? for a comparison.
