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 #2,047 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
TeachKit is a self-reported tool that converts textbook pages, PDFs, or typed topics into printable lesson packs with guided, independent, and challenge practice for mixed-level classrooms. It uses GPT-5.6 APIs and is built with React, Next.js, TypeScript, and Tailwind.
What changed
The project description indicates this was built as a hackathon submission (OpenAI 2026 hackathon) and is currently in a preview state. The live workflow is described as using two GPT-5.6 API calls, but the preview disables live generation and uses an authored fallback instead.
Single most important open question
Is there any evidence of traction, revenue, or customer adoption beyond the self-reported project description?
Note
This analysis is based entirely on the author's own account, as supplied in the project description. No external verification or historical data is available. All claims are self-reported and unverified.
What The Product Actually Is
- The description states that TeachKit turns a textbook page, PDF, or typed topic into a printable lesson pack.
- The lesson pack includes:
- Guided Practice
- Independent Practice
- Challenge
- Five-question exit quiz
- Discussion prompts
- Parent note
- The live workflow uses two GPT-5.6 API calls:
- First call analyzes the source into a schema: topic, grade, subject, source language, and essential concepts.
- Second call generates the structured lesson pack.
- The interface supports photos, PDFs, and typed topics using the same pipeline.
- The output is designed for print (A4 pages) with browser print styles.
- The project uses Next.js, React, TypeScript, Zod, pdf-lib, and OpenAI Responses API.
- A single server route handles validation, two-stage request budget, streaming, and fallback handling.
- The browser never receives the API key.
Inference The product is a proof-of-concept or prototype built for a hackathon. It is not yet live in production as described by the author.
Positioning & Claim Evolution
- The author states that TeachKit was built to solve a practical problem: teachers need printable practice materials that support different learning levels, but making them manually takes time.
- The positioning is centered on:
- Simplifying lesson planning for teachers
- Supporting mixed-level classrooms
- Reducing manual effort in creating differentiated content
- The claim evolution shows a focus on:
- Automation of lesson creation
- Differentiation without changing learning objectives
- Print-ready outputs
- The author emphasizes that the feature is not just about generating text but ensuring readability, meaningful differentiation, and print readiness.
Inference The positioning reflects a teacher-focused, content-automation tool. It is positioned as a time-saving solution for educators, though no evidence of market traction or adoption exists.
Target Customer & ICP
- The description states that the target audience includes teachers who need to support mixed-level classrooms.
- The tool aims to help teachers create printable lesson packs without spending too much time on manual preparation.
- The author does not specify a clear ICP beyond "teachers" and does not describe segmentation or persona development.
Not evidenced No evidence of specific customer personas, buyer personas, or market segmentation is provided.
Business Model & Pricing Evidence
- The description does not mention any pricing model or business model.
- There is no indication of monetization strategy, revenue streams, or customer acquisition plans.
- The project is presented as a hackathon submission and is currently in preview mode with live generation disabled.
Not evidenced No evidence of pricing, monetization, or business model is provided.
Technical & Delivery Signals
- Built with:
- Next.js
- React
- TypeScript
- Zod (for schema validation)
- pdf-lib
- OpenAI Responses API (GPT-5.6)
- The system uses a two-stage GPT workflow:
- First call: source analysis
- Second call: lesson pack generation
- The system is designed to avoid retries and uses fallbacks when live generation fails.
- Print layout is handled via browser print styles, with A4 page flow tested for clipping, overlap, and spacing.
- The project includes automated tests for:
- Request limits
- Schema validation
- Incremental worksheet extraction
- File checks
- Fallback behavior
Inference The technical architecture is built for a prototype or MVP. It uses modern web stack with strong schema validation, but lacks production-grade features like rate limiting and spend controls.
Traction & Maturity Signals
- Team size: 0 (as stated)
- No customers, users, or adoption data are mentioned.
- The project is described as a hackathon submission.
- The live workflow is not yet enabled in the preview.
- The project includes six original sample pages but no evidence of real-world usage or feedback.
- No mention of revenue, ARR, or funding rounds.
Not evidenced No traction, adoption, or maturity indicators beyond the self-reported development status.
Competitive Context
- The description does not mention any direct competitors.
- No market analysis or competitive positioning is provided.
- The tool is described as solving a problem in teacher lesson planning and content creation.
- It appears to be in a niche space of AI-powered educational materials, but no evidence of existing players or market dynamics is shared.
Not evidenced No competitive landscape or market context is provided.
Key Risks & Red Flags
- The project is described as a hackathon submission with no live production use.
- The live GPT-5.6 generation is disabled in the preview, and fallbacks are used instead.
- No evidence of customer feedback, testing, or real-world validation.
- The team size is 0, which raises questions about execution capability.
- The system uses a strict two-call limit for GPT usage, which may be a design constraint that limits scalability or robustness.
- The tool is English-only, with no indication of localization plans.
Inference The project is not yet mature or validated in the market. Risks include lack of traction, limited team capacity, and unproven product-market fit.
Diligence Questions To Ask The Founders
- What is the exact use case for which this tool was designed? Is it intended for teachers in K-12, higher education, or corporate training?
- How does the fallback content differ from live-generated content in terms of quality and alignment with learning objectives?
- Has there been any feedback from educators or teachers on how they would use this tool?
- What are the plans to enable live GPT generation and scale beyond the current preview state?
- Are there any plans for localization or support for languages other than English?
- How does the team plan to monetize this product, if at all?
- What is the long-term vision for TeachKit beyond the hackathon?
Investment/Partnership Verdict
- The project is described as a hackathon submission with no evidence of traction, revenue, or customer adoption.
- It is in an early prototype phase and not yet live in production.
- The team size is 0, which raises concerns about execution capability.
- No pricing model, monetization strategy, or business model is evident.
- The tool is positioned for teachers but lacks any market validation or user feedback.
Verdict Not ready for investment or partnership. The project shows potential but is not yet proven in the market. It requires further development, testing, and evidence of traction before it can be considered a viable opportunity.
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.
