Tburnout-sentinel

What the company appears to be: Burnout Sentinel is a student wellness project that presents itself as an early warning system for student burnout. The author describes it as an MVP prototype focused on helping students detect overload early and rebalance their week before stress becomes burnout. It combines planning inputs with risk scoring, personalized recommendations, and trend tracking.

What changed: The project is described as a research-focused tool built for the OpenAI 2026 hackathon. It currently exists as an MVP prototype with a polished UI, backend analysis API, and competition-ready demo flow. The author states it uses explainable rules-based risk scoring and has a roadmap that includes replacing this with trained models once data is available.

Single most important open question: Is there evidence of any real-world usage or adoption by students? The description contains no information about actual users, revenue, customer traction, or market validation beyond the author's own claims.

Analysis basis: This report is based entirely on the self-reported project description provided by the caller. It has not been independently verified and contains no evidence of revenue, customers, or adoption. All statements are labeled as "the author states" and should be treated as unverified claims.

The author states that Burnout Sentinel is a student wellness tool designed to help detect overload early and rebalance schedules before stress becomes burnout. It functions as an MVP prototype with:

• A frontend UI for weekly workload and recovery input
• An API backend that computes risk scores and recommendations
• Features including:
  • Weekly planner with preset weeks (Balanced, Heavy, Overloaded)
  • Burnout risk score (0–100) with labels (Low/Moderate/High)
  • Explainable breakdown of contributing factors
  • What-if simulations for schedule adjustments
  • Trend tracking and visualization

The system is described as using a rules-based approach to risk scoring, with plans to transition to machine learning models in the future.

Evidence: The author's own write-up describes the product’s functionality and architecture. No third-party verification or independent assessment of its actual use or performance is provided.

The author positions Burnout Sentinel as an early warning system for student burnout, emphasizing prevention over reactive management. It is described not just as a to-do list but as a tool that combines planning inputs with analysis and guidance.

Key positioning elements:

• Focus on early detection of overload
• Emphasis on personalized recommendations
• Use of explainable risk scoring
• Integration of trend tracking

The project is framed as a research effort, with the author stating it was submitted to the OpenAI 2026 hackathon. The roadmap indicates future expansion toward ML-based models and persistence features.

Inference: The positioning suggests an intent to evolve from a prototype into a scalable student wellness platform, though no evidence supports current traction or adoption beyond its development stage.

The author states that Burnout Sentinel is aimed at students, specifically those who may be experiencing or at risk of burnout due to academic workload. It targets individuals seeking tools to manage their weekly schedules and maintain balance.

There is no evidence of segmentation beyond student demographics, nor any indication of specific subgroups (e.g., college vs. high school, STEM vs. humanities students).

Evidence: The description only identifies the general user group as "students" without further detail on target personas or customer types.

The author does not provide any information about pricing, monetization strategy, or business model. There is no mention of paid features, subscriptions, or revenue streams.

Not evidenced: No evidence exists in the description regarding how the product would generate value or income.

The project is built using:

• Frontend: Next.js, React, TypeScript, Tailwind CSS
• Backend: FastAPI, Pydantic
• Data validation: Zod, React Hook Form
• Visualization: Recharts
• Deployment: Vercel (frontend), Render/Railway/Fly/Azure (backend)

The system includes:

• A RESTful API (/api/v1/analyze)
• Local fallback logic when backend is unavailable
• Session-based authentication
• Paged loading for research feed
• Support for drag-and-drop panel reordering

Evidence: The author describes the tech stack and architecture in detail, but no information on scalability, performance metrics, or production deployment is provided.

The project is described as an MVP prototype with version 0.4.0, last updated April 19, 2026. It includes:

• Polished UI
• Backend analysis API
• Competition-ready demo flow

However, there is no evidence of:

• Real-world usage or adoption
• User feedback or engagement data
• Customer acquisition or retention metrics
• Product-market fit validation

Not evidenced: No traction signals are present in the description.

The author does not reference any competitors or existing solutions in the student wellness or academic planning space. The project is described as a hackathon submission, implying it may be an original concept rather than a direct competitor to an existing product.

Not evidenced: No competitive landscape or market positioning relative to other tools is provided.

• No real-world usage: The tool is described only as an MVP prototype with no evidence of actual users.
• Unproven business model: No pricing, monetization, or revenue strategy is evident.
• Limited scope: The current version focuses on frontend experience and research signals; full functionality remains hypothetical.
• Self-contained development: Only one team member (Minh Duy Do) is listed, suggesting limited capacity for scaling or iteration.
• No external validation: No third-party reviews, testimonials, or usage data are included.

Inference: These factors suggest a high risk of failure if the project does not gain traction or evolve beyond prototype status.

1. Has the tool been tested with real students? If so, what were the results?
2. What is the plan for transitioning from rules-based to machine learning models?
3. Are there any plans to monetize the product or build a sustainable business model?
4. How do you intend to scale beyond the current prototype and hackathon context?
5. Have you considered privacy implications of collecting personal schedule data?

Note: These questions are based on the author's own claims and are intended to probe for deeper truths behind the self-reported narrative.