Trust & persuasion / 02
Your best proof might be in the wrong place.
Credibility depends on more than having good evidence. It also depends on where a visitor encounters it.
A claim creates a question.
When your website says you produce exceptional work, the natural next question is: can you show me? If the answer is three sections away, the visitor has to keep investing attention before they can judge the promise.
This is not always a lack-of-trust problem. Sometimes you already have persuasive evidence: a well-documented project, a relevant testimonial, a clear demonstration, or a useful example of the finished product. The problem is that the evidence arrives after the decision it was meant to support.
Match the proof to the promise.
A wall of logos can establish familiarity, but it may not explain what you did. A testimonial that says you are a pleasure to work with supports a claim about the experience of working together. It does not, by itself, support a claim about commercial results.
Choose evidence that answers the particular doubt your message creates. If you promise clear website advice, let visitors read the advice. If you promise thoughtful design, show the work and explain the decisions. If you describe a dependable process, make that process visible.
Move one piece, not the entire portfolio.
A useful first change is often a compact proof block immediately after the main offer: one relevant project, a short attributed quotation used with permission, or a preview that links to a fuller example. Keep the opening readable and let visitors choose how deeply to investigate.
More evidence is not automatically better. Six unrelated testimonials can make a page longer without answering the visitor’s actual concern. The right example earns its space by making a specific claim easier to assess.
Before / Page sequence
Promise → Long introduction → Request a consultation → Client work
After / A clearer direction
Promise → Relevant client work → How it works → Request a consultation
Audit the decision points.
Walk through the page as a prospective customer. At each meaningful request, pause and ask what someone would reasonably want to know before continuing.
- Before an inquiry: have I shown the kind of work and clients this service is for?
- Before a purchase: can someone see what they receive and understand the terms?
- Before a sensitive submission: have I explained what happens to the information?
Percensa’s own example: let people inspect the thinking.
On Percensa, the sample report gives visitors a way to examine the kind of guidance the product provides. The useful question is not simply whether the report looks polished. It is whether someone can understand the observation, follow the reasoning, and see what to do next.
Your equivalent may be a case study, a demonstration, or a sample deliverable. Put it where it helps someone evaluate your offer. Then observe whether visitors use it and whether subsequent inquiries become better informed. A layout change is a hypothesis to evaluate, not a guaranteed conversion lift.