Why two apparently similar applications cost different amounts
A simple request form can lead to a straightforward internal list or to a multi-company approval process with sensitive attachments, several roles and connections to legacy systems. The screen looks similar; the work behind it does not.
Rather than applying an unverified price range, compare projects by their assumptions: what is included, what is excluded, what must be investigated and what counts as acceptance.
The factors to include in an estimate
| Factor | Questions that change the scope |
|---|---|
| Workflows and rules | How many complete processes, exceptions, calculations and approvals are required? |
| Users and permissions | Who can read, change, approve or export each kind of information? |
| Interface and design | Which tasks, devices and accessibility needs must the interface support? |
| Integrations | Are usable APIs available? What happens when another system is unavailable? |
| Migration | How much cleaning, mapping, history and verification do the existing files require? |
| Data and operating requirements | What volumes, availability, access controls, backup and recovery expectations apply? |
| Testing and adoption | Who checks the application, trains users and supports the changeover? |
Three scope scenarios to compare
A focused internal tool
One team follows one workflow with a limited number of roles. The estimate still needs to cover validation, deployment and how the tool will be operated.
An application connected to existing systems
Data flows between the new tool and other software. Matching records, handling failures and testing external dependencies become significant parts of the work.
A customer-facing portal
Several organizations or customers access their own data. Account journeys, permissions, support and operating expectations require more detailed planning.
What costs remain after delivery?
The initial build is one part of the cost. Compare the intended period of use and include the operating work that each option requires.
Hosting and external services
Infrastructure, storage, email delivery, third-party APIs or AI usage may create recurring charges. Usage assumptions belong in the estimate.
Maintenance and support
Updates, incident handling, backups and checks need a responsible owner. Coverage and response expectations must be agreed; they are not automatically included in development.
Changes and internal effort
New features, changing external APIs, data cleanup, user training and time spent validating releases all affect the total cost.
Reduce the first scope without losing the purpose
Choose one complete business outcome rather than fragments of many workflows. Retain working tools, defer uncommon exceptions when a safe manual process exists and avoid rebuilding standard features already available in a suitable product.
Do not remove essential access checks, data verification or failure handling simply to make the first quote look smaller. Record deferred features and dependencies explicitly so the first release remains usable.
Compare SaaS, no-code and custom softwareWhat to prepare for a useful estimate
The process and its owner
Who does the task, what triggers it, how often it happens and where time or information is lost.
An example and desired outcome
An anonymized file or walkthrough, including an exception, plus a description of what a successful first version must let users do.
Constraints
Existing tools, expected users, important dates, data sensitivity and any budget boundary you already have.
Commercial questions
Ask about exclusions, change requests, code rights, access, hosting, support and recurring charges before comparing quotes.
Common questions
Can BSAE give a price before reviewing the project?
A meaningful quote needs a defined scope and its main assumptions. Describe the process first so that the simplest suitable solution can be identified and estimated.
Is custom software always cheaper than subscriptions?
No. Compare configuration, licences, integration, internal work, maintenance and exit costs over the same period. A subscription may be the more economical choice.
How can we compare two quotes fairly?
Compare the same workflows and acceptance criteria, then check migration, testing, hosting, support, ownership terms and exclusions. A lower initial amount may cover a different scope.