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,725 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
Workly AI is an AI-powered platform for electricians, described by the author as a tool to generate estimates, manage jobs, and automate field service operations. It was submitted to the OpenAI 2026 hackathon on Devpost.
What changed
There is no evidence of prior development or traction. The project appears to be an early-stage concept or prototype, submitted for a hackathon.
The single most important open question
Is there any evidence of customer validation, product-market fit, or commercial viability beyond the author’s self-reported description?
What The Product Actually Is
The description states that Workly AI is “an AI-powered platform for electricians to generate estimates, manage jobs, and automate field service operations.” It was built as a hackathon submission.
Evidence
- The project was submitted to the OpenAI 2026 hackathon.
- The author lists technologies used: ai, api, app, artificial, automation, cloud, codex, computing, css, firebase, firestore, gemini, google, gpt-5, hosting, html, intelligence, javascript, openai, productivity, web.
Inference The product is likely a web-based or mobile application integrating AI models (e.g., GPT-5, Gemini) to support electricians in field operations. However, no functional details, UI, or technical architecture are provided.
Positioning & Claim Evolution
The author positions Workly AI as an AI-powered solution for electricians to automate tasks such as estimating, job management, and field service operations.
Evidence
- Tagline: “AI-powered platform for electricians to generate estimates, manage jobs, and automate field service operations.”
- Submitted to the OpenAI 2026 hackathon.
Inference The positioning is early-stage and self-reported. No evidence of prior market testing or customer feedback exists. The claim is that it solves problems in electrician workflows, but no proof of traction or adoption is provided.
Target Customer & ICP
The description states that Workly AI targets electricians.
Evidence
- Tagline: “AI-powered platform for electricians to generate estimates, manage jobs, and automate field service operations.”
Inference The target customer is electricians in the field. However, there is no evidence of segmentation or identification of specific subtypes of electricians (e.g., residential vs. commercial), nor any indication of how the product addresses their needs beyond general claims.
Business Model & Pricing Evidence
There is no evidence of pricing, monetization strategy, or business model in the description.
Evidence
- No mention of revenue streams, pricing tiers, or customer acquisition costs.
- No indication of whether it’s a SaaS, freemium, or one-time purchase model.
Inference The project appears to be at an early stage where the business model has not been defined or disclosed. The author does not state how the platform will generate revenue.
Technical & Delivery Signals
The author lists several technologies used in building the product.
Evidence
- Technologies: ai, api, app, artificial, automation, cloud, codex, computing, css, firebase, firestore, gemini, google, gpt-5, hosting, html, intelligence, javascript, openai, productivity, web.
Inference The platform likely uses AI models (e.g., GPT-5, Gemini) and is built with modern web technologies. However, no information on architecture, scalability, or delivery mechanism is provided.
Traction & Maturity Signals
There is no evidence of traction, adoption, or product maturity.
Evidence
- Submitted to a hackathon.
- Team size: 1 (Felipe Oliveira).
- No mention of customers, usage metrics, or product development history.
Inference The project is likely in an early prototype stage. There is no indication of user feedback, market testing, or product iteration.
Competitive Context
There is no evidence of competitive analysis or awareness of existing solutions in the field service automation space.
Evidence
- No mention of competitors.
- No indication of how Workly AI differentiates from other tools for electricians or field service operations.
Inference The author does not appear to have conducted a competitive landscape review. The product is described without reference to existing solutions or market positioning.
Key Risks & Red Flags
Several key risks and red flags are present due to the lack of evidence:
- No traction or validation: Submitted as a hackathon project with no prior development.
- Unproven business model: No pricing, monetization, or revenue strategy.
- Limited team: Only one founder, which may limit execution capacity.
- No customer feedback or market testing: Claims are unvalidated.
- Unclear differentiation: No evidence of how it stands out from existing tools.
Diligence Questions To Ask The Founders
- What specific problems in electrician workflows does Workly AI solve?
- How did you identify the need for this product?
- Have you tested the concept with any electricians or field service professionals?
- What is your plan to monetize the platform?
- How do you intend to scale beyond a single founder?
- What are the key technical challenges in building and deploying this solution?
Investment/Partnership Verdict
Not evidenced.
The description provides no evidence of revenue, customers, traction, or commercial viability. The project is presented as an early-stage hackathon submission with no indication of product-market fit or business model.
Confidence Low. This analysis is based entirely on self-reported information and lacks any corroboration or external validation.
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.