Services

Product Strategy

If what gets built never quite matches what you meant, the missing piece is usually product. It sits between the business and the build, and speaks both languages: technical in business conversations, commercial in technical ones.

We work out what you actually need, specify it so it holds up beyond the easy cases, and then build it with you, or alongside whoever is building it.

Product as the bridge between business and technicalTwo lanes. Business: goals, customers, budget. Technical: requirements, data model, vendors. Product sits between them and translates in both directions.BusinessTechnicalGoalsCustomersBudgetRequirementsData modelVendorsProductSPEAKS BOTH

Built for the happy case

Systems and data are very literal. A system does exactly what it was told, and nothing it wasn't. Most are built for the happy case: the order that arrives complete, the customer who fits the form, the month with no exceptions.

Then real work arrives, and people handle the exceptions: a spreadsheet on the side, a field used for something it wasn't meant for, a step someone does from memory. When someone fixes "that" issue, the fix is usually another workaround, built into the system. Each one makes the next harder, and the system becomes more fragile, not less.

Worse with an LLM

Hand a vague brief to a good developer and they'll ask questions. Hand it to an LLM and it's eager to please: it builds something, quickly and confidently, whether or not it helps.

Without a product person in the loop, the questions that would have caught the edge cases never get asked, and the workarounds arrive faster than ever. Product is the work of thinking through the exceptions before anything is built, so the system handles the business you actually run.

Sounds familiar?

"It works, as long as nothing unusual happens."

"We keep a spreadsheet next to the system for the cases it can't handle."

"Every fix seems to break something else."

"Only one person knows how to do that bit."

"We asked for a small change and got a quote for a rebuild."

"The AI built it in a weekend. Now nobody knows how it works."

What we do

Define

We start from what you know about your business and your customers, test it where it matters, and agree what the first version has to do. That might be an MVP of a single feature, or of a whole product or platform. We run workshops and design thinking where they help, not as a ritual.

Specify

We write requirements and a data model that agree with each other, including the exceptions: what happens when the order is incomplete, the customer doesn't fit, or two rules disagree. That's the part a developer or a model can't guess.

Build, or work with your builder

We build it with you, or act as your product function alongside your build team, vendor, or LLM. With your vendors, we're a trusted third party, on the side of the commercial outcome you're after.

Prioritise

We order the roadmap and backlog by business metrics and customer need, so the next thing built is the thing that matters most, and the system stays something you can change.

How we engage

By the project, by the day, or to a fixed scope. We agree the scope with you for each engagement, so you know what you're getting before we start.

Often goes with

Most problems don't arrive labelled. If yours turns out to be about how your systems fit together, or who makes the technical calls, we'll cover that too.

Ready for a conversation?

No sales pitch. No obligation. Just a chat about what you're building and where the opportunities might be.