We turn assumptions into evidence, and evidence into product decisions.

Before larger work, we often start with discovery.

Discovery is a short paid phase before a larger build, program, retainer, or partnership. It helps us understand the decision behind the request, the risks that matter most, the constraints around the work, and the kind of proof needed before execution begins.

It is not an open-ended strategy deck. It is a way to turn a broad request like "build an MVP", "help with GTM", "launch an AI workflow", or "enter a new market" into a clear scope, timeline, team shape, and recommended path.

Discovery answers how to approach the work. Validation answers whether there is enough market, workflow, buyer, or product proof to justify the next commitment.

Discovery usually takes a few working days to a few weeks depending on the complexity of the product, GTM motion, technical system, stakeholders, and decision at stake. Not every engagement needs a separate discovery phase. Validation Sprints and Demand Validation Sprints usually include enough discovery inside the sprint itself. For larger builds, programs, retainers, and partnerships, discovery protects both sides from starting with the wrong scope. Discovery can also be useful as a standalone diagnostic when the next step is unclear.

Sometimes that is a landing page, offer narrative, customer interview sequence, or concierge workflow. Sometimes it is a real MVP, internal tool, AI workflow, dashboard, or integration. The point is not to avoid building. The point is to build when the artifact can create better evidence than conversation alone.

The methodology adapts to maturity. The proof question changes with the stage, and so do the engagements that answer it.

Build-stage engagements live in the Build family.

You should not have to brief one team on strategy, another on development, another on marketing, and another on analytics. Proof Engine keeps the core question visible while moving across the work needed to answer it.