Proof points should route to evidence
A homepage stat earns more trust when it points directly to the case study, project, or note that makes the claim inspectable.
I like outcome cards on a homepage. They still need one more job. A stat by itself is only a claim.
If I want the card to build trust, it should also tell the reader where to inspect the underlying work.
A proof point should not be a dead end
The problem with many proof rows is not that the numbers are unbelievable. It is that they stop the path. The reader sees:
- the result
- a short sentence
- no obvious route to the deeper evidence
That creates a small trust gap. The card is asking for belief before it has offered inspection.
The route can stay simple
I do not think a proof card needs a long explanation. Usually it only needs one explicit next move:
- case study
- project guide
- published post
That is enough to tell the reader what kind of evidence sits behind the result. The surface gets stronger because the card stops behaving like decoration and starts behaving like navigation.
This is the same rule as the other homepage routes
I already want start cards to say whether they lead to proof, context, or published work. I already want discovery cards to name the first move. Proof points need the same discipline.
The outcome can stay short, but the supporting route should be visible.
The real job is inspectability
What I keep wanting from public surfaces is not more explanation. I want less interpretation work between a claim and the material that supports it. If the card says 80% growth, the next click should tell me where that idea came from.
If the card says regional delivery moved from three months to thirty days, the route should show me the orchestration story rather than forcing me to search the site for it. That is the bar. A proof point is doing enough when it gives me one believable reason to trust it and one obvious place to inspect it.