RAPID SERVICE TRANSFORMATION: Your Fast Lane to Success

Bring us a project that has failed twice or failed to get funding twice. We’ll make it happen.

Our teams excel on these platforms:

What Clients Say

WE BUILD DIGITAL SOLUTIONS TO OUTCOMES, NOT SCOPE DOCUMENTs

Scope docs kill the projects they’re meant to enable.
Most tech projects started with a problem worth solving.
Teams then get distracted by building a scope that covers every possible issue and budgets for every possible feature.
Big 4 Consultancies love charging through the teeth for these paper piles.
And it can take years.
Worst of all, the initial problem is too often forgotten, buried under a growing list of external stakeholder “requirements”.
At ThunderLabs, we deploy teams of developers, called Lightning Teams, trained to do problem discovery, prototyping and deployment — lightning-fast.

The first full solution will be live in as little as 4 weeks.

We then roll out a full deployment, with all the integrations and essential functions.

THAT’S HOW OUR TEAM DROVE REVENUE UP AND INTERNAL HEADACHES DOWN FOR…

Saved $10 million per annum in field force efficiency with a collaboration tool that cost $2 million less than the original budget.
Delivered over $20 million per annum in savings by creating 35 cloud-based solutions for students, educators, parents, and agents at Monash University.
Saved News Corp $20 million per annum in a ground-up reengineering of their customer service platform.

WE FINISH PROJECTS 5X FASTER, AND FOR HALF THE COST. HERE’S HOW:

1.

We’ve replaced technical scopes with business outcomes so we can start coding in days, not months.

Technical scopes are attempts to predict everything that needs to be included in the solution. They take months to write and get approved and include many requirements that don’t end up contributing to the business outcome but contribute heavily to the budget.
We define a Lightning Rod, the one business outcome that matters. We know the value a solution will deliver and set a budget proportionate to that.
It only takes one or two meetings to agree to, and then we begin coding.

Our Head of Projects, Andrew Walker, helped Monash University Law School focus on a single issue — speed of processing applications — which ultimately led to cost savings and better applicants.

2.


We exclusively use cloud tech, rather than on-premises infrastructure (saving months of pre-project effort)

This choice alone saves hundreds of hours of meetings about architecture and infrastructure. Using cloud platforms, we can start coding immediately, knowing that everything we build is scalable and can integrate with your existing tech.

3.


We launch a live pilot with a small group of users within just days and for less than 20% of the budget.

The only way to know we’re achieving the business outcome is to use the software in real situations, which is why our pilot versions are live in under 3 weeks. We ask ourselves, “Have we gotten closer to the business outcome? What will make the next biggest impact on reach the goal?”
Compare this to the traditional approach, which is dependent on meeting every possible requirement in version 1 — including edge cases and the needs of external stakeholders. That’s why it takes months to deploy to a real situation, which means the entire budget is spent going down the wrong path. We prefer to start small and with certainty.

In a project that ultimately saved News Corp $20 mil per year, the initial pilot was deployed to just 5 of the 300+ call centre staff. This gave absolute confidence in how successful the project would be, just weeks after beginning.

4.


We then iteratively scale and deploy to meet the needs of more and more users until the objective is met.

We then expand the user base and solve the objective for them too. We add integrations and also make sure we’re meeting the needs of other stakeholders in the business, too.

After AusGrid made multiple frustrating attempts to deploy business-wide changes, we helped them create a new works-management software that was deployed depot by depot. Each additional deployment addressed new edge cases and ensured 100% adoption.

 

5.


We then celebrate the customers won over, the lives improved, and THE MONEY SAVED.

Traditionally, IT projects are judged on whether they were “on time and on budget” — forgetting about the business outcome!
Instead, at every stage, we return to our Lightning Rod — the singular business objective we needed to meet. Just weeks or months after starting, we’re ready to celebrate another successful lightning strike.

Ready to see if there’s a spark?

Let’s do coffee, Zoom with pets in the background, or just solve the world’s problems on a whiteboard.