“What will it cost?” is the first question on every call, and the honest answer at that point is always a range. That is not evasion. Two projects described in the same sentence — “a portal for our customers” — can differ by an order of magnitude depending on what sits behind the portal. What follows is what actually moves the number, and which of those levers are in your hands.
The Big Drivers
1. Integration surface
The application itself is often the cheaper half. Cost concentrates in the seams: every external system you must read from or write to adds authentication, error handling, retry logic, data mapping, rate limits, and a test environment you may not control. A standalone tool with its own database is comparatively cheap. The same tool that must stay in sync with an ERP, an accounting package and a scheduling system is a different project.
2. How well the current process is understood
If nobody can describe the current process end-to-end without disagreement, discovery is going to take longer — and discovery is where scope either gets controlled or quietly explodes. The single biggest cost saving available to most buyers is doing the internal work of agreeing what the process actually is before development starts.
3. Data migration
Migrating years of accumulated data from a legacy system is routinely underestimated. Real historical data contains duplicates, records that violate the rules the new system will enforce, free-text fields carrying meaning nobody documented, and edge cases created by staff working around limitations. Migration is rarely a script; it is a series of decisions about what to keep and what to correct.
4. Compliance, security and audit requirements
Handling payment data, health information or government data changes the engineering, the hosting, the testing and the documentation. These requirements are legitimate and they are not free. They also cost far less when they are known at the start than when they surface during a customer security review after launch.
5. Non-functional requirements
“It has to be fast” and “it has to be available” are cost decisions in disguise. Ninety-nine percent uptime and 99.99% uptime are different architectures with different price tags. Concurrency targets, offline capability, and mobile support all belong in the estimate conversation rather than the surprise conversation.
What You Can Actually Control
- Sequence. Shipping the highest-value slice first, then extending, costs less and de-risks more than building everything before anyone uses it.
- Scope discipline. Every “while we are in there” request has a price. Keeping a parked list and revisiting it after launch is cheaper than absorbing changes mid-build.
- Decision speed. Idle time waiting on an internal decision is real project cost. Naming one person who can decide is worth more than most tooling.
- Access. Delays getting credentials, test environments or sample data are common and entirely avoidable.
- Reuse. Existing licences and platforms you already pay for often cover part of the requirement. Building what you could configure is the most expensive kind of custom software.
What a Credible Estimate Looks Like
Be cautious of a fixed price quoted before anyone has looked at your systems. It is either padded to cover the unknowns, or it will be defended later through change requests. A more honest structure is a small paid discovery that produces a documented scope, an architecture, and a costed plan you own — and can take elsewhere if you want to.
Ongoing cost belongs in the conversation too. Software has a running cost after launch: hosting, dependency updates, security patches, browser and OS changes, and the changes your own business will ask for. A build quote without a support conversation is an incomplete picture.
The Short Version
Cost tracks complexity, not screens. Integrations, data, and compliance drive the number more than feature count does. The buyer-side levers — a clear process, fast decisions, disciplined scope, and shipping in slices — are usually worth more than any negotiation on rate.
Related service: Product engineering and custom software delivery