open summer of code
HomeWebsiteGitHub
  • Welcome to osoc!
  • Code of Conduct
  • The osoc Way of Work & Play
    • Working Together in a Remote Setting
  • Students
    • Applying as a student at osoc
      • Privacy Policy for Open Knowledge Belgium
    • Being a student at osoc
      • Practical: When, where, how long, food
      • Health, COVID, Insurance, Sick Days
      • Study material
    • The Student Job
    • Salary & Reimbursements
  • Coaches & Student coaches
    • Being a coach at oSoc
    • The Coaching Job
      • Soft Skills & Expectations
      • Tasks
      • How to Manage a Team: Techniques
      • Coaching Cases
      • Battle Prep
      • Student Coaches
      • Screening students
    • Projects
    • Partner Communication
    • Practical
  • partners
    • Being a partner at oSoc
      • Apply
      • Attend
    • The Partner's Job
    • Projects
  • Tools & Resources
    • Discord
      • Basics
      • Discord etiquette
      • Setting your nickname & description
      • Managing notifications
      • Offering and Receiving Help
      • Find Your Discord Username
    • NextCloud
    • The #osoc Emoji
    • Big Blue Button: Video Calls
    • Deployment
    • Maps & Cartography
  • Tutorials
    • Create Crests
    • Pitching
      • Pitch and Interview Tips
      • Pitch on Discord
      • Pitch Content Tips
    • Interviews
    • Hosting
    • Deliver Like a Pro
      • Publish a Github Page
    • Conduct (Remote) Tests and Interviews with Real People + Archetypes
  • Organisers
    • How to set up oSoc for your country
      • Preparation
      • Selection
      • Practical
        • Setting Up a Remote Edition
      • Informing people
    • On-site editions: 4 weeks of well-organised serendipity
      • Calendar Example Remote Edition (BE)
        • Week 1: Explore
          • Day 1: Welcome (to the Madness 😏)
          • Day 2: Meet the Client + Prepare for Hackathon
          • Day 3: Hackathon & Pitching
          • Day 4: Pitch & Battle Plan
        • Week 2: Build
          • Day 1: Build, test, document + Learn how to vlog
          • Day 2: Build, test, document
          • Day 3: Build, test, document, ship
          • Day 4: Pitch & Battle Plan
        • Week 3: Build more
          • Day 1: Build, test, document + How to deploy
          • Day 2: Day off!
          • Day 3: Build, test, document, ship
          • Day 4: Pitch & Battle Plan
        • Week 4: Deliver
          • Day 1: Ship ship ship
          • Day 2: Pitch pitch pitch
          • Day 3: Delivery Day
          • Day 4: Demo Day
      • Kick-off day 1 (or chaos day)
      • Hackathon day 2 — 4
      • Build — week 2
      • Build — week 3
      • Delivery week — week 4
      • Evaluation — follow-up
    • Taking over the world
    • Salary & Reimbursements
    • Managing teams
  • test
Powered by GitBook
On this page
  • Mood
  • The Project
  • The Structure
  • The Base
  • How to Explain Your Project
  • You Can Do This

Was this helpful?

  1. Tutorials
  2. Pitching

Pitch Content Tips

PreviousPitch on DiscordNextInterviews

Last updated 3 years ago

Was this helpful?

Mood

Tell us a story, take us on a journey. Grab our attention, slow down, ramp up the speed, build up – give us a plot twist. Build up so we want to find out more about your project.

💡 Don't be high-energy or low-energy all the time. People will lose their attention.

Create momentum, make a connection. Tell us a story humans can relate to.

The Project

What did you make? What problem are you solving? Why would it matter – to me?

Tell me a story that I can relate to.

Remember those moments where you stare at people while they’re talking and you’re nodding because they sound like it’s important – but you have no idea what they’re saying? This is what people like us sound like, 90% of the time. Make your audience understand.

That's how you turn other people into advocates of your project.

The Structure

The Base

What is the project about? Who is the client? Who are you?

How to Explain Your Project

This will help us understand your project

Vision Problem Audience Strategy Goal

In order to… our product or service will solve… which is the problem of… by giving them… We will know if our product or service works, if we see…

Examples

You Can Do This

If you start on time, and work together with your team.

💡No need to stick to this order, .

find what feels good
Grab attention – play with speed – build up to have them yearn for more.
Help us understand why we should listen
Make a connection
You don’t need to sound smart, you need to make other people feel smart.
The Base
Night-time Knitters
Mobile Ratchet Ticker (Mobiele Rateltikker)