How to Share a Design Mood Board With Clients (and Get Real Feedback)

Why client feedback dies in a Slack thread

Every agency and freelance designer has run this loop: you gather ten reference sites, drop the screenshots into Slack or a shared doc, and ask the client which direction feels right. Three days later you have a mess. One reply says "I like the third one, or maybe the fifth," someone forwards the thread to a stakeholder who wasn't looped in, and by the kickoff call nobody can find the message with the actual images anymore.

The problem isn't the client. It's the format. A chat thread has no persistent layout, no way to browse by look, and no lightweight way to react. Every response has to be typed out as a sentence, which means only the most opinionated stakeholder actually responds, and everyone else just scrolls past.

It gets worse on the agency side too. You end up maintaining the same references in three places at once: a folder on your machine, a deck for the client call, and whatever survived the Slack thread. When the client asks for a revised shortlist two weeks later, you're rebuilding it from scratch instead of just re-filtering something you already saved.

What a client-facing mood board actually needs

Before building one, it helps to be specific about what makes a shared board usable for someone outside the design team. It needs to work for a client who has ninety seconds between meetings, not a designer who lives in the tool all day. That rules out most internal tools built for someone who already knows the file structure and just wants raw storage.

• A single link, no account or login required on the client's end
• A layout the client can scan visually, not a list of file names or dates
• A way to filter or narrow the set, so a board of 20 references doesn't read as noise
• A lightweight reaction, like a vote or a heart, instead of requiring a written comment
• A link that still works next week, so you can point back to it in the next call

How to build a client-ready mood board in about 15 minutes

1. Save references as you find them, not at the end

The habit that actually sticks is saving a site the moment you find it, while you're browsing competitor sites, Awwwards, or a client's own bookmarks folder. A one-click browser extension works better here than a "collect them all in a doc later" plan, because half of what you find during research never makes it into the doc. With Moodmark, clicking the extension on any open tab saves the full screenshot, the color palette read straight from the page, the fonts, and the tech stack automatically, no manual note-taking required. You can also save a whole batch of open tabs in one pass, which matters when you've had fifteen reference sites open across two windows for a week.

2. Narrow it down by filtering, not by scrolling

Ten references is a mood board. Forty is a mess nobody will look at closely. Instead of manually re-sorting a folder, filter your saved library by color or style to pull out the references that actually share a visual thread with what you're proposing. This is also where you catch yourself: if your "cohesive direction" only holds together when you squint, the filter view makes that obvious before the client ever sees it.

3. Turn the shortlist into a public board

Once you have a tight set, share it as a public collection rather than exporting images into a deck. A link-based board keeps the layout intact (a real visual grid, not a row of thumbnails in an email) and means you're not rebuilding the same deck every time a reference list changes. Drop the link in your usual client channel, whether that's email or a project management tool, and skip the file attachment entirely.

4. Let clients vote instead of asking them to write essays

This is the part that actually changes the response rate. On a public board in Moodmark, each reference has a vote button the client can click without logging in or writing anything. Visible vote counts do double duty: they tell you which direction is winning, and they let a client see that a colleague already leaned toward option three, which nudges everyone toward an actual decision instead of an open-ended debate. You still get to ask for comments on the top pick, but you're asking after you already have a shortlist, not before.

Getting feedback that's actually useful

• Cap the board at 8 to 12 references. More than that and votes spread too thin to mean anything.
• Group by direction, not by source. A board that mixes three unrelated visual languages just confuses the read.
• Set a deadline in the message you send with the link. "Vote for your top two by Thursday" gets replies; "take a look when you get a chance" doesn't.
• Follow up on the winner, not the whole board. Once votes cluster, move the conversation to why that direction works, not a recap of every option.

A quick example

Say you're pitching a rebrand for a coffee roaster. Over a week of research you save twenty-odd reference sites the moment you spot them, packaging brands, other roasters, unrelated sites with a texture or type treatment worth stealing. On Friday, instead of scrolling through all twenty, you filter down to the ones sitting in warm, earthy tones, since that's the direction you're leaning. Nine references match. You share that filtered set as a board with a one-line message: "vote for your top two by Monday." By Monday you have vote counts instead of a vague "they seemed to like the earthy ones," and the kickoff call starts from an actual shortlist instead of a slideshow nobody has seen yet.

When to skip the mood board step entirely

Not every project needs this. If a client has already signed off on a style guide, or you're doing a small tweak to an existing site, a formal voting round just adds a day to the timeline for no real gain. This workflow earns its keep at the start of a new engagement, a rebrand, or any project where "what should this feel like" is still an open question. Use it there, and skip it everywhere else.

Where this fits with your usual tools

None of this requires abandoning the tools you already use for project management or client comms. The board is just a link, so it drops into an email, a Notion doc, or a project management ticket exactly like a screenshot would. It replaces the part of the process that was already broken, which is passing loose screenshots back and forth and hoping feedback lands somewhere you can find it again, not the rest of your workflow.