Start a project
All work

Case study 08 of 08

CURBD RSARoadside memberships and live dispatch on one platform

More work:Office Dojo All case studies

Sector
Platform · Roadside assistance
Core modules
06
Technologies
08
Status
Live in production

01Overview

One platform for the full roadside-assistance lifecycle: selling a membership, taking payment, dispatching a tow, tracking the job live and paying the provider — with separate portals for admins, dispatchers, agencies and towing companies.

02Problem & solution

The challenge

Agencies sell memberships, dispatchers take the call, independent towing companies do the work and finance pays everyone. Run on phone calls, spreadsheets and disconnected billing, that meant wrong coverage, double-assigned trucks, expired insurance and unpaid jobs.

What we built

We built role-based portals around a single dispatch state machine, map-based provider matching and a payments ledger, so membership, dispatch and payouts share one record instead of separate tools.

03Inside the product

  1. 01

    Membership wizard

    Plan, member, vehicles, drivers, documents and checkout — coverage goes active only once payment succeeds.

  2. 02

    Verified dispatch

    Dispatchers confirm the member, vehicle and driver before a request can continue.

  3. 03

    Smart provider matching

    Only approved, insured companies with a free truck and driver inside their service radius are offered the job.

  4. 04

    Live tracking

    Members watch the truck arrive in the app and confirm completion with a one-time code.

  5. 05

    Towing-company portal

    Guided onboarding, job offers, trucks, drivers, rate cards, invoices and payouts.

  6. 06

    Automated payouts

    Invoices from each company's rate card, with payouts to towing companies and agencies.

04Technology

  • Laravel
  • PHP
  • Vue 3
  • Inertia.js
  • MySQL
  • Stripe
  • Google Maps
  • Firebase
Job lifecycle
  1. Membership
  2. Verified call
  3. Provider match
  4. Live job
  5. Invoice
  6. Payout

05How we built it

Business rules live in services, not screens. Writes that must not race use transactions and row locks, so two dispatchers can never take the same job, and payment retries can never charge or pay twice.

Want something like this?

Tell us what you're building — a senior engineer will reply with next steps.

Start a project
Next case studyOffice DojoSaaS · PropTech