Patent

What the company appears to be: The description states that Patent is a tool for "patent IP Research". It was submitted as a project to the OpenAI 2026 hackathon on Devpost, and was built using AI tools like Claude, Cursor, Gemini, GPT, and VSCode. The author is a single individual, 민수 김.

What changed: No evidence of prior version or evolution is provided. This appears to be a new project submitted for a hackathon.

The single most important open question: What is the actual functionality of Patent? The description provides no clarity on whether it's a search tool, analysis platform, visualization tool, or something else — all are possible interpretations of "patent IP Research".

Commercial due-diligence read: Based on self-reported evidence only, there is insufficient information to assess commercial viability, traction, or business model. The project is described as a hackathon submission with no indication of product-market fit, revenue, or customer adoption.

The description states that Patent is a tool for "patent IP Research". It was built for the OpenAI 2026 hackathon and uses AI tools such as Claude, Cursor, Gemini, GPT, and VSCode. No further details are provided about what the product does or how it functions.

Evidence: The description states that Patent is a tool for "patent IP Research" and was built using AI tools like Claude, Cursor, Gemini, GPT, and VSCode.

Inference: It is possible that Patent is a search or analysis tool for patent data, but this cannot be confirmed from the provided information.

The description states only the tagline: "patent IP Research". There is no evidence of any positioning statement, messaging, or claim evolution. No indication of how the product differentiates itself or what value it claims to deliver beyond its name.

Evidence: The description states only the tagline "patent IP Research".

Inference: The lack of further detail suggests that this is a very early-stage idea or prototype, possibly without a defined market positioning.

The description does not state who the target customer is or what the ideal customer profile (ICP) might be. No information is provided about whether the tool is for patent attorneys, inventors, corporations, researchers, or others.

Evidence: Not evidenced.

Inference: Without further details, it's impossible to determine the intended user base or ICP.

There is no evidence in the description of a business model or pricing structure. No mention of monetization strategy, subscription tiers, usage-based pricing, or any commercial approach.

Evidence: Not evidenced.

Inference: The project appears to be a hackathon submission and not yet developed for commercial use.

The description states that the project was built using AI tools such as Claude, Cursor, Gemini, GPT, and VSCode. It was submitted to the OpenAI 2026 hackathon on Devpost.

Evidence: The description states that Patent was built with Claude, Cursor, Gemini, GPT, and VSCode, and was submitted to the OpenAI 2026 hackathon.

Inference: This suggests a rapid development process using AI-assisted tools, but does not indicate technical maturity or scalability.

There is no evidence of traction or maturity. The project is described as a single-person hackathon submission with no indication of user adoption, revenue, or product development beyond the initial prototype.

Evidence: Not evidenced.

Inference: The lack of any mention of users, customers, or product development milestones suggests that Patent is at an early stage and has not yet demonstrated traction.

The description does not provide any information about the competitive landscape. No mention of existing tools in the patent research space or how Patent might compare to them.

Evidence: Not evidenced.

Inference: Without knowing what tools already exist for patent IP research, it's impossible to assess where Patent might fit in the market.

• Lack of clarity on functionality: The description does not explain what Patent actually does.
• No evidence of traction or adoption: It is a hackathon submission with no indication of real-world usage.
• Single-person team: A team size of one may limit development capacity and scalability.
• Unverified claims: All information is self-reported, with no independent verification.

Evidence: Not evidenced.

Inference: These are common risks for early-stage hackathon projects, but cannot be confirmed without further details.

1. What specific problem does Patent solve in patent IP research?
2. How does Patent differ from existing tools in the market?
3. What is the intended user experience or workflow?
4. Is there a plan for product development beyond this prototype?
5. Have you identified any potential customers or use cases yet?