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 #2,987 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
Boothly is a self-reported bilingual event marketplace for DJs and event hosts/businesses in the Greek events industry. The platform supports structured booking workflows, availability-aware matching, AI-assisted brief creation, and trust/safety features.
What changed
This is a hackathon project submitted to the OpenAI 2026 hackathon. It was built by one person (Iraklis Gougoudis) using a stack including Next.js, React, Node.js, PostgreSQL, Stripe, OpenAI, and Vercel. No prior version or commercial activity is evidenced.
Single most important open question
Is there any evidence of traction, revenue, customer adoption, or market validation beyond the author's self-description?
What The Product Actually Is
The description states that Boothly is a bilingual event marketplace connecting hosts and businesses with DJs. It supports:
- Professional DJ profiles
- Portfolio reviews
- Structured event briefs
- Direct booking coordination
- Availability management via iCal integration
- AI-assisted event brief creation
- Review systems
It also includes separate workspaces and permissions for hosts and DJs.
The platform is described as designed specifically for the Greek events industry, with support for both Greek and English languages.
Evidence Self-reported by author. No independent verification or demonstration provided.
Positioning & Claim Evolution
The author positions Boothly as a solution to a fragmented market where event hosts rely on informal methods like social media, phone calls, and message threads without knowing if DJs are available or suitable.
Key claims:
- “Finding the right DJ for an event is still surprisingly fragmented.”
- “I created Boothly to bring those workflows together in one bilingual marketplace designed for the Greek events industry.”
The positioning evolves from a general problem (fragmented booking) to a specific solution (structured workflow with availability-aware matching and AI tools).
Evidence Self-reported. No external validation or market research cited.
Target Customer & ICP
The description identifies two main user types:
- Hosts and businesses looking for DJs
- DJs seeking clients and managing their availability
It is explicitly stated that Boothly is designed for the Greek events industry, with bilingual support (Greek/English).
No further segmentation or targeting details are provided.
Evidence Self-reported. No evidence of customer personas, user interviews, or market research.
Business Model & Pricing Evidence
There is no mention of pricing models, monetization strategies, or business model in the description. The author does not state how Boothly will make money or what its revenue streams are.
Evidence Not evidenced.
Technical & Delivery Signals
The project was built using:
- Frontend: Next.js, React, Tailwind CSS, Framer Motion
- Backend: Node.js, PostgreSQL, Stripe (for payments)
- AI integration: OpenAI
- Other tools: iCal, Zod, Resend, GSAP, Vercel
It includes features like:
- iCal calendar import
- AI-assisted event briefs
- Structured request and offer workflows
- Public DJ profiles with media uploads
The project was submitted to the OpenAI 2026 hackathon, suggesting it is a prototype or proof-of-concept.
Evidence Self-reported. No evidence of production deployment, scalability, or delivery beyond the hackathon submission.
Traction & Maturity Signals
There is no evidence of traction, customers, revenue, or adoption beyond the author’s own description.
The project was built by one person, and there is no mention of:
- Users
- Customers
- Revenue
- Growth metrics
- Product usage data
It is described as a hackathon submission.
Evidence Not evidenced.
Competitive Context
No competitive analysis or market positioning relative to existing platforms is provided in the description. The author does not name competitors or describe how Boothly differentiates from them.
Evidence Not evidenced.
Key Risks & Red Flags
- Single founder: Only one person built this, which may indicate limited execution capacity.
- No traction: No evidence of users, customers, or revenue.
- Hackathon project: Likely a prototype, not yet validated in the market.
- Unverified claims: All descriptions are self-reported and unverified.
- No pricing or monetization strategy: Unclear how Boothly will generate revenue.
Inference The lack of any commercial evidence raises concerns about viability and scalability.
Diligence Questions To Ask The Founders
- What is the current stage of development beyond the hackathon submission?
- Have you tested the platform with real DJs or event hosts?
- How do you plan to acquire users in the Greek events industry?
- Is there any evidence of demand or interest from potential customers?
- What is your path to monetization?
- Are there any existing partnerships or early adopters?
Investment/Partnership Verdict
Not evidenced.
There is no evidence of revenue, customer traction, market validation, or commercial progress beyond a hackathon submission by one individual.
This is a self-reported prototype, not a product with demonstrated market fit or business model.
Confidence level Low. The description provides no basis for assessing commercial viability or investment potential.
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.
