One of the strangest things about commissioning any product — a new app, a new tool, a new piece of hardware — is that the moment of greatest commitment usually happens before the product exists. You have to decide whether to build the thing based on a description of the thing. The description is necessarily incomplete. The decision is necessarily a guess.
A good mockup changes this equation. It lets a client see the finished thing before committing to build it. It collapses some of the uncertainty between brief and delivery, lets stakeholders react to something concrete rather than something abstract, and surfaces the questions that would otherwise only emerge in the third round of revisions. Most of the value of a mockup is not in how it looks. It is in what it makes possible.
But mockups vary enormously in how well they actually do this job. Some convince. Some decorate. Knowing the difference is most of the craft.
The job a mockup is really doing
The instinct, especially early in a career, is to treat a mockup as a presentation of the eventual design — a polished image showing what the finished product will look like. That is part of the job, but it is the smaller part.
The larger part is helping the client decide. A mockup is a decision-support tool, dressed up as a design artefact. It exists to let someone who has not yet committed to building the thing have an experience of the thing that is close enough to the real experience to inform the commitment. A mockup that looks beautiful but does not help anyone decide anything has missed its primary purpose.
This reframing changes how a useful mockup is constructed. It is not “here is what we will build.” It is “here is what it will be like to use what we propose to build, in enough detail that you can tell whether it is what you want.” The shift in framing produces dramatically different work — and dramatically different conversations with the client.
What makes a mockup convincing
A convincing mockup feels like it could be the real thing. The clue is in the word “feel.” Convincingness is not technical fidelity — a mockup does not have to be functional to feel real — but it does have to be specific, coherent, and committed in its details.
The specific part means using real content, not placeholder content. Lorem ipsum text in a software mockup is the single most common signal of a mockup that has not done its job. A mockup with realistic content — actual customer names, plausible product titles, sensible numbers — feels real in a way that a mockup full of “Sample Heading” and “Lorem ipsum” never will.
The coherent part means the mockup behaves like one thing, designed by one mind. The fonts, colours, spacing, and component patterns are consistent across every screen. The voice in the microcopy is consistent. The visual rhythm holds. A mockup that mixes design conventions, or that has clearly been assembled from several different sources, never quite reads as a finished product.
The committed part is the hardest to describe and the most important. A convincing mockup makes specific choices and presents them as if they are right. It does not hedge with “draft” labels, multiple options, or visible uncertainty. The mockup says: this is the thing. Whether the client agrees is the next conversation. The mockup itself does not invite that conversation by visibly second-guessing itself.
What makes a mockup merely decorative
The opposite is also recognisable. Mockups that decorate without selling tend to share certain patterns.
They show the product in idealised conditions that the real product will rarely encounter. The dashboard always has exactly the right number of items to fit. The chart always has data that fills the available space attractively. The user is always at the happy path; the empty states, error states, and edge cases are absent. This is the most common form of mockup dishonesty, and clients have learned to notice it. The mockup makes a promise the eventual product cannot keep.
They use stock imagery that calls attention to itself. The smiling stock model, the generic city skyline, the obviously commercial product photography — these tell the viewer that this is a mockup, not a real product. The illusion breaks. The client returns to evaluating the mockup as a presentation, not as a preview of the real thing.
They show only the front of the product. A single hero screen, polished to the point of perfection, with no indication of what happens when the user clicks anything. This is fine if the brief is for a single static image — a hero shot for a press release, for example. It is not enough if the brief is to help the client decide whether to commission the build. A decision needs more than a hero shot.
The role of unfinished detail
One of the more subtle craft questions in mockup work is how finished the unfinished parts should look. A mockup that is uniformly polished tends to suggest the work is done — which can be a problem when the brief is to commission further work. A mockup that is uniformly rough tends to suggest the work is preliminary — which is fine for exploration but does not convince anyone to commit.
The middle ground that tends to work best is what is sometimes called “selective fidelity.” The hero areas are rendered to a high standard, because they need to convince. The supporting areas are rendered with enough fidelity to feel real but with detail that signals “this is the direction, the specifics will be refined.” This calibration is harder than it sounds. It takes judgement to decide what to render in full and what to leave at a level that promises rather than delivers.
Done well, selective fidelity gives the mockup the right kind of incompleteness — the kind that prompts useful conversation without undermining the conviction of the hero areas. Done poorly, it just looks like a mockup that ran out of time.
Mockups as part of a sales conversation
For designers who build mockups on behalf of clients who are trying to sell an idea — to a board, to an investor, to an internal sponsor — the mockup is doing a different kind of work again. It is part of a sales conversation, and it has to be convincing not just to the immediate viewer but to the secondary audience the viewer will have to convince in turn.
This means anticipating the questions that will arrive in the next room. If the eventual audience will be a financial sponsor, the mockup probably needs to show numbers — even if the numbers are placeholders that will be refined. If the eventual audience will be an operations team, the mockup probably needs to show how the work flows, even at a sketched level. The mockup that wins the room in front of you may not be the mockup that wins the room behind it.
This is the part where the designer’s job overlaps with the writer’s job. The microcopy in the mockup, the captions on the screens, the narrative implied by the choice of which states to show — all of this contributes to whether the mockup tells a coherent story. A polished image with no story behind it can present beautifully and convince nobody.
When the mockup is overkill
It is worth saying that not every project warrants a heavily produced mockup. For small projects, simple briefs, or clients who already know what they want, a fast sketch is often the better tool. The mockup pays back its production cost by reducing the uncertainty of a major commitment. For a small commitment, the production cost can exceed the uncertainty it would have removed.
The decision to invest in a polished mockup should be driven by the size of the commitment the mockup is helping to unlock — and by how much of that commitment is currently being held back by uncertainty. A high-stakes decision being delayed by lack of conviction is exactly what a mockup is for. A low-stakes decision being delayed by indecision is something else, and a mockup is unlikely to fix it.
The short version
A mockup’s job is not to look impressive. It is to help a client see what they will be committing to, in enough detail to decide. The mockups that do this job well use real content, hold together as coherent products, and commit to specific choices rather than hedging across options. The mockups that fail to do it tend to show idealised states, use distracting stock imagery, or polish the front while leaving the rest implied. The craft is in the calibration — making the mockup feel like the thing it represents, complete enough to convince, incomplete enough to still be commissioned. Get that right and a mockup earns its keep many times over. Get it wrong and it is just decoration.
