drafty

How to get feedback on a logo

Quick answer

To get useful feedback on a logo, pair every concept with a specific question tied to the brief — not 'what do you think?' but 'which of these best reads as premium to your target customer?' Then give clients a way to click the exact element they're reacting to rather than describe it in words. Vague feedback ('make it pop') almost always comes from clients who can't point at what they mean — not from clients who don't know what they want.

Step 1

Present in context, not on a white canvas

A logo on a blank slide invites abstract opinions. Show it on a mock business card, a letterhead, a tote bag — whichever application matters most for this client. In Illustrator or Figma, drop the lockup onto a Smart Mockup template before you export the presentation PDF. This one change shifts client feedback from 'I don't love the font' to 'the wordmark disappears on the dark background' — which is a specific, actionable note. Black-and-white before colour is also worth building in: if the mark only works in full colour, that's feedback you want to surface in round one, not after the client has approved the palette.

Step 2

Ask two or three brief-anchored questions alongside the concepts

Send the concepts with a short list of questions written against the brief, not against your personal preferences as a designer. For a law firm logo: 'Which of these feels most trustworthy to a first-time client?' is useful. 'Which do you like more?' is not — it hands the decision to personal taste rather than audience fit. Limit to three questions per round; more than that and clients stop at the first one. If you need a verdict between two concepts, frame it as a forced choice: 'Concept A or Concept B — which would you stop scrolling for?' Forced choices are faster and produce cleaner rounds.

Step 3

Share a Figma view link for spec-level review

In Figma, click Share → 'Anyone with the link can view' → Copy link. Your client can inspect spacing, font size, and hex values in the browser. For a client who needs to check that the icon clears 16px or that a colour meets their brand standards document, this is the right format. The known limitation: leaving a comment in Figma requires a Figma account. Many clients will hit that prompt and email you instead. Worth knowing before you send it. If your client is already inside Figma day-to-day, the friction is zero. If they're not, budget an extra round of back-and-forth email to convert the notes they couldn't leave directly on the file.

Step 4

Share a review link they can annotate without an account

The most reliable method for a non-technical client who needs to mark up specific elements: share a URL that opens the logo export in any browser and lets them click the exact element they mean — the letterform, the icon, the colour swatch — and pin a note right there. No Figma account, no extension, works on their phone. Their comment lands anchored to the exact spot, not described loosely in an email. You see it in a thread, reply, and push the next version to the same link. Tools in this category include Markup.io, GoVisually, and Drafty. The practical difference shows up when you have two or three reviewers: each one's notes stay on the artifact, not split across three different iMessage threads trying to describe the same corner of the icon.

The faster way

If you're collecting client sign-off on a logo — not annotating it yourself — drop the PNG or PDF export into Drafty and share the link. Your client clicks the exact element they're reacting to: the wordmark, the icon, the colour. Their note pins right there. You reply, resolve it, push the revised version to the same URL. No Figma account required on their end, no re-emailed files, no 'the bit in the top right' emails to decode.

Open a live demo

Questions

How do I stop getting vague logo feedback like 'make it pop'?
Vague feedback almost always means the client can't point at what they mean — so they describe instead. Two fixes: ask specific, brief-anchored questions ('which feels more trustworthy to a first-time buyer?') rather than open ones, and give clients a way to click the exact element rather than describe it in text. When they can click the letterform and pin a note, the note becomes 'this feels too light at small sizes' instead of 'not sure about the font'.
Should I ask clients to annotate the logo themselves or just answer questions?
Both, in sequence. A short set of forced-choice questions (two or three, tied to the brief) gives you the decision. Annotation on the specific element gives you the detail behind it. Asking only questions can leave you with 'I prefer Concept B' but no idea which part of B to keep. Asking for open annotation with no frame gets you everything and nothing.
Can my client comment on a logo without a Figma account?
Not in Figma — leaving a comment requires a login, which has been a documented friction point for freelance designers since at least 2021 and still applies. For a client who isn't already a Figma user, export the logo as a PNG or PDF and share it through a browser-based review tool where they comment as a guest — no account, no extension.
What file format should I send a logo in for client feedback?
PNG at 2x works for most visual feedback — it's fast to open on any device and renders accurately in any browser. PDF is worth adding when the client needs to check how the mark reproduces in print or wants to zoom into the vector. For a browser-based review link, PNG or PDF both work; the tool wraps it in an annotation layer either way.
How many rounds of revisions are normal for a logo project?
Two structured rounds is the standard when feedback is specific and anchored to the brief. The first round covers the concept direction; the second covers refinements to the chosen direction. Unstructured rounds — where the scope of feedback isn't defined and clients can reopen closed questions — regularly run to four or five. Setting a revision limit in the contract and giving clients a way to annotate rather than describe tends to keep it to two.
How do I get feedback from multiple stakeholders on a logo without conflicting notes?
Share one link and make it the only place for notes — not email, not Slack, not a Zoom call where someone screenshots their screen. When all reviewers comment on the same artifact at the same URL, conflicting opinions are visible to each other and the person with sign-off authority can resolve them in the thread rather than sending you two contradictory emails to reconcile alone.

Keep exploring

Stop emailing files back and forth.

Share one link. They comment on the exact spot — no account, always the current version.