Actrol Virtual Engineer: pivoting from retail vision to internal impact
Reece · Senior Product Designer / Product Manager
TL;DR
- What we achieved: A live tool that saves Sales Engineers an estimated 20 minutes per quote.
- What I did: Made the case to pivot the whole product from end customers to the 24 internal Sales Engineers, then shipped in small, frequent releases.
- The call to make: Keep building the retail product the team had started, or change course this late in the project?
- What I inherited: A journey map, research and wireframes all built for a retail experience that interviews showed wasn't practical.
- The business: Actrol, a Reece Group refrigeration business, where engineers quoted using spreadsheets, printed manuals and a 15-year-old tool.
A bit about Actrol
Actrol is a Reece Group business unit serving the small-to-medium commercial refrigeration market across Australia and New Zealand. It's the trade that keeps everything from a small fridge to a walk-in cool room running for pubs, hotels, grocery stores and farms.
Reece acquired Actrol in 2016. As part of Reece's 2030 digital transformation, Actrol's systems needed integrating, and its fragmented, partly paper-based processes needed replacing with something faster and more reliable.
The people at the centre of it were 24 Refrigeration Sales Engineers. Their day was gathering customer requirements, calculating heat load for a cool room or freezer room, finding and selecting the right products, and putting together a quote. All without getting the heat load, equipment or pricing wrong.
All of this ran across disconnected systems and processes, which limited how quickly the business could respond to customer enquiries.
What I inherited
An internal group had already run the initial evaluation and discovery. They saw long-term business value and set up a small team of three to get it moving: an Engineer, a Product Manager and a UX Designer.
I joined after kickoff and inherited a journey map, some in-person research insights and early wireframes. All of it was built around a retail experience for the end customer, not the internal Sales Engineers.
After working through what I'd inherited, I pushed for more interviews, this time with the 24 Sales Engineers and the project stakeholders, to properly align on the vision. What came out was real misalignment. The value the project had been built on wasn't practical.
On top of that, the team was small for a product this deep in domain knowledge.
Keep going, or change course?
Do we keep building the retail product the team had already started, or pivot to a different user and problem? And how do we make that case credibly, this late into the project?
Changing course
Making the case to pivot
I worked with the Product Manager and Engineer to make the complexity and effort of the retail product visible. Then I made the case to pivot the whole product to the 24 internal Sales Engineers instead of end customers.
This was a big scope change on a live project. It meant getting engineering, product and stakeholders to agree on why the original premise didn't hold up.
Mapping the real workflow
We mapped the journey from enquiry to install through three people's eyes: an engineer, a branch manager and a customer.
Learning in small releases
We kept looping through research, experiments and improvements, and released in small beta milestones instead of one big launch.
We rebuilt Actrol Virtual Engineer around how the engineers actually work: heat load calculation, product selection and quoting. It's live and in use at ave.actrol.com.au.
What we achieved
The tool saves Sales Engineers an estimated 20 minutes per quote. That's the turnaround problem the original brief set out to solve. We just got there through a different user, and a more accurate read of where the value actually was.
What we learned
Additional visual reference: Dribbble shot.