Evidence Workbench

Note: This analysis is based solely on the self-reported project description provided by the caller — no external verification or historical data available. All claims are attributed to the author’s own account and should be treated as unverified.

The description states that Evidence Workbench is a visual workspace for organizing evidence from multiple sources into defensible cases. It supports:

• Importing material from email servers, local drives, cloud storage, photos, documents
• Preserving untouched originals and their provenance
• Visual exploration through:
  • Balloon-style canvas
  • Timelines
  • Flowcharts
  • Relationship maps
  • Claim maps
  • Coverage views
  • Location views

It also includes optional AI assistance, which is described as under human control, helping with search, finding related material, tracing entities, suggesting relationships, highlighting contradictions or gaps, and prioritizing content.

The system uses a local-first model where source items are separate but connected across views. It supports exporting submission-ready packages containing evidence, chronology, claim maps, manifests, and integrity records.

Inference: The tool appears to be built for investigative or legal use cases involving complex, multi-source data.

The author positions Evidence Workbench as a private, visual workspace that helps ordinary people think like investigators without requiring specialist software or training. It is framed as solving the problem of scattered, disconnected evidence.

Key claims include:

• Users can bring together material from various sources while preserving originals.
• Visual tools help connect claims and events.
• AI acts as an assistant, not an authority.
• The tool supports export for tribunals, courts, audits, etc.
• It is designed to be accessible to individuals but useful to professionals.

Inference: The positioning suggests a niche market focused on personal or small-team evidence management, with potential crossover into legal, journalistic, and research domains.

The description states that Evidence Workbench is intended for:

• Individuals handling disputes (e.g., tenancy, insurance claims)
• Advocates, investigators, researchers
• Legal professionals, organisations
• Journalists, auditors, incident reviewers, historians

It is described as useful to both ordinary users and specialist practitioners, aiming to make complex evidence accessible.

Inference: The ICP likely includes people who need to manage multi-source, multi-format evidence in adversarial or investigative contexts. However, no specific customer segments or personas are defined.

No explicit business model or pricing information is provided in the description.

The author mentions that the tool supports exporting submission-ready packages, suggesting a possible value proposition around presentation and compliance.

Not evidenced: No mention of monetization strategy, subscription tiers, licensing models, or revenue streams.

The system is built using:

• Frontend: React, TypeScript, HTML5, CSS3
• Backend/Infrastructure: Cloudflare Workers, IndexedDB, Web Crypto API, Web Speech API
• AI Integration: OpenAI API, GPT-5.6, OpenAI Codex
• Other Tools: GitHub, JSZip, Vite, Vinext

It uses a local-first architecture, meaning data remains on the user’s device unless explicitly shared.

Inference: The tech stack suggests a modern web-based application with strong focus on privacy and offline functionality. AI integration is optional and modular.

The project was submitted to the OpenAI 2026 hackathon, indicating it is in early development or prototype stage.

There is no evidence of:

• Revenue
• Customers
• Paid users
• Product-market fit
• Market traction
• Prior funding or investor interest

Not evidenced: No signs of product adoption, usage metrics, or business growth beyond the author’s own account.

The description does not reference direct competitors. However, it implies a space that includes:

• Legal document management systems
• Evidence-gathering tools for investigators or journalists
• Case management platforms (e.g., for law firms)
• Visual collaboration tools (e.g., Notion, Miro)

It distinguishes itself through its local-first approach, preservation of original evidence, and optional AI integration.

Inference: The tool may compete with general-purpose case management or visual planning tools, but no competitive landscape is described.

• No commercial traction or revenue: The project appears to be a hackathon submission with no evidence of real-world usage.
• Single founder: Limited team size raises questions about scalability and execution capability.
• Unproven AI integration: While AI is mentioned, there’s no indication of how it performs in practice or whether it adds value.
• Unclear monetization path: No business model or pricing strategy described.
• Highly specialized use case: The target audience may be narrow, limiting potential market size.

Inference: Without traction, funding, or clear commercial intent, this project is likely pre-product-market-fit and not yet ready for investment or partnership consideration.

1. What specific problem are you solving, and how do you know users have that problem?
2. Have you tested the tool with real users? If so, what feedback did they give?
3. How does your local-first architecture protect user data in practice?
4. Is there any plan to monetize or scale this beyond a prototype?
5. What are the key technical challenges remaining before launch?
6. Are there any existing tools in this space that you’re aware of?