Can your team explain why a product initiative moved forward?

Research and product data often live in separate places. Proofrun brings the available context together around an initiative, so your team can see what led to the decision, what remains unclear and what could change it.

When the team revisits a priority, the reasoning should still be there.

  • A PM inherits a roadmap item.The context behind the priority has to be pieced together again.
  • Research and product data point to different explanations.The team needs to see what supports each one.
  • New information arrives after a priority is set.The team needs to know whether it changes the current reading.

THE DECISION GAP

Product teams have limited time to investigate every question.

The survey reports faster shipping, while many product teams say decision-making has not sped up.

  • 80% ship faster with AI
  • 69% say decision-making hasn’t sped up
  • 4% can trace every roadmap decision back to customer feedback or evidence

Follow a product question from signal to evidence.

See the explanations being investigated, the evidence connected to each one and the questions that still need an answer.

NEW DISCOVERY · INITIAL RESEARCHILLUSTRATIVE

Decision question

How should we respond to the activation drop?

What do you currently believe?FROM YOU

Users abandon onboarding because setup feels too complex.

Competing hypothesisADDED BY PROOFRUN

Many sign-ups never intended to activate.

See which evidence supports each explanation.

Each piece of evidence keeps its source and its place in the investigation.

  • SUPPORTED

    Setup friction drives the drop.

    H12 evidence · 2 support

  • CHALLENGED

    Low intent explains the drop.

    H21 evidence · 1 contradiction

  • STILL OPEN

    Technical friction or unclear steps?

    Critical gap · Primary validation

Review what the available evidence supports so far.

The Current Reading summarizes what the available evidence supports now. Sources, contradictions and gaps stay connected so the team can revisit the reasoning later.

Start a Discovery

CURRENT READINGV1 · CURRENT

Available evidence points more strongly to setup friction than to low intent.

  • SUPPORTED

    62% of drop-off happens in the setup steps.Google Analytics · Behavioral signal

  • CHALLENGED

    Returning users activate at a higher rate.Google Analytics · Behavioral signal

  • STILL OPEN

    Technical friction or unclear steps?Needs primary validation

Current evidence. Not a final product decision.

QUESTIONHow should we respond to the activation drop?

  • H1Signals supportSetup friction drives the drop.

    • EVIDENCE+ SupportsDrop-off concentrates during setup.
    • EVIDENCE+ SupportsSupport tickets mention setup confusion.
    • RESEARCH GAP? CriticalTechnical friction or unclear steps?
  • H2Signals challengeLow intent explains the drop.

    • EVIDENCE× ContradictsReturning users activate at a higher rate.

Keep the Discovery current as relevant evidence appears.

Keep Alive checks supported sources for new evidence. Quiet checks leave the reading unchanged; material evidence can create a new version. Deeper research waits for your approval.

A quiet check changes nothing. Deeper research waits for your approval. Keep Alive is included in every plan.

Start a Discovery

What would change your mind?

  1. V1

    Available evidence points more strongly to setup friction than to low intent.

  2. Mon

    No material change

  3. Tue

    No material change

  4. Wed

    New evidenceIntegration step completion ↓ 18% vs. the previous period.

  5. V2

    INTERPRETATION CHANGEDThe drop is concentrated at the integration step.

REAL RUN · PROOF #001

See a real Proofrun Discovery, including what it leaves open.

“The original thesis didn’t survive intact.”

hypotheses
3
research artifacts
18
evidence claims
10

INITIAL HYPOTHESISProduct teams have recurring discovery questions and may benefit from a system that autonomously researches, accumulates evidence and revisits what is already known.

WHERE IT LANDEDThe research shifted the center of gravity away from simply storing research. A stronger pattern emerged around how evidence is reconciled, trusted and reconstructed when a decision has to be made.

A real run about Proofrun’s own thesis. It shows the shape of the work. It is not a customer case, a result or market validation.

Start your own Discovery

Keep the hypotheses, sources and changes in one Discovery

Proofrun keeps the question, evidence, contradictions, gaps and version history together so the team can return to the investigation with its context.

GENERAL AI
  1. Question
  2. Answer
PROOFRUN
  1. Question
  2. Evidence
  3. Reading
  4. New evidence
  5. Reassessment

Proofrun keeps the state between those steps: hypotheses, sources, contradictions, gaps and every version of the reading.

Use public research, uploaded files, read-only Google Analytics and Notion

AVAILABLE NOW

  • Public webAvailable
  • Uploaded filesAvailablePDF · DOCX · PPTX · XLSX · CSV · MD · TXT
  • Google AnalyticsAvailable · Read only
  • NotionAvailable

PLANNED

Analytics
Knowledge
Customer signals
Product & delivery
CRM

Select the planned sources your team needs, then request access.

Start small. Scale when you need to.

Starter

$10/ month

For focused product research by an individual or small team.

Monthly Research Capacity

Choose Starter

ProRECOMMENDED

$20/ month

Early adopter offer$15 for the first month

For teams that use Discovery more frequently.

2x Starter’s monthly Research Capacity

Choose Pro

Enterprise

Custom

For teams that need more capacity, more connected sources or a setup built around their workflow.

Research Capacity sized to your team

See Proofrun for product teams

INCLUDED IN EVERY PLAN

Prices in US dollars, billed monthly. You choose your plan after creating your workspace. The early adopter offer is applied at checkout for eligible workspaces.

  • Public web research
  • Google Analytics (read only) and files
  • Current Reading, Evidence Map and version history
  • Keep Alive

Questions about getting started

What is Proofrun?

Proofrun is product discovery that keeps going after the first answer. Frame a question around a requirement, problem, opportunity or hypothesis. Proofrun investigates it across public web research and your own data, shows what the evidence supports, challenges and leaves open, and updates that Current Reading as new evidence arrives. Your team makes the product decisions.

Who is it for?

Product Managers, Product Designers, Product Leaders, Product Ops, founders and small product teams who need evidence they can trace when choosing priorities, responding to requirements, comparing approaches or deciding when to act.

What can I start a Discovery with?

A regulatory requirement, customer request, feature gap, analytics signal, opportunity, improvement or hypothesis can all raise questions worth investigating. Write the question your team needs to answer and, optionally, what you currently believe. Proofrun treats that belief as a hypothesis and investigates competing explanations.

Which sources can Proofrun use?

Public web research, files you upload and connected sources you authorize. Google Analytics is available now with read-only access, Notion is available too, and more connected sources are planned. Every piece of evidence keeps its source, and behavioral data is treated as showing what happened, not why it happened.

What is a Research Brief or Current Reading?

The Current Reading expresses what the Discovery's evidence supports, challenges or leaves open right now. A Research Brief is a readable view of that state, not a validation certificate or a final product decision.

Can Proofrun disagree with me?

Yes. Evidence can support, challenge or complicate a hypothesis. Mixed and inconclusive results remain visible.

What does Keep Alive do?

When you turn it on, Proofrun checks the Discovery every day for new evidence from public web research and connected Google Analytics. A quiet check changes nothing. When new evidence changes a hypothesis, a contradiction, an open gap or the next decision, Proofrun records a new version of the reading and shows what changed. Checks use your workspace’s Research Capacity, and deeper research never starts without your approval.

Does a Discovery end?

Individual research work has a boundary. The Discovery remains available until you pause or archive it, and it can incorporate new evidence or further research when appropriate.

How is this different from ChatGPT, Claude or Deep Research?

Those tools are great at answering a question in the moment. Proofrun keeps the Discovery itself: the hypotheses, the sources behind each piece of evidence, contradictions, open gaps and a Current Reading that changes as new evidence arrives. It doesn’t start over every time you ask.

What happens when Proofrun needs a decision from me?

It stops at the relevant guardrail and shows what requires your judgment or authorization. Proofrun does not make the product decision for you.

What is Initial Research?

It is the first bounded work inside a Discovery. It creates a useful first reading of hypotheses, evidence, contradictions and gaps. It is not a separate product tier.

Start with a product question

Bring a question your team is already discussing. See the research, evidence and open questions in one Discovery.