ClearOK

ClearOK is a self-reported tool for turning casual conversations into shared records, built by one person (Daniel Lee) over a hackathon period. The product allows users to paste messages, upload screenshots, or combine both, then generates a draft record that both parties can review and sign. It was launched publicly on July 15 with live Stripe payments and is built using Cloudflare Workers, TypeScript, and AI models including GPT-5.6 and GPT-4o mini.

The author states that ClearOK is designed for everyday situations such as confirming plans or recording agreements between friends, freelancers, or family members — not for legal contracts. It does not present these records as legally binding or provide legal advice.

Key commercial due-diligence questions include: What is the actual adoption rate? How many users are signing up and using the service? Is there any evidence of customer feedback or retention? Does the product have a sustainable business model beyond initial launch?

The most important open question is whether ClearOK has traction, revenue, or user engagement beyond its initial public launch.

• The description states that ClearOK turns ordinary conversations into concise shared records.
• Users can paste messages, summarize a conversation, attach up to four screenshots, or combine text and screenshots.
• ClearOK reads the provided context and creates a draft identifying people involved and commitments reached.
• The creator reviews and edits the draft before sending it.
• The recipient signs in and can agree or reject.
• Both parties retain the same shared record.
• It supports:
  • Text-only input
  • Screenshot-only input
  • Combined text and screenshots
  • Mobile attachment and sharing flows
  • User review before sending
  • Two-sided response and shared record retention

• The description states that ClearOK was created for "the space between a casual message and a formal contract."
• It aims to reduce potential disputes by providing a clear record of agreement.
• The author claims it helps people remember exactly what both sides understood after an agreement.
• It is positioned as a tool for everyday situations such as confirming plans, clarifying changes, or recording approvals — not for legal contracts.
• The product does not present records as contracts or legal advice.
• The author notes that the biggest win was launching a product, even if its long-term adoption is unknown.

• The description states that ClearOK is designed for everyday situations such as:
  • Confirming who is bringing something
  • Clarifying a small change in plans
  • Recording a freelancer or client approval
  • Confirming permission or responsibility
  • Preserving a decision that would otherwise disappear inside a chat
  • Or simply ridiculous promises made among friends

• The author does not specify a defined ICP beyond general use cases.
• No evidence of segmentation by industry, geography, or user type is provided.

• The description states that ClearOK launched publicly on July 15 with live Stripe payments.
• It is described as a functioning paid application.
• No pricing tiers, plans, or revenue models are specified in the description.
• There is no evidence of customer acquisition costs, monetization strategy, or recurring revenue streams.

• The product is built using TypeScript on Cloudflare Workers with a D1 database.
• Development began on June 27 and launched publicly on July 15.
• It uses GPT-5.6 Work mode for development and refinement.
• The screenshot workflow uses GPT-5 mini, while text generation continues to use GPT-4o mini.
• It supports multimodal input (text + screenshots).
• Mobile-friendly sharing experience is claimed.
• OAuth integration with Google is mentioned.
• Web push notifications are included in the tech stack.

• The description states that ClearOK became a publicly launched product during Build Week.
• It was described as:
  • A functioning paid application with live Stripe purchases
  • A complete two-person workflow
  • A production Cloudflare deployment
  • A multimodal application supporting text, screenshots, or both
  • A mobile-friendly sharing experience

• No evidence of user growth, retention, or engagement metrics is provided.
• There is no mention of customer feedback, usage analytics, or product iteration history.

• The description does not provide any information about competitors or market positioning.
• No mention of existing tools that address similar needs (e.g., shared agreement platforms, chat summarization tools).
• No evidence of competitive differentiation or market analysis is present.

• The product was built by a single individual with no prior software engineering experience.
• The author states they are not a software engineer and have no product launch experience.
• There is no evidence of customer feedback, retention, or traction beyond initial launch.
• No pricing model, monetization strategy, or revenue data is provided.
• The lack of competitive analysis raises questions about market demand and positioning.
• The product’s long-term viability depends on user adoption, which is not evidenced.

1. What is the actual adoption rate since launch?
2. How many users are signing up and using the service?
3. Is there any evidence of customer feedback or retention?
4. What is the monetization strategy beyond initial launch?
5. Are there any plans to scale beyond a single developer?
6. How does ClearOK differentiate from existing tools in this space?
7. What are the key metrics being tracked post-launch?