OpenAI 2026 hackathon

PHQ.new - Personal Health Questionnaire

Mental Health screening should't reduce a patient to a single number. The current PHQ-9 was created in 1999. We need to use an adaptive and modern one using current tech to really help people. HELP!

Solo project by Brian Pointer · 1 likes · 0 comments

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 #1,658 place in the like-ranked listing is a tie-break inside that group, not a ranking.

Projects (log scale)

1
10
100
1k
10k
05,592
11,758
2285
3–4132
5–975
10+14

Likes on Devpost. ▲ marks this project's group.

Show the figures
LikesProjectsShare of archive
05,59271.2%
11,75822.4%
22853.6%
3–41321.7%
5–9751.0%
10+140.2%
Devpost like counts for all 7,856 archived projects, captured when this archive was built.

Executive Summary

What the company appears to be

PHQ.new is a self-reported mental health screening tool built using AI (specifically Codex and GPT-5.6) that aims to modernize the PHQ-9 questionnaire, which was created in 1999. The author states it uses an adaptive questioning system to gather information corresponding to the domains evaluated in the original PHQ9 form. It is intended for use by patients before clinical sessions and to generate reports for doctors.

What changed

The project description indicates a shift from a static, single-number scoring system (PHQ-9) to an AI-assisted adaptive questionnaire that collects richer data and generates detailed clinical reports. The author emphasizes the need for updated tools in mental health care due to outdated methods.

Single most important open question — commercial due-diligence read

Is there any evidence of a viable path to market, including customer validation, regulatory compliance (especially HIPAA), or integration with existing healthcare systems? The description provides no information on these critical aspects.

Back to contents

What The Product Actually Is

The description states that PHQ.new is an AI-powered mental health screening tool designed to replace the PHQ-9 form. It leverages large language models (LLMs) like Codex and GPT-5.6 to ask adaptive questions based on the original PHQ-9 domains. The system compiles responses into a report for doctors, including estimated scores, graphs over time, clinical portraits, follow-up suggestions, and raw transcripts.

Inference The product is described as a digital tool that automates part of the mental health assessment process, but it is not clear whether it functions as a standalone application or integrates with existing platforms. The author also mentions using AI for code development, suggesting the tool may be built on a web interface using technologies such as Node.js, HTML5, CSS3, and JavaScript.

Back to contents

Positioning & Claim Evolution

The author positions PHQ.new as an evolution of the outdated PHQ-9 form, which they describe as reducing complex human experiences to a single number. They claim that current mental health screening lacks nuance and fails to reflect the full scope of patient needs. The tool is framed as a way to improve care by providing more context and depth in assessments.

Inference The positioning reflects personal motivation rooted in trauma and family support, rather than market research or clinical validation. It appears to be driven by empathy and a desire for change, not strategic positioning or competitive analysis.

Back to contents

Target Customer & ICP

The description states that PHQ.new is intended for use by patients prior to clinical sessions, with the goal of helping doctors better understand their patients' conditions. The tool is meant to assist clinicians who are "stretched too thin" and need more efficient ways to assess mental health.

Inference The primary users appear to be both patients (who complete the questionnaire) and healthcare providers (doctors or therapists). However, no specific segmentation or targeting criteria are provided beyond general categories like mental health professionals and individuals seeking help.

Back to contents

Business Model & Pricing Evidence

There is no evidence of a business model or pricing structure in the description. The author does not mention monetization strategies, subscription models, or any revenue streams.

Inference The project seems to be in early conceptual or prototype stage, with no indication of commercial viability or monetization plans.

Back to contents

Technical & Delivery Signals

The tool was built using Codex, GPT-5.6, HTML5, CSS3, JavaScript, and Node.js. The author notes that AI was used extensively for brainstorming, coding, testing, and even emotional support during development.

Inference While the technology stack suggests a web-based application, there is no evidence of deployment, scalability, or technical architecture beyond what was described in the submission. The use of LLMs implies potential integration with APIs, but no details are given about how this would be implemented securely or at scale.

Back to contents

Traction & Maturity Signals

There is no evidence of traction, customers, revenue, or adoption. The project is presented as a hackathon submission and has not progressed beyond the idea stage. The author explicitly states that they cannot continue working on it alone and hope others will take it forward.

Inference This is an early-stage concept with no demonstrated product-market fit or user engagement. It lacks any form of market validation or pilot testing.

Back to contents

Competitive Context

The description does not provide information about competitors or the broader mental health tech landscape. The author mentions the PHQ-9 as the current standard but does not reference other tools or platforms that might address similar needs.

Inference There is no evidence of competitive analysis or awareness of existing solutions in the mental health screening space, which raises questions about market understanding and differentiation.

Back to contents

Key Risks & Red Flags

  1. Regulatory Compliance Risk (HIPAA): The author acknowledges HIPAA as a major challenge and expresses uncertainty about finding an LLM provider that meets safety requirements.
  2. Lack of Technical Depth: The project relies heavily on AI for development, but there is no evidence of robust engineering practices or scalability.
  3. No Commercial Viability: No business model, pricing, or customer base are evident.
  4. Founder Dependency: The entire project appears to be driven by a single individual with limited technical background and no team structure.
  5. Unproven Impact: There is no demonstration of effectiveness or impact beyond the author’s personal experience.

Back to contents

Diligence Questions To Ask The Founders

  1. What specific clinical workflows will PHQ.new integrate into, and how does it align with current healthcare practices?
  2. How do you plan to ensure compliance with HIPAA and other data protection regulations?
  3. Have you validated your approach with mental health professionals or patients? If so, what feedback did you receive?
  4. What is the intended user experience for both patients and clinicians?
  5. Are there any partnerships or pilot programs in place with healthcare providers or institutions?
  6. How do you plan to scale beyond a single developer’s involvement?

Back to contents

Investment/Partnership Verdict

Not evidenced.

The description provides no evidence of traction, revenue, customers, or even a clear product roadmap. The project is presented as a personal endeavor with limited technical execution and no commercial strategy. While the idea has emotional resonance and potential societal value, there is insufficient evidence to assess its viability for investment or partnership.

Confidence Level Very Low This analysis is based entirely on self-reported information from one source — the author’s own account. No external validation, data points, or third-party confirmation are available.

Back to contents

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.