Product roadmap

What we're building next, in the open.

The three columns below are the honest state of the platform. Items move left-to-right as work progresses; shipped items also land on the changelog with a dated write-up. Missing something? Request it— every roadmap addition here started as an operator email.

Planned

2
  • Native GNet affiliate trip exchange

    Planned

    Target: Q4 2026

    Send and receive GNet trips inside the dispatch board without email/SMS trip sheets. Tracked as the top-voted affiliate request.

  • In-platform affiliate directory

    Planned

    Target: Q1 2027

    Discover and connect with other Limozoft operators for farm-in / farm-out. Opt-in per operator; rate agreements remain bilateral.

In progress

3
  • Corporate self-serve portal (v2)

    In progress

    Target: Q3 2026

    Travel managers log in, book on behalf of executives, view consolidated PO invoices and download month-end statements without emailing the office.

  • AI-assisted rate quoting from inbound email

    In progress

    Target: Q3 2026

    Paste a corporate RFQ email; the assistant proposes a quote against your published rate cards for a human to review and send.

  • Public API v1 (reservations, chauffeurs, vehicles)

    In progress

    Target: Q3 2026

    REST + webhook access to reservation, chauffeur and vehicle objects. OAuth 2.0 client credentials, rate-limited, versioned.

Shipped

3
  • Two-way SMS conversations on the reservation record

    Shipped

    Every SMS to a passenger threads onto the reservation and is visible to dispatch and the assigned chauffeur.

  • Stripe-native tips and split payments on the driver app

    Shipped

    Tips route through the operator's own Stripe account and settle on the standard payout schedule.

  • Docs site (docs.limozoft.com) — first 50 articles

    Shipped

    Public knowledge base for dispatchers, chauffeurs and account admins. Covers onboarding, common workflows and API auth.

How we prioritise

The queue is set by three signals, weighted in this order: paying operators asking for the same thing more than twice, migration blockers for prospects in active evaluation, and platform hygiene (performance, reliability, security). We don't accept paid roadmap placement.

ETAs are targets, not commitments

We publish target quarters so you can plan around them, and we tell you the moment something slips instead of quietly reshuffling. If a roadmap item is a hard requirement for you to switch, ask on the demo — we'll either commit to a date in writing or tell you honestly it's further out than you can wait.

Missing something on this board?

Tell us what would make Limozoft the obvious pick for your fleet. We reply personally to every roadmap request.

Send a roadmap request →