You know what you want to build
Most clients come to us at this stage. Some arrive with a tight brief. Others have a strong instinct but the details aren’t fully resolved. Either way, the job doesn’t start at the build. It starts at the question.
We look at the brief before we touch the code


What it looks like in practice
Detector Testers came to us with a new smart product in their range. It was Bluetooth-enabled and they needed an app to go with it. The brief, on the surface, was simple.


What we actually built was more than an app. We worked with them on the subscription model, the payment processing, the onboarding method, and how device management would work across companies. We built the back-office compliance reporting. We put the full product architecture together around what their customers would need and what the business would need to grow.
They knew what they wanted to build. We knew how to build it in a way that would work.
What you end up with
A product that does what it’s supposed to, is built to scale, and doesn’t close off options you’ll want later. We stay involved after launch, which means the decisions we make in scoping are ones we have to live with too.
If the brief needs challenging, we’ll tell you before we start. If something in the scope is going to cause problems, you’ll hear it from us in week one, not week twelve.
