Sanad connects stranded drivers, verified technicians, fleet operators and workshops through one real-time dispatch platform — Saudi Arabia's connected roadside-response infrastructure.
No single network — drivers rely on word-of-mouth mechanics and informal tow operators with no shared standard.
Roadside prices are negotiated on the spot, case by case, with no reference rate the customer can trust.
Requests move by phone call, not by system — no automatic matching to the nearest qualified provider.
A fleet operator has no central view of roadside events across their vehicles — every incident is its own phone call.
Every request — whoever submits it — moves through the same matching engine, the same lifecycle, the same real-time tracking. The surface is just who's looking at it.
Consumer app — request help, track the technician in real time, pay, rate the job.
Technician app — accept jobs, navigate to the customer, update status, get paid.
Operations console — live dispatch map, SLA monitoring, escalations, reassignment.
Fleet portal — vehicle registry, centralized request submission, consolidated visibility per account.
Scroll to watch a single roadside request move through the network — the same sequence that runs in the live system today.
A driver opens Sanad, selects the service they need, and shares their location.
The matching engine finds the nearest verified technician qualified for the job — automatically, no dispatcher required.
The offer reaches the nearest qualified partner, who accepts and starts navigating to the customer.
Sanad Command tracks the job live on the dispatch map, ready to reassign or escalate if timing slips.
For a fleet vehicle, the job closes into the fleet's own record — no separate phone call needed to find out what happened.
National investment in infrastructure and logistics is expanding the vehicle parc this platform serves.
Logistics and delivery fleets are already moving core operations onto software — roadside support is the piece still missing.
Extreme summer heat drives battery and tyre failure well above averages seen in temperate markets — a structural, recurring demand driver.
Early EV adoption introduces new roadside failure modes — charge, battery health — that today's informal network has no way to serve.
Structure shown now; sizing, sources and assumptions to follow once market research is finalized with the founding team.
Vehicle parc, breakdown incidence and existing roadside spend across the GCC, formal and informal.
The portion reachable by a licensed, app-dispatched network under Sanad's service and coverage model.
Three initial Riyadh service zones — the actual near-term target this pilot is built to prove out.
Directional, not final pricing — each channel has a distinct, natural monetization path once payments land.
Per-job margin on top of the technician's price.
Subscription covering priority dispatch and reduced per-job fees.
Recurring fleet contracts billed centrally, not per job.
A share of the repair job handed off from a tow.
Platform licensing for partners running on Sanad's dispatch core.
A denser request volume gives technicians a reason to go exclusive to Sanad over informal work.
More technicians per zone means shorter distance to the next job — the core metric customers actually feel.
A proven Riyadh pilot is the credibility fleets and enterprise partners need before signing on.
Illustrative structure only — absolute figures pending real pilot data, not to be read as current unit economics.
Do not read any phase beyond Phase 1 as already live — each phase gates on the previous one's results.
The initial coverage area this platform is built and tested against today.
Expanding zone coverage across Riyadh once pilot performance holds.
Second and third Saudi metro markets.
Direct enterprise and large-fleet contracts layered on top of consumer coverage.
Multi-country expansion, reusing the same platform core M7 already proved out for Sanad Business.
The Riyadh pilot has not launched — there are no real operational results yet. What's below is engineering execution: built and automatically tested milestone by milestone, each with a manual end-to-end pass in a real browser before being called done.
Auth, API tokens, real-time broadcasting infrastructure, and core platform configuration.
Customer, technician, dispatcher, and admin roles with gated areas per surface.
The request/offer/rating schema, with database-level guarantees against duplicate active requests.
Web and API submission flow, with coverage-area and duplicate-request checks shared by both.
Nearest-technician dispatch with race-condition-safe claiming, offer expiry, and automatic retry.
Arrival through completion, cancellation with fair fee rules, and post-job ratings.
Live technician location and status changes pushed to every surface, with a live dispatch map for operations.
Fleet accounts and vehicle registries, dispatched through the exact same matching engine as individual customers.
Each phase extends the same core rather than forking it — the pattern set in M7, where fleet dispatch reused the consumer matching engine unchanged.
Real payment capture for jobs and automated invoicing for fleet accounts, replacing today's recorded-only pricing.
Handoff from a tow into a vetted workshop, with repair status visible back to the customer or fleet.
Coverage verification at request time and a claims/reimbursement path for insurance-partnered jobs.
Individual driver logins under a fleet account, so drivers can request directly rather than through a fleet admin.
Multi-country coverage configuration and localization, extending beyond Saudi Arabia.