Evaluation Framework

Submissions will be evaluated across two components:

• Business Case Submission- 70% weightage
• Prototype Demonstration- 30% weightage

The business case will be evaluated on the strength of the insight, quality of the proposed solution, business impact, feasibility and scalability.

The prototype will be evaluated on how effectively the team brings the proposed solution to working experience, demonstrates the core user journey and leverages the available Swiggy MCP capabilities.

Expected Submission

a. Business Case Submission - 70% Weightage

Teams will submit a presentation of up to 5 slides covering:

• Campus Insight: The student behaviour, unmet need, operational challenge or business opportunity identified by the team.
• Proposed Solution: The solution could be a product, AI-powered solution, tool, automation, marketing intervention, partnership, operational improvement or community-led initiative.
• User Journey & Experience: How the proposed solution would work in practice, including how students, restaurant partners, delivery partners or internal teams would interact with and benefit from it.
• Business Impact: The potential impact on Swiggy and its ecosystem. This could include adoption, transactions, frequency, retention, revenue, cost savings, operational efficiency, productivity or customer experience, depending on the solution.
• Execution Plan: How the solution can be piloted and scaled, including the implementation approach, estimated cost, dependencies, risks and measurable success metrics.

Primary Research Requirement

Each submission must include at least one form of campus-level validation, such as:

• Student survey
• Student interviews
• Campus observations
• Small experiment
• Prototype or concept test

Teams should highlight the key insight from their research and explain how it influenced the proposed solution.

b. Prototype Submission - 30% Weightage

Teams must submit a short video walkthrough of a functional or simulated prototype (preferably a webapp) that demonstrates how their proposed solution would work in practice.

The prototype should bring the proposed business case to life- it is not a separate idea.

Teams should demonstrate:

• Problem-Solution Fit: How the prototype addresses the problem identified in the business case.
• Core User Journey: How the intended user interacts with the solution from start to finish.
• Swiggy MCP Usage: Teams should use the available Swiggy MCP capabilities wherever relevant.
• Feasibility: The prototype should demonstrate the core functionality or experience. A production-ready application is not required.

Submission Format: A video walkthrough of the prototype, clearly showing the key use case and user journey.

Consent & Usage:

Any prototype or material submitted as part of the competition must not be published, showcased, or shared on any public platform by participants without prior approval from Swiggy. Any such publication or showcase will be subject to applicable internal reviews and approvals from Swiggy.