NotZero

The description states that NotZero analyzes a user’s curriculum, academic materials, project files, target role, and location. It identifies what remains current, what transfers, what needs a small bridge, what appears missing, and what cannot yet be concluded. It then provides evidence, prioritized next steps, and a concrete upgrade challenge.

• Claimed functionality: Analysis of user inputs (curriculum, materials, etc.) to map academic knowledge to professional expectations.
• Output type: Evidence-based recommendations with actionable next steps.
• Methodology: Uses AI models like GPT-5.6, structured outputs, schema validation, and progressive disclosure.

Inference The product is described as a knowledge mapping tool for recent graduates, using AI to assess gaps between education and job requirements.

The author states that NotZero helps graduates see they are not starting from zero — their existing knowledge can become a practical bridge to current work.

• Positioning claim: A tool that reduces the perceived gap between academic learning and professional expectations.
• Evolution of claims: From a hackathon MVP to a potential multi-disciplinary platform (e.g., law, accounting, nursing).

Inference The positioning is centered on reducing graduate anxiety by showing transferable skills. The evolution suggests ambition beyond a single-use tool.

The description states that NotZero is for recent graduates who are transitioning into the workforce and need to understand how their academic knowledge maps to current job requirements.

• Target customer: Recent software graduates (initially), with plans to expand to other disciplines.
• ICP (Ideal Customer Profile): Recent graduates, especially in technical fields, who are uncertain about how their education applies to real-world roles.

Inference The ICP is likely early-career professionals seeking clarity on skill relevance and next steps. No evidence of segmentation or targeting beyond this.

The description does not state anything about pricing, monetization, or a business model.

• Monetization: Not evidenced.
• Pricing: Not evidenced.
• Business model: Not evidenced.

Inference There is no evidence of any revenue-generating mechanism beyond the hackathon submission.

The project was built using:

• Tools: Codex, GPT-5.6, TypeScript, OpenAI API integration
• Frameworks/Stack: React, Flask, Cloudflare Workers, D1, Zod, Pandas, Scikit-learn, Vite, Vinext
• Features: Bounded file uploads, staged analysis, structured outputs, evidence locators, schema validation, checkpointed retries, progressive disclosure

Inference The product uses a hybrid of AI and structured engineering to deliver a user-facing tool with traceability and error handling.

The description states that this was built for the OpenAI 2026 hackathon. It is described as an MVP, with no mention of users, revenue, or adoption beyond the author’s own account.

• Traction: Not evidenced.
• Maturity: MVP-level product; no evidence of scaling or production use.
• User feedback: Not evidenced.

Inference The project has not demonstrated any real-world usage or impact beyond a hackathon submission.

The description does not mention any competitors. It is unclear whether similar tools exist in the market for helping graduates bridge academic and professional knowledge.

• Competitive landscape: Not evidenced.
• Differentiation: Not evidenced.

Inference No evidence of competitive analysis or awareness of existing solutions in this space.

• No traction or revenue: The project is described as an MVP with no evidence of adoption or monetization.
• Unverified claims: All claims are self-reported and unverified.
• Limited scope: Only one team member, a single founder (Cesar Reyes), suggests limited capacity for execution.
• AI dependency: Heavy reliance on GPT-5.6 and OpenAI APIs may create scalability or cost risks.
• No user feedback loop: No evidence of iterative improvement based on user input.

Inference The lack of external validation, revenue, or users raises significant concerns about product-market fit and viability.

1. What specific feedback have you received from recent graduates who used the tool?
2. How do you plan to validate that your AI outputs are accurate and actionable?
3. Have you tested the tool with actual users beyond yourself or your team?
4. What is your roadmap for expanding into other disciplines (law, accounting, etc.)?
5. Do you have any plans for monetization or user onboarding beyond the MVP?