Custom software costs in Quebec: compare equivalent quotes

Describe what someone must finish: receive a request, check a customer record, approve a proposal and send information to accounting. Include exceptions employees actually encounter. A list of screens leaves important decisions open. Who fixes an incomplete record? Who approves an exception? What happens when an external service replies late? Those answers affect the work a supplier must estimate.

For a custom CRM or ERP, separate the first usable workflow from later improvements. Searchable history may be enough for launch, with older attachments migrated in a later phase. Ask the business owner to approve that boundary before requesting quotes. Suppliers can then describe the same assignment rather than silently filling the gaps with different assumptions.

Create one row for each expected outcome. Ask each supplier for a deliverable, a volume assumption and exclusions. An empty cell requires a question; it does not mean the work is free. The comparable cost includes the supplier’s proposal and any activities your company must buy elsewhere or perform internally. Keep that internal effort visible even when it never appears on an invoice.

Check who funds preparation on the customer side. If your operations manager must clean data or approve hundreds of mappings, record that workload in the internal budget. Compare payment milestones and change procedures too. A fixed price with testable assumptions and time-based billing with an approved spending limit serve different situations. Both need a person who can authorize a change and explain its impact.

Consider a wholly fictional SME planning a request portal connected to its accounting system. The calculation uses 100 CAD per hour solely to make the arithmetic easy to inspect. This is neither a Daillac rate nor a Quebec market average. Assume 600 hours for the workflow, access controls and testing, followed by 120 hours for a documented integration.

With consistent source files, assume migration takes 80 hours. The illustrative total is 800 hours, or 80,000 CAD before tax. If those files require 240 hours of cleaning and reconciliation, the total becomes 960 hours, or 96,000 CAD. The 16,000 CAD difference comes from one changed assumption. These figures describe a planning exercise and do not report measurements from a real project.

Before accepting either scenario, have a representative sample examined. Include accented names, missing identifiers, duplicate customers, incompatible dates and closed records. Request an anomaly report and a rule for resolving each category. When two customers share an email address, the business team must decide whether they are duplicates. A developer cannot reliably infer that relationship from the file alone.

In the same fictional exercise, add 4,800 CAD for hosting over 36 months, 14,400 CAD for support and 12,000 CAD for authorized improvements. The consistent-data scenario reaches 111,200 CAD before tax. The difficult-data scenario reaches 127,200 CAD. Both exclude employee time and any unidentified third-party licence. Replace these assumptions with the terms of your actual project before using the model for approval.

Cash flow describes when money leaves the business. Ownership cost describes what the business takes on during the selected period. Request payment milestones linked to reviewable deliveries: a design package, a usable workflow, a validated migration and an operational handover. Keep an identified reserve for unresolved decisions and name the person permitted to spend it. A reserve without ownership can disappear into unrelated requests.

A custom web application project should define acceptance criteria during scoping. For an accounting synchronization, check a successful send, a rejected record, recovery and a repeated delivery. For permissions, request allowed and denied scenarios. OWASP ASVS helps frame application security controls, while NIST SSDF describes secure development practices. Naming either framework in a proposal does not certify the resulting application.

Where personal information is involved, ask the designated privacy lead to review applicable obligations. Quebec’s privacy regulator explains privacy impact assessments for the relevant projects. Data mapping and retention decisions can change the assignment and should have an owner and a schedule. Canadian hosting alone does not settle every obligation. Any legal assessment must address the actual organization and data flows rather than a generic location statement.

CRM and ERP automation also introduces operating expenses, including subscriptions, monitoring and failed-operation handling. Ask who receives an error and who may retry a transaction. A proposal becomes decision-ready when its assumptions, acceptance evidence and customer responsibilities are understandable. Keep the comparison grid with the signed scope so the same baseline remains available when someone requests an additional feature.