We Tested It With the Team. They Tested It With Customers. It Changed Everything.
A Northern Ireland service business discovered that the questions nobody asks in planning meetings are the ones that matter most.
Every growing business has a process like this. It works, just about. It's held together with spreadsheets, emails, and the institutional knowledge of whoever has been there longest. Nobody loves it. Everyone has learned to live with it. For one Northern Ireland service business, that process was quietly costing them more than they realised, until someone asked a question nobody had thought to ask.
The problem
Jobs tracked across three different places. Information entered twice. The wrong version of something sent to a customer at least once a week. The team knew what the solution looked like and had been talking about it for months. The brief was written. A development budget had been set aside. They were ready to build. Then someone asked: has anyone actually tested this with the team? With the customers who'd be using it? The answer was no. Nobody had.
Our approach
The client started with a conversation with Blu, followed by a couple of discovery sessions to work through the problem and identify the one thing the tool absolutely had to get right. Twelve days later (more complex than a standard sprint, with multiple user types, permission levels, and a customer-facing element), the team had a working prototype they could put in front of real people. Every prototype includes a built-in feedback tool so testers can flag bugs, highlight friction points, and mark what they love with a single click. Three small enhancements were made during the first week of testing alone, fixes that would normally surface in a post-launch review six months later. By the time the prototype reached real customers it had already been sharpened by the people who knew the work best.
The outcome
Internal testing surfaced three things that had never come up in any planning meeting: a sequencing issue, a notification timing problem, and a workflow step nobody had measured that turned out to be where the most time was being lost. Customer testing was more surprising. The feature the business had planned to lead with barely came up. What customers got excited about was a secondary feature added almost as an afterthought. They said it was the reason they'd use the tool over what they were currently doing. Two revision rounds later the prototype had been rebuilt around what the testing actually revealed. When they were ready to build the real thing, Bluprint introduced them to a trusted development partner. The full build is currently underway. When it launches, it will go to market with something most products never have: a specification that was tested, challenged, and validated before a line of production code was written. The whole process from first conversation to validated brief took just under six weeks, at a fraction of the full build budget. Building the original brief without testing and discovering the same problems in production would have cost eight to ten times more.