One system, however the work arrives.
One job board, one driver roster, one accounting ledger. Pull jobs from your suppliers, take direct bookings on your own domain, route work to your drivers, and close the books — all in the same tool.
One queue for every channel.
Jobs arrive from your suppliers, your booking site, direct posts, and bulk imports, and land on the same board. Route one to your own driver, or open it to the driver network.
Unified job board
Every source in one queue. Filter by trip type, car class, operator, supplier, status, or date.
Schedule-aware assign
Quick-assign with a 3-card schedule preview and a tight-gap warning when the SOP buffer is breached.
Bulk operations
Assign, open to the network, or cancel across dozens of jobs in one move.
Overflow goes to the network
Open a job to the driver network when nobody on your roster can take it. Only drivers who clear the claim checks can pick it up, and the client stays yours.
Driver bidding
Let drivers bid for jobs with a distributed lock — no 'I tapped first' arguments, the server arbitrates.
Audit trail per change
Every assign, cancel, edit, throwback recorded with the actor's identity denormalised on the entry.
Drivers and ops staff, all role-gated.
Onboard drivers, control what your ops staff can see, and verify licences and documents with AI assistance, without leaving Fusion Link.
Invite + apply flow
Public invite links for external drivers; in-app applications for internal hires. Approve, reject, suspend, ban — all role-gated.
5 roles, plus Owner
Admin, Finance, Operations, Support, Driver — each with its own navigation, its own permission boundary, and a full audit trail of who did what. Owner sits above all of them and is assigned only by transferring ownership, never from the role picker.
AI-assisted document review
Driver licences and supporting documents reviewed by a two-model pipeline (DeepSeek primary, Moonshot Kimi vision fallback).
Money is the sharpest line in the system.
The role you give someone decides which surfaces they reach and — more importantly — which numbers reach them. Financial fields are stripped server-side before the response leaves the API, so a role that cannot see a client rate never receives one to hide.
Both sides of the money
- Owner — everything Admin has, and the only seat that can hand ownership on
- Admin — dispatch, suppliers, booking site, settings, and the full ledger
- Finance — accounting, wallet, invoicing, payables, reports, period close
- All three see client rate and driver pay in full
Driver pay only
- Operations — jobs, roster, clients, fleet, analytics, and the audit log
- Sees driver pay, because you cannot dispatch a job without it
- Client rate is removed from the response — including inside audit-log diffs
- No access to suppliers, the booking site, accounting, or settings
No money at all
- Support — read access to jobs, drivers, and clients, plus customer success
- Both sides of the money stripped before the response leaves the server
- Driver — their own jobs and pay, never a client rate, on any surface
- Unrecognised roles fall through to this strip, so a new role leaks nothing
Cover the job you cannot fill, without handing over the client.
Your own roster gets every job first. When nobody on it can take one, open that job to drivers on the network instead of posting it in a chat group. The job stays on your board — your client, your record, your proof, your brand. What changes is who drives.
How a job reaches the network
- Open one job from the board, or dozens of your own jobs in a single bulk action
- Set the miss rule once: a direct or booking job opens itself when its driver goes quiet
- Supplier jobs go one at a time, so the supplier is told the job is covered
You keep control of the listing
- Withdraw the listing at any time and the job returns to your board
- Assign your own driver while it is listed and the listing closes with them
- Choose when you create the job whether drivers carrying a yellow card may claim it
Who can claim it
- A phone-verified driver with a complete profile, in the same country as the job
- Their vehicle class has to cover the job's tier, and a wheelchair job needs a wheelchair vehicle
- We ask for vehicle documents when a driver takes work, not at signup
First claim wins
- Every claim goes through a distributed lock, so two taps cannot both win
- The driver who misses out is told in the same second, by the server
- No 'I tapped first' argument ever reaches your ops team
The standard has teeth
- Report a driver who let you down; Fusion Link reviews it and decides the card
- A yellow card shows for every operator that driver works with
- It lapses after 6 clean months, and 3 active cards escalate to a red one
- A red card has no expiry date — only a successful appeal clears it
The client never sees the handover
- Tracking link, milestone emails and receipts stay in your brand
- Photo and GPS proof lands on your job, in your evidence export
- The driver sees Driver Pay only — your Client Rate never leaves your side
- No extra fee for using the network — the trip carries one job fee
From booking to dispatch in one flow.
Clients book on your own domain. Stripe takes the payment. The booking creates the job. Your driver picks it up, and nobody copies anything across.
- 01·step
Pick a template
11 templates across dark, light, and warm palettes — claimed exclusively, so no other operator runs your page. Live on your own domain with SSL provisioned automatically via Vercel.
- 02·step
Configure pricing
Base + per-km + minimum, trip-type multipliers (ARR / DEP / TRF), add-ons, time-of-day, airport proximity, holiday surcharges.
- 03·step
Take bookings
Multi-step booking form with quote, add-ons, payment. Multi-leg (chain) bookings supported. Stripe Connect direct charges to your account.
Win corporate without losing your margin.
Multi-traveller accounts with cost centres, applied discounts, and approval workflows — Stripe authorises but holds capture until an approver signs off.
Multi-traveller accounts
Cost centres, applied discounts (percentage or fixed rate card), dedicated traveller invite flow.
Approval workflows
Bookings hold in pending_approval until an admin signs off. Stripe captureMethod is 'manual' so the card is held but not charged.
Invoicing
Sequential invoice numbers per operator, real PDF rendering via React-PDF, country-driven tax rates snapshotted at issue time.
Accountant-grade, not spreadsheet-grade.
Two visible ledgers — your Fusion Link wallet and your driver payouts — with a double-entry general ledger underneath both, and the reports your accountant actually asks for.
Ledgers & journals
- Wallet — what you owe Fusion Link (top-ups, job fees, refunds)
- Driver payouts — what you owe your drivers (jobs, payables, settlements)
- Double-entry GL — 16-account seed chart, reversing voids
- Backfill button replays history into the GL if anything drifts
Reports
- Trial Balance, Balance Sheet, Account Ledger
- Profit and loss across jobs, drivers, clients, and revenue
- AR/AP aging waterfall (0-30 / 31-60 / 61-90 / 91-120 / 120+)
- Google Sheets export for accountants who live in spreadsheets
Period control
- Close a period to freeze financial fields on every job in it
- Operational fields stay editable for post-close corrections
- Admin-only reopen with a written reason, audit-logged
- Currency-safe money (JPY, SGD, USD) — no rounding drift
Reports, balances, analytics.
See what your operation actually did this week, this month, this quarter — without exporting to Excel.
Reports & balances
Jobs, drivers, clients, and revenue across every aging bucket. Live, with no overnight refresh.
Activity monitor
See ops actions as they happen. Audit log on every state change with denormalised actor identity.
Daily digest email
Daily digest delivered on a cron — so you don't have to log in every morning to know what's pending.
Prepaid wallet, no monthly bill.
Top up, run jobs, and never handle an end-of-month invoice for job fees. Promo codes help you win clients, and premium booking site templates debit daily from the same wallet.
Prepaid wallet
Self-serve top-up from MX$1,500, up to MX$70,000 per transaction via Stripe. Wire transfer for larger amounts.
Promo codes
Issue discount codes to win new clients. Each one is tracked through to the booking and into your reports.
Booking site templates
Your booking site is included in the per-job fee — building it, your own domain, and Stripe checkout all work today. Claiming a template exclusively is the paid extra, sold in Malaysia, Singapore and the UAE so far and not available in your market yet.
See it on your own jobs.
Sign up free. One flat MX$7 per job — log it or dispatch it.