What Drives the Cost of Custom Software, and How to Read a Quotation
November 11, 2026 · 4 min read · Etzal Group Team
A company asks three vendors to price the same application and receives three numbers that seem to describe different projects. In a sense they do. Custom software cost is the product of a few drivers, and each vendor has made different assumptions about them. Knowing the drivers lets you read a quotation properly and shape the price before you sign.
Driver 1: scope, counted honestly
The obvious driver is how much the system does. The less obvious part is how scope is counted. A feature is not one unit of work. "Manage purchase orders" includes creating, editing, approving, cancelling, printing, searching, exporting and handling the cases where something goes wrong.
Ask vendors to break the price down by feature or user story. A single lump sum hides what was and was not counted.
Driver 2: users, roles and permissions
Every role multiplies the work. A screen that looks the same for everyone is simple. A screen where staff see their own records, managers see their team's and finance sees everything, with different buttons for each, takes several times longer to build and test. Approval chains add more.
If you can simplify roles, you reduce cost directly.
Driver 3: integrations
Connecting to other systems is frequently underestimated. Each integration needs access, documentation that may not exist, handling for failures and testing against a system the vendor does not control. Old systems without an API cost more.
List every integration in your request, and say who owns each system. A vendor who has to guess will either pad the price or discover the cost later.
Driver 4: data migration
Moving history from the old system involves mapping fields, cleaning records, running trial migrations and reconciling totals. It is rarely glamorous and often a tenth or more of the project. Decide how much history you truly need. Migrating two years is cheaper than ten.
Driver 5: quality levels
Two systems with identical features can differ greatly in cost because of what you cannot see in a demo:
- Testing. Automated tests cost time now and save it at every later change.
- Security. Proper access control, audit trails, encryption and a security review.
- Performance. Built for fifty users or five thousand.
- Availability. Office hours with occasional downtime, or continuous with failover.
- Devices. Desktop only, responsive, or native mobile apps.
A cheap quotation often assumes the lowest level on each. Ask each vendor to state their assumptions.
Driver 6: design
A plain interface built from standard components is fast to produce. A custom visual design with careful user research, prototypes and revisions adds weeks. Internal tools usually need clarity more than polish. Customer-facing products usually need both.
Driver 7: uncertainty
Where requirements are vague, vendors add contingency or quote time and materials. A precise requirements document lowers the price because it lowers the risk the vendor carries. Spending two or three weeks on requirements before asking for quotations commonly pays for itself.
Driver 8: the team
Rates vary by seniority and location. More important than the daily rate is who actually does the work. A senior engineer who builds it right the first time can cost less in total than a larger junior team that reworks it. Ask who will be on the project and how much of their time.
Driver 9: what happens after launch
Software costs continue after go-live:
- Hosting and third-party services.
- Monitoring and backups.
- Security updates to frameworks and libraries.
- Bug fixes and a warranty period.
- Small changes as the business evolves.
A quotation that ends at launch is incomplete. Ask for the first-year running cost alongside the build price.
How to compare quotations
Put them side by side with the same rows:
- Features included, by story or module.
- Integrations included.
- Migration scope.
- Testing approach and who performs user acceptance testing.
- Documentation and source code ownership.
- Warranty period and what it covers.
- Maintenance fee and what it covers.
- Assumptions and exclusions.
- Payment schedule tied to milestones.
Differences in rows two to eight usually explain differences in price.
Ways to reduce cost without regret
- Phase the work. Launch the core process first and add the rest once it is in use.
- Use what exists. Standard components for login, payments, reporting and messaging are cheaper and safer than building your own.
- Simplify roles and approvals.
- Limit migration to what people need day to day and archive the rest.
- Decide quickly. Slow answers from the client side stretch every project.
We price Enterprise Software projects from a written scope, with assumptions and exclusions listed. If you would like a second reading of quotations you have received, send them to us or use the quote request form.
Summary
Price follows scope, roles, integrations, migration, quality levels, design, uncertainty, team and post-launch care. Ask every vendor to state assumptions on each, compare line by line, and reduce cost by phasing and simplifying, not by removing testing and security.
Frequently asked questions
Why do quotations for the same software project differ so much?
Vendors make different assumptions about scope, quality and what is included after launch. One may price the screens you described, another may include testing, migration, documentation and a year of support. Ask each to list assumptions and exclusions so that you compare the same thing.
Is the cheapest quotation a risk?
It can be. A price far below the others usually means something is missing: testing, security work, handover documents or realistic time for integrations. Ask what was left out. If nothing was, ask how the same work costs so much less.
How much should we budget for maintenance?
Plan an annual amount for hosting, monitoring, security updates, bug fixes and small changes. The right figure depends on how critical the system is and how often the business changes, so ask each vendor to state what their maintenance fee covers and what is charged separately.
Related service
Free consultation
Not sure where to start? We will map the right system for your business, free.
