Presenting Logo Concepts to Clients Using Production Context and Design Rationale

When you present a logo, you are not inviting an opinion on art. You are running a decision process, and the process fails the moment anyone says “I like it” or “I don’t like it.” The method for presenting logo concepts to clients is to ground every conversation in production reality, not personal taste. You do this by showing each concept only in the contexts that will expose its weaknesses, and by explaining each decision with a production constraint, not an aesthetic preference. The client who understands why a stroke weight holds at 16 pixels is a client who can approve a mark with confidence. The client who is asked whether they like the blue is a client who will ask for a different blue, then a different font, then a different concept entirely. You are the one who has done the research. You are the one who knows what happens when the logo hits a browser tab icon, a one-colour print run, or a dark background. Your job is to make the client see that too.

A logo that looks elegant on a 27-inch monitor at 200% zoom is a logo that may fail completely at 16 pixels in a browser tab. This is not a theoretical risk. It is the most common reason a mark gets rejected after it ships. The solution is to build the presentation around production context from the start. For each concept, you show the same mark in at least three to five application mockups, and you choose those contexts deliberately. A browser tab icon at 16×16 pixels. A one-colour variant on a dark background. A reversed variant knocked out of a photograph. A spot colour variant specified in Pantone Matching System values, and a process colour variant built from CMYK. You are not doing this to make the work look comprehensive. You are doing it because each of these contexts is a test, and every test reveals something about the mark that a screen proof cannot.

The Tests That Expose Weakness

The browser tab icon test shows whether the mark survives when all detail is stripped away. The one-colour test shows whether the mark has a shape, or just a palette. The reverse test shows whether the negative space holds up when the rules change. And the Pantone versus CMYK test shows whether the brand colour is even achievable on the materials where it will live. If a concept fails any of these tests, you do not present it. You go back and fix it, or you drop it. The presentation is not a gallery show; it is a filter.

The single most important decision you make before you enter the presentation is how many concepts to show. AIGA’s Professional Practices in Graphic Design is explicit on this: two to three distinct directions is the maximum. More than that and you are not a designer; you are a menu. The client will not pick a direction. They will ask for a combination of the best parts of all of them, and you will have created a monster that pleases no one. Three directions is enough to show range: one safe, one bold, one in between. Each direction must be resolved well beyond the logo itself. You bring the tab icon, the one-colour variant, the reversed variant, and the mockups for each. You do not bring a logo on a white background and let the client imagine the rest. The client will imagine the rest as whatever they wanted it to be.

The moment the client says “I like the font on number two but the colour on number one,” you have lost the plot. The font and the colour are not separable decisions. The mark, the type, the colour, and the negative space are one system. If the client cannot articulate which communication task a concept fails under a stated production constraint, then the concept has not failed. The client is failing to evaluate it on the terms that matter. You have to give them better terms.

Here is the rule for every rationale you write for the presentation. Every sentence must complete the phrase “this works because…” with a production fact. Not “this feels balanced” but “this stroke weight holds at 16 pixels.” Not “this colour is modern” but “this blue meets WCAG 2.2 contrast ratio of 4.5:1 against white, and 3:1 against the dark background we use on the website.” Not “this font is friendly” but “the x-height of this typeface is large relative to its cap height, which keeps the logotype legible at 14 px bold, which is the minimum size for large text under WCAG 2.2 Success Criterion 1.4.4.” When you have to explain why you chose a particular point size for the tagline, you do not say it looks nice. You say the baseline grid increment is one times the leading value of the primary typeface, and the tagline falls on that grid. The client may not know what a baseline grid is. That is fine; this is how they learn.

Making the Process Visible

The rationale is not a justification after the fact. It is the design process itself, made visible. When the client asks “why this blue,” you point to the Pantone value, you show the sRGB equivalent, you explain that the CMYK build is within the GRACoL 2013 ICC profile’s gamut, and you show what happens if you try to print it on a non-coated stock. The rationale is the difference between a designer who is trusted and a designer who is merely tolerated.

You have given the presentation. You have shown the mockups. You have cited the contrast ratios and the ICC profiles. And then the client leans back and says the magic words: “I don’t know, I just don’t love it.” This is the moment the client logo feedback process either works or collapses. You do not ask what they do not love. That leads to a shopping list of subjective preferences. You ask which communication task the mark fails. You ask which of the production constraints they saw in the mockups is the problem. Is it the tab icon that reads as a smudge? Is it the one-colour variant that loses the shape? Is it the reversed variant where the negative space disappears? You redirect every subjective comment to an objective criterion by asking a specific question: “Which variant performs the communication task under the stated constraints?” If they cannot name one, then the mark has not failed. The mark has done its job.

The client is talking about something else, and it is your job to find out what. Maybe they are worried about something they saw on a competitor’s site. Maybe they are nervous about approval from their own boss. You have to give them a tool for evaluating the work that does not depend on their mood, their lunch, or the last thing they scrolled past on their phone. That tool is the production constraint. It is the only ground on which you can both stand.

You have already applied this rule in your studio, before the presentation. Let us be explicit about how. No concept gets presented unless it has passed two tests. The one-colour test: the logo must work as a solid black shape on white, and as a solid white shape on black, with zero shades of grey. If it only works in colour, it is not a logo; it is a poster. The browser tab icon test: the logo must be legible at 16×16 pixels, which is the standard set by Google’s Material Design Icon Guidelines. That means the mark cannot rely on strokes thinner than 1.5 pixels at that size. It cannot rely on letterforms that will fuse together. It cannot rely on fine serifs that will disappear. If you cannot strip the mark down to a shape that is recognisable at that size, the mark has a scalability problem, and no amount of “it will look great on the sign” will fix it.

Why the Tab Icon Comes First

The tab icon test is not an afterthought. It is the first thing an audience sees when they bookmark the site, or open the browser tab, or share the link on their phone. If they cannot tell what the mark is, they will not remember it. Present the tab icon variant of each concept, not as a bonus, but as a gate. If it fails, you do not show the full logo on the slide. You show the failed icon, and you explain why the mark did not survive, and you show the revised variant that did. That is what a gate is for.

You are not asking the client to imagine the logo on a business card. You are showing it to them. David Airey’s Logo Design Love, 2nd edition, is the source for the range: three to five application mockups per concept. That is the minimum, not the maximum. Five contexts is better. You need a mix that covers the range of production realities the logo will face. A stationery suite in a PDF/X-4 file, because that is what the printer will use. A social media avatar at 400×400 pixels, because that is the size most platforms will crop it to. A website hero at 1920×1080 pixels, because that is the typical laptop screen. A physical sign, because that is where the safe area gets tested. And a one-colour merchandise print, because that is where the spot colour decision gets made.

You do not need a fancy 3D mockup for every context. A clean, flat presentation of the logo on a neutral background with the correct padding is more honest and more useful. The mockup is not about making the logo look good. It is about placing the logo into a situation where you can have a real conversation about how it performs. The client will not have to guess whether the logo works on a dark background. You are showing them. The guesswork is gone. That is the point.

You have shown the mockups. Now you show the details that make the mark technically sound. The primary one is scalability. A logo is not a single file; it is a system that has to work from 16 pixels to 4000 pixels on a side. Show the client the mark at 16 px, at 32 px, at 100 px, and at 1000 px. Show them the stroke weight at each size. Show them what happens to the letter spacing when the mark gets smaller. Then show them the clear space. The minimum safe area for logo isolation is one times the x-height of the logotype, a standard from ISO 3864-1:2011. You are not guessing at this; you are specifying it. You show the client a diagram with the clear space clearly marked, and you explain that this is the minimum, and that any application that goes below this minimum is a brand violation.

This is not about being difficult. It is about protecting the logo from being crowded, which makes it unreadable, which makes it fail its communication task. Then you show them the alternative: a variant with more clear space that reads better, and you explain why the extra space is necessary for the small sizes. The client does not have to care about the details of the ISO standard. They do have to care that you care. That is what tells them you will protect the logo after they stop looking at it every day.

Colour is where the client feedback process most often goes off the rails. The colour on their screen is not the colour they will get on paper. You pre-empt this by specifying colour in every relevant system in the presentation. For each concept, you provide the Pantone Matching System Solid Coated value, the CMYK build, the RGB value, and the HEX value. You explain that the Pantone value is the physical reference standard, the swatch you will use to match on press. The CMYK build is for process colour printing, where the colour is built from four inks and will not be exactly the same as the Pantone, but can be close if the correct ICC profile is used. The RGB and HEX values are for screen, and you specify sRGB IEC 61966-2-1 as the colour space. Web browsers assume sRGB.

Show the Failure, Not Just the Spec

You also show the client what happens when you do not manage this properly. You show a logo that was designed in Adobe RGB and displayed on an sRGB-only screen, and you show how the colour shifts. You show what happens when a spot colour is converted to process without soft-proofing: the orange becomes muddy, the green becomes olive. You specify the current Pantone book, and you tell the client that this value will be part of the brand guidelines. You are not giving them a colour. You are giving them a specification.

You have specified the logo mark. Now you specify the type. The typography rationale is not a footnote; it is a core part of the presentation. For each concept, you name the typeface, its classification, and its x-height ratio. You explain why the x-height matters: a typeface with a large x-height is more legible at small sizes, which is why it is often used for wayfinding, and it works better on screen. A typeface with a small x-height looks more elegant but suffers at tab icon size. You explain the choice of a geometric sans versus a humanist sans, or a transitional serif versus an old style serif, and you tie it to the communication task. The typeface is not chosen because you like it. It is chosen because its character, its contrast, its stroke weight, and its proportions all support the message the logo needs to send.

You will also specify the minimum size at which the logotype can be used. That minimum comes from WCAG 2.2, not from preference. If the logotype is treated as text, it must meet the contrast ratio of 4.5:1 for normal text and 3:1 for large text, which is defined as 18 pt or 14 pt bold. You show the client these numbers in the presentation, and you show the test results, so there is no argument later about whether the logo is legible.

Every good travel guide tells you what to do when the road is closed. This one is no different. Here is the failure case for logo presentations. You are in the presentation, and the client says they want to see a variant in a different colour. You know, because you have done your research, that the colour they are asking for will not work at the sizes and contexts you have shown. The client is not going to budge. If you refuse, you are difficult. If you agree, you are designing towards failure. What do you do when the normal route of rationale and standards is closed? You go back to the production tests. You do not say no. You say: we can spec that colour for the one-colour variant, but it will fail the WCAG contrast test on white, and it will not be legible on the tab icon. Let us show you what it looks like at 16 pixels. Then you pull up the mockup, and you show them the failure. If they still want it, you quote the cost of the redesign, and you put it in writing. The cost is not a punishment. It is the price of the change. You are the professional; you are the one who knows what the work has to endure. You do not have to be rude to be firm. You just have to be correct, and you have to have the evidence. The client who sees that you are protecting them from a costly mistake will trust you more, not less.

You have a 45-to-60-minute presentation. You are not going to fill it with more slides. You are going to use the time to have a conversation. The structure is simple. The first 10 minutes are for the context: what the business does, who the audience is, and the one communication task the logo must perform. The next 10 minutes are for the concepts, shown one at a time, in the mockups, with the rationale delivered out loud, not just on the slide. The next 10 minutes are for the feedback, and this is where the redirect question lives. The next 10 minutes are for the technical specifications, the Pantone values, the contrast ratios, the clear space, the tab icon. The final 10 minutes are for the decision.

Ending With a Decision

You need to end with a clear decision: which direction is approved, and what the next steps are. If the client cannot decide, you schedule a follow-up, but you do not leave without a decision. You do not leave with a list of changes to three different concepts. You leave with a direction. If the client has not decided, then you have not done your job. You have shown them a menu, and they are still hungry. The cure is to be specific about what is needed, and to be firm about the timeline. You are not being impatient. You are being structured, and structure is what the client needs.

The presentation ends, but the work does not. You do not email a single JPEG. You prepare a file package that has everything the logo needs to survive contact with a printer or a developer. The print-ready files are delivered as AI, EPS, SVG, and PDF/X-4. The PDF/X-4 is the ISO standard for print-ready PDFs, and it supports live transparency and ICC colour management. The SVG is the vector format for the web, and the PNG-24 is the raster format for the web, complete with alpha channel. You deliver the Pantone value, the CMYK build, the RGB values, and the HEX values in a one-page specification sheet. You also deliver the tab icon as a set of PNGs at 16×16, 32×32, and 48×48 pixels. You do not deliver a raster-only logo and call it a day. A raster-only logo is a source-file failure, not a design asset.

Delivering a System, Not Just an Image

You also deliver a variant of the logo in black and white, and a reversed variant in white, in addition to the full-colour variant. The client will need these, whether they know it now or not. You are not just delivering a design; you are delivering a system. And you are doing it so that the client can hand that system to a print vendor or a web developer and be confident that it will work. That is the difference between a designer and a technician who makes pretty pictures.

During the presentation, you are not going to rely on memory. You are going to capture feedback in a way that is structured and usable. Use an annotated PDF or a Figma comment thread for the feedback. Show the client the PDF or the Figma frame with the mockups on it, and ask them to comment on the specific block, not on the whole design. This forces the feedback to be specific. When a client says “this feels off,” ask them to point to the block, and ask again which communication task it fails. Do not accept “this feels off” as an answer. Annotate the PDF as they are speaking, and read it back to them: “So you are saying that the tab icon at 16 pixels is not legible, and you are not concerned about the full-colour variant.” This is a skill. You are doing two things: you are showing the client you are listening, and you are forcing them to be precise.

The goal is a feedback list that is a list of actions, not a list of opinions. An action is “increase the stroke weight by 0.5 pixels so the tab icon is legible.” An opinion is “I do not like the weight.” You can work with an action. You cannot work with an opinion. There is nothing to change that will not destroy the logo for the next person who looks at it.

Frequently Asked Questions

Question 1: How many logo concepts should I present to a client?

You should present two to three distinct directions. This is the standard from AIGA’s Professional Practices in Graphic Design. More than three invites the client to treat the presentation as a menu, which leads to requests for combinations that will not work.

Question 2: What is a context mockup and why is it necessary?

A context mockup is a presentation of the logo placed into a realistic production environment, such as a browser tab icon at 16 pixels, a one-colour print, a reversed variant on a dark background, or a sign. It is necessary because it tests the mark against production constraints and prevents the client from evaluating the logo only on a white background at 200% zoom.

Question 3: How do I explain a logo design rationale that cites production, not taste?

You complete the sentence “this works because…” with a production fact. For example, “this stroke weight holds at 16 pixels” or “this colour meets the WCAG 2.2 contrast ratio of 4.5:1 against white.” You never say “this feels balanced” or “this is modern.”

Question 4: What do I do when a client gives subjective feedback?

You redirect it to an objective criterion by asking which variant performs the communication task under the stated constraints. Ask them to point to the specific block in the mockup and name the production constraint that is failing. Do not accept “I do not like it” as an answer.

Question 5: What is the one-colour test and why is it required?

The one-colour test is showing the logo rendered as a solid black shape on white, and a solid white shape on black, with no mid-tones. It is required because a logo must have a shape independent of its colour. If it fails this test, it is a poster, not a logo.

Question 6: What is the favicon test and why is it 16 pixels?

The favicon test is rendering the logo at 16×16 pixels, the standard from Google’s Material Design Icon Guidelines. It is required because this is the size a logo appears in a browser tab or a bookmark. If the mark is not legible at this size, it has a scalability problem.

Question 7: What file formats do I deliver on approval?

For print, you deliver AI, EPS, SVG, and PDF/X-4. For digital, you deliver SVG, PNG-24, and WEBP. You also deliver a specification sheet with Pantone, CMYK, RGB, and HEX values, and standard black and white or reverse variants. You never deliver a raster-only logo as a source file.

You do not have to be rude to be firm, but you have to have the evidence, and the cost of the change is the price of the redesign, which you quote in writing when the client insists on a colour that fails the WCAG contrast test at tab icon size.