Archive position — measured, not model output
1 like on Devpost
506 of the 7,856 archived projects have more likes, and 1,758 share exactly 1 — so this project's #1,969 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
Sparky AI is a self-reported chatbot project built by one developer, Shedrach Ojonimi, for the OpenAI 2026 hackathon. The description states it is usable but provides no evidence of revenue, customers, or adoption.
What changed
There is no indication of prior activity or evolution — this appears to be a single project submission with no prior history or development trajectory.
Single most important open question
Is there any evidence of commercial traction, user adoption, or revenue generation beyond the author's self-statement that it is "usable"?
What The Product Actually Is
The description states: “Sparky AI Chatbot.” It was built using API, Claude, and OpenRouter technologies. The project is described as a chatbot application submitted to a hackathon.
Evidence
- The product is a chatbot.
- Built with API, Claude, and OpenRouter.
- Submitted to the OpenAI 2026 hackathon.
Inference
- The product likely interfaces with AI models via APIs.
- It may be a prototype or proof-of-concept rather than a production-ready tool.
Positioning & Claim Evolution
The description states: “Sparky AI Chatbot.” There is no evidence of prior positioning, messaging evolution, or claims about market fit or differentiation.
Evidence
- The tagline and name are consistent.
- No mention of target use cases, value propositions, or competitive claims.
Inference
- The project may be positioned as a general-purpose chatbot.
- There is no indication of prior positioning or evolution in its messaging.
Target Customer & ICP
The description does not state any information about target customers or ideal customer profiles (ICP).
Evidence
- No mention of customer segments, personas, or use cases.
Inference
- The project may be intended for general users or developers.
- Absence of evidence suggests no defined ICP.
Business Model & Pricing Evidence
The description does not contain any information about pricing, monetization, or business model.
Evidence
- No mention of revenue streams, pricing tiers, or monetization strategy.
Inference
- The project may be non-commercial or experimental.
- Absence of evidence suggests no defined business model.
Technical & Delivery Signals
The description states: “Built with (author-declared): api, claude, openrouter.” It also notes that the project was submitted to a hackathon.
Evidence
- Built using API, Claude, and OpenRouter.
- Submitted to a hackathon.
Inference
- The product likely integrates with AI APIs.
- May be a prototype or proof-of-concept rather than a scalable solution.
Traction & Maturity Signals
The description states: “Am proud it's usable now.” There is no evidence of users, adoption, or growth metrics.
Evidence
- The author claims it is usable.
- No mention of customers, usage data, or product maturity.
Inference
- The project may be in early development or prototype stage.
- Absence of traction signals suggests no commercial momentum.
Competitive Context
The description does not provide any information about competitors or market context.
Evidence
- No mention of competitive landscape or similar products.
Inference
- No evidence of awareness of existing chatbot or AI tools in the market.
- Absence of competitive analysis or positioning against other solutions.
Key Risks & Red Flags
- The project is described as a single-person hackathon submission with no evidence of traction, customers, or revenue.
- No business model or pricing strategy is evident.
- No indication of product maturity or scalability.
- The author’s claim that it is “usable” does not imply commercial viability.
Evidence
- One-person team.
- Hackathon submission.
- No revenue, customer, or adoption data.
Inference
- High risk of being a non-commercial prototype.
- Lack of evidence for product-market fit or scalability.
Diligence Questions To Ask The Founders
- What is the intended use case for Sparky AI?
- How does it differ from existing chatbot tools in the market?
- Is there any plan to monetize or scale this project?
- What are the key assumptions about user needs and behavior?
- Are there any early users or feedback loops?
Investment/Partnership Verdict
Not evidenced.
Evidence
- No revenue, customers, or traction data.
- No business model or pricing strategy.
- No indication of scalability or commercial viability.
Inference
- The project is likely a prototype or experimental tool.
- There is no basis 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.