funding · Guide
How to Prepare a Startup Competition Pitch for Judges
Turn judging criteria into a timed pitch, rehearse questions and prepare a version that works if the demo fails.

A judge hears several short presentations in a row. They do not have time to reconstruct a business from impressive slides or to infer what the speaker tested. They need an understandable case they can score under the event's rules, followed by answers that hold up when challenged.
Prepare from the scorecard and time limits. Turn each material claim into a proof point, build a timed story, and practice questions with someone who can identify unsupported claims. A pitch that earns trust can show where the company is uncertain without sounding evasive.
Key Takeaways
- Read the judging criteria, timer, presenter rules and disclosure policy before building slides.
- Give the judge a clear claim and matching evidence for each material criterion.
- Practice a compact answer to likely questions about customers, evidence and risks.
- Prepare an offline or verbal version that preserves the important claims if a demo fails.
Read the event as an evaluator would
Find official rules, current judging materials and competitor instructions. Note whether judges score criteria individually, rank overall investment potential or use different systems for different rounds. Capture presentation time and whether questions are counted in that time. Confirm who can present, accepted media and who can see the pitch or recording. A brilliant presentation in the wrong format can breach requirements before it is considered on the merits.
For an example, the Rice Business Plan Competition's 2026 judge instructions describe a timed full pitch and a separate question period. The event's published rules and format distinguish multiple pitch types and attendance expectations. Use the relevant edition's documents rather than treating those formats as universal. Different time limits call for different content, even if the business and core evidence are the same.
Build a sheet with criterion, claim, proof and likely challenge. For “commercial opportunity,” a founder might claim one narrow buyer group experiences a costly delay, supported by recent workflow observations and a paid pilot. For “execution,” the evidence may be a prototype and named people who delivered it. If the event asks for social or environmental benefit, show the specific outcome, how it is measured and the limits of what has been observed.
Make the first minute useful
Open with customer, job and consequence. For a fictional maintenance company: “A shift supervisor often finds out about a failing pump only after the line slows. Our retrofit kit flags a change in vibration and records it against that machine. We are testing whether maintenance staff can confirm the warning without stopping unrelated equipment.” The judge now knows the buyer's setting, what the product does and what remains unproven.
Follow with an example of the current alternative. Show the cost or inconvenience in a way that the audience can check. Quantify only what you can support and label illustrative estimates. A market slide can be useful after the buyer and repeatability are clear. Leading with an aggregate market number can leave judges unable to connect the headline to a purchasing decision.
Put the strongest evidence early enough that it survives a shortened pitch. If you have seconds, make one claim and give one proof point. If you have ten minutes, show how the proof was obtained, whether it applies beyond one customer and which milestone would increase confidence. Practice both versions. Do not take a longer deck and rush through all the same slides.
Build a timed arc and a backup
For an illustrative six-minute slot, reserve roughly one minute for the problem and current alternative, one for how the product works, two for evidence and market, one for the team and risk, and one for the requested next step. This is a rehearsal plan, not a recommended rule for every contest. Change it based on scoring. A technical review might need more time for evidence and constraints; a short speech might have no slides at all.
Make each slide earn its place. A diagram can show what happens in a customer's current process and where the product changes it. A chart can show a measured result if it has a defined axis, units and test conditions. An image of an imagined product should be labelled as a prototype rendering. Use readable figures and rehearse from the back of the room, not only on a laptop. Follow file naming and submission rules.
Live demos should have a failure mode. Prepare a short video or screenshots if permitted, and a narration that works without either. Test adapters, contrast and offline playback in advance. If hardware needs handling, confirm rules and practice showing it without blocking the audience. If failure prevents the main proof point from appearing, add a single clearly labelled backup slide that shows the evidence rather than apologizing for the missing software.
Rehearse skeptical questions, with limits
Ask someone unfamiliar with the company to judge the pitch, then ask a technical or commercial colleague to challenge assumptions. Capture where they disagreed or missed evidence. If both ask who pays, the presentation probably has a missing buyer. If one questions the test setup, prepare a brief response describing how it was run and what it does not prove. The aim is to find ambiguity before it affects the score.
- “Who has paid?” Answer with number, period and status. Separate a paid pilot from a customer who renewed.
- “What stops a competitor?” Describe actual barriers such as integration effort, distribution or evidence, and acknowledge where the advantage is still untested.
- “What happens if the main assumption fails?” State the test you will run and what decision the result will trigger.
- “What would you do with the prize?” Connect the money or resource to a specific test, and avoid claiming an award is guaranteed.
- “How big is the market?” Define the reachable segment and the assumptions used to calculate it.
Give the short answer first, then supporting detail. If you cannot verify the fact, say what you know and how you will find out. You can reply, for example: “We have tested with two sites. We don't yet know whether this works with mixed equipment; the next trial is designed to answer that.” Judges can evaluate a clear limit. They cannot evaluate an answer that changes the subject.
Practice answers for mixed audiences
Judges may come from different backgrounds. An engineer might want to know what the technology measures, an operator how it fits the shift, and an investor what must change for sales to repeat. Use short answers grounded in the same evidence. Say what was observed, give context and stop after addressing the question. If more detail is useful, offer it. Rehearse a plain-language explanation and an additional technical sentence so the team can choose the right level without changing the facts.
Have both presenters rehearse the handoff if the rules require multiple speakers. Agree which person starts an answer, when the other adds information and how to acknowledge a question you cannot answer. A teammate can handle the financing question without contradicting the prototype claim. Use a practice moderator to enforce time. A calm delivery under a shorter clock is a better fallback than simply asking a speaker to talk faster.
Build an evidence card for internal rehearsal. For each number, include its period, denominator, source and approved phrasing. For instance, “three pilot facilities used the prototype” is different from “three customers paid,” and “cut setup time in a controlled test” does not describe site-wide productivity. Mark anything you must not disclose. Then run a practice round with one intentionally misunderstood claim. A useful response gently corrects the premise before answering, so a judge leaves with the right information rather than a confident but misleading figure.
Worked example: revise for the scorecard
A hypothetical team enters an event scored on relevance, customer evidence, delivery and team. Its first pitch spends half the time on a technical demonstration and never says which budget pays for installation. The practice judge likes the demo but cannot score customer evidence because the team uses “partner,” “site” and “customer” interchangeably. The team reorders slides around the maintenance lead, names the procurement decision, and distinguishes two trial sites from the single paid contract.
It then replaces a blanket performance claim with a test record, including conditions and a false-alarm limit. The last slide names the next milestone: demonstrate acceptable performance over a defined monitoring period with mixed equipment. The ask is access to the right test environment, rather than unspecified “connections.” That reads as a plan the judge can assess even if the technology is unfamiliar.
Practice speaking the revision with and without slides. If a question about renewal arrives, the founders answer from a dated basis: one paid installation and no renewal decision yet. That response preserves the commercial claim and makes its scope clear. It also sets up a meaningful discussion about what evidence the team needs before growing.
Before the event, review the entry and attendance tradeoff in how to choose startup competitions. On the day, concentrate on the evidence and the clock. A judge should leave able to state whom you help, what you proved and what would make the next step worth the risk.
