Archive position — measured, not model output
3 likes on Devpost
128 of the 7,856 archived projects have more likes, and 93 share exactly 3 — so this project's #172 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
Lectly is a self-reported tool for tutors to plan lessons, assign homework, schedule practice, and manage student progress using AI. It is described as an application built for language, math, science, and coding tutors.
What changed
The project description indicates that Lectly emerged from a frustration with time-consuming pre- and post-class tasks for tutors. It was built to centralize lesson planning and student tracking around individual students, integrating AI in a way that supports but does not replace the tutor’s role.
Single most important open question
Is there evidence of real-world usage or traction by tutors? The description states no revenue, customers, or adoption data beyond the authors’ own claims.
Note: This analysis is based solely on the self-reported project description provided. No external verification, archived data, or third-party sources are available. All findings are derived from what the authors wrote and declared — not confirmed or corroborated.
What The Product Actually Is
The description states that Lectly helps tutors build a learning space around each student by tracking student level, goals, interests, previous lessons, homework, and progress. It allows tutors to use this context to create lessons, practice activities, study cards, and homework.
It is described as not just generating content from AI but allowing tutors to edit and refine that content. The tool supports structured generation using Markdown, KaTeX, and interactive components, aiming for usability across multiple subjects including language, math, science, and coding.
Claim: Lectly enables tutors to manage student-specific learning materials in one place.
Evidence: The description states: “Lectly helps tutors build a learning space around each student...” and “The important part for us is that the content does not appear from nowhere and get sent away untouched. It is there to be edited, changed, and used by the tutor who knows the student.”
Positioning & Claim Evolution
Lectly positions itself as an AI-powered tool that reduces the administrative burden of teaching while preserving the personal, human element of tutoring.
The authors describe a shift from “AI features” to “a place where teaching can happen.” They emphasize that the value of AI is not in automating lessons but in removing repetitive tasks so tutors can focus on relationships and instruction.
Claim: Lectly aims to make AI feel less like a tool and more like a learning environment.
Evidence: The description states: “We are proud that Lectly is starting to feel less like an AI feature and more like a place where teaching can happen.”
Target Customer & ICP
The target customer is described as independent tutors who teach in subjects such as language, math, science, and coding.
Claim: The tool is for independent tutors working with individual students.
Evidence: The description says: “Lectly is our attempt to build that home...” and “We want Lectly to become better at understanding what happens over time: what a student keeps struggling with, what they improve at, what kind of materials work for them.”
Business Model & Pricing Evidence
There is no evidence in the description of pricing, monetization, or business model.
Finding: Not evidenced.
What would fill this gap: Statements about revenue streams, subscription tiers, or customer acquisition costs.
Technical & Delivery Signals
Lectly was built using Next.js, TypeScript, Convex, Clerk, and OpenAI. The authors emphasize structured generation over chat-based AI outputs, focusing on editable lessons that render properly in Markdown, KaTeX, and interactive components.
Claim: Lectly uses modern web stack and structured AI output.
Evidence: “We built Lectly with Next.js, TypeScript, Convex, Clerk, and OpenAI.” and “We focused on structured generation instead of just putting AI text into a chat window.”
Traction & Maturity Signals
There is no evidence in the description of revenue, customers, or adoption. The project was submitted to a hackathon and has no stated traction beyond the authors’ own account.
Finding: Not evidenced.
What would fill this gap: Data on active users, revenue, customer testimonials, or product usage metrics.
Competitive Context
No mention of competitors or market positioning is provided in the description. The authors do not reference similar tools or platforms in the marketplace.
Finding: Not evidenced.
What would fill this gap: Information about existing tools for lesson planning, tutoring platforms, or AI-assisted education products.
Key Risks & Red Flags
- No traction or revenue data: The project is described as a hackathon submission with no evidence of real-world use.
- Unproven market fit: No customer validation or feedback from tutors is mentioned.
- Limited team size: Only three members are listed, which may limit execution capacity.
- Self-reported claims only: All descriptions are unverified and lack external corroboration.
Inference: The lack of traction suggests a high risk that the product has not yet proven its value in real-world use cases.
Diligence Questions To Ask The Founders
- Have you tested Lectly with actual tutors? What feedback have you received?
- How do you plan to monetize this product, and what is your go-to-market strategy?
- What are the key challenges in scaling beyond a small team of three?
- Are there any existing competitors or similar tools in the market that you're aware of?
- What metrics do you track to assess whether tutors are actually using the tool?
Investment/Partnership Verdict
There is no evidence of traction, revenue, or customer adoption. The project is described as a hackathon submission with no external validation.
Verdict: Not evidenced.
Confidence level: Low — this analysis is based entirely on self-reported claims and lacks any independent data or market signals to assess viability or commercial 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.
