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 #7,680 place in the like-ranked listing is a tie-break inside that group, not a ranking.
Projects (log scale)
Likes on Devpost. ▲ marks this project's group.
Show the figures
| Likes | Projects | Share of archive |
|---|---|---|
| 0 | 5,592 | 71.2% |
| 1 | 1,758 | 22.4% |
| 2 | 285 | 3.6% |
| 3–4 | 132 | 1.7% |
| 5–9 | 75 | 1.0% |
| 10+ | 14 | 0.2% |
Executive Summary
What the company appears to be
The description states that “What’s To Do? — The Procedure Mill” is a tool designed to process messy emails, documents, receipts and forms into a clear, source-linked chronology. It claims to explain jargon, spot gaps, and show what needs doing next. The author describes it as a product built for executive or knowledge management contexts.
What changed
This project was submitted to the OpenAI 2026 hackathon, suggesting an early-stage development effort, likely prototyping or proof-of-concept. No evidence of prior traction, revenue, or customer adoption is provided.
The single most important open question
Is this a tool intended for personal productivity or enterprise knowledge management? The description does not clarify whether it targets individuals or organizations, nor does it indicate how it would be monetized or scaled.
What The Product Actually Is
The description states that the product “turns messy emails, documents, receipts and forms into a clear, source-linked chronology—explaining jargon, spotting gaps and showing what needs doing next.” It is built using technologies such as Flask, Python, GPT-5, JavaScript, HTML, CSS, SQLite, and OpenAI APIs. The author declares it to be a productivity tool with language processing and automation capabilities.
Evidence
- Tagline: “What’s To Do? turns messy emails, documents, receipts and forms into a clear, source-linked chronology—explaining jargon, spotting gaps and showing what needs doing next.”
- Technology stack: accessibility, analysis, artificial, automation, css, document, executive, flask, function, gpt-5, html, information, intelligence, javascript, knowledge, language, management, natural, openai, processing, productivity, python, retrieval, sqlite, summarization
Inference The product appears to be a document and data-processing tool that uses AI to extract meaning from unstructured inputs and generate structured outputs. It is not clear if it is a SaaS offering or an internal tool.
Positioning & Claim Evolution
The author states that the product “turns messy emails, documents, receipts and forms into a clear, source-linked chronology—explaining jargon, spotting gaps and showing what needs doing next.” This positioning suggests a focus on clarity, organization, and task generation from disorganized inputs.
Evidence
- Tagline: “What’s To Do? turns messy emails, documents, receipts and forms into a clear, source-linked chronology—explaining jargon, spotting gaps and showing what needs doing next.”
Inference The product positions itself as an assistant for managing complex workflows or information overload. It is not evident whether it targets individuals or teams, nor does it describe how it differentiates from existing tools like Notion, Airtable, or email automation platforms.
Target Customer & ICP
The description states that the tool is designed to process “messy emails, documents, receipts and forms” and generate a clear chronology. The author declares its use of “executive,” “management,” and “knowledge” in its tech stack, suggesting it may target executives or knowledge workers.
Evidence
- Tagline: “What’s To Do? turns messy emails, documents, receipts and forms into a clear, source-linked chronology—explaining jargon, spotting gaps and showing what needs doing next.”
- Technology tags include: executive, management, knowledge
Inference It is possible that the target customer is an executive or knowledge worker who handles large volumes of unstructured data. However, no explicit ICP (Ideal Customer Profile) is defined.
Business Model & Pricing Evidence
There is no evidence in the description regarding pricing, monetization, or business model. The author does not state whether this is a freemium, subscription, or one-time purchase product.
Evidence
- No mention of pricing, revenue model, or monetization strategy
Inference The project is in an early stage and likely not yet monetized. If it were to be commercialized, the business model would need to be determined based on its use case and target audience.
Technical & Delivery Signals
The author states that the tool is built with Flask, Python, GPT-5, JavaScript, HTML, CSS, SQLite, and OpenAI APIs. It is described as a productivity tool with language processing and automation capabilities.
Evidence
- Built with: Flask, Python, GPT-5, JavaScript, HTML, CSS, SQLite, OpenAI APIs
- Technology tags include: artificial, automation, language, processing, intelligence
Inference The tool appears to be a lightweight, AI-powered web application. It is not clear if it is a standalone product or integrated into other systems.
Traction & Maturity Signals
There is no evidence of traction, customers, revenue, or adoption. The project was submitted to a hackathon and lacks any indication of prior use or market validation.
Evidence
- Submitted to OpenAI 2026 hackathon
- No mention of users, customers, or revenue
Inference This is an early-stage idea or prototype, not yet validated in the market. There are no signs of product-market fit or user engagement.
Competitive Context
The description does not provide any information about competitors or how this tool compares to existing solutions such as Notion, Airtable, Slack, or document automation tools like DocuSign or PandaDoc.
Evidence
- No mention of competitors or market positioning
Inference It is unclear whether the product competes with existing tools or fills a niche. The lack of competitive analysis makes it difficult to assess its potential value proposition.
Key Risks & Red Flags
- No evidence of traction or revenue: The project is in an early stage, submitted to a hackathon.
- Unclear target audience and use case: No indication of whether it targets individuals or organizations.
- No pricing or monetization strategy: No business model is described.
- Unproven AI integration: While GPT-5 is mentioned, there is no evidence of how it is used or what value it adds.
- Single-person team: The project is built by one person, which may limit scalability and development speed.
Diligence Questions To Ask The Founders
- What specific problem are you solving, and for whom?
- How does your product differ from existing tools like Notion or Airtable?
- What is the intended business model and monetization strategy?
- How do you plan to scale this beyond a hackathon prototype?
- What are the key technical challenges in building and deploying this tool?
Investment/Partnership Verdict
Not evidenced.
The project is described as a hackathon submission with no evidence of traction, revenue, or customer validation. It is unclear whether it represents a viable business opportunity or a proof-of-concept. The lack of information on target customers, pricing, and scalability makes it difficult to assess its potential for investment or partnership.
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.