Product roadmap

From compliance platform to all-in-one

VahaanAI already leads on the compliance, onboarding and operator-licence lifecycle. This roadmap closes the remaining gaps to conventional fleet-telematics tools — tracking, tachograph remote-download, DVLA licence checks and driver performance — on top of a real backend.

Capabilities shipped

On the roadmap

Close the gap vs telematics tools

ShippedPlanned▲ vs telematics tools closes a competitive gap

Now

Shipped (Step 1)

Live in the app today — built on a local mock data layer ahead of the real backend.

Driver self-onboarding

Shipped

Bulk doc upload, GREEN/RED validation, cross-doc identity, FORS modules, e-signed declarations, Admin/HR approval.

Operator-licence & DVSA suite

Shipped

O-licence parsing, Operating Centres, Waste Carrier, OCRS & prohibitions, Tachograph records, one-click Audit Pack.

Vehicles & maintenance

Shipped

V5C upload, simulated DVLA MOT/tax sync, Maintenance Planner, Contractors, VOR register.

Multi-actor portals

Shipped

Operator, driver, Transport Manager (invite), maintenance vendor, customer self-onboarding, platform super-admin.

Walkaround, incidents, PTO & timesheets

Shipped

DVSA walkaround + defect report, incident/PCN with video, leave/PTO, Sign-In/Sign-Off duty sheets.

SaaS shell

Shipped

Banded tiers, plan finder, Companies House lookup, marketing landing.

Phase 1

Foundation — real backend

The prerequisite for every integration below. Graduates the app out of the localStorage mock.

Supabase backend

Planned

Auth, Postgres with Row-Level Security, private file storage + signed URLs (replaces the mock store).

Effort: High

Live transactional email

Planned

Real onboarding / approval / reminder emails (Resend/SES) instead of the in-app simulation.

Effort: LowNeeds: Backend

Document OCR

Planned

Read licence/CPC/passport fields from uploads to drive validation (today it matches on filename).

Effort: MediumNeeds: Backend + storage

Phase 2

High-control integrations

The items we fully own — fastest wins once the backend lands. These start closing the gap to Convey.

DVLA licence checks

Planned

Active driving-licence eligibility checks via DVLA ADD / a licence bureau, with driver consent. Nav item already stubbed.

▲ vs telematics toolsEffort: MediumNeeds: Backend

Live DVLA vehicle data

Planned

Promote the simulated MOT/tax sync to the real DVLA Vehicle Enquiry Service (server route + key).

▲ vs telematics toolsEffort: LowNeeds: Backend

Driver performance scoring

Planned

An analytics layer over walkaround, incident, infringement (and later tacho/tracking) data.

▲ vs telematics toolsEffort: MediumNeeds: Phase 3 data for full depth

Phase 3

Telematics partnerships

Integrate, don't build hardware — these need an external data feed, not just code.

Tachograph remote download

Planned

Ingest driver-card & VU downloads from a tacho provider, then extend the existing infringement engine.

▲ vs telematics toolsEffort: HighNeeds: Telematics partner

Real-time GPS tracking

Planned

Live vehicle location & data feed via a telematics API, with a map/live layer.

▲ vs telematics toolsEffort: HighNeeds: Telematics partner

Phase 4

Accreditation & scale

Process, trust and commercial maturity — partly time-and-regulator, not just engineering.

DVSA Earned Recognition

Planned

Pursue accredited ER status — the KPI scaffolding (Audit Pack, OCRS, maintenance, infringements) is already in place.

▲ vs telematics toolsEffort: MediumNeeds: Track record + DVSA approval

Billing & subscriptions

Planned

Stripe-backed plan & billing against the existing seat tiers.

Effort: MediumNeeds: Backend

Platform hardening

Planned

Server-side RBAC, audit, super-admin controls for multi-tenant scale.

Effort: MediumNeeds: Backend

Internal planning view · timelines are directional, not commitments. Tracking, tacho remote-download and Earned Recognition depend on external partners or regulators, so they mean “integrate & get approved,” not just “build.”