If you are weighing an internal mobile app for field staff in Canada, you probably already know what the current system costs. Someone re-keys timesheets on Friday. A photo of a serial number sits on one technician's phone. An invoice waits three days because the customer's signature is on a clipboard in a van. An app is the usual way out, but the decision has two parts: whether to buy existing field software or commission something built for your business, and what the app must do when the signal drops in a basement.
Internal mobile app for field staff in Canada: what it has to do
An internal app is used by your own employees to do their work. Crews receive jobs, log time, take photos, complete checklists and collect signatures. Customers may receive the output, such as a job sheet by email, but they never log in. A customer-facing app is about winning and keeping customers. An internal app is about getting the crew and the office working from the same facts.
Most builds use a cross-platform framework such as React Native or Flutter, or native code in Swift for iPhone and Kotlin for Android, with data held on services such as Firebase, Supabase or a Node.js back end. Those choices matter to your developers. For you, the question is what the app has to do on site.
Jobs, photos, forms and signatures
Walk through a normal day for one crew. The crew lead opens the phone and sees the jobs assigned to them, rather than a spreadsheet that may or may not be current. On arrival they check in, and the time is recorded. They take photos before, during and after the work, each tied to the job. They complete a checklist of safety or inspection steps that must be done before the job can close. They log the parts they used from the van, so stock in the office updates without a separate count. The customer signs on the screen, and a copy goes out by email. The job is marked complete, and the office sees it that afternoon.
Each step sounds small. Together they are the work, and each one is a place where information can get lost.
Where spreadsheets break down
Spreadsheets work until there are two of them. The office has one copy, the crew has a copy on a tablet, and the version on the van is last Tuesday's. Timesheets get entered from memory a week after the shift. Photos live on personal phones, and some disappear when those phones are replaced. Invoices wait for paperwork, so billing slips by days or weeks.
None of this is a people problem. Your team has built workarounds that get the job done with the tools they have. The cost of those workarounds is delay and error, and the office pays for it in re-keying and chasing. That cost is the number to put in front of the board.
Buy or build: when each option wins
This is a framework for deciding, not a verdict. Packaged field service platforms, such as Salesforce Field Service and IFS, are built for common field workflows and can go live quickly. A custom build makes more sense in other cases.
Off-the-shelf usually wins when:
- Your jobs match the vendor's standard job types closely.
- You need to be running in weeks, with a small number of users.
- The vendor's data model and reports cover what management asks for.
- You do not need deep links to your own accounting, ERP or CRM.
Custom usually wins when:
- Your process has steps the templates do not cover, such as specific inspection sequences, multi-stage approvals or unusual pricing rules.
- Offline use is central and a standard product's offline mode is limited.
- The app has to write directly into your own ERP, accounting or CRM.
- You want to own the code and the app store accounts, rather than rent them.
Eskore builds custom internal apps. If a standard product fits your workflow better, we will say so on the scoping call, and you can decide from there. If you are unsure which route suits your business, our consultancy and strategy team can give independent advice. The choice should rest on your workflow, not on what we happen to sell.
Do per-user licences add up over time?
Per-seat pricing is simple with ten users and awkward with eighty. Each new technician adds a monthly line. For illustration only: at a hypothetical CAD 10 per user per month, 40 field staff come to CAD 4,800 a year, before setup, configuration or add-on modules.
Check the current pricing page for any product you are considering, and read what each tier includes. Offline use, reporting and integrations are often the features that decide which tier you need. Then ask three further questions. Who pays for configuration? Who updates workflows when your process changes? Can you export your data if you leave?
When a custom build pays back
A custom build pays back in three situations. The first is a workflow that does not fit a template, where staff have worked around the software for years. The second is data that must stay in your own accounts, for legal, commercial or operational reasons. The third is a need to talk to your ERP or CRM, so the office does not re-enter what the crew has already recorded.
Payback comes from removing re-keying, chasing and workaround spreadsheets. Put a number on the hours the office spends re-entering field data each week, and on the days invoices sit waiting for paperwork. Those two figures usually decide the business case more than the build price does.
Our custom software built around your process and mobile app development for field teams services cover this kind of build.
Offline first: questions to put to any builder
Offline is the central technical risk for field staff, and the part most often underestimated. Offline-first means the phone is a place to work, not just a window onto a server. Jobs are downloaded in advance. Entries are saved to the device first. When a connection returns, the app sends the queued changes to the server. The idea is simple to describe and hard to build well.
These are the questions an operations manager should put to any builder:
- Which screens must work with no signal, and which can wait for a connection?
- How much data is stored on the device, and what happens when the job list outgrows the phone's storage?
- How are photos and forms queued, and do they upload in a set order?
- What does the user see while something is waiting to sync?
- When two people change the same record, who wins, and where is that rule written down?
- What happens if a phone is lost or damaged with unsynced data on it?
- Is every change logged, with who made it, from which device, and when?
- How will offline behaviour be tested: in a basement, in a truck, on a weak connection?
A builder who answers these in detail has done this before. A builder who says "it works offline" and moves on has not.
How sync and conflicts work in plain English
The phone keeps its own copy of the data it needs. Changes made on the phone go into a queue. When the connection returns, the queue is sent to the server, usually in the order the changes were made, because some changes depend on others. A new job has to exist before a photo can be attached to it.
A conflict happens when two people change the same piece of data without seeing each other's change. The resolution rule can be simple, such as "the most recent change wins". It can be more detailed, such as "the office controls the scheduled date and the crew controls the status". It can also require a person to review the clash.
The conflict rule is a business decision, not a technical detail. Your operations manager has to decide who owns which information, and a builder cannot guess that from the outside. If the rule is not in the scope, you will discover it during testing, or in a dispute about a job.
Worked example: two supervisors edit the same job in a basement
An illustrative example: a crew is servicing a commercial boiler in a building basement, where the phone has no signal. At 10:12 am, the crew lead changes the job status to "On site, parts needed." The phone saves the change locally and queues it. The screen shows "Saved, waiting to sync."
At 10:20 am, the dispatcher in the office learns the parts supplier has delayed delivery. She moves the job's scheduled date from Thursday to Friday. That change saves to the server immediately.
At 11:05 am, the crew lead climbs the stairs and gets a signal. The queued status change is sent to the server.
Here is what a well-built app should do.
The two edits do not actually conflict. Status and scheduled date are separate fields. Both changes apply, and the job shows "On site, parts needed" with a Friday date. A good scope lists which fields each role can change, so most apparent clashes never reach the conflict rule.
A true clash needs a rule. Suppose the dispatcher had set the status to "Cancelled" at 10:20 while the crew had set "On site" at 10:12. Both edits touch the same field. A sensible rule keeps both entries, flags the job and asks the dispatcher to confirm the result that day. Silently overwriting one edit is how jobs get lost. Whatever you choose, write it into the scope before anyone builds it.
The audit trail shows the sequence. Each entry should record the user, the device, the time on the device, the time the server received it, and the old and new values. The server's time is the reference, because phone clocks can be wrong. Here, the trail shows the 10:12 status change arrived after the 10:20 office change, so anyone reviewing the job can see exactly what happened.
The users see something useful. The crew lead sees "Saved, waiting to sync" at 10:12 and, after the sync, a notice that the office changed the scheduled date to Friday at 10:20. The dispatcher sees the field status in the job history, marked with the time it was made offline. Designing those notices clearly is part of UI/UX design.
How much does an internal field app cost in Canada?
Published cost guides disagree, and they rarely explain why. The figures below are published estimates, not quotes. Use them to ask better questions, not as a budget.
Published Canadian cost ranges
The closest match to an internal staff app is the Edmonton range from Digital Heroes. Its 2026 Edmonton guide puts an internal tool or simple web app at CAD 25,000 to 60,000. Its 2026 Calgary guide gives CAD 60,000 to 100,000 for an offline-first field app on a single platform.
Modall's 2026 mobile app cost guide puts a simple MVP at CAD 15,000 to 40,000 and a standard app at CAD 40,000 to 100,000. Its 2026 custom field service software guide gives CAD 30,000 to 500,000 or more, depending on scope. The same 2026 guide lists developer rates of CAD 80 to 150 per hour for reputable Canadian developers.
These sources do not agree, and the gap is mostly scope. An MVP with one user role and no integrations sits at the bottom of the range. A multi-role app with offline sync, ERP links and data migration sits at the top. Ask any builder which of those they are pricing before you compare numbers.
Cost drivers for an internal tool
Use this table to compare quotes line by line:
| Driver | What moves the cost | Question to ask |
|---|---|---|
| Number of roles | Each role adds screens, permissions and test cases | Which roles exist, and what can each one see and change? |
| Offline depth | A few screens working offline costs far less than a fully offline app | Which screens must work with no signal? |
| Integrations | Each ERP, accounting, CRM or payroll link needs a data map and error handling | Which systems, and what happens when one rejects a record? |
| Reporting | A standard dashboard costs much less than custom management reports | What reports do managers need on day one? |
| Platforms | iPhone only is one build and test cycle; iPhone and Android is two | Which phones do the crews carry? |
| Data migration | Importing years of spreadsheets means cleaning duplicates and mismatches | How much historical data must move across? |
| Compliance features | GPS, audit logs, retention and consent screens need legal review and testing | Which features need review before the build starts? |
| Support after launch | Maintenance is separate from the build | What is covered after handover? |
If a builder quotes by the hour, the published Canadian rate is CAD 80 to 150 per hour. That is a rate, not a project price. Multiply it by the hours in a written plan, and be wary of open-ended estimates.
What belongs in a written scope
A written scope turns an idea into something you can compare and hold a builder to. It should contain:
- User roles, and what each role can see, create and change.
- Screens and the job flow, from assignment to close-out.
- Offline rules, covering which screens work with no signal and what is stored on the device.
- Sync and conflict rules, field by field, including what the user sees while changes are waiting.
- Integrations, with the data each system sends and receives.
- Data ownership, covering who holds the code, the app store accounts and the data.
- A test plan, listing the devices, connection conditions and who signs off.
- Out of scope items, so nobody is surprised later.
- A launch date and a fixed price.
Eskore's standard is a written scope, a fixed price and a launch date before any work starts. If a builder cannot put those on paper before you commit, treat that as information.
Staff monitoring and privacy in Canada
Once an app records where staff are and what they do, it is also a monitoring tool, and the rules change. What follows is general information, not legal advice. Your province, your industry and your employment contracts all matter. Take advice before you switch on location tracking.
Ontario's written electronic monitoring policy
Under Ontario's Employment Standards Act, employers with 25 or more employees on 1 January must have a written policy on electronic monitoring of employees in place by 1 March. The policy is required even if you do not monitor electronically, provided it says so. The Ontario government's page on the written policy is the primary source. Check its current wording before you rely on this summary.
For a field app, the policy has to match the features. If the app records GPS check-ins or activity logs, the policy must describe them. A policy that says "we do not monitor" while the crew app logs every location is a problem waiting to happen.
Federal and provincial privacy: GPS and device data
Canadian privacy law is a patchwork, so treat these points as starting positions.
The Office of the Privacy Commissioner has treated location data as personal information in some cases. In PIPEDA Case Summary #2006-351, it considered location data collected from company vehicles, where the driver could be identified. Read the summary's wording on the OPC site before relying on it, but assume that GPS data about named staff is personal information.
Whether federal PIPEDA applies to employee information depends on the business. For federally regulated employers it applies directly. For most provincially regulated employers, provincial law is what counts, and the rules differ by province.
Alberta's PIPA treats device and location data about employees as personal employee information. A summary of Alberta PIPA and employee device monitoring is a useful secondary read, but confirm the position with Alberta's regulator. BC's PIPA and Quebec's Law 25 also need checking with each regulator for employee data.
Ask your legal adviser whether consent is needed before location is collected, and for which staff, in your province. Do not rely on a general rule you have read online.
Features to review before the build starts
Map each feature to what it collects and what you need to tell people about it. Use this as a review step with your legal adviser, not a checklist you complete alone.
- GPS check-ins. Disclose that location is captured at check-in. Limit capture to check-in moments rather than continuous tracking. Record the purpose and how long the data is kept.
- Photo timestamps and location tags. Disclose that photos carry time and place data. Limit metadata to what the job needs. Record who can view it.
- Activity logs. Disclose what is logged, such as status changes and edits. Limit logging to job-related events. Record who has access and for how long.
- Screen capture. This is highly intrusive. Disclose it clearly, and ask whether job outcomes can be checked without it.
- Idle detection. Disclose it, and ask whether it is needed at all. This is the feature most likely to need a careful explanation to staff.
Settle these decisions in the scope, not after launch. Changing data collection once a crew is using the app is harder than designing it in at the start.
Connecting the app to your accounting system or ERP
A field app is only as useful as what happens to its data afterwards. Jobs flow in from the office. Time, parts, photos and signatures flow back. Those records need to reach invoicing, payroll and inventory without someone copying them across by hand.
The integration points are concrete:
- Jobs: job ID, customer, site, scheduled date and status, sent to the app and updated from it.
- Timesheets: hours, job code and shift, sent to payroll or your time system.
- Parts: SKU, quantity and job reference, used to adjust inventory.
- Invoices: labour and parts lines, built from the completed job and the signed close-out.
Decide three things early. Will each integration run in real time or in batches? What happens when the receiving system rejects a record, and who sees the error? Who owns the mapping between the app's fields and your accounting codes?
If you are still choosing or rebuilding your core system, our ERP systems for inventory, finance, HR and operations and CRM development for pipelines and customer history pages cover the other side of the same flow. Our write-up on ERPNext implementation in Toronto covers costs, timeline and set-up. If the data will live in the cloud, cloud setup and migration covers the hosting side.
How an Eskore internal app project runs
Three commitments apply to every project, and they are the ones to hold us to:
- A written scope, a fixed price and a launch date are agreed before work starts.
- One team covers software, design, cloud and marketing, working from offices in Toronto, Thornhill, London and New York.
- You own the code and the accounts.
The steps run in this order:
- Scoping call. We start with a free 30-minute scoping call to walk through the workflow: who does what, where the work happens, and where the spreadsheets currently fail.
- Written scope. The roles, screens, offline rules, sync and conflict rules, integrations, data ownership, test plan and launch date are written down.
- Fixed price. The price is set against that scope and agreed before work starts.
- Build and launch. The app is built to the scope and launched through the route it sets, whether the App Store, Google Play or another agreed distribution method.
- Handover. You receive the code and the accounts.
We do not promise a launch timeline beyond what the written scope states. If your field teams are in the United States, the same scoping approach applies. You can see our past work on the case studies page.
Ready to scope your internal mobile app for field staff in Canada?
If you are ready to replace spreadsheets and paper forms with an internal mobile app for field staff in Canada, book a free 30-minute scoping call. Bring a sample job and the spreadsheet your office uses now. We will turn the workflow, offline rules and monitoring questions into a written scope, a fixed price and a launch date. If a standard tool would do the job, we will tell you that too.