What we build for telecommunication teams
Self-service portals, provisioning flows and usage analytics over high-volume event data. The work usually falls into three buckets: a customer-facing journey that has to convert, an internal system that has to be correct, and the integration between them that stops people re-keying data.
Typical problems we are called in for
- A process that works at current volume and visibly will not at double.
- Two systems that both hold “the truth” and disagree with each other.
- A customer journey with a drop-off nobody can explain because nothing is instrumented.
- A product built fast by a team that has since left, and nobody wants to touch it.
How an engagement usually starts
With a two-week discovery: we sit with the people who run the process, map it as it really happens, and come back with a scope, an approach and an estimate.
Related work
Rebuilding organic search for a multi-category online storeA store with thousands of SKUs was ranking for its brand name and almost nothing else. We rebuilt the category architecture and the content behind it.Cutting cost per qualified lead for a B2B services firmThe account was generating plenty of leads and almost no clients. We changed what was being optimised for.