How to show proof of work when your clients are under NDAs

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.

Five Real-World Examples of Asset-Based Proof vs. Stakes-Based Proof

Example 1: A cybersecurity penetration-testing firm

Asset-based proof:

“For a financial-services client, we identified 14 critical vulnerabilities across its public-facing infrastructure. The project included a full penetration test, exploit validation and a 72-page technical report.”

The firm may have impressive evidence, but the actual report, screenshots and system details cannot be published because they belong to the client and may expose sensitive information.

But the proof is restricted:

“If you can’t show me the findings or the report, how do I know you actually uncovered anything significant?”

The firm’s portfolio becomes dependent on evidence it is not allowed to display.

A stakes-based version could say:

“A regulated financial business asked us to test whether an attacker could reach systems that were assumed to be protected. We identified multiple exploitable weaknesses, including one path that could have allowed unauthorized access to sensitive systems. The client closed the vulnerabilities before they were discovered through a real attack and used the findings to strengthen its security controls.”

Now the firm demonstrates capability through the problem, severity and outcome, without revealing the client, infrastructure or confidential findings.

The proof comes from explaining what was at risk and what changed, not from publishing the evidence itself.

---

Example 2: A specialist executive recruiter

Asset-based proof:

“We placed a Chief Financial Officer with a €500 million manufacturing company. The search included a detailed candidate assessment process, interview scorecards and a shortlist of six executives.”

The recruiter cannot publish the company’s internal hiring materials or identify the executives involved.

But the proof is restricted:

“If you can’t show me the candidates or the company’s hiring process, what evidence do you have that this was a difficult search?”

The recruiter risks making a successful placement sound like an unsupported claim.

A stakes-based version could say:

“A European manufacturing group needed a CFO during a period of rapid expansion, but the role required someone capable of managing both international growth and tighter financial controls. The first round of candidates looked strong on paper but lacked the required combination of experience. We narrowed the search around that specific requirement and helped the company appoint an executive who had already managed the same kind of transition.”

Now the recruiter demonstrates the difficulty of the mandate and the quality of the match without revealing the company’s identity or confidential hiring information.

The proof lies in showing that the recruiter understood the stakes and solved the difficult part of the search.

Example 3: A corporate crisis-communications consultancy

Asset-based proof:

“We developed the crisis-response messaging, prepared executive statements, created the media Q&A document and managed communications across multiple channels during the incident.”

The actual statements, internal communications and media strategy may be confidential, particularly when the client is dealing with an active reputation issue.

But the proof is restricted:

“If none of the communications can be shown, how can a prospect judge whether the consultancy actually handled a serious crisis?”

Showing the documents may violate confidentiality, while showing nothing leaves the work difficult to evaluate.

A stakes-based version could say:

“A national consumer brand faced a sudden public complaint that was spreading rapidly online. The immediate risk was not simply negative attention; inconsistent responses could have turned the original issue into a larger reputational problem. We helped the leadership team establish one clear position, prepared the responses around the facts that could be confirmed and gave them a framework for handling new developments without contradicting themselves. The company was able to respond consistently while the situation developed without exposing confidential internal communications.”

Now the consultancy demonstrates crisis judgment and risk management.

The prospect does not need to see the confidential statements. They can see the seriousness of the situation, the decision that mattered and the risk the consultancy helped control.

Example 4: A commercial data-analytics consultancy

Asset-based proof:

“We built a predictive model for a large distributor using five years of customer, inventory and sales data. The project included data cleaning, feature engineering, model development, testing and deployment.”

The underlying dataset, model and dashboards belong to the client and cannot be displayed publicly.

But the proof is restricted:

“Without seeing the dashboard or model, how do I know this wasn’t just another analytics project?”

The technical assets cannot provide the visual proof normally used in a portfolio.

A stakes-based version could say:

“A large distributor was carrying inventory based largely on historical ordering patterns, leaving the business exposed to both shortages and excess stock. We built a forecasting model around the signals that were actually predicting demand and identified where the existing planning approach was systematically overestimating requirements. The business used the new forecasts to make purchasing decisions with better visibility into upcoming demand, reducing the risk of tying up cash in stock that was unlikely to move.”

Now the consultancy demonstrates commercial impact and decision improvement without exposing the underlying data or model.

The proof is in the business problem solved and the decision that became more reliable.

---

Example 5: A specialist employment-law firm

Asset-based proof:

“We represented a senior executive in a complex employment dispute involving termination, restrictive covenants and confidential compensation arrangements. Our work included reviewing the employment agreement, preparing correspondence and negotiating the settlement.”

The legal documents and correspondence cannot be published because they contain confidential client information.

But the proof is restricted:

“If I can’t see the agreement or settlement documents, how can I tell whether this was actually a significant case?”

The firm’s most compelling evidence is precisely the material it cannot disclose.

A stakes-based version could say:

“A senior executive faced a dispute in which the consequences extended beyond the immediate termination: the employer was also seeking to enforce restrictions that could have affected the executive’s ability to work elsewhere. We assessed which obligations were genuinely enforceable, challenged the provisions that created the greatest exposure and negotiated an outcome that allowed the executive to move forward without accepting the full restrictions originally proposed.”

Now the firm demonstrates legal judgment and protection against a consequential risk.

The confidential agreement does not need to be displayed. The prospect can understand the stakes, the strategic problem and the outcome without learning the client’s identity or private terms.

---

What these examples demonstrate

In each case, the provider cannot safely publish the traditional portfolio evidence that would normally prove the work.

• The cybersecurity firm is communicating its ability to identify and eliminate serious security exposure.
• The executive recruiter is communicating its ability to solve a difficult, high-stakes hiring mandate.
• The crisis consultancy is communicating its ability to protect a company’s reputation through disciplined decision-making during a crisis.
• The analytics consultancy is communicating its ability to improve important business decisions without exposing proprietary data.
• The employment-law firm is communicating its ability to reduce a client’s exposure in a consequential legal dispute.

The key distinction is whether proof depends on showing the artifact or demonstrating the consequence.

Asset-based proof says:

“Here is the confidential work we produced.”

Stakes-based proof says:

“Here was the problem, here was what was at risk, here was the decision we made, and here is what changed.”

That is what makes outcome evidence useful when traditional portfolio evidence is unavailable. The NDA may prevent you from showing the artifact, but it does not necessarily prevent you from explaining the problem you solved, the stakes involved, the strategic decision you made and the resulting change — provided the description itself remains within the client’s confidentiality boundaries.