FleetRoute
Multi-tenant fleet management SaaS with route optimization, staff scheduling, and CRM integration.
FleetRoute is a full-stack SaaS platform designed to streamline fleet operations for service-based businesses. The platform handles real-time route optimization across multiple service areas, intelligent staff scheduling with availability management, and deep CRM integration for seamless job-to-technician assignment. Built from the ground up as a multi-tenant system with organization-level isolation, Stripe billing, and role-based access control.
React + Supabase + Stripe + Google Maps
Enterprise-grade fleet operations in the browser.
A complete operations platform replacing spreadsheets and manual scheduling with intelligent automation, live map views, and integrated billing.
Technical Architecture
Multi-tenant architecture with row-level security.
The platform is built on React 18 with TypeScript strict mode, backed by Supabase Postgres with comprehensive row-level security policies ensuring complete data isolation between organizations. The Google Maps API powers real-time route optimization, distance matrix calculations, and geocoding for service area management. Stripe handles subscription billing with usage-based pricing tiers, automatic invoice generation, and self-service plan management.
Core Platform Features
Route optimization, scheduling, and CRM in one platform.
The route optimization engine processes daily job lists against technician locations, availability windows, and skill requirements to produce optimal route sequences. The scheduling system accounts for travel time, job duration estimates, and break requirements while respecting individual technician availability patterns. Real-time updates push through Supabase Realtime channels so dispatchers see live position updates and job completion status without page refreshes.
CRM integration connects bidirectionally with Pipedrive, syncing contacts, deals, and activities in real-time. When a job is completed in FleetRoute, the corresponding deal stage updates automatically in the CRM. The Stripe integration supports multiple pricing tiers based on fleet size and feature access, with automated usage tracking for overage billing. Organization admins manage team members, service areas, and billing through a self-service portal built with Radix UI primitives.
Route Optimization Algorithm
Efficient routing reduces travel time and increases jobs completed per day.
The core algorithm solves the Vehicle Routing Problem (VRP), a classic operations research challenge: given a set of locations and a fleet of vehicles with constraints (time windows, capacity, skills), find the lowest-cost routes. FleetRoute uses a hybrid approach combining Google Maps distance matrix API for real-distance calculations and a custom optimization algorithm that considers time windows (jobs that must be done between certain hours), technician skills (plumber, electrician, etc.), and vehicle capacity. The optimizer runs continuously as new jobs are added through the day, resequencing routes to accommodate urgent jobs while minimizing disruption to already-planned schedules.
Multi-Tenant Architecture and Data Isolation
Enterprise security through row-level security policies.
Building a SaaS platform requires absolute data isolation — each organization's data must be completely separate from others, with no risk of cross-company leakage. FleetRoute uses Supabase's row-level security (RLS) policies to enforce this at the database level. Every table has a user_id or organization_id column, and RLS policies ensure that queries always filter by the authenticated user's organization. This means even if a bug or security vulnerability exposes raw SQL queries, they can't access another organization's data. Authentication uses Supabase Auth with support for email/password, Google OAuth, and Microsoft SSO, so teams can use their existing corporate identity providers.
The backend runs on Supabase's PostgreSQL with custom edge functions (Deno-based serverless) for business logic that shouldn't live in the frontend. These functions handle CRM syncs, billing calculations, and sensitive operations with logged audit trails. The React frontend is split into organization-level and user-level components, with role-based access control limiting what dispatchers, technicians, and admins can see. A technician's mobile view shows only their assigned jobs and route, while a dispatcher's dashboard shows the entire fleet. This permission model is defined in Supabase RLS and enforced before any data reaches the client.
Mobile-First Technician Experience
Field teams need a lightweight, offline-capable mobile app.
Technicians don't spend their day at a desk — they're in vans, at job sites, in areas with spotty 4G coverage. The FleetRoute mobile view is built for these realities: a lightweight React Native component that shows assigned jobs with navigation links to Google Maps, job details, and a checklist for job completion. Job photos can be captured and uploaded, with automatic retry logic for areas with poor connectivity. Offline-first architecture using SQLite means technicians can work through their route even if they temporarily lose signal — changes sync up when connectivity returns.
Analytics and Performance Insights
Data-driven operations management.
Beyond day-to-day scheduling, FleetRoute provides analytics dashboards that reveal operational patterns: average job duration by type, idle time between jobs, technician utilization rates, peak scheduling hours, and customer density by area. These insights guide hiring decisions (if you're consistently over-capacity from 2-4pm, you need more afternoon availability), pricing decisions (high-density areas can command premium pricing), and route planning (cluster jobs by geography to minimize drive time). Historical data is exported to BigQuery for advanced analysis and machine learning experiments.
Custom reports let organizations track KPIs specific to their business: jobs completed per technician per day, average revenue per route, customer acquisition cost by service area, or technician retention rates. These dashboards are built with Looker Studio for flexibility, connecting to BigQuery for fast queries across millions of historical job records. For Gold Coast service businesses, this data often reveals surprising patterns — perhaps one suburb has 3x better margins than another, or certain technician pairings are more efficient together. Data-driven insights compound over time, continuously improving operational efficiency.
Subscription Billing and Pricing Optimization
Stripe integration enabling flexible, usage-based pricing.
SaaS platforms require flexible billing to support different customer segments. FleetRoute uses Stripe's subscription and usage-based billing APIs to support multiple pricing models: fixed monthly subscriptions based on fleet size, usage-based charges for additional routes or teams beyond the base tier, and premium feature add-ons for advanced analytics or custom integrations. The Stripe integration handles invoice generation, payment processing, subscription lifecycle (upgrades, downgrades, cancellations), and dunning (retry attempts for failed payments). Customers can self-serve plan changes through the application without contacting support, reducing friction and improving conversion. This flexibility is what allows FleetRoute to serve customers from small 2-person trades businesses through to large multi-fleet operations — pricing scales with the customer.
SaaS as a Service Delivery Model
Replacing spreadsheets and manual processes with software.
FleetRoute exists to replace broken workflows. A dispatch manager checking spreadsheets for technician availability, calling techs to confirm schedules, and manually assigning jobs is inefficient and error-prone. FleetRoute automates this: technician availability is entered once and reflected everywhere, jobs are assigned automatically based on location and skills, and notifications reach technicians instantly. This efficiency translates to real cost savings: fewer administrative overhead costs, faster job assignment means faster service delivery, fewer scheduling conflicts means fewer rescheduled jobs.
SaaS platforms succeed by solving real problems that customers currently solve manually. FleetRoute's ROI for customers is quantifiable: if a dispatch manager spends 10 hours per week scheduling jobs manually, and FleetRoute reduces this to 2 hours per week, that's worth $400-800 per week depending on labor cost. That's $20,000-40,000 annual savings before considering the value of improved customer response times and technician efficiency. This ROI is so compelling that customers happily pay $500-2000/month for the platform. Pricing is negotiated based on fleet size and value delivered, ensuring both customer and vendor benefit as the relationship scales.
Need a custom SaaS platform?
Let's connect.
From the blog
Latest thinking
Tech news, design insights, and development deep-dives from the Gold Coast.