Perception Learning

What the company appears to be: Perception Learning is a self-reported educational technology project that aims to make learner reasoning visible during learning, with a focus on real-time feedback and adaptive instruction. It was submitted as a hackathon project by one individual developer (Aditya Das) for the OpenAI 2026 hackathon.

What changed: The project is in an early stage — it's a hackathon submission, not a product in production or with any demonstrated traction. There are no claims of revenue, customers, or adoption beyond what the author states.

Single most important open question: Is there evidence that this concept can be scaled into a viable educational SaaS product with real-world impact?

Analysis basis: This report is based entirely on the self-reported project description provided by the caller. No external verification, archived data, or third-party sources are available. All claims in the description are treated as stated by the author and not independently confirmed.

The description states that Perception Learning is a system designed to make learner reasoning visible while it can still change. It includes functionality for generating lessons, questions, answers, and simulations using AI tools, but also emphasizes deterministic simulations and learner evidence flow.

• The product appears to be a prototype or proof-of-concept built as part of a hackathon.
• It integrates with Cloudflare Workers, Cloudflare D1, React, TypeScript, Vite, and various AI models (e.g., Codex, GPT-5.6, NVIDIA NIM).
• The system supports both model-backed actions (which are currently unavailable due to API credit exhaustion) and deterministic reference modes.
• It includes a public interface deployed via Cloudflare Workers.

Evidence: Based on the project write-up and technology stack listed by the author.

The tagline “Make learner reasoning visible while it can still change” suggests a focus on formative assessment and real-time feedback in learning environments. The author positions this as an educational tool that helps educators understand how learners think during instruction, potentially enabling adaptive teaching strategies.

• The project is positioned as a tool for enhancing learning through visibility into cognitive processes.
• It implies integration with AI to generate content dynamically but also supports deterministic simulations — indicating flexibility in implementation approaches.
• No indication of prior positioning or evolution from earlier versions; this is a new submission.

Evidence: Tagline and project write-up. The claim is self-reported and unverified.

The description does not explicitly identify target customers or personas. However, the focus on learner reasoning and adaptive instruction implies potential use cases in education settings such as schools, universities, or corporate training programs.

• The system could be aimed at educators, instructional designers, or learning platform developers.
• It may appeal to institutions seeking tools that support personalized learning or real-time feedback mechanisms.
• No specific customer segments or ICPs are named.

Evidence: Inferred from the stated purpose and use case implications in the write-up. Not directly evidenced.

There is no evidence of a business model, pricing strategy, monetization approach, or revenue streams mentioned in the description.

• No mention of licensing, subscriptions, usage fees, or other commercial structures.
• The project appears to be a prototype without any indication of how it would generate value for users beyond its demonstration.

Evidence: Not evidenced. The author does not describe any business model.

The project is built using modern web technologies including React, TypeScript, Vite, and Cloudflare Workers. It integrates with several AI services such as Codex, GPT-5.6, NVIDIA NIM, and others.

• The system uses serverless architecture via Cloudflare Workers.
• It includes a deterministic simulation mode that does not require API credits, suggesting some level of offline capability or fallback logic.
• The public repository contains local setup instructions, indicating openness to replication or further development.

Evidence: Technology stack and deployment details provided by the author.

There is no evidence of traction, adoption, or maturity beyond the hackathon submission. The project is described as a prototype with limited functionality due to API credit limitations.

• No data on user engagement, retention, or performance metrics.
• No indication of product-market fit or customer feedback.
• The system is not in production; it's a demonstration-only version.

Evidence: Not evidenced. The author states the system is a hackathon submission and that some features are currently unavailable due to API limitations.

The description does not include any information about competitors or market positioning relative to existing solutions in the educational technology space.

• No mention of similar products, platforms, or tools.
• No indication of competitive advantages or differentiation strategies.

Evidence: Not evidenced. The author does not reference the competitive landscape.

Several key risks and red flags emerge from the lack of evidence:

• No traction or validation: This is a hackathon project with no demonstrated adoption or usage.
• Limited functionality: Many features are currently broken due to API credit exhaustion, suggesting instability or incomplete development.
• Single-person team: With only one member (Aditya Das), there may be limited capacity for scaling or long-term maintenance.
• Unproven concept: The idea of making learner reasoning visible is not backed by any real-world testing or data.

Inference: These risks are inferred from the lack of evidence and the nature of a hackathon submission.

1. What specific educational outcomes does this system aim to improve, and how would you measure success?
2. How do you plan to scale beyond the current prototype and API limitations?
3. Are there any early adopters or pilot users who have tested this system?
4. What is your roadmap for monetization or commercial viability?
5. How do you intend to integrate with existing learning platforms or LMS systems?

Inference: These questions are based on the lack of evidence and the speculative nature of the project.