It’s usually the first question on a scoping call, and it’s a fair one. You have a budget to defend, a partner or a board to answer to, and every vendor you talk to says “it depends.”
It does depend, but not in a mysterious way. The price of custom software follows a short list of things you can name and write down before anyone writes code. Once they’re on paper, a fixed price becomes possible.
This article walks through those cost drivers in plain terms, shows the prices we actually publish, and explains how to get a quote you can hold a vendor to. You won’t find a market average here. We haven’t seen one we’d trust, and your project won’t be average anyway.
1. Why a one-line brief can’t get you an honest number
“An app like Uber, but for dog walkers” could be a three-screen booking tool. It could also be a two-sided marketplace with payments, payouts, ratings and dispute handling. Both fit the same sentence. A vendor who prices that sentence on the spot is either guessing or padding the number to cover the guess.
What turns a guess into a price is detail: who uses the system, what each person needs to do, which other systems it talks to, and where the data lives. Getting there usually takes a focused conversation or two, not a months-long study.
For managers: Be careful with any firm price given before someone has asked about your users, your data and your integrations.
2. Scope: workflows and user roles move the number most
Count the jobs people do in the system rather than the screens. “A customer books, a staff member confirms, a manager sees the report” is three workflows. Each one needs its own screens, rules, error cases and tests.
User roles add up faster than most people expect. Once customers, staff, managers and admins each see different data and can do different things, permissions become a feature of their own. Getting them wrong is a security problem, so they deserve real design and testing time.
For managers: Before you ask for a quote, list every type of user and the few things each one has to do. That list does more for accuracy than any feature wish list.
3. Every integration is a small project of its own
Payments, accounting, your CRM, a shipping carrier, a government portal, an AI model: each connection needs authentication, error handling, retries and a plan for when the other side changes or goes down. Some providers have clean, well documented APIs. Others have thin documentation and a test environment that behaves differently from production.
This is also where surprises tend to show up. An integration a vendor lists as “supported” and one that works with your setup aren’t always the same thing, and we’ve learned that on our own products.
For managers: Name every outside system the software has to talk to, and ask how each one is priced and tested.
4. Your existing data has a cost too
If you’re replacing spreadsheets or an older system, the data has to come across. Old fields get mapped to new ones, duplicates and gaps get cleaned up, and someone decides what happens to records that don’t fit the new rules. Migration is often scoped late and priced as an afterthought, which is exactly how it becomes the line item that runs over.
A trial migration on a copy of the real data, early in the project, shows how messy things actually are while there’s still time to plan for it.
For managers: Ask for data migration as its own line in the quote, with a trial run on real data well before go-live.
5. Compliance and where the data lives
Software that handles health records, financial data or personal information about Canadians has to be designed for privacy from the first data model. You need to know who can see what, where it’s stored and how access is logged. PIPEDA and sector rules are far cheaper to build in than to retrofit before an audit.
Hosting location belongs in the same conversation. When a client needs data kept in Canada, we can run the system in AWS’s Canadian region (ca-central-1). It’s an easy choice on day one and an expensive one to change later.
For managers: If your data is sensitive, say so in the first conversation. It shapes the architecture, so it shapes the price.
6. Launch isn’t the last invoice
Software in production needs hosting, monitoring, security updates and someone who answers when something breaks. Libraries age, cloud providers retire services and browsers change. A quote that stops at launch leaves all of that out, which makes it look cheaper than one that includes it.
For small businesses, the closest thing we publish to a price list shows the shape. Our website, CRM and advertising packages have a fixed setup fee and a fixed monthly fee: Foundation at CAD $4,500 plus $650 a month, Growth at $8,500 plus $1,200 a month, and Scale at $15,000 plus $2,250 a month, all before tax. The monthly part covers hosting, the CRM, campaign management and ongoing optimization. Custom software beyond those packages gets its own written quote, but it follows the same pattern of a build price plus a running price.
For managers: Compare quotes on the total cost of the first year or two, build plus running costs, rather than on the build price alone.
7. How to get a quote you can hold someone to
Start with a scoping conversation where the vendor asks about users, data, integrations and deadlines. What should come back is a written proposal with scope, architecture, milestones and price. At CS2 we quote a fixed price once that written scope exists. The work then runs in four phases: scoping, architecture with a first working slice, short build increments with demos, and handover. Each phase is signed off in writing before the next one begins.
Changes will come up, because you learn things once you see working software. The fair way to handle them is to price each change before it’s built, so you decide with the number in front of you. If the starting point is an older system nobody fully understands, a fixed-scope technical assessment with a written report is a smaller first step that gives the bigger quote a solid base.
Finally, check who owns the result. With us, the code lives in your repository and the cloud accounts are in your name from the start.
For managers: A quote you can rely on rests on a written scope, a clear change process and ownership in your name. Ask for all of it before you sign.
The short version
Custom software costs what its scope, integrations, data, compliance needs and running costs add up to. None of that is mysterious, and all of it can be written down before the build starts. Get it on paper, ask for a fixed price against it, and compare vendors on the full cost over time.