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,687 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
WhosNext Event Command Center is a self-reported event-operations tool built for organizers managing multiple events. The author states it aims to reduce cognitive load by summarizing next six events, calculating an explainable readiness score, and prioritizing actions based on consequence and deadline.
What changed
The project was submitted as part of the OpenAI 2026 hackathon. It is a single-person effort (Brad Wagoner) with no evidence of prior traction or funding.
Single most important open question
Is there any evidence that event organizers actually use this tool, or that it solves a real operational problem beyond the author's stated intent?
What The Product Actually Is
The description states that WhosNext Event Command Center is a decision-oriented command center for event operations, designed to reduce cognitive load on organizers. It provides:
- A summary of the next six events.
- An explainable readiness score based on unfinished, weighted work.
- Prioritized actions by consequence and deadline.
- A 30-day rolling calendar combining events and tasks.
- Event-specific views (e.g., players, sponsors, volunteers, scoring).
- Live issue detection and recommendations.
It is built using Codex and GPT-5.6, with a focus on human control over AI-generated decisions.
Evidence
- The author describes the product’s functionality in detail.
- It supports multiple event types: golf, bowling, pickleball, basketball, volleyball, and running.
- It includes both portfolio-level and event-specific views.
- It integrates live signals such as pace-of-play risks.
Inference The tool is described as a dashboard that aggregates scattered operational data into one actionable output — but no evidence of actual integration with external systems or real-time data sources is provided.
Positioning & Claim Evolution
The author positions WhosNext as an event-operations command center, not just another dashboard. It claims to:
- Turn scattered tasks and signals into a single readiness score.
- Provide one next action that matters.
- Offer transparency in how the readiness score is calculated.
- Reduce mental load by focusing on consequence and deadline.
Evidence
- The tagline: “An explainable event-operations command center that turns scattered tasks, risks, and live signals into one readiness score and the next action that matters.”
- The write-up emphasizes reducing cognitive load and prioritizing decisions based on impact.
- It is described as a decision-oriented tool rather than an analytics platform.
Inference The positioning suggests a shift from generic dashboards to purpose-built command centers for event organizers. However, there is no evidence of prior market validation or adoption.
Target Customer & ICP
The description states that WhosNext targets event organizers, particularly those managing multiple events (e.g., golf, bowling, pickleball, etc.). It is designed for people who:
- Manage schedules, volunteers, sponsors, scoring, and live operational issues.
- Need to make decisions quickly amid scattered information.
Evidence
- The write-up focuses on the organizer’s challenge: “organizer is left to mentally combine them while the event clock keeps moving.”
- It supports multiple sports formats, implying a broad but specific audience of event managers.
Inference The ICP appears to be event organizers who manage complex, multi-event operations. However, no evidence exists about whether these users actually exist or have been tested with this product.
Business Model & Pricing Evidence
There is no evidence in the description of a business model or pricing structure.
Evidence
- No mention of revenue, customers, subscriptions, or monetization.
- The project was submitted to a hackathon — no indication of commercial intent beyond prototype development.
Inference The tool may be early-stage and non-commercial. If it becomes a product, the business model is unknown.
Technical & Delivery Signals
The author states that WhosNext was built using:
- Codex for implementation.
- GPT-5.6 to generate summaries, recommendations, and explanations.
- A two-tier interface: portfolio view and event command center.
- Browser-based testing and iteration.
Evidence
- The write-up mentions Codex and GPT-5.6 as tools used in development.
- It includes a description of the interface design process.
- It describes how it handles different event types without generic workflows.
Inference The tool uses AI to assist with summarization and prioritization, but there is no evidence that it has been deployed or tested at scale. The technical stack implies early-stage development.
Traction & Maturity Signals
There is no evidence of traction, customers, or adoption beyond the author’s own description.
Evidence
- The project was submitted to a hackathon.
- Team size is listed as 1 (Brad Wagoner).
- No mention of users, revenue, or product usage.
- No indication of prior funding or milestones.
Inference This is a prototype or proof-of-concept. There is no evidence that it has moved beyond the idea stage or been tested in real-world conditions.
Competitive Context
The description does not provide any information about competitors or market positioning.
Evidence
- No mention of existing event management tools.
- No reference to how WhosNext compares with other platforms.
Inference It is unclear whether this tool addresses a gap in the market or duplicates existing solutions. The author makes no claims about competitive advantage.
Key Risks & Red Flags
Several risks and red flags are present due to lack of evidence:
- No traction or adoption: No users, customers, or revenue.
- Unproven market need: No evidence that organizers actually struggle with the described problems.
- Unverified AI integration: The use of Codex and GPT-5.6 is stated but not demonstrated in practice.
- Single-person development: No team or support structure for scaling.
- No business model: No indication of how the tool will be monetized.
Inference The project appears to be a concept or prototype, not a product with commercial viability or market traction.
Diligence Questions To Ask The Founders
- What specific event types do you plan to support beyond those listed?
- Have you tested this with actual event organizers? If so, what feedback did you get?
- How does the readiness score change in response to live events or new data inputs?
- What are your plans for integrating with real-time systems (e.g., registration, scoring)?
- Is there any evidence of user engagement or retention beyond the prototype phase?
Investment/Partnership Verdict
Not evidenced.
The project is a self-reported hackathon submission with no evidence of traction, revenue, customers, or business model. The author describes a concept and its intended functionality but provides no data to validate whether it solves a real problem or has commercial potential.
Confidence Low This is a single-person prototype with no external validation or market proof. Any investment or partnership decision would require further due diligence into actual usage, user feedback, and product-market fit.
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.