Fleet integration hub
Hypothetical. Not a client, not a result.
// The problem
A fleet's ELD, fuel card, shop software, dispatch system and payroll are joined by staff copying numbers between them, and the scripts someone wrote stop without telling anyone.
// What we would build
An internal API that connects five systems through their published APIs, moves odometer readings, fuel purchases, work orders and hours where they are needed, and sends webhooks when something changes. We run it on managed cloud with monitoring, backups and alerts, so you know when a provider's API changes.
// What is in it
- Connectors for ELD, fuel card, shop, dispatch and payroll systems
- Webhooks when a unit, a work order or a fuel purchase changes
- Monitoring, alerts and retries when a provider is down
- Infrastructure as code, backups and a written runbook
- OpenAPI documentation for anything else you connect later
// Stack
- Node.js
- PostgreSQL
- OpenAPI
- Terraform
- AWS Canada
// estimate
- Build
- ≈ US$56,700 to US$86,800, delivered within 14 weeksCAD 80,800 to 123,600
- Hosting
- ≈ US$492 a monthCAD 700 a month
- Support
- ≈ US$5,010 a monthCAD 7,135 a month
Prices in your currency are estimates from today's Bank of Canada rate. All invoicing is in CAD or USD.
Timeline by milestone
- API contract agreed
- 2.9 to 3.9 weeks
- Core resources built
- 2.9 to 4.4 weeks
- Security, gateway and connections
- 1.9 to 2.9 weeks
- Docs, SDKs and load tests
- 1.4 to 1.9 weeks
- Launch and first callers
- 0.9 to 1.4 weeks
Outside our hands, and added to the calendar
- API access from each ELD and telematics provider
- 1 to 4 weeks
How it is paid
- Deposit 20%
- CAD 16,160 to 24,720
- API contract agreed 8.7%
- CAD 7,029.60 to 10,753.20
- Core resources built 26.2%
- CAD 21,169.60 to 32,383.20
- Security, gateway and connections 17.5%
- CAD 14,140 to 21,630
- Docs, SDKs and load tests 8.7%
- CAD 7,029.60 to 10,753.20
- Launch and first callers 8.9%
- CAD 7,191.20 to 11,000.40
- Holdback, 30 days after launch (10%)
- CAD 8,080 to 12,360