About Webspringcore
A Malacca-based practice reading rider-app events for shared scooters and bikes — so field crews and city managers share the same picture of what the fleet is doing.
Why we exist
Shared e-scooters and city bikes live or die on short loops: unlock, ride, park, repeat. When the rider app and the depot diary disagree, vehicles sit idle while riders walk away. Webspringcore was formed to sit between those two worlds — translating event exports into language ops leads already use on the floor.
Origin
The practice began after years of freelance review work for small Malaysian fleets that could not justify a full-time analyst. Clients kept asking for the same things: why first rides fail in the rain, which blocks waste battery overnight, and how to brief partners without a 40-page deck. We standardised that work into named engagements and kept the office in Malacca for calm call schedules and easy travel to west-coast cities.
How we work
- Exports, not credentials — we analyse files you send; we never need live database access
- Ops in the room — every flagship review includes someone who moves vehicles
- Malaysia-first context — wet-season patterns, e-wallet friction, and tourism weekends are treated as first-class inputs
- Plain delivery — action lists first; charts only when they settle an argument
People
Farah Lim — Practice lead
Former fleet coordinator for a peninsula bike-share pilot. Farah scopes engagements, runs debriefs, and guards the line between analysis and product speculation.
Hafiz Rahman — Event analyst
Specialises in trip completion and geofence refusal patterns. Hafiz builds the sample checks and time-band idle maps used in rebalancing briefs.
Mei Tan — Client editor
Turns findings into partner-ready summaries and keeps legal and privacy wording aligned with Malaysian expectations for anonymised mobility data.
Values we hold to
We refuse vanity metrics that cannot change a depot shift. We document assumptions. We name mild uncertainty when sample windows are thin. We do not claim to replace your product team — we sharpen the questions they already face.
Community
Where useful, we share anonymised field notes on Malaysian corridor quirks (festival road closures, campus term calendars, harbour promenade spikes). Operators remain anonymous unless they ask to be named in a client story.