Logo Design Presentations: What I Stopped Doing

The Mockup Trap

For a while I was spending nearly as much time on mockups as on the actual logo design. Phone screens, coffee cups, embossed business cards, etched whiskey glasses — the full lifestyle presentation. The work looked impressive. It also created a problem: clients were evaluating the mockup styling, not the logo.

I'd hear feedback about the color of the coffee cup, or questions about whether the logo would really look like that on a phone. The mockup was doing the selling instead of the logo.

What I Replaced It With

I still use one or two contextual mockups — a business card, a signage application — but I present them at the end, after I've already walked through the logo on a neutral background.

The core of my presentation is now the logo on white, the logo on black, the logo on the primary brand color, and the logo at several sizes. This is the most honest context I can offer, and it focuses the feedback where it belongs: on the actual design decisions.

Presenting Three Concepts, Not Six

I used to present up to six concepts. More options, more value — that was the logic. In practice, more options spread the conversation thin. Clients would combine elements from different concepts, try to have three logos instead of one, or get so overwhelmed by choice that decisions stalled.

Now I present three concepts maximum. Each is fully developed, each represents a genuinely different strategic direction, and I can articulate a clear rationale for each. Three is enough to show range and give the client a real choice without creating paralysis.

Presenting With Rationale

I used to silently hand over a presentation PDF and wait for reactions. Now I always walk through the work verbally first. I explain the strategic thinking behind each concept before the client has a chance to react to the aesthetics.

This changes the conversation. Instead of "I don't know, something feels off," I get feedback relative to the stated intent: "This concept is supposed to feel approachable, but that letterform feels a bit cold to me." That's specific. I can work with that.

The Revision Process

I build one round of revisions into every logo project, with a clear scope: refinements to the chosen direction, not a new direction. This needs to be in the contract and explained verbally before the project starts. Revisions does not mean a new logo.

This boundary protects the work. It also protects the client — unlimited revision cycles produce worse work, not better, as the design gets committee'd into mediocrity.

The Approval I Actually Want

My goal in a presentation isn't applause. It's informed agreement. I want the client to understand what problem the logo is solving and why the design solves it, and then to decide whether they agree. That informed sign-off is worth far more than an enthusiastic reaction that evaporates the first time someone on the client's team asks why the logo looks like that.