Spotz

Spotz is a self-reported tool built by one developer (El Elyon) for finding local spots recommended only on local forums in any country or city. The project was submitted to the OpenAI 2026 hackathon and is described as a first-time hackathon effort, completed with three days' notice. It uses Codex CLI and ChatGPT 5.6 for guidance during development. The author states that the tool is not yet public, but they intend to make it available to anyone who can use it — possibly monetizing it in the future if API costs are reduced or if it proves valuable.

What changed: The project was built as a personal solution for travel planning, with no evidence of prior traction, revenue, or customer adoption. It is described as a proof-of-concept and not yet a product with a market presence.

Key open question: Is there any indication that Spotz will evolve into a sustainable product or business beyond the hackathon context? The author states they are unsure if it will be monetized, suggesting no clear commercial plan or revenue model is evident.

The description states:

• Spotz finds local spots recommended only on local forums of any country and city.
• It was built using Codex CLI and ChatGPT 5.6 for guidance.
• The author describes it as a tool they needed for travel planning.

Inference: Based on the self-reported description, Spotz is a prototype or proof-of-concept tool that leverages AI to extract local recommendations from forums. It is not described as having an API, marketplace, or user-facing interface beyond its initial development phase.

The author states:

• “Have you ever visited somewhere and just wanted to explore the place like a local?”
• “Love to explore? Find spots with Spotz”
• “I’m going to travel to Japan in 2 weeks, and I built a tool that I needed.”

Inference: The positioning is personal and exploratory — it targets travelers or explorers who want local insights. The claim evolution appears to be from a personal need (travel) to a potential public tool, but no evidence of market validation or broader positioning exists.

The description states:

• “Love to explore?”
• “Ever want to get recommendations for your own city?”
• “I’m going to travel to Japan in 2 weeks…”

Inference: The target customer appears to be individuals who enjoy exploring places, particularly travelers or locals seeking new experiences. However, no explicit ICP is defined beyond the personal use case described.

The description states:

• “Honestly, just making it a public tool anyone can use…”
• “If I can ever get the API costs down, or if it turns out to be worth monetizing, maybe it becomes something bigger.”

Inference: There is no evidence of a business model or pricing structure. The author indicates uncertainty about monetization and does not describe any revenue streams or pricing plans.

The description states:

• Built with Codex CLI and ChatGPT 5.6 for guidance.
• “I usually use Claude Code, so building with Codex without my usual harness/setup was an adjustment at first.”
• “It got easier as I went, and I picked up a better sense of how to prompt Codex effectively.”

Inference: The tool is built using AI tools (Codex, ChatGPT) and is described as a hackathon prototype. No evidence of scalability, API, or production-grade delivery is provided.

The description states:

• “This is my first ever hackathon.”
• “I joined with only three days left.”
• “I was genuinely surprised I was able to get this working in that time.”
• “It’s not public yet.”

Inference: No traction or maturity signals are evident. The project is described as a hackathon prototype, not yet available to the public, and without any evidence of user adoption or growth.

The description does not mention competitors or market context beyond the author’s personal use case.

Not evidenced: No information on existing tools that do similar things (e.g., local recommendation platforms, travel apps, forum scrapers).

• No commercial traction or revenue model: The tool is described as a hackathon prototype with no evidence of monetization.
• No public availability: It is not yet available to users, suggesting no market presence.
• Unproven scalability: Built using AI tools in a short timeframe, with no indication of production-grade architecture or API support.
• Unclear path to product-market fit: The author expresses uncertainty about whether the tool will be monetized or expanded.

1. What is the current status of Spotz? Is it publicly accessible?
2. Have you identified any specific local forums or sources that are being scraped for recommendations?
3. What is your plan for monetization, if any?
4. How do you intend to scale this beyond a hackathon prototype?
5. Are there any legal or ethical concerns with scraping local forum content?