The honest answer is “it depends”, but that is not a useful answer. So here are ballpark figures, what makes them vary, and the costs people often forget to plan for.
Ballpark figures
These ranges reflect projects delivered by a small team in Quebec. They help frame a budget; they do not replace an estimate.
| Type of project | Typical budget | Typical duration |
|---|---|---|
| Simple automation (a report, a sync) | $3,000 to $15,000 | 2 to 6 weeks |
| Internal tool (quotes, timesheets, inventory) | $20,000 to $80,000 | 2 to 4 months |
| Client portal or mobile app | $40,000 to $120,000 | 3 to 6 months |
| Complex platform or SaaS product | $120,000 and up | 6 months and up |
An experienced developer in Quebec typically charges between $100 and $175 an hour. The price of a project therefore depends mostly on the number of hours, and that is where the gaps appear.
What drives the price
The number of screens and business rules. A form that saves data is cheap. The same form with calculations, per-client exceptions and an approval process costs much more. Rules, not screens, take the time.
Integrations. Connecting to software with a modern, documented API takes a few days. Connecting to an old system without an API can take weeks.
External users. A tool used by five employees at the office is simpler than a portal used by hundreds of clients, which needs more thought about security, support and the mobile experience.
The quality of existing data. Migrating ten years of inconsistent Excel data is often the most underestimated part of a project.
Recurring costs
Software is not a one-time purchase. Plan for:
- Hosting: $20 to $300 a month for most small business tools.
- Maintenance: security updates, fixes, compatibility with new browsers. Budget roughly 15 to 20% of the initial cost per year.
- Third-party services: email sending, maps, artificial intelligence, billed by usage.
How to lower the cost without cutting quality
The best way is to deliver a limited first version that solves the most expensive problem, then add the rest based on what users actually ask for. On many projects, some of the features planned at the start are never requested once the first version is in use.
Two other habits help:
- Write down the current process before talking about software. Grey areas on paper turn into development hours.
- Check whether an existing product will do. If it does, it will almost always cost less. We cover this in our article on custom versus off-the-shelf software.
What about grants?
Some government programs can fund part of a digital transformation project. Programs change often: check with your MRC, Investissement Québec or your local economic development office before you start.
Getting an estimate
A serious estimate takes a one-hour conversation about your actual need. We then provide a written estimate broken down by stage, so you know what each part costs. Tell us about your project.