Methodology

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

How we decide what to do, how we deliver it, and the ways you can work with us, from a consultation to a dedicated team.

1 · How we decide

The proof loop

Every engagement moves through the same five steps, whatever the function involved.

1

Define the decision

What choice is on the table?

2

Map the assumptions

What must be true?

3

Choose the proof

The cheapest credible evidence.

4

Build or run the test

Only what creates the evidence.

5

Decide what changes

Build, narrow, reposition or stop.

How we decide

Discovery Before Larger Work

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.

How we decide

Not all signal is proof.

Different stages need different standards of evidence. A conversation can be useful, but it is not the same as a paid commitment. A prototype demo can reveal usability, but it is not the same as workflow adoption. A pilot can create learning, but only if it has success criteria and a conversion path.

  • Weak signal: compliments, vague interest, broad market size, passive survey responses.
  • Useful signal: specific problem stories, active pull, repeated use cases, buyer urgency.
  • Strong proof: paid commitments, signed pilots, repeated usage, conversion, retention, operational adoption, or budget allocation.

For how this plays out in real engagements, see our case studies.

How we decide

Build the smallest thing that can create the right evidence.

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.

  • Do not build complexity to hide uncertainty.
  • Do not over-validate when users need something tangible to react to.
  • Do not run GTM tests that the product cannot support.
  • Do not build products without knowing what evidence they are supposed to generate.
How we decide

GTM is part of the product system.

We do not treat marketing as a detached campaign layer. GTM work changes what should be built, how the product should be packaged, which buyer matters, and what proof the team needs. Product work changes what can be sold, onboarded, measured, and scaled.

  • If development is requested, we ask who it is for and what validates the need.
  • If GTM is requested, we may build or change product surfaces that block conversion.
  • If AI is requested, we map workflow adoption before building the tool.
  • If market entry is requested, we test the buyer path before recommending scale.

This is what the full range of capabilities is for.

How we decide

Stage-specific proof

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

StageMain proof questionCommon engagements
Operator-led ideaIs this worth leaving comfort, budget, or career capital for?Validation Sprint, Demand Validation Sprint
Pre-seedIs there real demand and a wedge worth building?Validate, Validation MVP Build
SeedCan we turn product into revenue, pilots, or repeatable traction?MVP Diagnostics, V1 Product Build, Grow
Growth-stageWhich motion, product bet, or market should scale next?GTM Motion Buildout, First Traction System, Scale
Mature companyShould this initiative receive serious budget and roadmap commitment?Market Entry Proof, AI / Data / Cloud Modernization Engagement
Fund or partnerHow do we create repeatable proof across multiple opportunities?Portfolio Proof Program, Co-Build / Joint GTM Partnership

Build-stage engagements live in the Build family.

How we decide

Good proof creates a decision, not just a deliverable.

A useful engagement may lead to a build, launch, market entry, GTM investment, or modernization plan. It may also show that the team should narrow the segment, change the offer, revisit the workflow, or stop. That is not failure. That is the point of proof.

  • Build
  • Launch
  • Sell
  • Pilot
  • Scale
  • Sequence
  • Change
  • Stop
How we decide

Working with us should feel like one connected product conversation.

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.

  • Clear assumptions before execution.
  • Tangible artifacts when evidence needs something real.
  • Fast loops between customer signal, product work, and GTM.
  • Decision summaries that make next steps explicit.
  • Scope discipline tied to the proof needed.
How we deliver

The way we run delivery, or fit into yours.

We can run any of these ourselves, join the one you already have, or help you introduce it and make it routine.

Sprint1–2 wksPlanBuildReviewRetroBacklog → increment, every cycle

Scrum and sprints

Fixed-length sprints, a prioritized backlog, planning, review and a retrospective.
When it fits
Product work where scope changes as you learn.
What we do
Run the sprints as your scrum team, or join yours with engineers and a delivery lead.
To doDoingDoneWIPlimit 2

Kanban

A continuous flow of work, with limits on how much is in progress at once.
When it fits
Support, maintenance and operations, where work arrives unpredictably.
What we do
Set up the board and the policies, then run the flow, or take over the one you have.
Portfolio · shared prioritiesProgram · teams planning togetherTeam 1Team 2Team 3Team 4

Scaled Agile (SAFe)

Several teams planning and releasing together on a shared cadence.
When it fits
Large organizations with many teams on one product.
What we do
Join your release train, or introduce and run one.
RequireDesignBuildTestReleasesign-off before the next stage

Waterfall and stage gates

Sequential stages, each ending in a documented sign-off. This is the classic form of a formal software lifecycle (SDLC).
When it fits
Fixed scope, regulated work, or software that depends on hardware.
What we do
Plan the stages and gates, write the lifecycle down, and keep change controlled and visible.
our approach

However you run the work, we build with an agentic harness.

AI coding agents write the code inside a controlled loop. Specs go in, automated tests and evaluations decide what passes, and a person reviews before anything ships. All of our delivery now runs this way: the same quality gates, reached faster.

  • Specs before code. Agents work from what was agreed, not from guesses.
  • Tests and evaluations as the gate. Failures go back to the agents.
  • A person approves what ships. Nothing reaches production unreviewed.
YOUR PROCESSScrumKanbanSAFeWaterfall / stage gatesall of them run onOUR AGENTIC HARNESSSpecwhat to buildAgentswrite the codeTests & evalsthe gateHuman reviewbefore it shipsfailures go back to the agentsGuardrails · tooling · monitoring
Your process
ScrumKanbanSAFeWaterfall / stage gates
↓ all of them run on
Our agentic harness
Specwhat to build
↓
Agentswrite the code
↓
Tests & evalsthe gate
↓
Human reviewbefore it ships
Guardrails · tooling · monitoring
Failures go back to the agents.
Not sure which fits? Most teams use a mix. We pick the lightest process that keeps the work visible and the decisions fast.
Ways to work with us

Pick the format that fits.

From a single consultation to a dedicated team, the format follows what you need.

Consulting

Advisory work: second opinions, architecture and process guidance, answers to the hard questions, written down.

Good for: A decision you need to get right.

Work by the hour

Engineers and leads billed by the hour, with no minimum, for work that does not fit a fixed scope. Fixed-scope engagements start at $4,500.

Good for: Uncertain, small or variable work.

Dedicated team

A multi-role team, with engineers, QA and a delivery lead, that works only on your product, as an extension of yours. Three months minimum, then month to month with 30 days’ notice.

Good for: Ongoing product work with a clear mission.
FAQ

Questions about how we work.

Can you work inside our process, or do we have to adopt yours?
Either. We can join the process you already have, run delivery ourselves, or help you introduce a new one. We pick the lightest process that keeps the work visible.
What is the agentic harness?
AI coding agents write code inside a controlled loop. The harness is what keeps them on rails: written specs going in, automated tests and evaluations as the gate, and a person reviewing before anything ships.
Does the harness replace Scrum or SAFe?
No. Sprints, boards and release trains stay as they are. The harness changes how the work inside them is built, so the same process delivers faster without lowering the quality gates.
Can you provide a dedicated team?
Yes. A multi-role team on a clear mission, working month by month as an extension of yours. See the Dedicated Product Squad offer for how it is shaped.
Do you work by the hour?
Yes. Hourly work has no minimum. Fixed-scope engagements start at $4,500 for a two-to-six-week scope, and larger work is scoped custom.
Have you run SAFe?
Yes. We can join the release train you have or help you set one up.
What is the difference between discovery and validation?
Discovery decides how to approach the work. Validation decides whether there is enough proof to justify the next commitment.
What is the Proof Loop?
Five steps every engagement moves through: define the decision, map the assumptions, choose the cheapest credible proof, build or run the test, and decide what changes. The capability involved — research, software, GTM, AI, data — follows the proof needed rather than being fixed in advance.
What is the difference between signal and proof?
Weak signal is compliments, vague interest, broad market size, and passive survey responses. Useful signal is specific problem stories, active pull, repeated use cases, and buyer urgency. Strong proof is paid commitments, signed pilots, repeated usage, conversion, retention, operational adoption, or budget allocation.
Why is discovery paid, and what do you get from it?
Because it produces a practical Discovery Brief — recommended engagement type, scope, timeline, risks, proof needed, team shape, and a 30/60/90-day path — instead of an open-ended strategy deck. It turns a broad request like "build an MVP" or "help with GTM" into a defined scope. Sometimes the recommendation is to validate first, narrow the wedge, or not engage.
How do you decide what to build for a test?
Build the smallest thing that can create the right evidence. Sometimes that is a landing page, offer narrative, interview sequence, or concierge workflow; sometimes a real MVP, internal tool, AI workflow, or integration. The point is not to avoid building — it is to build when the artifact creates better evidence than conversation alone.
What happens if the evidence says stop?
Then the engagement has done its job. A useful outcome can be to scale, sequence, change, or stop, and a stopped initiative saves time, budget, and focus. Proof that says no is still proof: it prevents a commitment that would otherwise be discovered as wrong much later and much more expensively.

Tell us how you like to work.

Describe the team, the process and the problem. We reply with a clear next step — usually within 24 hours.