Custom software has no single reliable price without a defined scope. Ask for a CAD quote that separates discovery, implementation, integrations, migration and ongoing support. Compare proposals against the same acceptance criteria and assumptions. This guide explains the cost drivers; it does not present unverified market price bands or a 360ISS price list.
How should you compare project estimates?
Ask each supplier to explain the work behind its quote. A screen count alone does not capture integration failures, permission rules or migration effort.
| Project type | Scope questions for the quote |
|---|---|
| Single integration | Which API, authentication, retries and reconciliation are included? |
| Internal workflow tool | Which roles, approvals and exception cases must work? |
| Customer portal | What access controls, support and data migration are required? |
| Business system | Which integrations and existing records must move together? |
| Regulated platform | Which applicable controls and evidence must be delivered? |
Request a schedule tied to these deliverables, with dependencies and acceptance tests. Treat any estimate as conditional on the written scope.
What drives the cost of custom software?
The biggest cost drivers are integrations, unclear requirements, data migration, security and compliance, and the number of user roles. Screens and features matter, but they are rarely what blows a budget. In our experience, the surprises come from the systems around the software and from decisions nobody made before the build started.
- Integrations. Every connection to accounting, CRM, ERP or a bank adds design, testing and failure handling. An older system with no API costs far more to connect than a modern one.
- Requirements clarity. A process that has never been written down gets discovered during the build, which is the most expensive time to discover it.
- Data migration. Moving years of messy spreadsheet or legacy data is often a project of its own.
- Security and compliance. Personal information under PIPEDA, financial data, or audit trails add design work, testing and documentation.
- Roles and permissions. Three user types with different access is a different system from one.
- Who builds it. Compare relevant experience, deliverables and support responsibility rather than hourly rate alone.
The cheapest way to reduce cost is to map the process before quoting. Our business process mapping template is a reasonable place to start.
Should you build custom software or buy off the shelf?
Buy when an existing product covers most of your process and your process is not what makes you different. Build when the workflow is specific to how you win, when off-the-shelf tools force costly workarounds, or when you need several systems to behave as one. Often the right answer is buy, then integrate.
| Factor | Buy (SaaS or package) | Build (custom) |
|---|---|---|
| Upfront cost | Subscription and configuration | Discovery and implementation |
| Time to start | Depends on setup and migration | Depends on scope and dependencies |
| Fit to your process | You adapt to the tool | The tool adapts to you |
| Ongoing cost | Per-user subscription, rising with headcount | Hosting, support and changes |
| Ownership | Vendor licence and roadmap | Rights defined by the contract |
| Switching risk | Vendor price changes or shutdown | Dependence on the team that built it |
A middle path is common: keep the SaaS tools your team already likes and connect them properly. That is often cheaper than replacing them, and it is the core of our system integration work. For lighter connections, a low-code platform may be enough; see n8n vs Zapier vs Make.
What ongoing costs should you budget for after launch?
Budget hosting, monitoring, updates, support and integration upkeep separately. Ask for the assumptions behind each line and a process for approving changes. There is no verified universal support percentage in this guide; use your actual systems, traffic, service level and supplier quote.
- Hosting and infrastructure. Often modest for internal tools, higher for customer-facing systems with real traffic.
- Third-party services. Email delivery, maps, AI model usage, payment processing and similar per-use fees.
- Security and dependency updates. Libraries and frameworks need patching, whether or not you add features.
- Integration upkeep. When a connected vendor changes its API, your integration has to change too.
- Enhancements. Once people use the software, they ask for improvements. That is a good sign, and it costs money.
Ask any vendor, including us, what a support arrangement looks like before you sign the build contract.
Can SR&ED help pay for custom software?
Eligibility depends on the work, not on calling it software or AI. The CRA eligibility guidance explains the scientific or technological uncertainty and systematic investigation requirements. Review those criteria with a qualified adviser before assuming any incentive in a project budget. Source checked October 8, 2026.
We mention these programs in general terms only. Eligibility rules, documentation requirements and funding availability change, and a claim that fails review is worse than no claim. If you think your project involves real technical uncertainty, talk to an accountant or SR&ED specialist early, because the documentation needs to be kept during the work, not reconstructed afterwards.
How do you keep a custom software budget under control?
Keep budgets under control by fixing the scope of the first release, building the smallest version that solves a real problem, and paying in milestones tied to working software. Projects go over budget when the first release tries to do everything, or when nobody owns decisions on the client side.
- Map the current process first. Know what happens today, including the exceptions.
- Define a first release. Pick the one workflow that saves the most time or removes the most risk.
- Ask for a phased quote. Discovery, then build, then support, each with its own price.
- Name one decision-maker. Slow decisions cost more than most features.
- Measure the return. Our AI automation ROI calculator shows the kind of numbers worth tracking.
A fixed price on a vague scope usually means either padding or change orders. A clear scope makes both sides more honest.