Pitch Framework — MYHack ISNA 2026

Before you present

Judges aren't grading your code.

They're grading whether you understand a real problem, built a thoughtful and differentiated solution, and show real potential for impact. "People don't buy products; they buy solutions to problems." Use the framework below to prepare — it maps directly onto the judging rubric.

The framework

10 steps, one story.

This is the order judges expect your pitch to follow. Tap each step to expand it.

1. Begin with the Problem (Why?)

What problem are you solving, and who exactly experiences it?
Why does it matter — how widespread or painful is it?
Start with the problem, not your app.

2. Define Your Target User

Never "for everyone" — describe your ideal user specifically.
Age, occupation/role, community, current challenges.
Existing alternatives, and why they fall short.

3. Validate the Need

Conversations with potential users, surveys, or interviews.
Community observations, existing market demand, research.
Show judges what you learned — don't just tell them what you think.

4. Show Your Research

What products already exist? What do users like about them?
What frustrates people about current options?
What gap did you find that they missed?

5. Explain Your Unique Insight

Why you, and not the other 100 products already out there?
Better algorithm, personalization, workflow, UX, matching, automation, or accessibility.
"Everything in one place" isn't a real advantage — dig deeper.

6. Explain Your Algorithm or Decision Process

Don't just demo features — explain the thinking behind them.
How do you recommend, personalize, prioritize, match, or learn from behavior?
This is where the real innovation lives.

7. Demonstrate the Product

Show a realistic user journey — not every screen you built.
e.g. "A student searching for a local internship gets personalized matches based on location, interests, skills, and availability."

8. Discuss Trade-offs and Challenges

What obstacles did you hit, and what compromises did you make?
What limitations still exist, and what would you improve with more time?
Judges respect honesty over "everything is perfect."

9. Think Beyond the Hackathon

Start with a wedge: "we begin by serving one community well."
Then grow — local masjids → regional Islamic centers → nonprofits, schools, community orgs.
Start focused. Think globally.

10. Explain the Impact

If this succeeds, who benefits and what changes for them?
Why will people's lives actually improve?
Leave judges with a memorable vision.

Get ready

Time your pitch, and know what's coming.

An 8–10 minute run of show, and the questions judges are most likely to ask afterward. Click a question once you've got a solid answer ready.

Presentation structure (8–10 min)

1 minThe Problem — what it is, why it matters

1 minThe User — who has it, how they cope today

1 minResearch & Validation — what you learned from users and competitors

2 minYour Solution — the unique insight, and why it's different

2–3 minLive Demonstration — a realistic user scenario + the key algorithm

1 minChallenges & Trade-offs — obstacles, and what's next

1 minVision & Impact — where this goes from here

Questions judges will ask

✓What exact problem are you solving?
✓Why is this problem important?
✓Who is your target user?
✓How do people solve this today?
✓Why are current solutions insufficient?
✓What research did you conduct?
✓What makes your solution unique?
✓Why is your algorithm better?
✓How did user feedback shape your design?
✓What challenges did you overcome?
✓With another six months, what would you build next?
✓How could this become sustainable, as a product or business?

Avoid these

Common mistakes that cost teams points.

✕

Starting with tech, not the problem

✕

Claiming it's "for everyone"

✕

Assuming no competitors exist

✕

Showing every screen, not the value

✕

Features over user outcomes

✕

Skipping user research & validation

✕

It's not about the most sophisticated app in 24 hours.

It's about understanding a meaningful problem, listening to real users, researching what already exists, and building a thoughtful prototype that delivers real value. Use AI to move fast — let curiosity, empathy, and craftsmanship define the product.

Ready to lock in your pitch?

View the full rubric → Read the submission guide