The problem

Products fail before development begins

Most digital products do not fail in the build. They fail earlier: an unvalidated problem, a proposition nobody sharpened, requirements that lived in someone's head, a roadmap shaped by enthusiasm rather than evidence.

Development then builds the confusion faithfully, and at full price.

Our role is to make the thinking rigorous before the spending starts, and to keep it rigorous as the product takes shape. That includes telling you when the evidence says stop.

A good product decision is one a sceptical engineer, a cautious investor and a real user would all accept.

Services

What this covers

Define the opportunity

Testing whether the idea deserves investment, and in what form.

  • Opportunity definition and problem validation
  • Target-market analysis
  • User and stakeholder requirements
  • Proposition refinement and business-model review
  • Pitch and narrative refinement
Shape the product

Turning a validated opportunity into a buildable definition.

  • Product strategy and concept development
  • MVP definition and feature prioritisation
  • Product and requirements documentation
  • Product roadmaps and implementation briefs
  • Website and application strategy
  • Framework and algorithm design
Build and review

Moving into delivery, and keeping it honest.

  • Prototype direction, no-code and AI-assisted builds
  • Websites and applications
  • Technology delivery, coding and implementation
  • Product and technology due diligence
  • Critical product reviews of existing products and plans
  • Startup advisory and founder and leadership advisory
  • Fractional strategic support through delivery

Who this suits

Founders and teams at a decision point

Startups deciding what to build first. Established organisations weighing a digital product or platform. Teams with a product in-market that has stalled and needs an unsentimental review. Leaders who need an independent, technically fluent second opinion before committing budget.

The work is grounded in having built products, not just advised on them: websites, applications, prototypes, algorithms and the documentation that connects an idea to a delivery team.

A typical engagement

From idea to implementation brief

A representative sequence: a validation sprint tests the problem and market with real evidence. A product definition phase produces the proposition, MVP scope and prioritised requirements. An implementation brief hands a delivery team everything needed to build without guesswork, with advisory support continuing through the build if useful.

Read: why products fail before development

When to bring us in

When an idea needs testing before money is committed, when a product has stalled between concept and build, when a board wants a direction it can defend, or when a raise is approaching and the numbers and the story both have to hold.

How this work runs

Your point of contact is always a Principal, and which Principal depends on the work and the stage it has reached. That Principal scopes the engagement, coordinates the work and remains accountable for it. Delivery is carried out by the Principals, by trusted consultants, or by both. Current specialist capability includes risk, fraud risk and anti-money laundering.

Outside scope. We do not provide legal, tax or intellectual-property advice. Where a build needs a permanent engineering team rather than a defined piece of delivery, we will tell you that plainly.

Next step

Have an idea that needs pressure-testing?

Send a short description of the product, the stage it is at and the decision you are facing. We will reply with how we would approach it.