Context.

Leading Germany shared-mobility operator. Expanding into three new German metros in the same quarter. Previous city-launch pattern: serial, 45–60 days per metro, with launch-month uptime typically 70–75% before stabilizing.

The problem.

• Serial launches bleed momentum. Marketing spend ahead of operational readiness burns CAC.
• Each metro requires its own crew, warehouse, and permit track. Coordination at HQ impossible.
• Permits moved at different speeds in each city — launch dependencies nobody could single-thread.

What we did.

1. Day 1. Three country managers, one per metro. Permit work kicked off in parallel from day one.
2. Day 1–10. Local crews hired and Binny-employed in all three metros. Vans leased, thermal cases staged.
3. Day 11–14. Shadow run in each metro. Operator team observes two overnight shifts per city.
4. Day 14+. First swap on the street in all three metros within the onboarding window. Daily 08:00 report covers all three cities in one view.

Outcome.

• Three cities live, simultaneously
• First swap on the street within weeks of signing
• Month-one uptime 88–91% across all three metros (historic baseline 70–75%)
• One ops contract, one invoice, three cities

Metric	Industry baseline	Germany outcome
Cities live in parallel	1 (serial launch)	3
Days to first swap	45–60	within weeks of signing
Month-one uptime	70–75%	88–91%
Ops contracts	3 (one per metro)	1

Parallel city launches are usually a coordination nightmare. Binny absorbed that coordination. We focused on marketing and regulatory. They focused on the street.

Head of Launch, German operator