# Week 11: Pitching and poster

## Studio abstract

> In this studio, your team will compare pitching advice from five startup organisations, build and test a one-minute pitch suited to the course showcase, and use the agreed story to begin an A2 poster.

The activities total 140 minutes and begin after the 30-minute innovation seminar and a 10-minute transition.

By the end of the studio, your team should have:

- defined what its showcase audience should understand and remember;
- compared pitching advice from five startup investors and accelerators;
- selected and combined useful elements rather than copying one formula;
- drafted, timed, delivered and revised a one-minute pitch;
- identified which claims in the pitch are supported by project evidence; and
- begun an A2 poster that connects the problem, value proposition and evidence.

## 1. Define the audience and outcome

⏱️ 10 minutes — team

The Week 13 showcase asks you to pitch to an audience of “investors”, but your actual audience will include students, teaching staff and visitors. Treat them as people deciding whether your product addresses a worthwhile problem and whether your claims are credible.

Agree on three outcomes:

| After one minute, the audience should… | Team decision |
|---|---|
| Understand | What is the one thing they must understand about the problem and product? |
| Remember | What is the most distinctive or convincing point? |
| Do | What response do you want: ask a question, view the demonstration, discuss the evidence, or something else? |

These decisions should guide what you include and what you leave out.

## 2. Review five pitching perspectives

⏱️ 10 minutes — individual review followed by team discussion

Divide the following sources across the team. If your team has fewer than five members, one person may review two shorter sources.

| Organisation | Source | Look for |
|---|---|---|
| Startmate | [Getting through the first round of the Startmate Accelerator](https://www.startmate.com/writing/your-ultimate-guide-for-getting-through-the-first-round-of-the-startmate-accelerator) | Team, problem, approach, traction, authenticity and energy |
| Blackbird | [So you’ve got an idea—now what?](https://www.blackbird.vc/blog/so-youve-got-an-idea-now-what) | Customer understanding, validation, evidence and distinctive strengths |
| AirTree | [How to nail your first meeting with a VC](https://www.airtree.vc/open-source-vc/how-to-nail-your-first-meeting-with-a-vc) | Connection to the problem, product demonstration, metrics and honest gaps |
| Y Combinator | [How to pitch your company](https://www.ycombinator.com/blog/how-to-pitch-your-company/) | A plain explanation of what the company does, who wants it and why it matters |
| Techstars | [The keys to creating the perfect 30-second pitch](https://www.techstars.com/blog/founder-advice/the-keys-to-creating-the-perfect-30-second-pitch) | Customer, problem, product, importance, traction and team |

Each reviewer should report:

1. the source’s most useful advice;
2. one element that could strengthen your team’s pitch; and
3. one element that does not suit the course showcase or your current project stage.

The sources were written for different organisations, stages and audiences. They are perspectives to examine, not five authoritative formulas.

## 3. Choose the ingredients and build a hybrid

⏱️ 20 minutes — team

Select the elements that serve the audience and outcome defined in Activity 1. Do not include an element merely because an investor or accelerator mentioned it.

Use the following table to make the decisions explicit:

| Possible element | Include? | Why, and what evidence or artefact supports it? |
|---|---|---|
| Customer or intended user |  |  |
| Problem and why it matters |  |  |
| Product or MVP |  |  |
| Value proposition |  |  |
| Interview or testing evidence |  |  |
| Team |  |  |
| Difference from alternatives |  |  |
| Purposeful close or invitation |  |  |

Arrange the selected elements into a coherent sequence. The sequence does not need to follow the table, and it does not need to resemble another team’s pitch.

## Break

⏱️ 10 minutes

## 4. Draft the one-minute pitch

⏱️ 25 minutes — team

Write a first version using your own project evidence. Draw from:

- problem interviews and deidentified transcripts;
- accepted, refuted and unresolved hypotheses;
- the Value Proposition Canvas and Business Model Canvas;
- competitor analysis;
- solution-testing and MVP-testing evidence;
- implemented MVP features; and
- learning cards and resulting decisions.

Keep only material that advances the agreed story. Avoid unsupported market statistics, vague claims such as “everyone needs this”, and technical detail that the audience does not need.

Aim for approximately 120–130 words. This is a guide rather than a requirement: speaking pace varies, and clarity matters more than reaching a particular word count.

Read the draft aloud with a timer. Revise it until it can be delivered clearly within one minute without rushing.

## 5. Pitch, review and revise

⏱️ 25 minutes — team, with feedback from other teams

Work through repeated one-minute pitch cycles:

1. one team member delivers the pitch without interruption;
2. listeners record what they understood, what they remembered and what they wanted to ask;
3. listeners identify which claims sounded supported and which needed evidence;
4. the team decides what to retain, clarify, support, remove or reorder; and
5. another team member delivers the revised version.

Repeat the cycle with different speakers and listeners. Where possible, test a revised pitch with someone who did not hear the previous version.

Do not begin by debating personal preferences about wording or presentation style. Compare the audience response with the outcomes from Activity 1 and revise based on what listeners actually received.

Before moving on, record one remaining improvement for the next rehearsal.

## 6. Turn the agreed story into a poster

⏱️ 35 minutes — team

The poster is not a transcript of the pitch. The pitch establishes the story; the poster lets a visitor inspect its important claims while talking with the team and viewing the demonstration.

Begin an A2 poster containing, at minimum:

- the team members;
- the customer problem;
- the value proposition; and
- concise evidence connecting the problem and value proposition.

“Link your data to the value proposition” does not mean placing interview transcripts, raw data or a large spreadsheet on the poster. Select a small amount of deidentified evidence and state what claim it supports.

For example:

| Evidence shown on the poster | Claim it supports |
|---|---|
| A short deidentified quotation describing repeated difficulty coordinating a task | The customer problem is experienced in practice |
| A count from relevant interviews, such as “6 of 8 participants…” | The problem recurred across the team’s interview sample |
| A percentage accompanied by its count, such as “75% (6 of 8 participants)…” | The proportion observed in the team’s sample, without implying that it represents all potential customers |
| A recurring theme identified across several interviews | Different participants described a related need, behaviour or difficulty |
| A task-completion result or observed difficulty from MVP testing | A feature helps deliver the proposed value, or still needs revision |
| A before-and-after measure, such as time or number of steps required to complete a task | The MVP may improve a specific aspect of the customer experience |
| A comparison with an existing alternative | The proposed value is meaningfully different |
| A relevant statistic from a credible external survey, report or dataset, with its source, year and sample size | The problem also appears in evidence beyond the team’s own participants |

Use honest language. A small interview sample supports a claim about what your team observed; it does not establish what all potential customers believe. Do not include names, contact details, identifiable quotations or links to private recordings.

Sketch the poster before polishing it. Check that a visitor can quickly follow this relationship:

`Problem evidence → customer problem → value proposition → MVP response`

The finished poster may be printed as one A2 sheet, two A3 sheets or four A4 sheets. A PDF copy must also be included with the Iteration 3 submission.

### Optional AI-assisted poster workflow

Your team may use an AI tool or coding agent to help organise, design or implement the poster. For example, you could:

- ask for several layout alternatives based on your agreed content;
- create a reusable repository skill that checks the poster’s required content, evidence links, dimensions and export settings;
- build the poster in HTML and CSS, using an A2-sized print stylesheet, then export it to PDF; or
- ask an AI tool to review hierarchy, readability, contrast and consistency before printing.

AI should help present the team’s work, not invent it. Do not provide an external AI service with identifiable participant information, private transcripts, recordings or consent records. Check every generated summary, statistic, quotation, source and claim against the original evidence. The team remains responsible for the poster’s content, design decisions, accessibility and final PDF.

If using HTML and CSS, test the exported PDF at A2 size. Check that fonts, images and colours render correctly; text remains readable; links or QR codes work; content is not clipped across print boundaries; and the PDF is committed in the location required for Iteration 3.

## Exit ticket

⏱️ 5 minutes — team and legend

Show your legend:

1. the intended audience response;
2. the selected hybrid pitch structure;
3. a timed one-minute pitch;
4. feedback from at least two listeners and one resulting revision;
5. the evidence used to support the pitch’s important claims; and
6. the initial poster showing how evidence connects to the problem and value proposition.

After the studio, continue rehearsing with different listeners and refining the poster as MVP testing produces further evidence. Keep the pitch, poster and demonstration consistent with what the team has actually built and learned.
