Clients cannot read a flat file the way you can
Years of practice have taught you to look at a mark on white and see it on a shopfront, a business card and an app icon. A client has not had that training and is not going to acquire it during your project. When they say the logo feels small, they are usually not making a size judgement — they are reporting that the flat presentation gave them nothing to calibrate against. Showing the same mark on a sign, a card and a tote answers the question they were actually asking. This is not decoration around the deliverable; for most clients it is the only version of the deliverable they can properly evaluate.
Present a decision, not a gallery
A deck with nine directions invites a client to combine them, which is how projects lose their shape. Two or three developed routes, each shown in the same set of contexts, gives a comparison a non-designer can actually make. Keep the contexts identical across routes so the variable is the design and not the staging — otherwise you are unintentionally testing which photograph they prefer. It is worth being deliberate about which contexts you pick, too: choose the applications the client will genuinely encounter, because a beautifully rendered application they will never use invites feedback on a problem that does not exist.
Realistic renders raise expectations you must then meet
There is a real failure mode here. A convincing mockup of embossed stock, spot varnish or a neon sign creates an expectation of a finish the client's budget may not cover, and the gap surfaces at the worst moment — when the print quote lands or the sign goes up. If you present a finish, be explicit about whether it is specified and costed. The same caution applies to scale and environment: a poster rendered on a clean gallery wall sets an expectation that the actual pillar it will be pasted to cannot meet. Presenting honestly is not less persuasive; it removes the argument you would otherwise be having later.
The portfolio case for mockups is separate
Beyond client approval, contextual imagery is what makes speculative and unshipped work presentable. Plenty of good design never reaches production — the client folded, the budget moved, the project was killed. Flat artefacts of dead projects look like homework. The same work staged in context reads as professional output, provided you are honest in the caption about what shipped and what did not. The distinction matters more than designers assume: prospective clients are largely evaluating whether you can solve their problem, and unbuilt work shown honestly demonstrates that fine, while unbuilt work implied as shipped is the kind of thing that ends a relationship when discovered.
