Many first-time designers believe pitching is mostly about presentation. A polished prototype. Beautiful art. A slick logo. Maybe even a full business plan. In reality, publishers care about something much simpler:

Is the game good, and can they understand that quickly?

Publishers review an enormous number of submissions. Most are rejected long before anyone finishes reading the rules. Not because the ideas are bad, but because the pitch creates friction. It takes too long to understand. The prototype is difficult to play. The designer explains everything except the actual game. A successful pitch is not about impressing people with production quality. It’s about reducing uncertainty.

This article is based on personal experience gathered through nearly a decade of board game development and editorial work at Hans im Glück, as well as later work as a game designer, developer, and lately, games studio founder. The perspectives shared here are individual observations and workflows, not official publishing guidelines or statements on behalf of any company. Different publishers evaluate submissions differently, and those expectations can change over time.

If you’re already designing prototypes, iterating systems, and testing mechanics, this is the next layer:

How to present your game professionally
without overcomplicating the process.

First: Understand What a Publisher Is Actually Looking For

Most designers approach pitching from the wrong perspective. They think:

“How do I convince a publisher that I’m talented?”

But publishers are not evaluating you. They are evaluating whether the game deserves more time. That changes everything. The goal of a pitch is not:

The goal is much narrower:

Make the publisher want to play the game.

That means your pitch should optimize for:

If the core idea cannot be understood quickly, the pitch usually fails before the game even gets tested.

(TableHop note: we explore the idea of “core experience” in more detail in Core, Content, Balance: Why Most Board Game Designs Collapse (and How to Fix Yours))

The Pitching Framework: What Actually Matters

A strong publisher pitch usually comes down to five elements:

  1. Clear rules
  2. Functional prototype
  3. Short video pitch
  4. Sales sheet
  5. Digital implementation (optional, but useful)

Most designers focus on these in the wrong order. Presentation comes first. Usability comes last. It should be the opposite.

1) Rules: The Most Important Part Nobody Wants to Work On

Rules are rarely what gets someone excited about a game. But bad rules can kill even an excellent design immediately. A publisher cannot properly evaluate your game if the rules create friction. That usually happens when:

Your rulebook is not marketing. It is a usability document. That means clarity matters more than style. Consistent terminology, predictable structure, visual examples, and explaining systems in the order players encounter them all make a massive difference. Unnecessary lore and flavor text usually make rules harder to follow, not more immersive.

If players repeatedly ask the same question during testing, the issue usually is not the player. It’s the rules. This is also why testing rules separately from gameplay is important. A game can function perfectly in your head while remaining completely unreadable to everyone else.

2) Your Prototype Does Not Need to Look Good

This surprises many first-time designers:

Publishers generally do not care whether your prototype looks beautiful.

They care whether it is playable, readable, easy to understand, and simple to test. A prototype is a design tool, not a product. Sleeved paper cards, placeholder icons, and borrowed cubes from other games are completely fine. What matters is functionality.

Ironically, overly polished prototypes can sometimes send the wrong signal. They suggest the designer spent more time on visuals than iteration. A rough-looking prototype with strong gameplay is infinitely more valuable than a beautiful prototype with weak mechanics. Your prototype should communicate one thing clearly: “This game has been tested seriously.” In practice, that usually means:

A functional prototype lowers friction and makes publishers focus on what actually matters: the experience of playing the game.

3) The Short Video Pitch Is Extremely Powerful

A concise video pitch is one of the most efficient ways to get a publisher interested. Not because it replaces the game, but because it reduces effort. Remember:

Publishers go through an enormous number of submissions.

A short video helps them quickly evaluate whether the game is understandable, whether the flow looks engaging, and whether the concept feels commercially viable. The key word here is: short. A good pitch video should:

Think of it as answering one question:

“Why should someone spend time learning this game?”

Not:

“Everything about my game.”

One useful exercise is showing the pitch video to non-designers first. If they cannot clearly explain what players actually do, or whether the game looks fun, the pitch is probably still too complicated. In most cases, confusion means the video needs simplification, not more explanation. 

4) Sales Sheets Should Stay Focused

A sales sheet is useful, but many designers overload it with information publishers do not actually need. Manufacturing estimates, detailed expansion roadmaps, long lore explanations, or multiple paragraphs about your vision usually create more friction than value. A good sales sheet should communicate:

That’s enough. One sentence about possible expansions is completely fine. An entire ecosystem pitch usually is not. Again: you are not pitching your company. You are pitching the game.

Many beginner designers accidentally bury the strongest part of their design under unnecessary information. The clearer and more focused your sales sheet is, the easier it becomes for publishers to understand why the game is worth their attention.

5) Digital Versions Make Testing Easier

Platforms like Tabletop Simulator or Tabletopia can help significantly, especially for remote testing and international pitching. But the same rule applies: functionality matters more than presentation. A digital version should:

It does not need custom scripting, animations, or final art. A broken digital prototype creates the same impression as a broken physical one: insufficient testing.

Before the Pitch: How to Approach Publishers Properly

The process itself is usually simpler than many designers expect. Most publishers can be contacted directly, whether through email, convention meetings, or official submission systems.

If you attend conventions, bringing at least one playable prototype, a few sales sheets, and being organized enough to demo efficiently is usually more than enough. You do not need giant banners, expensive displays, or a fully branded company presentation. What matters most is preparation.

Publishers appreciate designers who communicate clearly, respect time, and understand their own game well.

One important mindset shift is realizing that publishers are not enemies guarding a gate. Most editors and developers are gamers themselves, and conversations usually work best when they feel natural rather than overly rehearsed.

If a publisher released a game you genuinely enjoyed or found inspiring, mentioning that briefly can help create connection. But only if it is genuine. Forced networking is usually obvious immediately.

During the Pitch: Focus on Play, Not Performance

If time allows, the best pitches often involve actually playing the game. Not presenting slides, reading prepared scripts, or explaining every rule upfront, just playing.

A good live pitch naturally blends explanation, demonstration, and onboarding together. This helps publishers quickly understand how turns feel, where decisions happen, and whether the game creates momentum.

You also do not need to explain everything. During a short pitch, it is completely acceptable to skip:

Focus on the strongest part of the experience. Players - and publishers - react emotionally before they analyze systems deeply. During a pitch, the publisher is unconsciously asking:

Your pitch should answer those questions quickly.

(TableHop note: if you want to explore emotional engagement in games more deeply, we covered it further in The 8 Types of Fun in Board Games: How the MDA Framework Helps You Design for Emotion)

One Important Rule: Don’t Manipulate the Demo

This sounds obvious, but it happens surprisingly often: designers intentionally lose their own game to make the publisher feel good during the demo. Experienced developers usually notice immediately, and it creates a strange impression. It either suggests the game lacks depth, or that the designer lacks confidence in their own design. Neither helps the pitch.

Treat the demo as a real game and play naturally. The goal is not to “win the meeting.” The goal is to let the design speak honestly. 

Your Pitch Should Iterate Like Your Game

One of the biggest mistakes designers make is treating the pitch as separate from development. It isn’t. 

A pitch is another system that requires iteration. If people repeatedly misunderstand the hook, the genre, the player experience, or even the objective of the game, the issue is usually not random. The pitch itself needs redesign.

Feedback is rarely perfectly literal, but patterns matter. If multiple people become confused at the same moment during your pitch, that is a strong signal that something in the communication is unclear.

Improve the pitch the same way you improve mechanics: through iteration.

Final Thoughts

Pitching a board game is not about theatrical presentation. It’s about clarity. Publishers are not searching for perfect prototypes or flawless branding. They are looking for games that create strong experiences, communicate clearly, and show evidence of serious iteration.

The strongest pitches are usually surprisingly simple. Clear rules, a functional prototype, and an explanation that helps someone quickly understand why the game is interesting. That is the foundation. Everything else is secondary.

If your game is genuinely compelling, your job is not to overwhelm the publisher with information or presentation. Your job is to remove as much friction as possible between the publisher and the experience of playing the game.

TableHop’s Note

Pitching is one of those parts of game design that seems simple from the outside, but becomes much more nuanced once you start approaching real publishers. We only scratched the surface here.

We don’t have a dedicated course on pitching board games yet, but if you’d like us to explore topics like publisher outreach, convention pitching, submission etiquette, contracts, or live demo preparation in more depth, let us know.

Your feedback helps shape what comes next at TableHop.