ServiceTitan dispatches your Quebec City crews in English and forgets it snows here

A core dispatch and invoicing tool runs $40k to $60k CAD over 3 to 4 months, and a platform with safety and inventory is $65k to $100k. Multi-crew enterprise systems start around $120k. French-first dispatch and integrations drive most of the cost.

Those tools are built for US trades, so they run English-first and patch QST onto a US tax model, and they do not handle CNESST safety or storm-season dispatch well. For a French-first winter operation, those gaps show up daily. Custom software makes French, Quebec tax, and winter scheduling native.

Yes, dispatch and the mobile app are French-first, which speeds crews and reads properly to clients under Bill 96. An English-only app slows every job. Bilingual communication with customers is built in.

Yes, GST and QST are built into invoicing rather than patched onto a US tax model, so every invoice is correct. That removes a recurring source of errors for Quebec City trades. The tax logic is tested against your real job types.

Yes, scheduling handles storm-season emergencies and seasonal capacity swings that generic schedulers manage poorly. For HVAC and snow-removal operators, that is the difference between coping and scrambling during a storm. The dispatch model is tuned to your peak.

Safety checklists and incident logs attach to each job, so CNESST records live with the work instead of a separate binder. US field-service tools have no concept of this. The specific safety workflows are captured in discovery.

A core dispatch and invoicing tool ships in 3 to 4 months and a fuller platform in 4 to 6 months. Field testing with crews adds time because adoption matters. We pilot with a crew before full rollout.

Yes, you own the code and data, with no per-technician subscription that grows with your crew. Ownership lets you adapt scheduling and safety workflows as you grow. You also choose hosting.

You retain the build team or an internal owner to update GST, QST, and CNESST logic when rules change. Budget for that maintenance. Documentation keeps updates manageable.

The reliable signals are re-typing the same data into multiple tools, one employee acting as human middleware between systems, and errors appearing in handoffs between teams. Hard limits force the issue too: Airtable's Team plan caps at 50,000 records per base, and Business costs $45 per seat per month, so a 20-person team pays about $10,800 a year for a tool it has already outgrown. When workarounds consume more hours than the tools save, the spreadsheet era is over.

Yes, when it is architected for growth from day one, and scale is where custom wins because cost per technician falls as you add crews instead of rising with every seat license. The real scaling work is operational: multi-branch dispatch, role permissions, and roll-up reporting, which usually arrives as a phase two costing 30 to 50 percent of the original build. State your three-year headcount plan in the first scoping call so the data model supports branch two before branch two exists.

No, most software projects run fully remote without any quality penalty, and what actually matters is 3 to 4 hours of working-hour overlap and a fixed weekly demo call. A team based in Quebec City earns its premium in specific cases: hardware installations, warehouse or clinic floor shadowing, and discovery workshops where watching your staff work beats any written brief. Choose for senior engineers and a track record first, and treat geography as a tiebreaker.

Ask one question first: how does your build handle a technician who goes offline mid-job and is reassigned server-side while disconnected. Teams that have shipped field service software answer in specifics about sync and conflict rules; teams that have not talk about frameworks. Then ask to see a previous dispatch board and technician app running, and have them spend a day riding along with your Quebec City crews before the spec is written, because software scoped from an office rarely survives the field.

A true ServiceTitan clone would cost millions and you do not need one, because companies that bring this request to Digital Heroes typically use 20 to 30 percent of its features. Building that slice, shaped to your exact dispatch board and technician day, runs $80,000 to $200,000 depending on offline requirements and integrations. The field service builds that succeed copy a workflow, not a product.

Version one needs the daily loop and nothing else: job creation, a drag-and-drop dispatch board, a technician mobile app that works offline, photo and signature capture, and invoicing that reaches your accounting system. Customer portals, route optimization, inventory, and reporting dashboards belong in phase two. The test for every feature is whether a dispatcher or technician touches it every day; if not, cut it.

Plan on 12 to 16 weeks for a working first release covering scheduling, dispatch, and a technician mobile app, and 5 to 7 months for a full platform with offline mode and accounting sync. Across 2,000+ Digital Heroes projects, field service timelines slip in two predictable places: underscoped offline behavior and integration testing against QuickBooks or the payment processor. Both belong in week one of planning, not month four.

Four mistakes cause most failures: scoping only the happy path so offline work and job reassignment surface later as change orders, leaving QuickBooks sync until the end instead of designing for it, skipping technician input until launch, and having no post-launch support plan. Across 2,000+ Digital Heroes projects, failed field service builds almost always failed on process, not programming. Every one of these is prevented in the scoping phase, which is why discovery matters more than the framework.

A one-page brief beats a 40-page requirements document: the business problem in plain words, who will use the system, the 5 to 10 workflows it must handle, the tools it must connect to, and your budget range and deadline driver. You do not need wireframes, a specification, or technical vocabulary; producing those is the agency's job during discovery. Stating a budget range up front is the single best move, because it gets you honest scoping instead of a quote engineered to win the meeting.

You should, completely, through a written intellectual property assignment that transfers everything on final payment; without that clause, copyright stays with whoever wrote the code by default. Insist that the repository lives in your own GitHub organization from day one and that hosting, domains, and third-party accounts are registered to you. Also check for licenses to the agency's proprietary frameworks buried in the contract, because those can make switching vendors practically impossible even when you own your own code.

Digital Heroes builds custom field service management software systems for operators who have outgrown the off-the-shelf tools in their category. The work is delivered remotely: our engineers work from Delhi and Lucknow, leadership is in New York, and some team members live in London and Sydney and work remotely from there. We have no office in Quebec City. You can chat with the team directly, and every form gets an email reply within 24 hours.