AlterScore

The description states that AlterScore is an educational financial-readiness assessment. It uses a mix of short calculations, judgment questions, and connected scenarios. Users make decisions in one situation that affect future situations within the same assessment.

It does not use isolated multiple-choice questions but instead tracks financial state changes (e.g., available cash, obligations, emergency savings) as users progress through the assessment. The final score is derived from a formula that evaluates how well users managed their resources across the full path of decisions.

The system includes:

• A frontend built with React, Vite, and CSS.
• A backend built with FastAPI, Python, and Pydantic.
• One-time attempts to prevent duplicate submissions.
• Signed, redacted summaries for verification without exposing personal data.

Not evidenced: whether this is a web app, mobile app, or other delivery method; no mention of monetization or pricing.

The description states that AlterScore aims to move beyond traditional quizzes by showing users where their financial knowledge stands and why. It emphasizes:

• Learning over judgment.
• Practical money situations (e.g., paying bills, handling unexpected expenses).
• Avoiding identity-based scoring like credit scores.
• Transparency in how the score is calculated.

It explicitly positions itself as an educational tool—not for lending decisions or professional advice.

Inferences:

• The product may be positioned to appeal to educators, financial literacy organizations, or individuals seeking self-assessment.
• It avoids traditional financial scoring models (e.g., credit scoring), which could differentiate it from competitors but also limits its perceived utility in certain contexts.

Not evidenced: how the positioning compares to existing tools in the market; no claims about user adoption, retention, or impact metrics.

The description states that AlterScore is meant for:

• Students
• First-time earners
• Anyone trying to become more confident with money

It also mentions that it avoids judging people based on salary, identity, credit history, or documents—suggesting a broad but non-traditional audience.

Inferences:

• The target segment likely includes young adults or those new to financial independence.
• It may be used in educational settings or as a personal development tool.

Not evidenced: specific customer personas, segmentation strategies, or usage patterns beyond the stated user groups.

The description does not provide any information about:

• Revenue streams
• Pricing models
• Monetization strategy
• Paid features or tiers

It states that AlterScore is meant for learning and does not decide whether someone deserves a loan, predict repayment, or replace professional financial advice.

Inferences:

• The product may be free-to-use with no direct monetization.
• Future versions might include premium content or subscriptions, but this is speculative.

Not evidenced: business model, pricing structure, or commercial viability.

The project was built using:

• Frontend: React, Vite, CSS
• Backend: FastAPI, Python, Pydantic
• Tools used during development: Codex, GPT-5.6, GitHub Actions, Docker, Hugging Face Spaces, OpenAI Codex, etc.

Key technical features include:

• Tracking of financial state changes across user decisions.
• Deterministic scoring based on user paths.
• Secure one-time attempts and signed results.
• Use of API endpoints and state management for connected scenarios.

Inferences:

• The system is built with modern web technologies.
• It supports complex logic involving interdependent decision-making.
• There is a focus on privacy and verifiability.

Not evidenced: scalability, performance data, or deployment architecture beyond the tools mentioned.

The description states that this was submitted to the OpenAI 2026 hackathon. It includes:

• A working prototype
• Testing of full assessment functionality
• User feedback loop planned for future development

Not evidenced: actual users, customer acquisition, retention rates, or revenue.

Inferences:

• This is a pre-product stage.
• The team has demonstrated technical capability and conceptual clarity.
• No evidence of product-market fit or commercial traction.

The description does not mention any competitors. It does not reference existing financial literacy tools, quizzes, or educational platforms.

Inferences:

• There may be no direct competitors in the specific niche of scenario-based financial assessments.
• However, there are likely other financial literacy tools and quizzes that could overlap with its goals.

Not evidenced: competitive landscape, market size, or differentiation from similar offerings.

Key risks identified from the description:

1. Lack of commercial traction: No evidence of users, revenue, or adoption.
2. Unclear monetization strategy: No indication of how the product will generate value or income.
3. Limited scope and maturity: Built as a hackathon project with no indication of long-term development plans.
4. Privacy vs. utility trade-offs: While privacy is emphasized, it's unclear if this limits usefulness or scalability.
5. User engagement assumptions: The description assumes users will engage with the full assessment, but there’s no evidence of actual usage.

Not evidenced: risk mitigation strategies, user feedback loops, or market validation beyond internal testing.

1. What is your plan for validating user engagement and learning outcomes?
2. How do you intend to scale beyond a hackathon prototype?
3. Are there any plans for monetization or revenue generation?
4. Have you tested the product with target users (students, first-time earners)?
5. What are the key assumptions about user behavior that underpin your design choices?
6. How do you plan to address potential issues around decision consistency and scenario logic?
7. Is there a roadmap for localization or regional adaptation?