Pitch competitions and demo days can help a startup gain visibility, test its story and begin investor conversations. They are not all the same, however. Some reward a polished competition pitch, while others are designed to introduce founders to investors, corporate partners or programme managers.
Preparation should therefore start well before the slides. Understand the audience, decide what outcome matters and build a presentation that fits the event rather than forcing a standard investor deck into every format.
Treat the process as a sequence: select a relevant event, confirm its rules, decide the desired outcome, prepare evidence, write the spoken pitch, build the deck, rehearse questions and plan follow-up. This avoids the common mistake of producing attractive slides before deciding what they need to communicate.
Choose the right pitch event
Look beyond the headline prize or the size of the audience. An event is useful when its focus, participants and expected outcomes match your startup’s stage and immediate goals.
A pre-revenue founder may benefit from feedback and accelerator exposure. A company already generating revenue may prefer an event attended by investors who understand its sector and funding stage. Startups seeking regional customers might prioritise corporate or cross-border showcases.
Before submitting an entry, check:
- The organiser and its track record
- The industries, technologies and company stages covered
- Whether the event is a competition, demo day or investor matching session
- The judging criteria and pitch duration
- Who is expected to attend
- Whether participation is in person, virtual or hybrid
- Any required travel, rehearsal or exhibition commitments
- How recordings, slides and confidential information may be used
- Whether finalists must join additional programme activities
- The official terms, eligibility conditions and current deadlines
Compare events against your actual objective. If funding is the priority, ask whether relevant investors attend and whether founders receive structured meetings. If customer acquisition matters more, examine the corporate audience and whether decision-makers participate. A large general audience may offer visibility but produce few useful conversations.
Also consider the full commitment. An event may involve selection interviews, workshops, rehearsals, exhibition duties or programme participation. Decide whether the likely value justifies the founders’ time and any travel or production work.
Malaysian ecosystem organisations such as MDEC, Cradle and MATRADE have supported different forms of startup, commercialisation and market access activity over time. Their initiatives and criteria can change, so confirm current information through the relevant official source.
For online opportunities, it can also help to understand how virtual funding conversations differ from room-based investor meetings.
Prepare the evidence before writing slides
Create an event preparation file containing the brief, judging criteria, submission instructions and your internal responsibilities. Record which founder will present, who will handle technical issues and who will capture investor details afterwards.
Gather the information likely to support the pitch:
- Current product status and customer use
- Revenue, pilot and sales pipeline records
- Market calculations and their sources
- Customer acquisition process and sales cycle
- Pricing, costs and unit economics
- Competitor and substitute analysis
- Ownership of technology and intellectual property
- Regulatory or approval requirements
- Founder roles, relevant experience and hiring gaps
- Funding need, intended use and target milestones
Check that the information is internally consistent. Revenue shown in the deck should match the underlying accounts. Customer totals should use the same definition throughout. Market claims should distinguish between the broad sector, the reachable segment and the customers the startup can realistically serve.
Decide what can be disclosed publicly. A pitch event may be recorded or attended by competitors. Remove personal data, confidential customer terms, private source code and information restricted by agreements. If a claim depends on confidential evidence, explain it at an appropriate level and prepare a more detailed version for later due diligence.
Structure a short startup pitch
A short pitch is not a compressed version of every fact about the business. It is a clear argument for why the company matters and why the audience should pay attention now.
A practical structure is:
- Opening: State the customer, problem and consequence in plain language.
- Solution: Explain what the product does and why it is meaningfully better.
- Market: Define the initial customer segment and the wider opportunity.
- Evidence: Present traction, revenue, pilots, retention or other relevant proof.
- Business model: Show who pays, what they pay for and how sales happen.
- Advantage: Explain why the company can compete and defend its position.
- Team: Connect founder experience directly to the problem being solved.
- Ask: State the funding, introductions, pilots or partnerships being sought.
The opening should be understandable without specialist knowledge. Avoid beginning with broad trends or technical architecture. Judges need to understand the customer problem before they can value the solution.
Build a clear chain of reasoning. The problem should lead naturally to the product, the target customer should fit the business model, and the traction should support the claims being made. If these elements feel disconnected, adding more slides will not solve the problem.
Use evidence carefully. Be precise about what has actually happened. A signed customer, completed pilot and informal expression of interest are not equivalent. Label forecasts as forecasts, and be ready to explain the assumptions behind them.
Time the pitch aloud. Allow space for pauses and slide changes rather than planning to finish at the final moment. Prepare shorter versions too, as event schedules can change. Identify the essential message that must survive if speaking time is reduced.
Hypothetical scenario: choosing the right emphasis
A hypothetical software startup is pitching at a corporate showcase. Its usual deck focuses on market size and fundraising, but the audience is mainly potential enterprise users. The founders adjust the story to explain the operational problem, implementation process, security controls and desired pilot. The underlying business has not changed, but the ask now fits the room.
Create a focused pitch deck
The deck should support the speaker, not compete with the speaker. Each slide should communicate one main point, with readable text and visuals that remain clear on a projector or laptop screen.
A typical short deck may cover:
- Company purpose and customer problem
- Product or service
- Target market
- Business model
- Traction and key milestones
- Competition and differentiation
- Go-to-market approach
- Team
- Funding or partnership ask
Do not add a slide merely because other startups use one. Include information that strengthens the investment case and can be explained within the available time.
Use slide titles that state the conclusion rather than merely naming the topic. “Customers reduce manual processing” communicates more than “Benefits”. The evidence beneath the title should then support that conclusion.
Charts need labels, dates and units. Financial figures should clearly identify the currency and period. If the business operates across Malaysia and other markets, distinguish current activity from planned expansion. Avoid claiming a regional presence when the company has only conducted preliminary discussions.
For market size, show how the estimate was produced. A calculation based on reachable customers and realistic pricing is often easier to defend than a broad industry figure. For competition, include the alternatives customers use today, including spreadsheets, manual work or established service providers.
Keep detailed financial projections, product architecture and market calculations in backup slides. These can support the question session without overcrowding the main presentation. Useful backup material may also cover customer cohorts, sales pipeline definitions, regulatory pathways and planned use of funds.
Check how the organiser will receive and display the file. Confirm the required format, aspect ratio, submission method and whether videos, animations or embedded fonts will work. Carry an offline copy where permitted, but follow the organiser’s latest technical instructions. Review the final exported file rather than assuming it matches the editable version.
Rehearse for in-person and virtual delivery
Good rehearsal is not memorising every sentence. It is learning the sequence well enough to recover when a slide fails, a question interrupts the flow or the allotted time is shortened.
Practise in front of people who do not know the company. Ask them to describe the business, customer and advantage after hearing the pitch once. If their answers differ from your intended message, simplify it.
Run separate rehearsals for content, timing and pressure. During a content rehearsal, improve clarity and transitions. During a timed rehearsal, speak at a natural pace without stopping to edit. During a pressure rehearsal, invite interruptions, difficult questions and technical problems.
For an in-person event:
- Visit the venue or review the stage arrangement if information is available
- Practise with a presentation clicker and visible countdown
- Test the deck on another screen
- Plan where to stand and when to face the audience
- Avoid reading from the projected slide
- Bring permitted adapters and a backup file
For a virtual pitch:
- Use a stable connection and a quiet, well-lit setting
- Position the camera at eye level
- Close unnecessary applications and notifications
- Test screen sharing, sound and video playback
- Keep notes close to the camera rather than reading from another screen
- Have a recovery plan if the connection drops
Virtual presenters should know whether they or the organiser will control the slides. Keep a local copy accessible and agree how another team member will continue if the main presenter loses connectivity.
Past examples of virtual pitch events for AI startups illustrate how online formats may centre on a particular technology or theme. Always check the current event brief rather than assuming that an earlier format still applies.
Handle judges’ and investors’ questions
Questions test more than factual knowledge. They show whether founders understand risks, listen carefully and can respond without becoming defensive.
Prepare concise answers on:
- Customer acquisition and sales cycles
- Revenue quality and pricing
- Market size assumptions
- Competitors and substitutes
- Product ownership and intellectual property
- Regulation and sector-specific approvals
- Unit economics and cash requirements
- Founder roles and hiring gaps
- Use of funds
- Expansion beyond Malaysia
- Key risks and upcoming milestones
Answer the question first, then provide supporting context. If a judge asks about revenue, do not begin with a long account of the company’s history. A useful pattern is direct answer, supporting evidence, then implication for the business.
When a question is unclear, briefly confirm what the person means. If you do not know the answer, say so and explain how you would verify it. Do not invent a figure under pressure.
Team members should decide in advance who will answer questions in each area. The lead presenter can direct a technical, financial or regulatory question to the most suitable colleague without creating confusion. Avoid having several founders answer simultaneously or contradict each other.
Some questions may expose a weakness. A credible response acknowledges it, explains what the team has learned and describes the next action. Investors generally expect risk. They need confidence that the founders can recognise and manage it.
Hypothetical scenario: answering a difficult question
A hypothetical marketplace is asked why a larger competitor could not copy its service. The founder does not claim that copying is impossible. Instead, the response explains the startup’s specialised supplier relationships, workflow knowledge and customer data, while acknowledging that continued execution is necessary. This is more credible than claiming to have no competition.
Follow up with investors after the event
The pitch is often the start of a conversation, not the decision point. Record useful details immediately after each discussion, including the investor’s interests, questions and any promised material.
Send a short, individual follow-up. Remind the recipient where you met, restate the company clearly and provide the specific information discussed. Avoid sending large attachments unless requested. A secure, organised data room can be shared later when there is genuine interest.
Before sharing sensitive material, consider what level of disclosure is appropriate. Early investor conversations do not normally require every customer detail, source file or confidential commercial term. Provide enough information for evaluation while protecting data and obligations owed to customers or partners.
Prepare the likely due diligence material before interest develops. This may include corporate records, financial information, ownership details, contracts, product documentation and evidence supporting important claims. Access should be controlled, and documents should be current, consistently named and easy to navigate.
Track responses and next actions in a simple pipeline. Note whether a person is a potential investor, adviser, customer or useful introduction. Record the promised action, owner and status. A polite update may be appropriate when the startup reaches a milestone relevant to the earlier discussion, but repeated generic messages are unlikely to help.
After the event, review what worked. Write down recurring questions, confusing slides and claims that needed stronger evidence. Revise the pitch while the experience is fresh, but do not change the story merely to satisfy every opinion. Look for repeated, relevant feedback.
Frequently asked questions
Should I use the same deck for every event?
Use a consistent core story, but adapt the emphasis, examples and ask. A competition judge, corporate buyer and early-stage investor may assess the same startup from very different perspectives.
Should I disclose my funding target on stage?
Follow the event brief and decide what supports your objective. If you state a target, be ready to explain how it relates to planned milestones, spending needs and the wider fundraising strategy.
What if the startup has little traction?
Use the strongest verifiable evidence available, such as customer interviews, product use, pilot learning or a credible sales pipeline. Do not present interest as revenue or describe an unfinished discussion as a partnership.
Do investors expect an NDA before hearing a pitch?
A public or semi-public pitch should not depend on disclosing trade secrets. Share enough to explain the opportunity, then assess confidentiality and disclosure needs before providing sensitive material later.
Who should deliver the pitch?
Choose the founder who can communicate clearly, answer core business questions and represent the team credibly. Other team members can support specialised questions, but their roles should be agreed before the event.
What should I do if the pitch goes badly?
Record what failed while the details are fresh, separate delivery problems from business questions and revise accordingly. A weak event performance does not prevent useful follow-up if an investor showed genuine interest.
As a practical next step, choose a suitable event, confirm its current official requirements, assemble the supporting evidence and rehearse the timed pitch with people who have never seen the deck.
