Scope
One active laundry partner, one configured market, a limited customer cohort and drivers known to the operating team.
Controlled launch
Prove one complete laundry order before scaling the market.
The first CleanLoop pilot validates the real chain: customer review, independent pickup, laundry production, independent delivery, payment reconciliation and visible exceptions.
Plan the pilotPilot boundary
Small enough to control. Complete enough to prove the business.
Success measures
Order completion, service acceptance, on-time handoffs, bag reconciliation, repeat use, support friction and contribution margin.
Output
A reconciled pilot scorecard, verified unit economics, documented exceptions and a factual decision on the next service area.
The proof path
The order is not complete until delivery and evidence reconcile.
01Customer submits
Reviews address, time, laundry, plan or pay-per-use quote and payment.
02Pickup completes
Driver confirms origin and destination, bags, arrival and handoff evidence.
03Laundry produces
Partner records intake, final weight, quality, evidence and readiness.
04Delivery completes
A qualified driver independently accepts and confirms destination custody.
05Operations reconciles
Completion, customer payment, driver earnings and partner settlement remain distinct and traceable.
Launch gates
We test the successful order and the failures around it.
A polished screen is not a pass. The pilot opens only when the transaction remains correct under retries, interruptions and competing actions.
| Gate | What must be demonstrated | Required result |
|---|---|---|
| Identity and environment | Customer login without company code, secure session persistence and zero fallback from pilot to demo. | No cross-tenant or demo data exposure |
| Order and service concurrency | Double submit creates one order; two drivers competing for one opportunity produce one assignment. | No duplicate orders or assignments |
| Custody | Bag counts and required evidence reconcile at customer, laundry and final recipient. | A difference creates a visible blocking exception |
| Money | Quote, final weight, membership pounds, customer charge, two service earnings and partner amount reconcile once. | No duplicate charge, earning or settlement |
| Recovery | Connection loss, app restart and proof upload failure preserve the user's work and allow a safe retry. | No silent loss or impossible state |
Pilot GO rule
One order crosses Customer, Driver, Laundry Partner, Admin and Stripe test without database editing, duplicate events or an unresolved custody gap.