NDAs block you from showing the work — but they don’t block you from showing the impact. Buyers don’t need screenshots, deliverables, or proprietary details; they need evidence that you solve high‑stakes problems. When your portfolio collapses because you rely on visuals you can’t legally share, prospects assume you lack meaningful results. The solution is shifting from project evidence to outcome evidence.
Understanding the difference between asset‑based proof and stakes‑based proof is the key to fixing this problem.
Asset‑Based Proof: The Restricted Layer
Asset‑based proof relies on showing the actual work. It signals:
- screenshots
- deliverables
- proprietary details
- client‑specific materials
NDAs kill this instantly. Buyers see nothing, so they assume nothing happened.
When your proof depends on assets, it becomes legally blocked, not commercially persuasive.
Stakes‑Based Proof: The NDA‑Safe Layer
Stakes‑based proof communicates outcomes without exposing protected materials. It signals:
- problem framing
- commercial stakes
- measurable shifts
- anonymized context
This is the version that keeps you compliant while still proving capability.
In practice, NDA‑safe proof means:
- leading with the problem and stakes, not the client identity
- describing the before/after shift in commercial terms
- using anonymized industry context instead of project specifics
- highlighting the strategic decision, not the proprietary asset
Summary of Differences
| Feature | Asset‑Based Proof | Stakes‑Based Proof |
|---|---|---|
| What it signals | Deliverables. | Impact. |
| Focus | Showing the work. | Showing the shift. |
| End Result | “I can’t see anything.” | “They clearly solve real problems.” |
In short:
NDAs block assets.
They don’t block outcomes.