Vehicle transportTaken over and rebuilt

Dilizy transport marketplace

Two-sided logistics marketplace (web)

A vehicle-transport marketplace taken over from a previous contractor: clients post jobs, carriers bid, split payouts through Stripe Connect.

The problem

We inherited an unfinished codebase from a previous contractor, and the flow from order to payout was not ready for production.

Before it could launch, the marketplace needed a money flow that holds up and an order lifecycle everyone can follow.

01
An explicit order lifecycle
Every order moves through defined states from posted to bid, accepted, delivered and confirmed. Carriers are matched by distance with PostGIS.
02
Split payouts through Stripe Connect
The client is charged when an offer is accepted and the carrier is paid when delivery is confirmed, with webhooks, scheduled reconciliation and retries of failed transfers.
03
Two front ends on one API
A client app and a carrier app in one Nuxt monorepo with a shared UI kit and maps, on a GraphQL API with team permissions and two-factor sign-in.

Built to launch: every branch deploys automatically, and the database is backed up before each migration.

It has not opened to the public yet.

Payments: Split payouts through Stripe Connect: charge on acceptance, transfer on confirmation.
Reconciliation: Scheduled reconciliation of payouts and automatic retries of failed transfers.
Matching: Carriers are matched to jobs by geographic distance.

Next step

Tell us where it is. A short call about what you have, what blocks launch and whether we are a fit.

No pitch deck. A straight answer on what's blocking your launch.