TeachingTurn

The description states that TeachingTurn is a web application built with Next.js. Students scan a QR code and answer two quick questions, with an optional comment. Responses are stored using Supabase, and OpenAI (specifically GPT-5.6) is used to identify themes and suggest teaching adjustments.

Evidence The author states that the app collects feedback after lectures and turns it into one practical adjustment for instructors to try in the next class.

Inference The product appears to be a lightweight feedback collection tool with AI-powered summarization and suggestion features, but no evidence of actual deployment or usage exists.

The author claims that TeachingTurn helps instructors turn small class signals into practical adjustments. It is positioned as a solution for professors who struggle to get useful feedback in time to improve a course, addressing the problem of end-of-semester evaluations being too late.

Evidence The description states: "It helps instructors turn a small class signal into one practical adjustment for the next class."

Inference This suggests an intent to solve real-time feedback loops and course improvement — but no evidence exists that this has been validated or implemented in practice.

The primary customer is described as professors or instructors. The author notes that students answer questions after lectures, indicating a focus on the classroom environment.

Evidence The description states: "As a professor, I often struggle to get useful feedback while there is still time to improve a course."

Inference The target is likely university-level educators who want real-time feedback and course improvement tools. No evidence of specific customer segments or personas beyond the author’s own experience.

There is no evidence in the description of any pricing model, monetization strategy, or business model. The project is described as a hackathon submission with no indication of commercial intent or revenue streams.

Evidence Not evidenced.

Inference If this is intended to be a commercial product, it has not been described or demonstrated in the provided material.

The app was built using Next.js and Supabase for backend storage. The author used OpenAI (GPT-5.6) for summarization and suggestions. Tools like Codex were reportedly used throughout development.

Evidence The description states: "We built TeachingTurn as a Next.js web app... Supabase stores the responses, while OpenAI and GPT-5.6 helps identify supported themes and suggest a concrete teaching move."

Inference The tech stack is standard for modern SaaS apps, but no evidence of production deployment or scalability exists.

The project is described as a hackathon submission with no evidence of real-world usage, pilot programs, or user engagement. The author states that the next step is to pilot it in real courses, suggesting it’s not yet in use.

Evidence The description states: "Next, I want to pilot TeachingTurn in real courses... learn from students and instructors."

Inference No traction, adoption, or usage data are provided. The project appears to be at a prototype stage.

No competitive analysis is provided in the description. There is no mention of existing tools or platforms that address similar feedback or course improvement needs.

Evidence Not evidenced.

Inference Without any reference to competitors or market positioning, it's unclear how TeachingTurn fits into the broader educational technology landscape.

• No real-world usage: The project is described as a hackathon submission with no evidence of pilot use.
• Unverified claims: The author states that professors don’t need complicated dashboards and that they learned about deployment — but these are self-reported insights without validation.
• Lack of commercial viability: No pricing, monetization or business model is described.
• Limited team size: Only one member (the author) is listed, which may limit execution capacity.

Evidence Not evidenced.

1. Have you piloted TeachingTurn in any real courses?
2. What specific feedback have you received from students or instructors during your testing?
3. How do you plan to scale beyond a single instructor’s use case?
4. Do you have any data on student participation rates or engagement with the tool?
5. Are there any plans for monetization or commercial deployment?