Rebuilt screen by screen. Every major feature under estimate.
Got a platform that needs to move forward without missing a day? We modernised Jumpstart's platform alongside their own engineers.
At a glance
- 01
Client. Jumpstart, a multi-channel customer engagement platform (CPaaS).
- 02
Industry. Technology & SaaS.
- 03
Delivered. The platform's administration rebuilt end to end, from sign-in to campaign design.
- 04
Approach. Design first, then rebuilt in stages.
- 05
Team. Development, design, analysis, testing and delivery, alongside their engineers.
Taking a proven platform further
Their platform had proven itself over many years, running campaigns across many channels every day. The business wanted to modernise how people work in it, while its own engineers kept the services and data behind it.
Every campaign had to keep running while it happened.
We built the foundation first, and every screen got faster
With a platform this size, it's tempting to start with the screens people use most. We started with a shared library of components instead: every form, table, button and sign-in step built once, tested once and reused on every screen after it.
It took time at the start and paid it back on every module that followed. Each of the eleven largest features came in under its estimate, 34% under in total.
It slowed the first weeks down and sped up every month after them.
How we built it
We agreed the plan before building anything
The work opened with in-person workshops, where their team walked us through the platform against a brief covering architecture, user experience, integrations, data and support. From there we profiled six user personas, benchmarked the product against its market, mapped the technical scope page by page and costed it.
Old and new ran side by side
We replaced the platform module by module, never in a single switch-over. A new shell wrapped the pages still waiting to be rebuilt, so users moved between old and new without noticing the seams, and nothing had to go offline. Each module followed the same discipline: document the old page and everything it did, define the new screen and the services behind it, then build.
Every year of data stayed intact
The data behind the platform was reorganised into clear areas and kept where it was. That preserved the full history of production data, and the behaviour the business relied on, exactly as it was, while the screens on top of it changed completely.
Built on their services, to their release rhythm
The new screens talk to the client's own services, which their engineers kept owning throughout. We estimated, sequenced and planned each module into two-week sprints, and translated our estimates into hours their planning could use. Releases ran on their schedule, and we fitted our delivery around it.
Access designed in from the start
Sign-in and account security were rebuilt as one complete flow, with sensitive details masked when data leaves the platform.
Every critical journey tested automatically
Ten automated end-to-end test suites cover the sign-in journeys and the key screens, so a change in one module can't quietly break another. Every change went through code review before it reached their release.
A small team, every discipline covered
Six people carried the work across development, user experience, business analysis, testing and project management, working alongside their engineers. Design and analysis stayed in the team for the whole build, so every screen was shaped around a real persona before anyone wrote code for it.
Built around the people who use it
Users set up their own teams, permissions and business rules, and see who changed what and when. Reporting lives inside the platform as dashboards people can read at a glance, and campaigns are designed visually on a canvas.
Every screen now works the way the people using it do.
What we delivered
- 01
1% rework. Measured across every hour of the build.
- 02
No defect above medium priority. Nothing high, critical or blocking was raised at any point.
- 03
Every work item closed. Not a feature, task or defect was left open at the end.
Brought into their planning
The work ran for 21 months and closed with every module in place. Along the way, their team brought us into their planning.
Keep going
Ask us for an estimate, then hold us to it.
Tell us about a project like this.