Loads Tracked, Hours Checked, Miles Put to Work
We build dispatch and TMS platforms, ELD and Hours-of-Service compliance, telematics, and shipper portals for Canadian carriers, fleets, brokers, and 3PLs. Software designed to work twenty kilometres past the last cell tower, built around the National Safety Code, and aimed at turning deadhead miles back into margin. Calgary roots, working with fleets across Canada.
The Canadian Reality
Canadian Trucking Runs on Margins Measured in Cents per Mile - and Most of the Software Was Built for the Lower 48
The dispatch is run on a whiteboard, phone, and text. The logbooks are paper or a half-implemented ELD nobody trusts. The TMS, the ELD, and the accounting system have never spoken to each other. We build the operation, not just the platform.
In many Canadian carriers the pattern is similar whether they run twelve trucks or two hundred. Dispatch is a whiteboard, a cell phone, and a string of texts - the dispatcher knows where the trucks are because they called the drivers, and the customer knows where the freight is because they called the dispatcher. Hours of Service live on paper logs or a bargain-bin ELD that throws false violations nobody trusts, so the safety manager keeps a parallel spreadsheet just in case an audit shows up. The TMS, the ELD, and the accounting system are three vendors that have never exchanged a single record, so somebody re-keys every load three times. None of this is anyone's fault - it is what happens when the tools were bought one fire at a time.
Off-the-shelf software does not fix it, partly because the strongest products were built for the US market and stop at the 49th parallel. Canadian carriers run under the National Safety Code, not the US FMCSA rules - 13 hours of driving, 14 on-duty, mandatory off-duty, and a 70-hour-7-day or 120-hour-14-day cycle that a US-tuned ELD models incorrectly. They cross the border under CBSA eManifest northbound and US ACE southbound, with CARM now reshaping how duties and the importer of record are handled. They haul dangerous goods under the TDG Act with placarding and documentation rules that differ from the US 49 CFR. And they do all of it across distances and winters - a Calgary to Thunder Bay run, a January closure on the Coquihalla - that a platform designed for dense regional freight never accounted for.
We build custom software for Canadian logistics because the operation is the product. A dispatch and TMS platform where a planner assigns a load and the system checks the driver's remaining Hours of Service before the truck is committed - and offers a relay or a swap when the math does not work, instead of finding out at a roadside inspection. A driver app that captures the log, the pre-trip inspection, and the proof of delivery offline in a dead zone and syncs the second it finds signal. A telematics and routing layer that turns the empty backhaul into a booked load. A shipper portal that answers where is my freight without a phone call. These are the kinds of tools we scope for carriers, brokers, and private fleets, with the goal of recovering cents per mile.
Headquartered in Calgary puts us inside one of the country's most important freight hubs - CPKC (Canadian Pacific Kansas City) is headquartered here, the city sits at the crossroads of the Trans-Canada and the QEII corridor, and the inland port and intermodal terminals in Rocky View and the Calgary Logistics Park move freight in every direction. Our engineers understand the difference between a long-haul, an LTL, and a drayage move, why a dispatcher will not adopt a tool that takes three extra clicks per load, and what a CVSA inspection or an NSC facility audit actually asks for. We bring that context to every screen.
What's Broken Today
The patterns we keep seeing
Dispatch run on a whiteboard, phone, and text
The dispatcher knows where the trucks are because they called the drivers, and the customer knows where the freight is because they called dispatch. There is no real-time visibility, no single board, and the institutional knowledge lives in one person's head and phone.
Hours-of-Service compliance risk and audit exposure
Paper logs or an ELD nobody trusts, a parallel spreadsheet kept just in case, and a constant low-grade risk that a violation surfaces at a roadside inspection or an NSC facility audit - where the cost is fines, a downgraded safety rating, and lost contracts, not just a ticket.
Deadhead and empty miles eroding thin margins
Trucks running empty on the backhaul burn fuel and hours for zero revenue. Without routing and load-matching tied into dispatch, a meaningful share of every mile earns nothing - on margins already measured in cents.
TMS, ELD, and accounting that do not talk to each other
The dispatch system, the ELD, the telematics, and the accounting package are separate vendors that never exchange a record, so a single load gets re-keyed three times and a clean billing or compliance picture takes a manual stitching exercise every week.
What We Build
Solutions tailored to logistics & transportation
Not a generic platform with industry skins. Architecture, workflows, and integrations chosen for logistics & transportation operations specifically.
A single live board for planners and dispatchers that replaces the whiteboard and the phone tree - load assignment, driver and asset status, and customer commitments in one place, with Hours-of-Service checked before a load is ever committed.
Logging built to the National Safety Code, not borrowed from US rules - with the cycle math, off-duty enforcement, and audit trail designed to help keep a carrier onside and prepared for an inspection or an NSC facility audit.
A telematics and routing layer that turns vehicle data into fewer empty miles and fewer breakdowns - Canadian-distance and winter-aware routing, with maintenance driven by actual engine and odometer data.
A self-serve portal that answers where is my freight without a phone call - live ETAs on a Canadian route map, proof of delivery, and document access for shippers, brokers, and consignees.
Dispatch to Delivery
Assign a Load Without Booking a Compliance Violation
An illustrative mock of a dispatch and fleet console, using fictional data. Assign a freight load to a truck and watch the board check the driver's remaining Hours of Service, flag the run before it breaks the National Safety Code, and offer a relay or swap to fix it. Track the ETA on a Canadian route map, then flip to the driver view for a live HOS clock and proof of delivery.
Auto-playing: assign a long haul to a near-limit driver, hit the HOS block, relay it legal, roll the truck, then deliver from the cab.
Dispatch freight, legally
Assign loads on Canadian lanes with an Hours-of-Service check on every dispatch
On-time
94.2%
Utilization
81%
Deadhead
12.4%
HOS compliance
99.1%
Live route map
Dispatch a load to light its lane and roll the truck across the corridor.
Load board
3 open- Open
L-4471YYCYWG13 h
Dry van - retail freight22tThu 14:00 - 18:00
- Open
L-4473YYCYVR11 h
Reefer - produce18tWed 08:00 - 12:00
- Open
L-4475YEGYXE5 h
Flatbed - steel24tWed 16:00 - 20:00
- Dispatched
L-4468YYCYEG3 h
Dry van - parcel9tTue 13:00 - 15:00
T-07Sukhdeep GillETA Tue 14:10
Pick a driver from the roster to dispatch the next open load. Every assignment runs an HOS check first.
Fleet & drivers
3 ready- Available
T-14Dwayne Cardinal
Calgary, AB
Drive11.5 hOn-duty12.0 hCycle48.0 h - Available
T-22Renee Beaulieu
Calgary, AB
Drive2.0 hOn-duty2.0 hCycle12.0 hLow hours - On a load
T-07Sukhdeep Gill
Edmonton, AB
Drive13.0 hOn-duty13.5 hCycle61.0 h
Dispatch log
Sukhdeep Gill on YYC - YEG, ETA Tue 14:10
just now
Shift board synced - 3 open loads, ELD hours current across the fleet
earlier today
Every assignment, HOS check, relay, and delivery is logged with the ELD hours - a full, auditable trail.
Illustrative mock of the dispatch and fleet console we build for Canadian carriers and logistics operators. The carrier, drivers, trucks, loads, lanes, Hours-of-Service figures, ETAs, and KPIs shown are entirely fictitious. The real product runs on Canadian data residency with ELD / HOS-aware dispatch enforcing NSC Standard 9 limits, telematics and route integration, and proof-of-delivery synced back to the board - built to WCAG 2.2 AA.
The Regulatory Map
The rules we design around
Compliance is architectural for us, not a checkbox added at the end.
Canadian ELD Mandate
Federally-regulated carriers must use a third-party-certified electronic logging device to record Hours of Service. We plan to integrate with certified ELDs rather than building an uncertified logger that an inspector could reject.
Applies to: Federally-regulated carriers and their drivers
National Safety Code Standard 9 - Hours of Service
The Canadian Hours-of-Service rules - 13 hours driving, 14 on-duty, mandatory off-duty, and 70-hour-7-day or 120-hour-14-day cycles. We build the cycle math and off-duty enforcement to the NSC, not to US FMCSA rules.
Applies to: Commercial carriers operating across NSC jurisdictions
Transportation of Dangerous Goods Act & Regulations
Federal rules for classifying, documenting, placarding, and handling dangerous goods - distinct from the US 49 CFR. We design shipment and document workflows so the right TDG paperwork, training records, and placarding details travel with the load.
Applies to: Carriers and shippers moving dangerous goods
CBSA eManifest / US ACE / CARM
Cross-border freight requires advance commercial information - CBSA ACI/eManifest northbound and US CBP ACE southbound - while CARM reshapes how duties and the importer of record are handled. We build the data capture and integrations so the border crossing is not a manual scramble at the bridge.
Applies to: Carriers and brokers running cross-border lanes
PIPEDA
Canada's federal private-sector privacy law governs driver and customer personal information, including telematics and location data - which is personal data when it tracks an identifiable driver. We design consent, retention, and access into how location and ELD data are stored and shared.
Applies to: Any carrier handling driver or customer personal data
IFTA / IRP - Fuel Tax & Registration
The International Fuel Tax Agreement and International Registration Plan govern how interjurisdictional fuel tax and plate registration are reported by distance travelled in each jurisdiction. We capture mileage by jurisdiction from telematics so quarterly IFTA filings come out of the data instead of a logbook reconstruction.
Applies to: Carriers operating across provincial and state lines
Illustrative Use Cases
What we could build for your team
These examples describe possible solutions, not completed client projects or measured results. Scope, integrations and expected benefits are established during discovery.
The scenario
A regional carrier moving from paper logs to a certified ELD
Certified-ELD integration and NSC-based cycle tracking could replace paper logs and give the safety team a single record instead of a parallel spreadsheet.
The scenario
A freight broker or 3PL with limited visibility into loads
A dispatch platform with live tracking and a self-serve shipper portal could answer status questions without check calls.
The scenario
A private fleet with empty backhaul miles
Routing and load matching could be wired into dispatch so the planner sees the legal, loaded option first.
Tools Chosen for the Job
Why we use what we use
React Native + Expo
One codebase for the driver app on iOS and Android that captures logs, inspections, and proof of delivery offline in a dead zone and syncs on reconnect - with over-the-air updates so a fix reaches the cab without an app-store wait.
PostgreSQL + PostGIS
A relational core with geospatial indexing for routing, geofencing, ETA calculation, and mileage-by-jurisdiction - the spatial queries a dispatch and routing engine lives on, without bolting on a separate GIS.
Geotab / Samsara / certified-ELD integrations
Direct integration with the telematics and ELD hardware fleets already run, so location, engine, fuel, and Hours-of-Service data flow into dispatch instead of being re-keyed - and the ELD stays certified.
Event-driven tracking pipeline
A streaming pipeline for GPS pings, status changes, and exception events so the board, the ETAs, and the shipper portal update in real time and notifications fire on delay, detention, or arrival.
Next.js + TypeScript
Server-rendered dispatch dashboards and a shipper/broker portal that load fast on a warehouse tablet or a phone in the yard - type-safe end to end from the portal to the API.
AWS Canada
Canadian-resident infrastructure can be scoped in the Calgary and Montreal regions, keeping driver, customer, and location data in Canada and aligned with PIPEDA, with the arrangements agreed for each project.
The Underlying Services
Services we draw on for this work
Mobile App Development
Cross-platform iOS and Android apps built with React Native — one codebase, native performance, faster launch
Explore serviceDatabase & API Solutions
Scalable databases and secure APIs that connect your systems — built for reliability and growth
Explore serviceCloud Integration & DevOps
AWS and Azure cloud infrastructure with CI/CD automation — reliable scaling without surprise bills
Explore serviceFAQ
Questions buyers ask first
Common questions about logistics & transportation software development in Canada
Ready to talk logistics & transportation software?
Book a 30-minute scoping call. We will walk through your operation, talk through what's worked for similar Canadian logistics & transportation operations, and tell you honestly whether we are the right team.