Archive position — measured, not model output
1 like on Devpost
505 of the 7,850 archived projects have more likes, and 1,758 share exactly 1 — so this project's #1,792 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,587 | 71.2% |
| 1 | 1,758 | 22.4% |
| 2 | 284 | 3.6% |
| 3–4 | 132 | 1.7% |
| 5–9 | 75 | 1.0% |
| 10+ | 14 | 0.2% |
User Stories BotA demo video on every pull request
Get a demo video on every new feature
GitHub App that watches your pull requests and records a narrated, captioned demo.
Save time on demo prep and make informed decisions faster with a video walkthrough of every new feature.
Executive Summary
What the company appears to be: Relay is a self-reported tool that processes meeting transcripts using GPT-5.6 to extract structured action items, decisions, and open questions. It allows users to approve these items before automatically filing them into Slack, Linear, and Notion.
What changed: The project was built as part of the OpenAI 2026 hackathon. It evolved from an initial approach that used LLM agents for all steps to a more reliable system using deterministic API calls after discovering reliability issues with LLM-based filing.
Single most important open question: Does Relay have any real-world usage or adoption beyond its hackathon prototype? The description provides no evidence of revenue, customers, or traction.
What The Product Actually Is
The description states that Relay:
- Processes meeting transcripts
- Uses GPT-5.6 to extract decisions and action items (owner, due date, priority)
- Grounds each extracted item to the exact transcript line it came from
- Requires user approval before filing
- Posts a recap to Slack
- Creates one Linear issue per action item
- Writes a full meeting-notes page in Notion
The product is described as a tool that transforms unstructured meeting data into structured, actionable records across multiple platforms.
Positioning & Claim Evolution
The description states:
- The tool is positioned as an automated "Meeting-to-Action Agent"
- It claims to use GPT-5.6 for extraction
- It emphasizes that nothing is filed until the user reviews and approves it
- It describes a shift from agent-based filing to deterministic API calls due to reliability issues
The positioning appears to be evolving from a generic meeting automation tool to one focused on structured data extraction and reliable filing.
Target Customer & ICP
Not evidenced. The description does not state who the target customer is or what their specific needs are beyond general meeting follow-through problems.
Business Model & Pricing Evidence
Not evidenced. The description provides no information about pricing, revenue streams, or business model.
Technical & Delivery Signals
The description states:
- Built with FastAPI + Python backend
- Single HTML frontend file (no build step)
- Uses GPT-5.6 for structured JSON extraction via JSON schema
- Filing to Slack/Linear/Notion uses direct API calls, not LLM in the loop
- Model provider is swappable: OpenAI directly or OpenRouter
- The team tested three different models for filing step, all failed differently
- Fixed reliability issues by switching from agent-based to deterministic API calls
Traction & Maturity Signals
Not evidenced. There is no evidence of revenue, customers, usage metrics, or any traction beyond the hackathon submission.
Competitive Context
Not evidenced. The description does not mention competitors or market context.
Open Questions & Risks
- The tool was built for a hackathon and has no demonstrated traction
- Reliability issues were discovered during development (three models failed differently)
- The team size is listed as 1 person, suggesting limited resources for scaling
- No evidence of revenue, customers, or adoption beyond the prototype
- The project description lacks any mention of real-world usage or testing
Questions the description leaves open
- What specific meeting problems did you observe that led to building this?
- Have you tested this with actual teams and users beyond your own?
- How do you plan to monetize this tool if you intend to commercialize it?
- What is the timeline for moving from prototype to a production-ready product?
- Are there any existing tools in this space that you're aware of?
Overall Assessment
Not evidenced. The description provides no information about valuation, funding rounds, or investment readiness. This appears to be a hackathon project with no demonstrated commercial traction or business model.
User Stories BotA demo video on every pull request
Get a demo video on every new feature
GitHub App that watches your pull requests and records a narrated, captioned demo.
Save time on demo prep and make informed decisions faster with a video walkthrough of every new feature.
Source
Submitted to the OpenAI 2026 hackathon on Devpost. Project home on Devpost. Back to the full gallery on Devpost.
This competitive analysis was produced by
top-founders.com (opens in a new tab)
Generated by a language model from this project's public Devpost page — its tagline, the author's own write-up and any built-with tags listed there — as captured in August 2026. Short quotations are the author's words. It is an opinion on the idea as a business, not on the people behind it, and it reflects the description as published then. If the project has moved on, request a correction below. The analysis is not independent research and contains no verified traction, revenue or customer data.
An independent guide by KFG International LLC — not affiliated with, endorsed by, or connected to Devpost or OpenAI.