OpenAI 2026 hackathon

ClaimDone

Turn 1 - 3 accident photos and a short description into a reviewed claim, then watch Computer Use submit your claim in an insurer portal.

Solo project by Janik Dotzel · 0 likes · 0 comments

Archive position — measured, not model output

0 likes on Devpost

2,264 of the 7,856 archived projects have more likes, and 5,592 share exactly 0 — so this project's #3,272 place in the like-ranked listing is a tie-break inside that group, not a ranking.

Projects (log scale)

1
10
100
1k
10k
05,592
11,758
2285
3–4132
5–975
10+14

Likes on Devpost. ▲ marks this project's group.

Show the figures
LikesProjectsShare of archive
05,59271.2%
11,75822.4%
22853.6%
3–41321.7%
5–9751.0%
10+140.2%
Devpost like counts for all 7,856 archived projects, captured when this archive was built.

Executive Summary

What the company appears to be

ClaimDone is a self-reported AI-powered tool that claims to automate insurance claim creation by using accident photos, text or voice descriptions, and simulated insurer portal navigation. It is described as a single-developer project built with AI agents (GPT-5.6, Codex, Computer Use) and frontend/backend technologies like Next.js and React.

What changed

The author describes building this tool in response to the friction of filing insurance claims after accidents. The product is positioned as simplifying claim submission through automation.

Single most important open question

Is there any evidence that ClaimDone has been used by real customers or integrated into actual insurer systems? The description provides no traction, revenue, or customer data — only self-reported development and conceptual claims.

Back to contents

What The Product Actually Is

The description states:

  • ClaimDone is a tool that takes 1–3 accident photos and a short text or voice description.
  • It uses AI (GPT-5.6, gpt-4o-mini-transcribe, Computer Use) to analyze the inputs and generate a claim.
  • The system then simulates navigating an insurer portal and filling in approved claim values using “Computer Use.”
  • The author claims to have used Codex for development, including planning, implementation, testing, and repository setup.

Inference The product appears to be a proof-of-concept or prototype built with AI agents. It is not evidenced to be live, deployed, or integrated into any real-world system.

Back to contents

Positioning & Claim Evolution

The description states:

  • The tool aims to simplify insurance claims by reducing the need for users to remember details and translate explanations into forms.
  • It positions itself as making the first step of claim filing feel “as simple as sharing a few photos and explaining what happened.”
  • The author emphasizes that it uses AI agents to automate analysis and form filling.

Inference The positioning is centered on ease-of-use for accident victims, but there is no evidence of how this differs from existing tools or whether the product has evolved beyond a prototype.

Back to contents

Target Customer & ICP

The description states:

  • The target is people who have had accidents and need to file insurance claims.
  • It is designed to be simple for users to input photos, text, or voice, and receive an automated claim.

Inference No specific customer segments or personas are defined. The ICP is implied but not evidenced.

Back to contents

Business Model & Pricing Evidence

The description states:

  • No pricing model or monetization strategy is described.
  • The project is presented as a hackathon submission, not a commercial product.

Inference There is no evidence of a business model or pricing structure. The tool appears to be conceptual and unproven in a commercial context.

Back to contents

Technical & Delivery Signals

The description states:

  • Built with Codex, GPT-5.6, gpt-4o-mini-transcribe, gpt-5.4-mini Computer Use, Next.js, React, TypeScript, Playwright, and OpenAI APIs.
  • The author used a structured development approach involving milestones and checkpoints to guide AI agents.
  • The system includes simulated insurer portal navigation and form filling.

Inference The technical stack is described as advanced but not validated in production. The use of AI agents for development suggests experimentation rather than a scalable or tested product.

Back to contents

Traction & Maturity Signals

The description states:

  • The project was submitted to the OpenAI 2026 hackathon.
  • It is described as a single-developer effort with no external validation or user feedback.
  • No revenue, customer adoption, or usage metrics are provided.

Inference There is no evidence of traction, adoption, or product maturity beyond a prototype. The project is not evidenced to be in use by anyone.

Back to contents

Competitive Context

The description states:

  • No mention of competitors or existing solutions in the insurance claim automation space.
  • The author does not reference similar tools or platforms.

Inference No competitive analysis is provided, and there is no evidence of awareness of the market landscape.

Back to contents

Key Risks & Red Flags

  • Unproven product: The tool is described as a hackathon submission with no real-world usage.
  • No commercial viability: No pricing, monetization, or business model is evident.
  • AI agent dependency: Reliance on AI agents for development and execution raises questions about scalability and control.
  • Lack of validation: No evidence of customer feedback, testing, or integration with real insurers.

Back to contents

Diligence Questions To Ask The Founders

  1. Has ClaimDone been tested with actual users or integrated into any insurer systems?
  2. What is the plan for monetization or commercial deployment?
  3. How does the system handle edge cases or incomplete data inputs?
  4. Are there any legal or compliance considerations around automating claim submissions?
  5. What are the technical limitations of the current AI agent-based approach?

Back to contents

Investment/Partnership Verdict

The description states:

  • This is a self-reported hackathon project with no evidence of traction, revenue, or customer adoption.
  • It is not demonstrated to be a viable product or business.

Inference There is no basis for investment or partnership at this stage. The project is unproven and lacks commercial viability indicators. It is not evidenced to be more than a prototype.

Back to contents

Source

Submitted to the OpenAI 2026 hackathon on Devpost. Project home on DevPost.

The analysis above was generated by a language model from the project's own one-line description. It is not independent research and contains no verified traction, revenue or customer data.