Logo Design Presentations: What to Show and How to Show It

I've presented logo designs hundreds of times. Early in my career, I made every presentation mistake you can make: showing too many options, showing underdeveloped options, presenting without context mockups, letting clients evaluate colors and typefaces in isolation. The result was feedback that was impossible to act on and decisions that got unmade.

The way you present a logo concept shapes how a client evaluates it. A good presentation makes the right choice obvious. A bad presentation invites subjective nitpicking about things that don't matter.

How Many Concepts to Show

I present three logo directions. Not two, not six. Three.

Two feels like a this-or-that choice, which invites clients to ask for a hybrid of both. Six overwhelms most clients and invites them to cherry-pick elements from different directions rather than committing to a concept.

Three options give clients a genuine choice between distinct strategic directions while keeping the decision manageable. Each direction should represent a genuinely different concept, not the same idea with different typefaces.

Every option I present is one I would be proud to defend. I don't present a weak "sacrificial option" to make the others look better. If I find myself doing that, it means I don't have three good directions and I need to keep working.

Developing Before Presenting

An underdeveloped option in a presentation does more damage than not showing it. A sketch-level concept shown alongside a polished concept will always look worse than it is, and clients will eliminate it before it gets a fair hearing.

Before I present anything, I develop every concept to roughly the same level: full vector construction, color variants, size testing. Not full brand system work, but enough to see if the idea is genuinely viable.

Context Mockups Are Required

A logo floating in white space tells you almost nothing about whether it works as a brand identity. Clients evaluate logos in isolation and then are surprised when the lockup looks awkward on a business card.

Every presentation I give includes context mockups for each concept: business card, letterhead, a social media profile, and at minimum one product or environmental application relevant to the client's business. These mockups do two things: they show the logo working in context, and they make the presentation feel like brand design rather than logo design.

Context mockups also surface problems early. A logo that looks fine in isolation might be awkward in a horizontal lockup required for letterhead. Better to discover this at the concept stage than after the client has approved it.

Structuring the Narrative

I present each concept as a direction with a rationale, not just a visual. I explain what strategic positioning the direction is responding to and what it's communicating. I frame the visual before I reveal it.

This matters because it shifts the evaluation from "do I like this" to "does this accomplish the objective." Clients who evaluate against a clear rationale give more useful feedback than clients who are reacting purely to personal aesthetic preference.

What to Do With Feedback

I tell clients at the start of every presentation: I want to understand what's working and what isn't working, not what to change. "I don't like the color" is not useful feedback. "This doesn't feel approachable enough for our audience" is useful feedback.

Most clients will give you the first type of feedback by default. Your job is to translate it into the second type. "You mentioned the color feels too cold. Can you say more about that? Are we missing warmth, or is the issue that it doesn't feel differentiated enough from competitors?"

Good translation turns aesthetic opinions into strategic direction. That's the feedback you can actually work with.