MDIA1007 Chap.8 Pitching the Entrepreneurial Journey
Pitching the Entrepreneurial Journey
The final chapter connects Week Nine pitching and next steps to the live Week Ten Shark Tank and AT2 submission. It builds a narrative from problem, first belief, test result, evidence-backed change, second-cycle finding and proportionate next move. The pitch, report, test cards and landing pages must agree on outcomes and interpretation.
The chapter also separates AT2's internal component shares from course-grade weights and treats AI disclosure, working links and privacy as part of credible digital entrepreneurship.
What this chapter covers
- 01
A pitch arc driven by evidence rather than chronology
- 02
Selective visuals that explain a venture decision
- 03
A proportionate next ask based on unresolved risk
- 04
Consistency across report, pitch, test cards and prototypes
- 05
Internal AT2 shares versus official course-grade weights
- 06
AI disclosure, privacy and working-link checks
Worked example · free
Building a pitch that earns its next ask
- +1Open with the niche problem and first belief, then report the weak result without hiding its limitation.
- +1Connect evidence to the narrower version and show the second-cycle interest and trust tension accurately.
- +1Ask for a verified handover experiment rather than claiming that the venture is ready to scale.
Key terms
- Pitch Arc
- A sequence connecting the problem, tests, changes, current evidence and next move.
- Evidence Visual
- A chart, prototype or comparison that helps an audience understand one venture decision.
- Next Ask
- A proportionate request for an experiment, resource or conversation supported by the current evidence.
- Cross-Component Consistency
- Agreement among test cards, report, pitch and prototypes about results and interpretation.
- AI Disclosure
- A factual account of tools, purposes, prompting, performance and retained generated material.
Pitching the Entrepreneurial Journey FAQ
What should the pitch focus on?
Focus on the causal journey: a specific problem, the first risky belief, what the test revealed, why the venture changed, what the second cycle showed and what should happen next. Feature lists and founder biographies matter only when they help explain one of those decisions.
How much evidence belongs in the pitch?
Select the smallest set that explains major changes and supports the next ask. A simple before-and-after prototype or test sequence is more useful than crowded raw screenshots. Give enough context for the evidence boundary and keep the detailed record in the report and test-card appendix.
How do I keep all AT2 components consistent?
Create a one-page fact sheet listing both assumptions, methods, criteria, outcomes, limitations, venture changes and final decision. Use it while editing the report, pitch and landing-page captions. If one format makes a stronger claim, return to the test record and use the same bounded interpretation everywhere.
Can a pitch be persuasive when the venture stopped?
Yes. Persuasion comes from a clear problem, disciplined tests and a justified decision, not from pretending every idea should continue. Show what the team believed, how the evidence altered that belief and why stopping protects resources or redirects them toward a stronger opportunity. Preserve the venture's limitations instead of adding optimism that the report cannot support.
A coherent learning journey can demonstrate judgement, leadership and ethical communication even when the commercial verdict is negative.
Assessment move
Draft the pitch as six headings before opening presentation software: niche problem, first belief, Cycle One evidence, version-two change, Cycle Two evidence and next move. Under each heading, write one sentence and one possible visual. Remove any visual that does not advance the argument. Build a cross-component fact sheet from the completed test cards and use it to audit the report, pitch and prototype descriptions.
Check that internal AT2 percentages are never presented as separate course-grade tasks. Rehearse aloud and listen for unsupported jumps from small evidence to broad claims. Keep an AI-use log, remove participant identifiers and test all public links outside the editing session. End with the next action the evidence supports, even if that action is another pivot or stopping the current idea.
Make an evidence-to-slide map in which every claim points to a test-card field, version record or bounded observation. Delete decorative detail that cannot answer why a decision changed. Rehearse the journey once as a success story and once as a learning story; keep the version that remains credible if the final venture is stopped.
Then compare every number and interpretation across the written report, landing page captions and spoken script. Ask a reviewer to identify the audience, two assumptions, two results and current verdict without prompting. Any mismatch signals a consistency problem to repair before submission.
Working through Pitching the Entrepreneurial Journey in MDIA1007? Sia is AskSia’s AI Management tutor — ask any MDIA1007 Pitching the Entrepreneurial Journey question and get a clear, step-by-step explanation grounded in how MDIA1007 is taught and assessed. Read this chapter free, then take your hardest questions to Sia.
