Buyer guide

What custom software costs in Canada and how to budget for it

Custom software costs what its rules, integrations, data and risk require, plus years of running it. Budget well by funding a short discovery, then a clearly scoped first release, with a yearly maintenance amount from day one.

The short answer

Nobody can honestly price custom software before understanding the work. Cost follows things you can identify early: business rules and exceptions, roles and approvals, integrations, data migration, and security, privacy and audit obligations, plus hosting, support and maintenance every year it runs. Budget in three pieces: a fixed-scope discovery, a first release on the most valuable problem, and a yearly running allowance. A quote without them? Ask why.

What actually drives the cost

Screens are not what make software expensive. Rules, connections and data are.

Cost driverWhy it matters
Business rules and exceptionsEvery "except when" needs design, code and tests; most effort goes here
User roles and approvalsEach role needs permissions, screens and tests, including what it must not see
IntegrationsYour ERP, CRM, accounting or Microsoft 365 set APIs, limits and data quality
Data migrationOld spreadsheets and databases hide duplicates, gaps and unwritten rules
Security, privacy and auditPIPEDA or provincial obligations; some processes need full audit trails
Accessibility and languagePublic software may need accessibility standards; many need English and French
Hosting and availabilityOffice-hours tools cost less to run than around-the-clock ones
What to have ready for each driver
  • Rules and exceptions: real awkward cases, not just the normal path.
  • Roles and approvals: who does what, and who signs off.
  • Integrations: system names, editions and administrators.
  • Data migration: sample exports, and an owner who decides what is correct.
  • Security, privacy and audit: privacy commitments, retention rules, customer or regulator requirements.
  • Accessibility and language: who the users are, including any members of the public.
  • Hosting and availability: how much downtime the business can tolerate.
Two Canadian notes. PIPEDA's ten fair information principles (or the provincial law that applies) shape consent, access and retention design. Ontario businesses and non-profits with 50 or more employees must make public websites and web content meet WCAG 2.0 Level AA, with limited exceptions. Designing for both from the start costs far less than retrofitting.

Why quotes for the same project differ so much

Far-apart quotes on one brief usually price different things:

Exceptions

One firm priced the happy path; another, the edge cases you mentioned in passing.

Testing and documentation

Tests, pipelines and handover docs take time. Leaving them out looks cheaper, then costs more to own.

Data migration

Often left vague as "your job". Ask who moves it and how results are checked.

Risk

A fixed price includes a buffer for uncertainty; time and materials shows you the uncertainty instead.

Ownership

Source code, infrastructure and accounts should end up in your organization's name.

On ownership: under section 13 of Canada's Copyright Act, the author (or the author's employer) is generally the first owner of copyright and an assignment is only valid in writing, so code from an outside firm needs a written assignment or licence in the contract.

Compare fairly by asking each firm to list its assumptions and exclusions. The cheapest total with the longest exclusion list is rarely the cheapest project.

How to build a realistic budget

  1. Fund discoveryMaps process, rules, data, systems; ends in scope, release plan, CAD estimate.
  2. Size release oneThe most valuable problem, not the whole wish list.
  3. Hold contingencyRequirements change once people see working software; that is healthy.
  4. Fund running costsHosting, security updates, monitoring, support, small improvements, every year.
  5. Check incentivesSR&ED rewards R&D in Canada; most routine software will not qualify.

Discovery is the cheapest point to learn the project is bigger, smaller or different. A release that properly replaces one painful spreadsheet or approval beats a broad one done half-way. Unfunded software becomes a risk, however good the first version. SR&ED eligibility is decided under CRA rules: speak to your accountant before counting on it. General information, not tax advice.

Example: a hypothetical budget structure
Demonstration, not a client project

Hypothetical budget structure: a mid-sized distributor replacing a spreadsheet-based returns process.

  • Discovery (fixed scope): map returns, list exceptions, review ERP integration options, produce scope and phased estimate.
  • Release 1: returns requests, approvals and credit notes pushed to the ERP, for two user roles.
  • Release 2 (only if release 1 proves its value): customer self-service portal and reporting.
  • Contingency: part of each release held for changes found in testing.
  • Yearly running allowance: hosting, monitoring, updates and a small block of improvement hours.

Each line carries its own CAD estimate and assumptions.

Rather talk it through? We can turn your process into a written scope and a phased CAD estimate before you commit a full budget. Talk to a Promatics specialist

The questions people ask before they call us

"We are too small for custom software." Sometimes true: if a packaged product fits with configuration, buy it. Custom earns its place when the process is yours alone and workarounds cost time every week (build, buy or integrate guide).

"Can AI tools build this for less?" AI coding assistants speed up parts of development, and we use them, with people reviewing the output. They do not uncover your exceptions, settle conflicting rules, test on your real data or answer for the result when it breaks. That judgement and accountability are most of what you pay for.

"What if the project runs over?" Each phased release is scoped, estimated and accepted on its own: you can pause, change direction or stop and still have something usable.

What working with Promatics looks like

  1. DiscoverA written recommendation, which may be buy or integrate, not build.
  2. First releaseAgreed scope, delivered in short iterations with regular demonstrations.
  3. MigrateYour data moved and reconciled.
  4. Hand overSource code, documentation and infrastructure in your organization's accounts.
  5. SupportA separate agreement, so you know exactly each year's cost.

See custom software development for the full approach.

When to bring in help

  • You can describe the process, not yet its exceptions or data.
  • It will hold personal information or support auditable decisions.
  • It must connect to at least one system you do not control.
  • Nobody will be funded to maintain it after launch.
  • Your quotes cannot be compared because they assume different things.

None apply and the tool is small and internal? A capable in-house developer or low-code platform may do. Two or more? An experienced partner usually pays for itself by getting scope and ownership right before money is spent.

Sources and further reading

Product capabilities and guidance change. These are the primary sources this article relies on, checked on the review date above.

  1. Scientific Research and Experimental Development (SR&ED) tax incentives, Canada Revenue Agency
  2. PIPEDA in brief, Office of the Privacy Commissioner of Canada
  3. How to make websites accessible, Government of Ontario
  4. Copyright Act, section 13 (ownership of copyright), Justice Laws Website, Government of Canada

This article is general information, not legal, accounting or security advice for your specific situation. Examples are hypothetical unless stated otherwise.

Talk to Promatics

Get a written scope and estimate before you commit a budget

Budgeting for unseen software is stressful, and sales-call numbers rarely survive. We map your process and give a phased CAD estimate with written assumptions.

  • Discovery ending in a written scope and CAD estimate
  • Phased releases, so you can stop or change course safely
  • You own the source code, documentation and accounts