ScheduleRU

Note: This analysis is based entirely on the self-reported project description provided by the authors. No independent verification, traction data, revenue figures, or customer feedback are available.

The description states that ScheduleRU is a tool that:

• Auto-schedules four-year academic plans
• Filters through over 500 class combinations per semester
• Supports multiple programs of study and double majors/minors
• Allows users to plan around a wishlist of courses without committing to full programs
• Includes quality-of-life features

It was built using cloudflare, css, html5, javascript, node.js, git, github, and reportedly with assistance from AI tools like Codex.

Inference: The product appears to be a web-based scheduling application aimed at students navigating complex university course structures. It is not evidenced to have any revenue model or monetization strategy beyond its initial development phase.

The author positions ScheduleRU as:

• A solution to "legacy scheduling systems" at colleges
• A way to reduce the time spent on scheduling from hours to minutes
• A tool that supports students in planning for double majors and minors
• An alternative to fragmented, outdated tools used by universities

It evolved from a personal problem-solving effort into a scalable idea with ambitions to integrate into university systems.

Claim: The author claims that the tool was developed during a hackathon and has already gained traction among ~400 Rutgers students via word-of-mouth. However, no independent validation or data on usage is provided.

The description states:

• Primary users are college students, especially those at large public universities like Rutgers
• The tool supports students who want to pursue double majors or minors
• It targets individuals planning four-year academic paths

Inference: Based on the author's own experience and stated goals, the primary ICP is incoming or current undergraduate students at large state schools with complex course requirements.

No evidence of a business model or pricing strategy is provided in the description. The authors mention no revenue streams, subscriptions, or monetization plans.

Claim: There is no indication that ScheduleRU has begun generating revenue or intends to do so through paid services.

The project was built using:

• Frontend: HTML5, CSS
• Backend: Node.js
• Infrastructure: Cloudflare
• Version control: Git, GitHub
• Development process: AI-assisted workflows (Codex)

It reportedly involved scraping thousands of prerequisites and managing complex logic for course sequencing.

Inference: The technical stack suggests a basic web application with backend logic. The use of AI tools implies a rapid development approach but does not indicate scalability or robustness in production environments.

The description states:

• ~400 students signed up to use the product within two weeks of development
• A waitlist has been started
• The team is in talks with Rutgers University for beta testing and implementation
• Plans to expand to other universities (e.g., Michigan, Georgia Tech, UC system)

However, no actual user data, retention metrics, or adoption rates are shared.

Claim: While there is anecdotal evidence of interest and early engagement, there is no verified traction or measurable impact on student outcomes.

The description does not provide any information about competitors or existing solutions in the market. It focuses solely on the problem of legacy scheduling systems and how ScheduleRU addresses it.

Inference: The competitive landscape remains unknown; however, given the nature of the tool, it likely competes with university-provided scheduling tools or third-party platforms that offer similar functionality.

• Unverified traction: No independent data on user numbers, engagement, or adoption.
• No revenue model: No indication of how the product will generate income.
• Limited technical maturity: Built in a short timeframe during a hackathon; no evidence of long-term stability or scalability.
• Dependency on AI tools: Reliance on AI for development may not translate into sustainable engineering practices.
• University integration claims: The claim of being in talks with Rutgers lacks confirmation.

Red Flag: Lack of concrete evidence regarding product-market fit, user behavior, or real-world deployment.

1. What specific data sources are used to build and validate the scheduling logic?
2. How many students have actually used the tool beyond the initial group of ~400?
3. Has Rutgers University confirmed any formal interest in integrating ScheduleRU into their system?
4. Are there any technical limitations or known bugs that affect real-world usage?
5. What is the plan for handling different university systems and data formats?
6. How will the product evolve beyond its current scope (e.g., club recommendations, etc.)?