BEFORE · V1
Public signals point to setup friction. Product behavior hasn’t been checked yet.
Public signals · not business validation
Can every squad explain why a product priority moved forward?
Research, customer feedback and product data often sit in different places. Proofrun brings that context together so each squad can see what informed the priority, what remains uncertain and what new evidence could lead the team to revisit it.
Prefer webmail?
What the next squad needs to know
- Why did this priority move forward?
- What evidence informed the decision?
- What remains uncertain or challenges the current reading?
- What new evidence could lead the team to revisit it?
- Can another squad understand why it advanced without relying on the original discussion?
DECISION QUESTION
Should we expand onboarding automation?
HYPOTHESES
- H1Manual setup delays first value+SUPPORTED
- H2Automation alone fixes the drop-off×CHALLENGED
- H3Larger accounts need guided setup?STILL OPEN
EVIDENCE
- claims
- 12
- sources
- 4
- contradictions
- 2
- critical gap
- 1
CURRENT READINGV3 · UPDATED
Automation helps smaller teams. Larger accounts still point to a guided path.
HUMAN JUDGMENT
Decision requiredExpand automation for every account, or only for smaller teams?
Proofrun stops here. Your team decides.
THE ORGANIZATIONAL SIGNAL
What product professionals report about execution and decisions
A survey of 1,000 product professionals points to faster execution while decision-making remains a challenge.
EXECUTION
- 80% ship faster with AI
DECISIONS
- 69% say decision-making hasn’t sped up
- 4% can trace every roadmap decision back to customer feedback or evidence
Source: Atlassian, The State of Product 2027 (opens in a new tab) Survey of 1,000 product professionals.
Keep the context behind important priorities visible across squads.
Teams can keep their own workshops, interviews and research practices. Proofrun keeps the question, evidence, open questions and changes together so the next squad can understand why the priority moved forward.
Context spread across teams
- SQUAD A
- Workshop notes
- Interview recordings
- Chat threads
- SQUAD B
- Whiteboard
- Analytics export
- Spreadsheet
- SQUAD C
- AI chat
- Tickets
- Customer calls
- Every team hands over a different artifact
- Sources disappear
- Contradictions disappear
- The rationale for the decision disappears
One record to review
- QUESTIONWhat the decision depends on
- HYPOTHESESWhat the team believes, and the alternatives
- EVIDENCEWhat the sources show, with provenance
- CONTRADICTIONSWhat doesn’t fit, kept visible
- OPEN GAPSWhat is still unknown
- CURRENT READINGWhat the evidence supports now
- HUMAN JUDGMENTWhere a person has to decide
- VERSION HISTORYHow the reading changed, and why
TRACEABLE DECISION CONTEXT
See the evidence behind each priority.
Review each source, its role and its limits. Version history shows what changed and when.
SELECTED · H1 · Signals support
Setup feels too complex.
Two signals from different sources support this explanation. One critical gap remains open.
RECORDED RELATIONSHIPS
- Investigated byQUESTION · What is actually causing the activation drop?
- Supported byEVIDENCE · Drop-off concentrates during setup.
- Supported byEVIDENCE · Support tickets mention setup confusion.
- Critical gapRESEARCH GAP · Technical friction or unclear steps?
RELATION KEY
- +Supports · Evidence increases support for the hypothesis.
- ×Contradicts · Evidence challenges this hypothesis.
- GAPCritical unresolved research question
Only links recorded by the research are shown.
Every piece of evidence keeps its source, its kind and its limits.
WHAT CHANGED OVER TIME
BRIEF HISTORY
Research state over time
WHAT CHANGED · V1 → V2
- 2 new evidence
- 1 hypothesis challenged
- 1 gap resolved
- Emerging interpretation changed
Triggered by bounded work
NOW · V2
Available evidence points more strongly to setup friction than to low intent.
Evidence-backed reading
3 product hypotheses · 1 critical gap
Proofrun pauses when a strategic choice, deeper research or new permission needs your team.
01 · INVESTIGATES
Investigates the question
Proofrun searches for and organizes evidence around the question, considering competing explanations, contradictions and gaps. Each research task has a defined scope and uses your workspace’s Research Capacity.
02 · STOPS
Pauses for team decisions
Strategic choices, deeper research and new permissions return to your team before work continues.
03 · KEEPS
Keeps the work reviewable
The Discovery keeps its evidence, sources, hypotheses, contradictions, current reading and changes available to review.
NEEDS YOUR DECISIONILLUSTRATIVE
Keep enterprise accounts in scope, or narrow this Discovery to self-serve teams?
No option is preselected. Research is waiting until this decision is resolved.
KEEP ALIVE
What new evidence could make your team revisit a priority?
Keep Alive checks supported sources for new evidence. Quiet checks leave the reading unchanged. Material evidence can create a new version, and deeper research still requires authorization.
- A quiet check changes nothing.
- Material new evidence creates a new version of the reading, with what changed.
- Deeper research still waits for your authorization.
- Every earlier version stays in the history.
Keep Alive checks public web research and connected Google Analytics, and uses your workspace’s Research Capacity.
CONTINUOUS DISCOVERY
Keep Alive
On
Checks daily for new evidence. New research never starts without your approval.
WATCHING
- Public web
- Google Analytics
- MonNo material change
- TueNo material change
- WedNo material change
- ThuNew evidence · Brief v3
- FriNext check
NEW EVIDENCE · BEHAVIORAL SIGNAL
Google Analytics
Integration step completion ↓ 18% vs. the previous period. Other setup steps are stable.
CURRENT READING · V3
The drop is concentrated at the integration step.
What changed since v2: +1 evidence · 1 hypothesis revised · Current interpretation changed
Triggered by monitoring check
NEXT STEPS · PROOFRUN CAN CONTINUE
Check integration errors
Addresses · Technical friction or unclear steps?
Could change · Whether the fix is technical or a design change.
Deeper research waits for your approval.
CONNECTED SOURCES
Use the sources available to your team
Public web research, uploaded files and read-only Google Analytics are available today. Notion is available too. Other sources remain labeled as planned until they launch.
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.
What each role needs to see
PRODUCT LEADERS
See why priorities advanced, where uncertainty remains and what could lead the team to revisit them.
PRODUCT OPS
Make the context behind important work easier to review across squads, without requiring one Discovery ritual.
PMs & PRODUCT DESIGNERS
Keep hypotheses, sources and contradictions together as the question develops.
ENGINEERING
Understand the problem, assumptions and open questions behind work entering the roadmap.
REAL RUN · PROOF #001
We asked Proofrun to investigate its own thesis.
“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, not a customer result.
Bring a real product case
Prefer webmail?
FAQ
Questions Product leaders ask
Does Proofrun replace Product Managers or Product Ops?
No. Proofrun does investigation work and keeps its evidence structured. Product Managers, Product Ops and leaders still frame the questions, interpret the context and make the decisions.
Does every team need to follow the same Discovery process?
No. Teams can keep their own workshops, interviews and research habits. Proofrun makes the same things visible around each decision: the question, hypotheses, evidence and its sources, contradictions, open gaps, the Current Reading and what changed.
Does Proofrun make the product decision?
No. It organizes the investigation and shows what the evidence supports, challenges and leaves open. When the work reaches a strategic fork, or needs new substantial research or a new permission, Proofrun stops and asks your team.
Can teams connect their existing data?
Today Proofrun works with public web research, uploaded files (PDF, Word, PowerPoint, Excel, CSV, Markdown and text), Google Analytics with read-only access, and Notion. Other sources, such as delivery tools and customer conversations, remain planned until they launch. You can tell us which ones your team needs.
Is this only for large companies?
No. It fits product organizations that need shared decision context, from a few squads to many teams. Smaller teams can also start on their own with the Starter or Pro plan.
How is this different from ChatGPT, Claude or Deep Research?
Those tools answer a question in the moment. Proofrun keeps a durable Discovery: hypotheses, evidence with its sources, contradictions, open gaps and a versioned Current Reading that Keep Alive can reassess as the evidence changes.
Bring one priority your team is working through.
We can show how Proofrun keeps its evidence, open questions and changes available as work moves between squads.
Prefer webmail?