Label concept work before you use it as proof

A useful example still needs an honest label

Concept work can help a customer picture a service before they buy. The trust problem starts when a mock-up looks like completed client work or a demonstration sounds like a measured result.

Use a plain label beside every example: concept, live demo, sample, or client project. Put it where the visitor sees the example, not in a disclaimer at the bottom of the page.

Explain what the example is meant to prove

A concept can show page structure, design direction, or how a booking or enquiry path may work. It cannot prove customer results, sales growth, or how a real business performed unless you have evidence and permission to publish it.

MDP Studio applies this boundary to its Industry Previews. They are presented as demo concepts for comparing website directions, not as completed client outcomes.

Give each type of proof its own wording

For a concept, say what the idea demonstrates. For a live demo, say what a visitor can test. For client work, describe the agreed scope and only include outcomes that the client has approved and you can support.

This distinction works beyond websites. A builder can separate display ideas from finished jobs, a clinic can separate general education from patient outcomes, and a consultant can separate a sample process from a client case study.

Run a proof-label check each month

Review portfolio cards, galleries, before-and-after sections, testimonials, and project pages. Ask whether a new visitor can tell what is real, what is illustrative, and what result is actually supported.

If the label is vague, fix the wording before adding more examples. Clear boundaries make the work easier to understand and reduce the chance that a customer assumes more than the page can honestly promise.