How to Present Design Work to Clients (Even When You're Not in the Room)
Presentation shapes how clients react to your designs. How to present design work to clients with context and framing, including async review through a share link.
How you present a design changes how a client reacts to it, often more than the design itself does. The same layout can land as "confident and considered" or "I'm not sure about this" depending entirely on how it arrives. A design attached to a bare email with "let me know what you think" invites nitpicking. The same design, framed with the reasoning behind it and a clear ask, invites a decision.
Most advice on presenting design work assumes a meeting: you, the client, a screen share, a room. That advice is good, and I will cover it. But a lot of client work today is asynchronous. You send the work, the client looks at it on their own time, and there is no room to read. Presenting well when you are not there is a distinct skill, and it is the one most guides skip. This piece covers both.
Start with the brief, not the design
Whether you are presenting live or sending a link, resist the urge to open with the visuals. Open with the problem you were solving.
Bring the client back to what you agreed at the start: the goal you set and the job the design was supposed to do. "You asked for a homepage that makes a first-time visitor understand what you do within five seconds and feel confident enough to book a call." Now the client is evaluating the work against a shared standard you both signed up for, instead of against whatever mood they happen to be in.
This reframes the entire review. Without the brief up front, a client evaluates a design on personal taste. Do I like this blue. With the brief up front, they evaluate it on fit. Does this help a visitor book a call. The second question is the one you want them answering, and it is also the one your work is actually built to win.
Show the thinking, not just the result
A design presented with no reasoning is just a picture, and everyone has an opinion about a picture. A design presented with the reasoning behind the key decisions is an argument, and an argument is harder to wave away with a gut reaction.
You do not need to narrate every pixel. Pick the handful of decisions a client is most likely to question and get ahead of them. "We kept the header minimal so the product photography carries the page, and that's what tested best for brands in your space." "The call-to-action repeats three times as you scroll because most visitors decide to act at different points." Now, when the client's instinct is to ask why the header is so sparse, you have already answered it, and answered it with a reason tied to their goal rather than your preference.
This is also your best defense against arbitrary revisions. A client can override "I liked it better bigger." It is much harder to override "we sized it this way because of X," at least not without engaging with X, which turns a reflex into a conversation.
Guide the feedback you want
An open-ended "what do you think?" is an invitation to comment on everything, including things that are not up for debate. If the brand colors are locked, do not present them as though they are open, or you will spend the review defending settled decisions.
Tell the client what kind of feedback is useful at this stage. "This round is about layout and structure. The copy is placeholder and the colors are still coming, so don't worry about those yet." That single sentence saves you a pile of notes about lorem ipsum and lets the client focus their attention where it actually helps. Direct the review and you get a better review.
And limit the options. If you show a client six directions, you have not given them a rich choice, you have given them a paralysis and a committee. Two or three considered options, or often just one strong recommendation with your reasoning, gets you a cleaner decision than a buffet does.
Presenting when you're not in the room
Here is the part most guides leave out. A growing share of client review never happens in a meeting. You send the work and the client reviews it alone, on their schedule, frequently on a phone between other things. Everything above still applies. It just has to survive without you there to deliver it.
The instinct is to compensate with a long email: all your framing piled in a wall of text above an attachment. It rarely works. The client skims the email, opens the attachment, and reacts to the visual with none of the framing you carefully wrote, because the framing and the design were in two different places.
The fix is to put the presentation and the work in the same place. When the reasoning lives right next to the design the client is looking at, the framing actually reaches them at the moment they are forming an opinion, not in an email they half-read first. This is a large part of why sending a design as a bare attachment produces worse feedback than sending it through a review that holds context and comments together. There is more on why attachments and email threads specifically degrade feedback in the piece on collecting feedback without endless emails.
A few things make async presentation work as well as being in the room:
- Put your framing where the design is. A short note at the top of the review, stating the goal and what this round covers, does the job your opening would do in a meeting.
- Let the client react in context. When a client can pin a comment on the exact element they are reacting to, you get the specific, located feedback a live session would surface, instead of a vague email you have to decode.
- Make the ask a clear action, not a question. "Reply with thoughts" is weak. A concrete step, like asking them to approve this version or request specific changes, gives the review an ending, which a design in an inbox never has.
End with a decision, not a maybe
However you present, the presentation should drive toward a specific next step, and the strongest one is a real decision.
The weakest way to end is "let me know your thoughts," which lets a review dissolve into silence or a vague "looks good" that commits to nothing. The strongest way to end is to ask the client to either approve the direction or tell you specifically what needs to change. That is the difference between a review that moves the project forward and one that leaves it exactly where it was, waiting on a reply that may never come.
An explicit sign-off also protects the presentation you just made. When a client approves a specific version, the reasoning you presented is now attached to an agreed decision rather than floating in an email thread. If the project later drifts, you have a clear point you can both return to. This is the whole idea behind a structured approval step, and it is what turns a good presentation into a closed loop instead of an open-ended one.
Frequently asked questions
How do you present design work to a client professionally?
Start with the brief so the client evaluates the work against a shared goal, explain the reasoning behind your key decisions, guide them toward the feedback that's useful at this stage, and end by asking for a clear decision rather than open-ended thoughts. Whether you present live or asynchronously, that structure keeps the review focused and moving.
How do you present design work when you can't meet with the client?
Put your framing and the design in the same place instead of splitting them between an email and an attachment. A short note stating the goal and what this round covers, a way for the client to comment directly on the design, and a clear approve-or-request-changes step together do the job your live presentation would.
How many design options should I show a client?
Usually two or three considered options, or a single strong recommendation with your reasoning. Showing many options tends to create paralysis and committee-style feedback rather than a clean decision. Fewer, well-argued directions get you a faster and better answer.
How do I stop clients from commenting on things that aren't ready?
Tell them at the start of the review what this stage is about and what to ignore. A single line, such as "the copy is placeholder and colors are still coming, so this round is about layout," redirects attention to where feedback actually helps and saves you a pile of notes on unfinished elements.
Aligno lets you present a design through one link, with your framing and the client's pinned feedback in the same place, ending in an explicit approval. No client account required. Try it free.