FusionEd: Campus Management System

FusionEd: Campus Management System is a self-reported project by one individual (KAUSTUBH DESHPANDE) submitted to the OpenAI 2026 hackathon. The author describes it as an ERP-like system for colleges, aiming to centralize attendance management, notices, calendars, and other administrative tasks. It is built using React, TypeScript, Tailwind, and Supabase.

The description states that the project was built in a short timeframe (presumably during a hackathon), with no evidence of revenue, customers, or traction. The author claims to have learned how to prompt and use AI effectively, and that the system can be rented to institutions at low cost, but provides no data to support these claims.

• The description states that FusionEd is a campus management system, designed to centralize college administration tasks.
• It includes features such as attendance management, notices, calendars, and day-to-day college operations.
• The system is described as having faculty, HoD, and administration roles, with attendance marked by teachers instantly reflected across the platform.
• It is built using React, TypeScript, Tailwind, and Supabase.

Note

This is a self-reported description. No independent verification or demonstration of functionality exists beyond the author’s account.

• The author positions FusionEd as a solution to inefficiencies in current college ERP systems, particularly around attendance tracking.
• It is described as addressing the problem of manual attendance updates and information loss due to lack of backup or real-time updates.
• The system is framed as an alternative to traditional ERP systems, using modern web technologies like Supabase for backend.

Inference The positioning suggests a move from fragmented communication (e.g., WhatsApp groups) to a centralized digital platform. However, this is a claim, not a fact.

• The target customer is described as colleges and educational institutions.
• The system is intended for use by faculty, HoDs, and administration.
• The author mentions the goal of renting it to institutions, implying a B2B model.

Note

No evidence of actual customers or institutional partnerships exists. The description does not clarify whether the target customer is K-12, higher education, or specific types of colleges.

• The author states that FusionEd will be rented to institutions at dirt cheap prices, with pricing varying based on selected features.
• There is no evidence of pricing tiers, revenue model, or monetization strategy beyond the author’s self-reported intention.

Inference The business model appears to be SaaS-based, but no details are provided about how it will be sold or priced.

• Built with React, TypeScript, Tailwind, and Supabase.
• The system is described as using "vibe coding", which may refer to rapid prototyping or AI-assisted development.
• It is claimed that the system was built in a short time (presumably during a hackathon).
• Challenges included using Supabase instead of traditional ERP backend systems.

Note

No evidence of scalability, security, or production readiness. The use of Supabase suggests a modern, serverless approach, but no deployment details are provided.

• Not evidenced.
• The project is described as a hackathon submission, with no mention of user testing, feedback loops, or real-world usage.
• No evidence of customer acquisition, retention, or revenue generation.

Absence of evidence

There is no indication that FusionEd has moved beyond the prototype stage or has any traction.

• Not evidenced.
• The author does not reference existing ERP or campus management systems.
• No competitive analysis or differentiation strategy is provided.

Absence of evidence

No information on competitors, market size, or positioning in the broader education technology landscape.

• The project is a single-person hackathon submission, with no team or external validation.
• The author claims to have used AI for development ("how to prompt", "correct use of AI") — this may indicate a lack of deep technical or product experience.
• No evidence of real-world testing, user feedback, or adoption.
• The business model is highly speculative, with no pricing, customer data, or revenue projections.

Inference The project lacks commercial viability indicators and may be in early conceptual stages.

1. What specific problems in current college ERP systems are you solving, and how do you know?
2. Have you tested this with any real users or institutions?
3. How does the pricing model work, and what features are included in each tier?
4. What is your plan for scaling beyond a single developer?
5. Are there any existing partnerships or pilot programs with colleges?