CASE STUDY · NORDIC OPERATOR · STOCKHOLM · 90 DAYS
The underlying capability: our 24/7 swap operations service line.
Uptime 74% → 92% in 90 days.
Same fleet, same cities, new 3PL. Here is what changed in the first operational quarter.
Context.
Top-tier Nordic shared e-scooter operator. Active in Stockholm, Gothenburg, Malmö. Pre-Binny operations run through a rotating set of staffing agencies. Fleet uptime at 74% p75, repair backlog at 210 vehicles, municipal SLA breaches at 4 per month. Municipality had issued a formal warning on response time.
The problem.
- Overnight swap crews swapping drive-time, not swap-time. Swap efficiency dropping, billed drive-time up 15% QoQ.
- Morning deploy on a static grid — vehicles piling at transit hubs by 09:00.
- Repair queue growing faster than warehouse throughput. 210 vehicles off-street.
- No in-market shift lead. Every fire-drill escalated to Stockholm HQ.
What we did.
- Week 1. Country manager on the ground. Full route audit pulled from 30-day ride data. Replaced static deploy grid with demand-curve routes.
- Week 2. Local crew hired, Binny-employed. Thermal cases deployed. Shadow-run on overnight window.
- Week 3. Handover. Binny takes overnight swap + morning deploy. Daily 08:00 report to VP Ops + Finance.
- Weeks 4–8. Repair-queue workdown. Level 1 fixes moved to street (68% closed on pavement). Warehouse throughput doubled.
- Weeks 9–13. Municipal SLA breach to zero. Reporting established with city regulator.
Outcome at day 90.
| Metric | Pre-Binny | Day 90 |
|---|---|---|
| Fleet uptime (p75) | 74% | 92% |
| Repair backlog | 210 | 38 vehicles |
| Municipal SLA breaches | 4/month | 0 |
| Morning SoC median | 46% | 72% |
Binny took over overnight operations in week one. By month three, our city manager stopped spending mornings on Slack and started spending them on growth.
Operations Director, Nordic operator
Benchmark your numbers against this.
30-minute call. We read your last 30 days of data. You get a one-page diagnostic.