Presenting website concepts to clients as live pages instead of static mockups
Most advice on how to present a website design to a client assumes a mockup: a set of flat screens in a slide deck or a design file. AI tools now make it quick to turn a concept into a working HTML page, so some agencies show clients something clickable from the first meeting. It can lead to better feedback, or to a client who thinks the site is nearly done. Here is how to present either way, and how to make a live concept work in your favour.
How to present a website design to a client
Whatever format you use, a few habits make the meeting go better:
- Start with the goals, not the design. Spend the first few minutes restating what the client told you: who the site is for, what visitors should do, and what was wrong with the old one. Then every decision you show has a reason the client already agreed with.
- Show it in context. Present at real screen sizes, on a real phone if you can. A homepage squeezed into a slide is hard to judge.
- Walk through it in order. Scroll the page the way a visitor would and explain the main choices as you go. Keep it short; the client's reaction matters more than your commentary.
- Ask for specific feedback. "What do you think?" invites taste. "Does this headline say what you do in one read?" gets an answer you can use.
- Say what happens next. When feedback is due, where it goes, and how many rounds are left.
Those steps hold whether you show a static mockup or a working page. The rest of this guide is about the second option.
Why some agencies now show live pages
Building a concept in HTML used to mean days of front-end work before the client had agreed on anything. AI tools have made it much quicker to go from a sketch or a written brief to a working page, so the cost of showing something clickable early has dropped. Some studios now present the first concept as a link the client can open on their own phone, rather than a set of flat screens.
That changes what the client sees, and what they react to. It has real benefits and real risks.
What a live concept shows that a mockup can't
- Real responsive behaviour. The client sees how the layout stacks, wraps and reflows as the window changes. Problems that a single desktop mockup hides, like a navigation that doesn't fit or a three-column section that turns into a long scroll, show up straight away.
- Real copy length. If you use the client's actual text, they see whether the headline fits, whether the services section is a wall of words, and whether that testimonial is too long. Filler text in a mockup tends to be conveniently short.
- The phone view. Many visitors will arrive on a phone. A live page lets the client check it on their own device, at their own pace, instead of looking at a phone frame on a slide.
- How it feels to use. Scrolling, hover states, menus and section rhythm are hard to describe and easy to feel.
What can go wrong
- The client assumes it's finished. A working page looks like a website, because it is one. Clients may ask when it goes live, or wonder why the build stage costs what it does if the site already exists.
- Nitpicking too early. Real pages invite real-page feedback: a 4 px gap, a button colour, a typo in filler copy. Those notes crowd out the bigger questions you need answered first, like whether the page structure is right.
- Scope creep. Because the concept looks so close, small requests feel cheap. "Can we just add a booking form" or "could the menu do this" turns a concept round into unplanned build work.
- Concept code becomes production code. A quick AI-built page is rarely the code you want to launch. If the client signs off the concept as the site, you may end up maintaining something you never meant to ship. Our guide on reviewing AI-generated HTML covers what to check before any of it goes further.
None of these is a reason to avoid live concepts. They are reasons to set expectations before the client opens the link.
Setting expectations: a concept is not the build
Say it in three places, because clients rarely read everything.
1. On the page
Add a small, fixed label to the concept itself, something like "Concept 1 · Not the final site". Keep it visible at every screen size. If some content is filler, say so near it: "Stock photo for now" under an image, or "Draft copy" beside a section you wrote yourself.
2. In the message with the link
Keep it to a few lines:
- "This is a working concept so you can see the layout on your phone and computer. It is not the finished website."
- "Photos and some text are stand-ins. Spacing, animation and small details will change in the build."
- "At this stage we would love your thoughts on the structure, the order of sections and the overall look."
3. At the start of the call
A short script you can adapt:
- "Before we look, a quick reminder of what we agreed: the site is for first-time visitors who need to understand what you do and book a call."
- "What you're about to see is a concept. It's a real page, so you can open it on your phone, but it isn't the website we'll launch. The build comes after we agree the direction."
- "Today I'd like your reaction to three things: does it say the right thing, is the order right, and does it feel like you."
- "Small things like spacing, exact wording and final photos are coming later, so feel free to note them, but we'll handle them in the next rounds."
Then present as usual: scroll through, explain the big decisions, open it on a phone, and stop talking so the client can react.
What feedback to ask for at this stage
Give the client a short list of questions. It focuses them on direction and gives them permission to skip the details.
| Ask about now | Leave for later rounds |
|---|---|
| Does the page explain what you do in a few seconds? | Exact spacing and alignment |
| Are the sections in the right order? | Final photos and icons |
| Is anything important missing, or not needed? | Word-by-word copy edits |
| Does the look feel like the brand? | Animation and hover details |
| Does the phone version work for how your customers browse? | Browser-specific bugs |
When a client asks for something new during the concept round, note it, thank them, and say whether it fits the agreed scope. Writing your rounds and what counts as a change into the proposal makes that conversation easier; see how many revision rounds a website project should include.
Collecting comments on a live concept
After the call, the client will want to look again and show colleagues. If feedback comes back by email, you get notes like "the third bit looks odd on my phone" with no way to tell which bit or which phone.
A feedback tool keeps comments attached to the page. With HTMLAnnotate you can upload the concept as an HTML file, paste the HTML, or paste the address if it's already hosted, then send the review link. Reviewers click the heading, image or spot they mean and type a comment. They need no account. Desktop, tablet and phone comments are kept apart, so you know which layout each note is about. If your concept is a single file from an AI tool, sharing an HTML file as a link walks through the options.
When you revise the concept, publish the new version on the same review link. The client uses one link the whole way through, and earlier versions keep their comments, so you can check what was asked against what changed. When the direction is agreed, reviewers can approve that version, or ask for changes with a note, which gives you a clear record before the build starts. The guide to client website approval covers turning that into proper sign-off.
If you built the concept with an AI tool, the comments can go straight back to it. Copy for AI turns open comments into one brief you can paste into the chat, and HTMLAnnotate's MCP server lets tools such as Claude, ChatGPT and Cursor read the comments, reply and publish a new version themselves.
When a static mockup is still the better choice
Live concepts aren't always the right call. A mockup can be better when:
- You want reactions to several very different directions side by side, and building each as a page would be wasted work.
- The client is likely to fixate on details, and a flat, obviously unfinished image keeps them on the big picture.
- The final site will be built on a platform where your HTML concept won't carry over, and you'd rather not suggest otherwise.
Many studios do both: rough mockups or wireframes to pick a direction, then a live page for the chosen one, before the real build. For more on running these reviews with prototypes from AI builders, see reviewing v0, Lovable and Bolt prototypes with stakeholders.
Questions
How do you present a website design to a client?
Start with the goals and audience you agreed, so the client judges the design against them rather than personal taste. Then show the design in context, ideally at real screen sizes, explain the main decisions, and finish by asking for specific feedback on the things you need answered at this stage.
Should I show clients a mockup or a live page?
Either can work. A live page shows how the design behaves on a phone, how long the real copy runs and how the page scrolls, which a flat mockup can hide. A mockup feels more obviously unfinished, so clients focus on direction. If you show a live page, label it as a concept and set expectations before they open it.
How do I stop a client thinking the concept is the finished website?
Say it in three places: a visible concept label on the page, the message you send with the link, and the start of the presentation call. Explain what the concept is for, what is filler, and what happens between concept and build.
What feedback should I ask for on a website concept?
Ask about direction: does the page say the right thing to the right people, is the order of sections right, does the look feel like the brand, and does anything important seem to be missing. Leave pixel-level spacing, final images and exact wording for later rounds.
How do I collect client comments on an HTML concept?
Upload the HTML file or paste the page's address into a feedback tool, then send the review link. Clients click the spot they mean and type a comment, so each note stays attached to the right part of the page, and phone comments stay apart from desktop ones.
Upload your concept as an HTML file or paste its link, then send the review link. Clients click the page to comment, with no account.
Start a free review