IoT and connectivity
Moving an IoT platform to the cloud
I led the move from on-premises infrastructure and set the roadmap for reporting, analytics and AI.
- AWS
- Platform development
- UI and UX
- Full stack
- Cloud migration
- 3 months to real timereporting turnaround
- 4white-label clients onboarded
- 1on-premises to cloud migration
Overview
I led delivery of Eseye’s IoT connectivity platform through a complex migration from on-premises infrastructure to a cloud-native architecture.
Platform development
The problem
Eseye was moving from an on-premises environment to an AWS-hosted platform without a clear product strategy or well-defined requirements. Priorities were unclear, requirements arrived with no structured intake or validation, and most development capacity was offshore, so requirements were misunderstood and gaps surfaced late.
The platform was being rebuilt like for like with the legacy system instead of being refined around user needs. Projects shipped but missed expectations, and a disconnect between product and engineering slowed decisions.
What I delivered
- Critical platform capabilities, including dashboards, alerting and notification management, and existing features reworked for usability and performance. This helped Eseye secure additional clients and deliver against agreed statements of work.
- A realistic two-year roadmap that balanced new capability, underlying platform work (APIs, ETLs, SOLR and data) and paying down technical debt.
- End-to-end delivery ownership for Product Managers, covering statements of work, detailed requirements and collaboration between internal teams and clients. Teams began delivering solutions that met expectations first time.
- A product-centric delivery model using wireframes, acceptance criteria and non-functional requirements. Engineering was involved earlier, late rework fell and scope creep was limited.
- One intake and governance process for feature requests and defects, with traceability from request to release.
Reporting, analytics and AI
The problem
The on-premises reporting solution did not scale as client adoption grew. Reports ran on fixed schedules, struggled with large data volumes and produced static, PDF-style output. Earlier attempts to improve it lacked product ownership and made only incremental changes.
What I delivered
- Reporting moved from a 3-month turnaround to real time, through on-demand reports and a real-time customer dashboard.
- A scalable reporting architecture to replace the legacy solution, with redundant reports removed, a clear MVP and cloud data pipelines for query-driven reporting.
- A two-year reporting roadmap aligned to user needs and commercial priorities, moving from scheduled output to on-demand reports.
- On-demand reporting at scale, using structured aggregation and search-based retrieval (SOLR) for large and complex requests.
- The end-to-end reporting experience, so users can access, download, schedule and request reports from the interface.
- A real-time customer dashboard showing each customer’s estate, later extended with configurable widgets, comparative analysis and forecasting.
More case studies
Explore other projects across government, platforms, e-commerce and financial services.