How Small Freight Carriers Can Build a Custom TMS Dashboard Instead of Buying SaaS

tms software companies typically sell generic, subscription-based platforms that charge per truck and require ongoing licences. For carriers that run dispatch on spreadsheets, a custom dashboard built on the RouteMate stack can deliver the same visibility, compliance and driver-comms features while eliminating per-truck fees and giving full ownership of the code.

Key takeaways

• A one-time custom build costs $2,500-$3,500 for a 10-30 truck fleet, far below the $45-$70 per-truck annual SaaS spend reported by the American Trucking Associations.
• Using React, Express and PostgreSQL lets you host on a low-cost cloud VM and scale to 100 trucks without performance loss.
• WhatsApp Business API integration preserves drivers' existing habit while creating an auditable communication log.
• Compliance workflows (service intervals, registration, HOS alerts) can be automated with cron jobs and email/SMS triggers.
• ROI is measurable in saved admin hours (often 5-8 h/week) and reduced missed-pickup disputes.
• Ownership means no vendor lock-in; you can add features or migrate to a new host for a few hundred dollars a year.

What core modules should a lightweight custom TMS include?

Small carriers need only three functional pillars: dispatch board, driver-communication hub, and back-office automation. Each module can be a separate React component that talks to a shared Express API.

Module	Primary function	Typical UI element	Example tool used
Dispatch board	Assign loads, view truck status	Kanban-style cards with drag-and-drop	react-beautiful-dnd
Driver-comms hub	Send/receive messages, record acknowledgements	Integrated WhatsApp chat window	WhatsApp Business API + socket.io
Back-office automation	Timesheets, POD, invoicing, compliance alerts	Form wizard with PDF export	react-hook-form + pdfmake

Dispatch board details

• Load data is imported from a CSV or directly from a QuickBooks invoice export.
• Each load card shows origin, destination, weight, required equipment and ETA.
• Dragging a card onto a truck updates the PostgreSQL assignments table and triggers a WhatsApp template message.
• Real-time status colours (green = en-route, amber = delayed, red = issue) are calculated from GPS pings stored in a lightweight PostGIS extension.

Driver-comms hub details

• The hub uses the WhatsApp Business API to send templated messages (e.g., "Load #123 assigned, pick up at 08:00").
• Incoming replies are stored in the messages table, linked to driver ID and load ID for audit.
• A daily digest email summarises unread driver messages for the office manager.

Back-office automation details

• Timesheet entry pulls driver-hour logs from the ELD feed (if the carrier already uses an ELD) or from manual entry forms.
• Compliance reminders are generated by a scheduled Node job that checks service_intervals against last_service_date.
• Proof-of-delivery PDFs are created on the fly and attached to an email to the shipper.

Which technology stack works best for a 10-100 truck carrier?

RouteMate already ships a production-ready stack that matches the carrier’s needs:

• Frontend: React 18 with TypeScript for type safety, Material-UI for quick component styling, and Redux Toolkit for state management.
• Backend: Node.js 18 running Express, with JWT authentication and role-based access control (owner, ops manager, driver).
• Database: PostgreSQL 15 with PostGIS for optional geo-queries; hosted on a low-cost AWS Lightsail or Hetzner VM ($10-$15/mo).
• Messaging: Socket.io for real-time UI updates, Twilio for SMS fallback, and WhatsApp Business API for primary driver contact.
• DevOps: Docker Compose for reproducible builds, GitHub Actions for CI/CD, and a nightly backup to an S3 bucket.

The stack is deliberately lightweight: a single 2-core VM can handle 100 concurrent users and 5 000 API calls per hour, which covers typical peak dispatch windows.

Cost comparison: custom build versus per-truck SaaS

Cost element	Custom build (one-time)	Typical SaaS (per-truck)
Development	$2,500-$3,500 (one-off)	N/A
Hosting	$150-$200 / yr (cloud VM)	Included in subscription
Messaging (WhatsApp)	$0.008 / msg (Meta rates)	Often bundled, but hidden in per-truck fee
Maintenance retainer (optional)	$1,500 / mo (low-cost)	$45-$70 / truck / mo (US average, ATA 2023)
Total first-year cost for 30 trucks	≈ $4,200	≈ $18,000-$25,200

According to the American Trucking Associations 2023 survey, the median SaaS spend per truck is $55 / month, which translates to $660 / year. Over a five-year horizon a SaaS solution can cost three times more than a custom build plus modest maintenance.

Step-by-step roadmap to launch your dashboard

1. Scope the workflow – Interview the owner, ops manager and dispatcher to list every spreadsheet column and manual step. Map these to the three modules above.
2. Create a data model – Define PostgreSQL tables (trucks, loads, assignments, drivers, messages, compliance). Use ER diagrams to validate relationships.
3. Prototype UI in Figma – Keep the layout similar to the existing Excel view so staff adoption is painless.
4. Set up the repo – Fork the RouteMate starter repo, run docker-compose up, and confirm the API health check.
5. Build the dispatch board – Implement load import, drag-and-drop assignment, and status colour logic.
6. Integrate WhatsApp – Register a Business Account, obtain the API key, and configure a webhook endpoint in Express.
7. Add compliance jobs – Write a Node cron that runs nightly, checks service dates, and sends email alerts via SendGrid.
8. User acceptance testing – Run a two-week pilot with 5 trucks, collect feedback, and iterate on UI tweaks.
9. Go live – Migrate the master spreadsheet into the loads table, decommission the Excel file, and train the office staff.
10. Monitor & optimise – Use Grafana dashboards to watch API latency and message failure rates; adjust VM size if needed.

How to integrate WhatsApp Business API without breaking driver habits

1. Keep the phone number – Use the carrier’s existing driver mobile number; the API works with a virtual number that forwards to the driver’s handset.
2. Template messages – Pre-approve templates for load assignment, pickup reminder and delivery confirmation. Templates guarantee delivery and cost $0.008 / msg (Meta 2024 rate).
3. Two-way sync – When a driver replies “OK” the webhook records the timestamp and marks the load as acknowledged.
4. Fallback to SMS – If the API returns a 429 rate-limit, automatically switch to Twilio SMS for that driver.
5. Audit trail – All inbound and outbound messages are stored in the messages table; a simple admin view lets the ops manager export a CSV for dispute resolution.

Compliance automation that works for AU, US and UK carriers

• Australia – Use the rego_due field to trigger a 30-day email reminder before registration expiry. The reminder pulls the state-specific URL from the NVR (National Vehicle Register) API.
• United States – Implement an IFTA mileage calculator that aggregates GPS logs and emails the quarterly report to the carrier’s accountant. Add a daily FMCSA safety score pull (via the FMCSA API) and flag any BASIC rating increase.
• United Kingdom – Schedule MOT due alerts based on the mot_expiry date and send a Slack webhook to the fleet manager (many UK carriers already use Slack for internal chat).

All three jurisdictions share a common pattern: a scheduled job reads the relevant date field, compares it to NOW(), and sends a templated email if the delta is ≤ 30 days.

How to measure ROI of your custom TMS

Metric	Pre-implementation baseline	Post-implementation target	Measurement method
Admin hours per week	8-10 h (manual re-key)	≤ 2 h	Time-tracking tool (Harvest)
Missed pickup rate	4 % of loads	≤ 1 %	Load audit log comparison
Per-truck software cost	$660 / yr	$0 / yr (excluding WhatsApp)	Accounting ledger
Customer inquiry volume	15 calls / day	≤ 5 calls / day	Call-center log
Compliance penalty risk	2 incidents / yr	0 incidents / yr	FMCSA/ATO audit reports

Collect data for a 90-day period after go-live, then calculate the dollar value of saved hours (average admin wage $30 / hr) and reduced penalties. Most carriers see a payback within 4-6 months.

Frequently asked questions

What is the biggest advantage of owning a custom TMS?

Ownership eliminates per-truck subscription fees, gives you full control over feature road-maps, and lets you integrate with existing tools like WhatsApp without waiting for a vendor release. It also protects you from vendor lock-in and price hikes.

How long does a typical build take?

For a 20-truck carrier the end-to-end timeline is 8-10 weeks: 2 weeks for discovery, 4 weeks for development, 2 weeks for testing and training. Larger fleets add a week or two for data migration.

Do I need an in-house developer to maintain the system?

No. The optional retainer covers hosting, security patches, API key renewals and minor feature tweaks. Most carriers can rely on the vendor for all ongoing work.

Can the dashboard handle real-time GPS tracking?

Yes. By adding a cheap OBD device that pushes latitude/longitude to the Express API, the dispatch board can display live positions on a Mapbox map. The hardware cost is about $15 / unit per month.

Will my drivers have to learn a new app?

No. The driver-comms hub works inside WhatsApp, which they already use. All they see are templated messages that look like any other chat.

How secure is the data?

The system uses HTTPS, JWT tokens, role-based access, and nightly encrypted backups to an S3 bucket. PostgreSQL row-level security ensures drivers can only see their own loads.

What happens if I want to add a new feature later?

Because you own the source code, a developer can add modules (e.g., load-matching marketplace) for a few hundred dollars. The retainer includes up to 8 hours of change work per month.

Is this approach compliant with FMCSA and UK regulations?

The core platform is neutral; compliance workflows are configured per jurisdiction. For the US you must integrate the FMCSA ELD API and follow the 2024 safety-score reporting guidelines. For the UK you must respect MOT and tachograph data handling rules.