PathPilot AI

The description states that PathPilot AI is an AI-powered education and career guidance platform. It enables students to:

• Create profiles with information such as intended major, extracurriculars, leadership experiences, projects, skills, and interests.
• Receive personalized AI mentorship.
• Generate customized career roadmaps.
• Be recommended verified scholarships, internships, competitions, volunteer positions, and educational programs.
• Save opportunities they are interested in.

The platform is built using Next.js 15, TypeScript, Tailwind CSS, Supabase, and OpenAI APIs (GPT-5.4 Mini and GPT-5.6 Terra). It includes an “Opportunities Hub” that uses deterministic profile matching with a curated database of verified opportunities.

Inference The platform appears to be a full-stack web application designed for student users, integrating AI for personalization and structured data for trust in recommendations.

The author states that PathPilot AI was inspired by their own struggle to find meaningful opportunities as a high school student. The platform aims to help students discover opportunities before missing deadlines while offering personalized guidance.

Inference The positioning is centered on solving a personal pain point — the difficulty of finding relevant, time-sensitive opportunities. The platform positions itself as a tool that bridges the gap between student profiles and opportunity discovery.

The description states that PathPilot AI targets students, particularly those in high school or early college, who are seeking scholarships, internships, competitions, volunteer positions, mentorship programs, and educational opportunities.

Inference The primary customer is a student user base with interests in education and career development. The ICP appears to be students who are proactive about planning their futures but lack time or tools to efficiently find relevant opportunities.

No evidence of pricing, monetization strategy, or business model is provided in the description.

Inference The platform is described as a prototype or hackathon project. There is no indication of how it would be monetized, whether through subscriptions, freemium models, partnerships, or other mechanisms.

The platform was built using:

• Frontend: Next.js 15, TypeScript, Tailwind CSS
• Backend: Supabase (for authentication and database)
• AI Tools: OpenAI APIs (GPT-5.4 Mini, GPT-5.6 Terra), Codex
• Other Tech: React, Node.js, PostgreSQL, Vercel

The author mentions using deterministic matching to improve trust in recommendations.

Inference The technical stack suggests a modern, full-stack web application with AI integration and structured data handling. The use of Supabase and Vercel indicates a focus on rapid development and deployment.

There is no evidence of traction, revenue, or customer adoption in the description.

Inference The project is described as a single-developer hackathon submission with no prior users or business activity. It has not been scaled beyond its initial prototype.

No competitive analysis or market context is provided in the description.

Inference There is no evidence of existing competitors or market positioning. The author does not reference similar platforms, suggesting either limited awareness or lack of market research.

• Single-founder project: The platform was built by one person, which raises questions about scalability and long-term maintenance.
• No traction or revenue: No evidence of users, adoption, or monetization.
• Unverified opportunities: The platform relies on a curated database of verified opportunities, but no details are given about how this curation is done or maintained.
• AI integration risk: The use of AI for guidance and recommendations may be limited without sufficient training data or user feedback loops.

1. What is the source of the verified opportunity database, and how is it curated?
2. How many students have used the platform, and what is their engagement level?
3. Are there any partnerships with schools, universities, or organizations that provide opportunities?
4. What is the plan for monetization and scaling beyond a single developer?
5. How does the deterministic matching system handle edge cases or new types of opportunities?
6. What are the technical challenges in maintaining and updating the platform at scale?