Start with the person, not the stack
Most of us open with the tech: “It's a Laravel app with MySQL and…” The listener has nothing to hang that on yet. Start with who it helps and what was hard for them: “Our barangay health center tracks check-ups on paper, so follow-ups get missed.”
Then say what your project does in one sentence: “Our system reminds patients by SMS and shows the nurse who is due this week.” If it doesn't fit in one sentence, you're listing features, not the job the app does.
Show one proof, then stop
Pick one thing that shows it works: a screen, a number you actually measured, or one user's reaction. “We tested it with two nurses for a week” lands better than ten features.
End with what you want from the listener: feedback on the flow, the question they'd ask, or simply “Ask me anything about it.” Then stop talking. Silence after a pitch is normal; hindi ibig sabihin na pangit.
Practise out loud, not in your head
Set a 60-second timer and record yourself on your phone. Watch it once for what you said, then once on mute for posture and hands. The first take will feel awkward. That's why you do it here and not in front of the panel.
Count your fillers (“uhm”, “parang”, “so yeah”). Don't try to remove all of them; swap the worst one for a short pause. Do three takes, keep the best, and post it in Pitch Practice if you want kind, specific feedback.