One Saudi platform in EV manufacturing.
For the road, the coast, and the sky.

Discipline. The case has two parts — the delivery cash cow (the CP02 subscription business, Saudi first then GCC) and the build-out of the full range (CP02 hardware sales, CP03–CP04 vehicles, IP licensing, sea / air variants). The 2026 financial model prices the cash cow only because that is the part with production-intent hardware (CP02, validated forward from the CP01 prototype), validated unit economics, and month-by-month projections through Expansion. The full-range build-out is real engineering — Bills of Materials, controller schematics, and CleverPod Bridge architecture in the data room — but it is not assumed in the headline IRR or MOIC. PIF gets the underwritten number on the cover page; the upside is roadmap, not promise.

The CP01 hardware is validated prototype, EU L2e-U class certified, with engineering documentation and a Bill of Materials in the data room. The CP02 takes that engineering forward to production-intent design and is the model the planned Saudi fleet is to be built from. CP02–CP04 share the same drive, battery, and CleverPod Bridge controller — that is what makes the platform claim structural rather than rhetorical.

No. The sea and air slides carry a 'platform potential, not in seed plan' label and the seed-stage capital plan does not allocate against either. They are shown to make the platform's reach legible, because the same drive, battery, and software stack does extend that far in principle. Building either one becomes a separate funding decision after the cash cow is paying its own way.

UAE is a crowded fleet market with little room for a subscription entrant at early-stage scale. Saudi has larger delivery volumes, explicit sovereign-capital appetite for Vision 2030 investments, and a regulatory posture that rewards Saudi-resident operators. Subscription is unusual for both markets; the Kingdom is where the policy tailwind is actually paid in SAR.

The subscriber is comparing a predictable monthly service fee to a lumpy total cost of ownership: vehicle, battery, maintenance, insurance, compliance, downtime, training, resale risk. Our number is higher on the sticker; the TCO is lower for any operator that values uptime and compliance. We are not competing with the sticker price — we are competing with the real cost of running a small fleet without infrastructure.

Cleverpod is not leading with autonomy. The thesis is a modular electric platform with a software ecosystem, deployed first as a subscription delivery fleet from a Saudi entity. Autonomy features (operator-assist, remote-monitoring, eventual limited-domain automation) are upside that can be added without changing the business model. The thesis does not depend on autonomy.

Fair and acknowledged. The company's earlier iterations covered multiple geographies and product lines, and never reached operating scale. What is different now: one geography, one launch product, a Saudi-resident operating plan, and a model designed to pay its own way by the Startup stage. The 2026 financial model and the cap table are stage-gated — PIF capital arrives only when the prior milestone is hit. The governance is designed to enforce focus.

Revenue is in SAR. Major costs with CNY exposure sit inside the Shenzhen procurement entity, matched by CNY cost-plus revenue from the Saudi entity — a natural hedge at the consolidated level. The model carries the SAR/CNY cross explicitly with a single FX sensitivity ready to toggle. Tail-risk from broader China supply disruption is real; mitigation is inventory policy at Shenzhen Procurement and optional second-source qualification in Phase 3.

A subscription-hostile regulatory surprise in KSA (unlikely given current policy direction), a cost-of-capital shock that re-prices the DCF terminal (the model shows sensitivity), or operational under-delivery on the uptime SLA in the first 100 pods (the service wrapper has to work before stage 2 capital is released). Each has a named-range line you can stress-test.