How to pitch an early idea and ask for useful feedback

An early idea pitch can simply be a short explanation followed by a question. You do not need to present yourself as an investor-ready founder or persuade everyone to join you. The task here is to help a willing listener understand the idea and identify something you still need to learn.

This guide is for informal learning conversations, not an investment solicitation, sales promise or clinical product demonstration. If you are preparing an actual deck, use the separate pitch-deck evidence review.

Check the setting and ask first

At an event, read the format and participation rules. During a break, try: “Would you be open to hearing an early idea and telling me what is unclear?” If the person declines or is busy, leave it there. An online session may have a designated question channel; do not interrupt or send unsolicited decks to attendees.

Ask before recording, quoting someone or adding them to a contact list. Remove private customer details from examples. You can describe a problem without exposing a client, employer or participant.

Draft five short parts in your own words

1. Person and task: who is doing what, in which setting?
2. Observation: what have you actually seen or heard? If it is only an assumption, say so.
3. Proposed change: what would your idea do, and what would stay with a person?
4. Current status: idea, sketch, prototype or something used in practice?
5. Question: what relevant experience or clarification would help you learn?

The Australian Government Style Manual recommends familiar words and explaining unfamiliar terms. That supports the language choice here, not a claim that this five-part exercise has been proven to win pitches. Prefer “draft a reply from approved event information” to unexplained phrases such as “agentic engagement orchestration”.

Read two real pitch examples critically

These are the original recordings linked by this guide, not fictional success stories. The notes below are MLAI editorial interpretations of selected captioned passages, not endorsements or independently verified business results. Use the written lessons without watching; they are not full transcripts.

Support-Sorted: distinguish a story from a measured outcome

Watch The Story of Support-Sorted on Loom. The page identifies Dr Sam Donegan as uploader; the recording is 4:54. The exact recording date was not verified.

• 0:01–0:18: the opening introduces the service and a personal story. A specific situation helps explain the problem; permission to tell a story is separate from evidence that a solution improves outcomes.
• 0:42–1:13: the story contrasts someone seeking help with a provider seeking clients. Identify both sides of the proposed connection; do not treat one account as a verified market-wide waiting-time estimate.

Access limit: select Transcript on Loom. In our signed-out check, text was visible through 1:52, followed by a signup prompt. The captions contain errors; these notes cover the opening only. Health, availability and business claims in the recording were not independently verified here.

CliMate: distinguish a demonstration from evidence of reliability

Watch CliMate Pitch Video, uploaded by the mlai-au channel on 24 April 2024; duration 5:13. This is a historical project pitch, not current carbon-credit or financial guidance.

• 2:19: the presenter describes farmer interviews. A research claim needs methods and context before you can infer demand.
• 2:44–3:31: the explanation moves into a website walkthrough. Label what the demonstration shows and what remains untested.
• 3:40–4:02: implementation technologies are described. Naming a model or retrieval method is not an accuracy test.

Transcript: expand the YouTube description and choose Show transcript; the full caption text was available signed out in our check. Automatically generated names and technical terms need correction before quotation.

Neither recording proves that following its structure improves conversion. We have not reproduced their full transcripts or cleared reuse of their footage, personal stories or deck images. The exercise below is our separate, explicitly fictional before-and-after comparison—not a claim that either presenter made these revisions.

Before and after: a fictional event-information idea

Fictional teaching example—not a real MLAI project or participant result. All dialogue, observations and permissions in this exercise are invented.

Before: “Our revolutionary AI platform eliminates event admin and guarantees a better experience. Sign up now before you miss out.”

Draft for the first rehearsal: “I’m exploring a draft assistant for volunteer event organisers. In this fictional scenario, an organiser described repeatedly answering questions about arrival instructions. The idea would draft replies using approved event notes, with the organiser checking every reply before sending. It is only a sketch; I have not tested whether it saves time. If you organise events, how do you handle changes to arrival instructions today?”

For your own version, replace the invented observation with a permission-cleared real observation or explicitly state that it is a hypothesis. Do not copy the example as your personal experience.

Match the question to what you need to learn

• Clarity: “What do you think the idea would do?” Ask before supplying more explanation.
• Current practice: “Can you describe the last time this happened?” Avoid asking for confidential details.
• Limits: “When would this approach be unsuitable?” Record the objection rather than arguing it away.
• Next conversation: “Would you be open to discussing this again?” A yes is permission to arrange that conversation, not a sale or endorsement.

Do not turn every conversation into customer research. A supportive community peer may not have the problem you are exploring. Record that distinction. If the person has no relevant experience, their response can still reveal unclear wording without establishing market demand.

Practise, then change one sentence

Read the draft aloud or share it in writing with someone who agrees to help. Notes, a sketch, captions or an asynchronous message are all possible supports. You do not need a prescribed personality, eye-contact pattern or speaking style to take part.

1. Check your actual timing against the time offered by the listener or organiser.
2. Ask the listener to describe the intended user, proposed change and current status.
3. Identify one misunderstanding and revise the relevant sentence.
4. Check that the revision has not removed an important uncertainty or added an unsupported benefit.

Here is the supplied fictional exchange, including a misunderstanding and the actual replacement sentence. It does not report a real rehearsal.

1. P1: Share the draft with a willing peer

   Fictional peer: “I can read one draft and tell you what I think it does. Please do not record me or contact me afterwards.” The writer shares the draft above, not a working demo.

   Boundary: Permission covers this one written exchange only. No recording, mailing-list signup or follow-up.

2. P2: Read the retelling before explaining

   Fictional peer: “It answers attendees automatically after the organiser approves the event notes. I have not organised an event, so I cannot tell you whether this solves a real problem.”

   Boundary: A specific misunderstanding of sending authority; no evidence of customer demand or workflow effectiveness.

3. P3: Revise internally; leave the retest open

   The proposed assistant would prepare a reply inside a review screen. It would not send messages or update the event page. The organiser would check each draft against the latest approved notes and decide whether to copy it into their existing messaging tool. This is a proposed boundary, not a feature we have built or tested.

   Boundary: Retest not run. Do not send another version to this peer. A future rehearsal requires a different willing listener or fresh explicit permission; the revised wording is not proven clearer.

The rubric describes the text, not a validated score or an observed improvement. Wide tables scroll sideways; focus the region and use arrow keys, or use the matching text download below.

Keep a conversation record, not a confidence score

Save the editable pitch rehearsal record. It contains the ten blank and completed fields, all three steps, wording comparison and seven-slide fictional example. No signup is required for this file.

1. Intended user and task:
2. Observation versus assumption:
3. What exists and what is proposed:
4. One question for this conversation:
5. Permission and setting:
6. Listener understanding before clarification:
7. Relevant experience or lack of it:
8. Objection or contradictory information:
9. Next change, owner and investigation:
10. Follow-up permission and note handling:

Do not equate compliments, a QR scan or contact exchange with a customer, contract or validated business. A peer’s clear retelling would still not establish willingness to pay.

Use the original deck as a reference, not ready-made evidence

View the original MLAI pitch template. The public slideshow has seven slides; use its previous/next controls. It contains instructions and third-party example images, not just blank fields. Viewing worked without an account; editable-copy access and reuse rights were not verified.

Create your own text-first outline using the worked example below. Replace teaching fiction with your actual evidence or an explicit unknown. Do not copy another team’s logos, screenshots, numbers or endorsements. A roadmap is proposed work, not traction; a rising graph is appropriate only when you have the underlying data and context. Ask the owner for reuse permission before reproducing template assets.

A conversation may not need slides at all. For a formal submission, check the organiser’s requirements and use the linked pitch-deck evidence review to distinguish claims, sources and missing evidence.

Take your revised question to a relevant MLAI event

Look for a topic and experience level that match your interests, then check the location or online format. Bring your draft as a starting point, not a demand for feedback. Event attendance does not guarantee cofounders, investors, clients or a pitch slot.

If you are still exploring an AI idea, an event can help you learn from relevant discussions. For this exercise, bring “Who would check and send the reply?” rather than a claim that the concept is validated. Choose pitch practice only when the actual event listing offers it, and ask before requesting feedback.

Sources, access and editorial scope

The linked resources were checked on 11 September 2026. The Style Manual page was updated 20 December 2024. Caption access, historical source claims and reuse permission are separate checks; access can change. Speaker/audio verification, full accessible transcript provision and media reuse review remain pending.

AI-assisted editorial exercise; independent source, accessibility and founder review pending. Retest not run. The script, scenario and record are MLAI editorial exercises, not measured interventions. No funding, conversion, safety or clarity improvement is claimed. The original publication date is retained; this revision adds source annotations and a worked rehearsal.

Frequently Asked Questions