Startup Launch Arena
BUILD. PITCH. PROVE.
Start with a problem. Build something people can use. Pitch a product that proves its potential.
01 The challenge
Not an idea contest. A product test.
Propose a real problem, build one working core feature, demonstrate your MVP, and present the path toward a potential startup.
A
Pick a Problem
Choose from a curated catalogue of startup problems drawn from Y Combinator’s requests for startups — a shortcut to problems worth solving.
Browse 13 Challenges in Catalogue →B
Bring Your Idea
Submit your own original idea. Show a real problem, a clear target user, a plausible solution, a practical workflow and a path to a useful product.
Choosing a track does not approve an idea — every submission is reviewed by the panel.
02 How it works
Nine steps from problem to podium.
Discover the challenge
Join the launch session to understand startup mechanics, competition rules, and what an authentic MVP is.
Register & questionnaire
Pick a track (Track A or B) and submit your idea. Teams must have 3-4 members registered before October 22.
Panel feedback
Rolling evaluation: Approved with feedback, or direction to pivot within 24–48 hours.
Pitch 1
Early concept & problem validation pitch in NIC-style format. Exact date to be announced.
Build the MVP
Build one working core feature. Mandatory weekly SHOWDOWN PULSE progress updates.
Submit Startup Launch Pack
By November 9: working demo link or video, pitch deck, Startup Brief, business model, financial plan, validation, roadmap, and team contributions.
Demo Day & final pitch
Live demo tables showcasing working prototypes, followed by stage pitches and judges’ Q&A.
Voting & panel evaluation
Audience votes combined with jury scores across problem clarity, solution quality, MVP completeness, and pitch delivery.
Top three announced
The three strongest teams and MVPs are awarded at the Grand Finale on November 15.
03 — Official timeline · 2026
The master plan.
04 What counts as an MVP?
One working core feature. Not just an idea.
An MVP (Minimum Viable Product) is a working version of a product that demonstrates at least one core feature solving a specific problem for its intended user.
It must demonstrate something that actually works. It does not need to be a complete, mature, or commercially polished product. It may be a web application, AI product, mobile app, hardware prototype, or research-oriented system.
⚠️ A presentation alone does not qualify
A slide deck explaining a concept, a set of static Figma screens, or a video of an unimplemented idea is not sufficient on its own. Teams must clearly identify what works, what is simulated, and what remains unfinished.
The Working Product
The actual functional software, AI agent, or hardware prototype with at least one core feature that real users can test. This is what you build during the 2-week build phase (Oct 26 – Nov 9).
The Startup Launch Pack
The complete package evaluated by the jury: your working MVP plus 9 essential supporting deliverables demonstrating customer understanding, business thinking, financial planning, and founder trajectory.
Deadline: Nov 9, 2026 · 23:59:59 PKT
05 Final Submission Deliverables
The Startup Launch Pack.
Judges evaluate not just whether your product runs, but whether your team understands the problem, the user, the costs, and the practical path forward as a real venture.
Working MVP
A functioning product or prototype with at least one working core feature solving a specific problem for real users.
Software app, AI tool, hardware device, or research prototype. Teams must clearly identify what works, what is simulated, and what remains unfinished.
Recorded Product Demo
A concise 2–3 minute video demonstrating the product live and walking through the primary user workflow.
A simple screen recording or phone camera demo is perfect. No high-budget production or professional editing required.
Final Pitch Deck
A clean 8–10 slide presentation covering problem, user, solution, demo, business model, validation, financials, team, and next steps.
Used for panel scoring and stage presentations at the Grand Finale on November 15.
Startup Brief
A 1–2 page executive summary describing the product, target users, value proposition, alternatives, and go-to-market approach.
Concise documentation that gives judges instant context before reviewing your code or demo.
Business & Revenue Model
Who would use the product, who might pay for it, and how the startup creates value and generates revenue.
Subscriptions, usage-based fees, one-time purchases, or marketplace fees. Existing paying customers are not required.
Financial Forecast & Spending Plan
An estimated 3-month forecast of development, hosting, API, hardware, and operating expenses alongside expected revenue.
Realistic estimates are completely acceptable. Clearly state the assumptions behind your numbers. No private bank statements required.
Customer Validation
Evidence from user interviews, surveys, prototype testing, or pilot feedback proving the problem is real and the solution is needed.
Report honest findings and user reactions. Never invent customers, survey responses, or traction.
Next 90-Day Roadmap
A practical post-Demo Day plan outlining product improvements, customer validation milestones, and resources required.
Shows judges your team has clear direction and momentum beyond the competition.
Team Roles & Contributions
A brief breakdown of how each member contributed across engineering, design, user research, business planning, and testing.
Demonstrates team chemistry and execution capability to the judges.
Risks, Limitations & Responsible Use
An honest assessment of technical constraints, dependencies, security/privacy factors, and unresolved edge cases.
Judges value intellectual honesty and self-awareness over hand-waving.
Technical Supporting Material
Source code repository, setup instructions, architecture diagram, hardware BOM, or experimental methodology.
Strongly recommended for technical or research-heavy projects to verify code authenticity.
Built for builders · Keep requirements realistic
You do not need an existing company or paying customers.
06 Weekly build updates
SHOWDOWN PULSE: Mandatory Every Week.
During the build phase (October 26 – November 9), all approved teams must submit weekly status updates through their private Team Dashboard. Reports demonstrate active momentum and allow mentors to assist before Demo Day.
- Goal set for the active sprint period
- Concrete work completed & tangible engineering progress
- Current blockers, bugs, or resource challenges
- Prioritized next steps for the upcoming milestone
- Optional demo link, video snippet, or code commit evidence
Accountability Rule
Unresponsive Teams Disqualify
Teams that miss consecutive weekly updates without notifying the organizers risk losing their Demo Day table and stage pitch slot.
06 — Pitch & Demo Day · Nov 15
From building in private to the spotlight.
*Industry guest subject to confirmation.
Confirmed
Top 3 MVPs
The main competition result, announced at the Grand Finale.
Pending organizer confirmation
Best Problem Fit
Best Use of AI
People’s Choice
07 FAQ
Questions, answered.
What is Startup Showdown?+
SHOWDOWN '26 is a startup competition where teams go from a raw idea to a working MVP and pitch it live. Teams pick a real problem from our curated challenge catalogue (Track A) or bring their own original idea (Track B), build over several weeks, and present at the onsite Grand Finale on November 15.
Who can apply?+
Any team of 3 to 4 members can register. Teams must include a designated team leader who handles all official communication and submissions. All members must be registered before the window closes on October 22 — no late additions are allowed after that.
What is the difference between Track A and Track B?+
Track A teams pick a problem from our curated startup challenge catalogue — each challenge comes with a problem brief, suggested directions, and MVP guidance inspired by real Y Combinator requests. Track B is for teams with a completely original startup idea. Both tracks follow the exact same evaluation, build, and pitch process.
Can I submit my own idea?+
Yes — that is Track B. You bring your own original startup concept. You still need to submit the idea questionnaire during the registration window (Oct 15–22) and pass the panel review before you can start building.
What exactly is an MVP?+
An MVP (Minimum Viable Product) is a working version of a product that demonstrates at least one core feature solving a specific problem for its intended user. It must demonstrate something that actually works. It does not need to be a complete or commercially polished product, and can be software, an AI application, a hardware prototype, or a research-oriented solution.
Does my MVP need to be a complete product?+
No. You are not expected to build a fully mature, production-grade business in two weeks. An MVP demonstrates depth in one working core feature rather than shallow, incomplete coverage of ten features. Focus on making one key user workflow function reliably.
Is a presentation or recorded video alone enough?+
No. A slide deck, static UI screens, or a video of an unimplemented concept does not qualify as a working MVP on its own. Your product must have at least one feature that actually functions and can be demonstrated. The recorded demo video is submitted alongside the working product, not instead of it.
What must I submit alongside the working MVP?+
Teams submit the complete Startup Launch Pack by November 9 (23:59:59 PKT): (1) Working MVP, (2) Recorded 2–3 min Product Demo, (3) 8–10 slide Final Pitch Deck, (4) 1–2 page Startup Brief, (5) Business & Revenue Model, (6) 3-Month Financial Forecast & Spending Plan, (7) Customer Validation evidence, (8) Next 90-Day Roadmap, (9) Team Roles & Contributions breakdown, and (10) Risks & Limitations analysis. Technical materials like source repos or architecture docs are optional but recommended.
Do I need existing customers, revenue, or a registered company?+
No. You do not need paying customers, revenue, funding, or a registered legal entity to compete. The financial forecast, business model, customer validation, and roadmap assess your founder reasoning, problem understanding, and assumptions — not your commercial maturity.
What should my financial plan contain?+
A simple estimated plan explaining expected development and operating costs (hosting, APIs, software tools, hardware parts), a proposed pricing model where applicable, an illustrative 3-month forecast of revenue and expenses, and the assumptions behind your figures. Estimates are completely acceptable — do not submit personal financial statements.
How can I demonstrate customer validation?+
Show how you investigated whether the problem is real and whether your proposed solution is useful. Acceptable evidence includes 5–10 user interviews, targeted survey findings, prototype usability tests, pilot user feedback, or relevant domain research. Report what you actually learned — never fabricate feedback or traction.
Can I submit a hardware or research-oriented prototype?+
Yes. The MVP may be a web or mobile application, AI agent, hardware prototype, or research-oriented product. Teams building hardware or research solutions should clearly document what is functional, include a bill of materials or experimental methodology, and record a physical demo.
What happens if some features are incomplete or simulated?+
That is normal for an MVP. Teams should be transparent and clearly identify what works end-to-end, what is simulated (e.g. mock data or manual backend handling), and what remains unfinished on the 90-day roadmap. Judges reward honesty and penalize disguised mockups.
What happens at Pitch 2 and Demo Day?+
On Demo Day (November 15), teams showcase their working products at live demo tables where judges and attendees test the MVPs. Finalist teams deliver stage pitches (Pitch 2) followed by live jury Q&A. Final scores combine jury evaluation with audience voting to determine the Top 3 winners.
How are ideas evaluated?+
A panel reviews submissions on a rolling basis from October 26, returning decisions within 24–48 hours. Ideas are judged on clarity of the problem, feasibility of the solution, team fit, and potential impact. You will receive one of three outcomes: Approved, Approved with Feedback, or Not Approved.
What happens after I submit the questionnaire?+
Your submission enters the panel review queue. You will receive an email decision — Approved, Approved with Feedback (proceed with suggested improvements), or Not Approved (with a brief explanation). Approved teams unlock the build phase starting October 26.
What does approved with feedback mean?+
Your idea is cleared to proceed into the build phase. The panel has included suggestions — these might be scope adjustments, user clarity, or a tighter MVP focus. You are not required to implement every suggestion, but they are designed to improve your final evaluation score.
Are weekly progress updates mandatory?+
Yes. All approved teams must submit weekly SHOWDOWN PULSE updates throughout the build phase (Oct 26 – Nov 9). Teams that miss multiple updates without communication risk disqualification.
How do voting and panel scores work?+
Final scores combine jury evaluation (problem clarity, solution quality, MVP completeness, pitch delivery) with an audience vote at the Grand Finale on November 15. Winners are finalized on November 13 after jury scoring, with the audience vote counted on the day.
When and where is the grand finale?+
The Grand Finale is on November 15, 2026, onsite. Teams pitch live to judges and an audience. Venue details will be announced to all registered teams ahead of the event.
Who owns the idea and code?+
You do. All intellectual property — the idea, the code, the product — belongs entirely to your team. SHOWDOWN '26 claims no equity or intellectual property rights over what you build.
How are original work and copied work handled?+
If your startup is based on an existing product or idea, you must clearly explain what new features, improvements, or enhancements your version introduces and what specific problem it solves better than existing solutions. If your idea is completely original, you must demonstrate why — explain the gap in the market or the shortfall in current solutions that your idea addresses. Submissions that are straight copies with no meaningful differentiation will not be approved.
YOUR IDEA DESERVES A REAL-WORLD TEST.
Find the problem. Build the product. Prove what it can do.
Start Your Registration →