Personalised mobile dialogue at Fortune 1000 scale.
The platform serves Fortune 1000 CMOs who need to run personalised mobile campaigns across millions of users — push notifications, in-app messages, offline-first delivery, with the analytics to back the ROI conversation.
The hard problem is that mobile is hostile to backend assumptions. Devices go offline; campaigns have to schedule and fire on-device; sync has to be reliable when the connection comes back; analytics have to reconcile when events arrive late.
What we shipped, in order.
Campaign dashboards for marketers; user segmentation and targeting; push notification delivery; offline campaigns with on-device scheduling; reusable templates; an analytics pipeline; a data export layer; integrations with Microsoft Dynamics and Salesforce for sync with the CRM CMOs already run.
Each capability landed as a sprint or two of work, then matured over years of customer feedback. Nothing was built once and walked away from.
A multi-platform stack carrying millions of daily events.
Native iOS, native Android, two backend frameworks for different services, an analytics pipeline, and a frontend that has to render the campaign editor enterprise marketers actually use. The stack reflects 12 years of compounding scope.
Twelve years of compound shipping.
The engagement opened in 2013 with three Runtime developers, and grew through compounding scope to ten developers and two QAs. Same team, same product, same release cadence — across iOS overhauls, Android platform shifts, web stack changes and backend refactors.
Still shipping.
The platform is live, the codebase is theirs, and the team that built it is still on the PR queue. Long engagements, not transactional handoffs.
