How to Present Design Work to Clients (So It Gets Approved)

You finish a design you're proud of, drop the link in an email with "here's the homepage, let me know what you think," and brace. What comes back is hesitation: "Hmm, not sure about the hero, can we see some other options?" The work was good. The presentation was nonexistent, so the client had nothing to react to except their own uncertainty.

How you present design work shapes the response more than the work itself does. A client dropped into a finished design with no framing defaults to nitpicking and doubt, because that's what an unguided reaction looks like. A client who's been walked through the why evaluates the work against goals instead of taste. Same design, completely different conversation.

Here's how to present so clients make clear decisions instead of vague ones.

Why presentation changes the reaction

When you hand over a design with no context, you've left the client to invent their own frame for judging it. With nothing else to go on, they reach for personal preference ("I don't love orange") and false comparison ("my competitor's site has a video"). That's not a difficult client. That's the natural result of being handed a finished thing with no story.

Presentation replaces that vacuum with a frame. When the client knows what problem the design solves, what you decided and why, and what you're asking them to assess, they evaluate against that instead of against whatever floats into their head. You're not manipulating them. You're giving them the context you have and they don't, so their judgment has something solid to land on.

How to present design work to clients

1. Lead with the goal, not the design

Before you show anything, restate what this work is for: "The goal here was to get a first-time visitor to understand what you do and book a call within ten seconds." Now the design is being judged against a shared objective, not against the client's mood. Every reaction has a yardstick.

2. Walk them through your decisions

Don't just reveal the design. Narrate the thinking: "I led with the headline because your customers told you they didn't get what you sold. I kept one call to action so the path is obvious." When a client understands why something is the way it is, they stop reading it as an accident they should fix and start reading it as a choice that serves their goal.

3. Pre-empt the obvious objection

If you know what they'll question, address it first. "You might expect a hero video here. I went with a still and a fast load instead, because your audience is mostly on mobile and a video would slow the first impression." Naming the objection before they do turns a doubt into a decision you already made for good reasons.

4. Tell them exactly what to react to

End the presentation with a clear ask, scoped to the stage: "What I need from you now is whether this direction feels right for your audience. We'll nail the fine details in the next round." Without this, clients feel obliged to find something to say and reach for trivia. A specific ask gets a specific, useful answer. This is the same principle as asking for feedback well.

5. Make reacting easy and located

However you present, give the client a way to respond on the work itself, pointing at the exact spot, rather than composing a paragraph from memory afterward. The closer the reaction is to the thing, the more specific and less drifting it will be.

In a meeting vs async

Both work; they just need different handling.

Live (call or in person). You control the frame in real time, which is the advantage. The risk is that verbal "yes, love it" reactions evaporate the moment the call ends. So narrate live, but capture the outcome in writing afterward. A call is a great place to present and a terrible place to record a decision.

Async (a link they review on their own time). More common now, and often better, because the client reviews calmly without being put on the spot. The risk is the missing frame, which you solve by writing the context into the presentation itself: a short note on goals and decisions alongside the work, not just a bare link.

Either way, the principle holds: present with a frame, then capture the decision in a form that survives.

From presentation to decision

A good presentation earns a positive reaction. But a reaction isn't a decision, and this is where strong presentations still leak: the client says "love it" on the call, and three weeks later asks to change it, because "love it" was a mood, not a sign-off. The presentation should lead into an explicit approval on a specific version, which is a different and final step. That distinction, feedback versus approval, is what turns a good meeting into a closed round.

How Lyba carries presentation into sign-off

Lyba is built for the async version of this, which is how most Framer work is reviewed. You send one review link to your live site, the client reviews the real thing (real animations and interactions, no broken proxy render), and they react by pinning located comments exactly where they mean, so their feedback stays specific instead of drifting into vague prose.

Then it closes the loop a presentation alone can't: when the work is ready, the client signs off on a specific version, and Lyba records it as a dated approval in your dashboard. The presentation guides the reaction; the sign-off captures the decision. You finish with an approved version on the record, not just a good meeting you hope the client remembers the same way you do.

FAQ

How should I present design work to a client? Lead with the goal the design serves, walk through your key decisions and why you made them, pre-empt the obvious objection, and end with a specific ask scoped to the stage. This gives the client a frame to judge against instead of leaving them to default to personal taste.

How do I present designs so clients don't nitpick? Nitpicking is what an unguided reaction looks like. Replace the vacuum with context: explain the objective and your reasoning, and tell the client exactly what to assess right now ("is the direction right?" not "what do you think?"). A specific frame produces specific, useful feedback.

Is it better to present designs live or async? Both work. Live lets you control the frame in real time but verbal approval evaporates, so capture it in writing after. Async reviews are calmer and increasingly standard, but you must write the framing into the presentation since you're not there to narrate it.

How do I turn a good presentation into an actual approval? Treat the reaction and the decision as separate steps. After a positive presentation, ask for an explicit sign-off on a specific version and record it. A "love it" in a meeting isn't approval until it's captured against a version. Here's why that matters.

Present to guide, not just to reveal

A design dropped in an inbox gets judged on instinct. A design presented with its reasoning gets judged on whether it works, and then approved with confidence.

See how Lyba carries a Framer review from located feedback through to a recorded sign-off, or start a free 14-day trial.