The story: the problem, the yes, and action titles

Every pitch is a chain of small agreements, and the problem slide is the first link. It carries all the weight: the audience has to nod, silently and involuntarily, when they see it. "Yes, that is real. That annoys me too." If they instead think "is that actually a problem?", they close the topic in their heads, and nothing you say afterwards gets heard. Not because they are rude. Because attention follows agreement.

Make your problem statement so agreeable that nobody in the room can argue with it. That means no jargon, no insider knowledge, no setup that needs three slides of context. State it from the customer's point of view, not from inside your product. The bigger and more familiar the pain, the better. And show why the current options fail, because "why has nobody fixed this yet?" is the first silent objection in every room.

The solution slide has one job too: the quiet "wow". It does not need every feature. It needs the one move that closes the gap you just made everyone feel.

The problem slide from the last section has a name we use in almost every session: the yes slide. Some founders call it the wake-up slide, the one whose only job is to make the room think "yep, true, cool" before you have argued anything at all. Win that involuntary nod and the mind opens, and once the mind opens the heart opens. Miss it, and a doubter on slide one is still a doubter on slide four, because a question you plant early follows the listener through the whole deck.

Why it works is almost physical. The first agreement is the cheapest one to win, so you spend it early. Say something nobody can push back on and you have packed the entire room onto the bus with you. Everything after that is downhill skiing: they are already nodding, so each new claim lands with goodwill instead of resistance.

Which leaves the opener with one hard rule. Do not open on a debatable claim. A number that sounds invented, a preference dressed up as a fact, a jab at a competitor, each one plants a doubt you then spend the rest of the pitch defending. Lower a shaky claim until it is one the whole room accepts, and aim it at the person actually in the chair. An investor is not your player, so the opener that lands is the one they nod at, not the one your future user would.

Here is where game studios get stuck. A game is not a painkiller. Most games do not "solve a problem" in the classic startup sense, and founders with technical or scientific backgrounds resist the exercise hardest. We have heard the objection in almost exactly these words: "The mouse is good. The keyboard is good." True. And beside the point.

A bicycle was never a problem either. Nobody suffered from bicycles. Someone still invented the car, because underneath "the bicycle is fine" sat a gap: distance, speed, weather, cargo. When your product does not solve a problem, your job is to name the gap underneath the status quo. What can your players not do, not feel, not reach today? Which itch does the current market leave unscratched? That gap, stated plainly, does everything a problem statement does: it makes the room nod before you show the product.

Once the room has nodded at your problem, they want to know what you did about it. Here is where founders reach for the wrong slide. Out comes the feature tour: menus, screenshots, the systems diagram, the live demo. It is the thing you are proudest of, and it is the thing that loses them.

Lead with the dream instead. Describe the high-level solution, your approach, the step change you are claiming, and let the room lean in before you show a single screen. A bold claim first puts everyone on the edge of their seat. The mechanics answer "how", and "how" is a question for later, once they already want it to be true. Show the demo early and you invite ten questions you were not ready for, because the moment people see the machine they start poking at the machine. The product tour is a slide, and it comes after the dream, not instead of it.

There is a deeper reason to describe the solution rather than tour the features: in the real world there are many solutions to any problem, and a feature list argues about one of them. The dream argues about the outcome, which is the part the investor is actually buying.

Two questions we ask about every key slide. Could you explain this to your mother? Would a 14-year-old get it? If not, the slide is not finished, and the fix is not more words, it is fewer and plainer ones.

The goal is simple, not dumb. Those are different things, and founders with technical backgrounds mix them up, because plain language feels like it undersells the hard work underneath. It does the opposite. Jargon does not make a listener feel that you are smart. It makes them feel that they are slow, and nobody feels good about something they do not understand. Worse, they will nod anyway, out of politeness, and that nod is worthless. It is not the involuntary yes from your yes slide. It is a person hiding that they are lost.

So prime every technical claim with a plain-language picture first. One of the sharpest founders we coached kept a private motto for exactly this: "I am a fish, I am dumb, tell it to me." If a slide needs a glossary, it needs a rewrite.

If we could hand every founder one habit, this would be it. It comes up in almost every coaching session, because it fixes the most common deck disease: slides labeled "Problem", "Team", "Market", each buried under bullet points fighting for attention.

The method: every slide gets exactly one core claim as its title. Five to ten words. Written as a statement, not a label. "Team" is a label. "A lean team with deep experience and shipped success" is a claim. Everything else on the slide, the image, the number, the testimonial, exists only to support that one claim. If it does not support the title, it goes.

The workflow we demonstrate live in sessions: start with blank slides. Write only the one sentence you want to say on each. No visuals, no charts, nothing else. Read the sentences in order and fix the story at that level first, because it is cheap to fix there. Only then add the supporting material.

Read only your slide titles aloud, in order: if that is not your 30-second pitch, your titles are labels, not claims. Here is what the rewrite looks like in practice, blended from real coached decks and anonymized:

Notice what changed. Each title now makes a claim someone could disagree with, which means each title now carries information. A label tells the audience what category of slide they are looking at. A claim tells them what you believe, and dares them to check the evidence underneath.

A personal story belongs in your pitch. It is the only real emotional connection in an otherwise numbers-driven few minutes, and we push almost every founder to include one. Then we cut it down, because the same founders tell it for ninety seconds.

The line that ended one of these origin stories mid-session: "I do not want the whole life story. Thirty other founders are waiting." Harsh, and exactly how a jury feels by pitch number twelve.

Three sentences, maximum. The moment, the itch, the decision. "I asked a friend what his most valuable gaming asset was. It was an account worth more than his PC, protected by nothing. That is the day we started building." Everything past sentence three is biography, and biography is not connection.

A good analogy is the shortest pitch there is. "Airbnb for garages." "Tinder for dogs." "Google Maps for bathrooms." A few words each, and the listener already understands the model, the market and the interaction. Games get the same effect through references: "Civilization meets chess, with the strategic depth of Slay the Spire" tells a genre-literate listener more than a paragraph of feature descriptions ever could.

The trap: an analogy only compresses if the listener already knows the picture you are borrowing. Compare your game to a niche title only your community knows, and the analogy does the opposite of its job. The listener now holds two things they do not understand. We call it the insider analogy, and it shows up constantly when gaming founders pitch generalist investors.

Before you use an analogy, check whose knowledge it borrows. Pitching gaming investors? Reference deep cuts freely. Pitching a family office that has never held a controller? "Netflix" beats any game title you could name. Test the analogy on someone outside your bubble, and if they squint, swap the reference.

The masterclass walks through three classic frameworks. You do not need the books. You need what each one changes about your pitch.

The Golden Circle says start with why. People do not buy what you do, they buy why you do it, and competition usually fights on the "what" level, where everything sounds the same. So open with purpose, follow with your approach, end with the product. Emotional storytelling gets much easier once the purpose leads.

SUCCESs is a checklist for sticky messages: Simple, Unexpected, Concrete, Credible, Emotional, Stories. Run your pitch against all six. Most founder pitches score high on concrete and credible, and near zero on unexpected and emotional. That imbalance is fixable in an afternoon.

AIDA settles the question every founder asks about short formats: how do I fit everything in? You do not. Attention, Interest, Desire, Action are stages, and each pitch format owns different ones. The 30-second pitch covers attention and interest, nothing more. The investor meeting covers desire and action. A short pitch is not a compressed long pitch. It owns different letters.

Your story now has a spine: a problem people nod at, a solution that answers it, and titles that carry the whole argument on their own. How big to frame that story, and whether you are entering a category or creating one, is a positioning decision, not a craft one. Then two decks and the visual hierarchy and the deck, slide by slide turn the spine into slides, and the 30-second pitch compresses it into thirty seconds you can say in an elevator.