Two weeks of work back every month, and customer reports in 30 seconds.

A UK manufacturer's team built every customer test report by hand, across several tools, 20 to 30 minutes each. Now every test sits in one structured history in HubSpot, and the report comes straight from the records in about 30 seconds, in as many languages as the customer needs. The customer gets it faster, it's consistent every time, and it's built on data the business can finally trust and report on.

2 weeksof work back to the team every month
30 secondsto produce a customer test report, down from 20 to 30 minutes
6 languagespicked by the team and generated together
80,000+tests in one structured history, linked to the product, the site and the deals

Where they started

This manufacturer installs its products at customer sites all over the world, and every one of them is tested once a year.

The business knew where it wanted to get to. A test schedule it could rely on across the whole installed base, and reps who could open a customer and see every product and its full test history before they walked in. The trouble was that HubSpot had been set up for a much smaller programme. Each product held its results in a fixed set of fields, so the history couldn't grow with the business and nothing could be reported on properly.

After every site visit, someone had to take the results and build the customer's report by hand. The results went from paper into spreadsheets, into HubSpot, out again and into PowerPoint, then back to the team to send on. It took 20 to 30 minutes a report, and it was pure admin that kept the team from more useful work.

Why it wasn't just more fields

Adding more fields would only have moved the problem down the road. The right answer was to make every test its own record, and that meant bringing years of history into a new structure without losing any of it.

The plan we agreed

I started by working with their team to understand the challenge and what each part of the business needed from the data.

Then the order of work. Get the structure right. Move the history into it, rehearsed and reversible. Then build the apps, reports and AI on top, because anything built on the wrong structure would have to be built twice.

What happened

Every product's results became individual tests in one history, over 80,000 of them. Every active product due its annual test, including the overdue ones, is now scheduled with the team, across more than 2,300 customer accounts.

Where they are now

A rep opens a customer and sees every product, every test and the deals beside them. The team can see which sites are due for a visit, and products can be moved between sites with their test history.

The customer report is now a branded document built straight from the records, with hundreds of data points. Nobody retypes anything. It takes about 30 seconds, files itself against the site, and the customer gets the same report every time. That's around two weeks of work back to the team every month.

Pick the languages, and every version of the report is generated at the same time. A customer with sites in six countries gets the report in six languages, all at once.

The bigger change is what the structure makes possible. Breeze now has clean, connected data on every product, customer and deal to work from. It's also opened up a route to connect the maintenance tools their engineers and customers use, so the same history can follow the product wherever the work happens.

This isn't really about testing. Anything that happens on a customer's equipment on a cycle, like inspections, service visits or renewals, ends up the same way if it's squeezed into fields. If that sounds familiar, the first call is where I'd tell you what your version looks like.

Where to next

Not sure where to start?

A short call is usually enough to work out the next step. I'll tell you straight whether you're fine on your plan and just need training, need some support, or have outgrown your tier.

Book a call