Skip to content
CodeBeyonds

Concept project

Fleetboard

Multi-tenant operations dashboard for small logistics operators running 10 to 200 vehicles.

Type
SaaS, Web & mobile
Year
2026
Stack
Next.js, TypeScript, Supabase, PostgreSQL, Stripe
Open-plan studio with rows of desks and monitors

Interface shown with sample data.

The challenge

Regional operators track trips, drivers and payments across WhatsApp groups and spreadsheets. Enterprise fleet software is too heavy and too expensive for them.

Who it’s for

Fleet owners, dispatchers, and drivers using a phone in the cab.

Solution and product strategy

  • One workspace per operator with dispatcher and driver roles, invite links and an audit log.
  • Trip board with status updates drivers can post from a lightweight mobile view.
  • Subscription billing per active vehicle with a free trial and automatic invoices.

System architecture

The path a request takes through the system, and what each part is responsible for.

  1. 01Web appNext.js dashboard for dispatchers
  2. 02Driver viewInstallable web app, works on poor connections
  3. 03APITenant-scoped routes, row-level security in Postgres
  4. 04BillingUsage-based subscription via payment provider webhooks

What we’d measure

This is a concept project, so there are no client results to report. These are the numbers a real deployment would be judged on.

  • Time from sign-up to first trip created
  • Weekly active dispatchers per workspace
  • Trial to paid conversion

What we learned

  • Row-level security in the database is simpler to audit than checks scattered through the API.
  • Drivers need three buttons, not a dashboard.

Want something like this for your team?

Tell us what you're trying to do. A senior engineer reads every message and replies personally.