The consultant's portfolio page under NDA: how to prove expertise without naming clients

You're a consultant, and your best work is hidden behind an NDA. You can't post logos, you can't say "I worked with X," and sometimes you can't even admit the relationship exists. The result is a portfolio page that feels empty and the sensation of starting from scratch in every sales conversation.

The good news is that the client's name was never the real proof of your competence. A logo shows that someone hired you, not that you delivered. A serious buyer is convinced by something else: that you understand their problem better than they do. In this article I'll show you, concretely, how to communicate real expertise and results while staying fully inside your NDA.

The client's name was never the proof

The first thing to change is the reflex of equating credibility with a wall of brands. A logo proves you were paid, not that you solved anything hard.

What convinces a competent buyer is specificity. "I worked with a furniture manufacturer of about forty employees that was losing orders because of a chaotic quoting process" says far more than a row of famous logos with no context. The first shows someone who was there; the second, someone who collects names.

Shift the weight of the page from "who with" to "what problem" and "how I thought about it." You can do this without breaking anything, and it's actually stronger.

The anonymized case study: a formula that doesn't break the NDA

A good case study doesn't need a name. It needs structure. Use four blocks:

• The context, stripped of anything identifiable: the sector, the rough size of the company, and the situation. "A neighborhood dental clinic," not the city and exact number of chairs.
• The real problem, in the client's terms: what hurt, and what it was costing them.
• Your approach: the decisions you made and why. This is where the expertise shows.
• The result, exactly as much as you're allowed to share: either figures approved in writing by the client, or an honest qualitative description of the change.

Change the details that aren't essential to the story but could identify the company. Don't invent numbers you can't defend. A vague but true case study beats an impressive figure pulled out of thin air.

Show how you think, not just what you delivered

The best proof of expertise an NDA can never take from you is the way you think. That belongs to no client.

Publish your methodology: the steps you go through when you take on a project, the framework you use to make decisions, the mistakes you see repeated in your field. Do a public teardown of a hypothetical case or a well-known company you have no contract with, and show how you'd approach it.

A consultant who explains their reasoning in public is more convincing than a wall of brands. The buyer reads it and thinks, "this person thinks like me, but with more experience." That feeling is what brings the contact email, not the logos.

Testimonials and artifacts when the client can't appear

Even under an NDA, you have more options than it seems.

• Testimonials with partial attribution and written permission: "CFO, logistics company, roughly two hundred employees." Anonymous, but credible, because it's concrete.
• Sanitized artifacts: a dashboard with the data blurred, a sample audit built on dummy data, a fragment of a deliverable with everything identifying removed. Show the shape of your work, not the confidential content.
• Private references: clients who don't appear on the site but agree to take a call at the end of a conversation, for a serious prospect.

All of this requires one thing: that you asked for permission at the right moment and have it in writing.

What to ask the client, and what the page looks like

Many NDAs allow an anonymized reference if you have the client's explicit consent. The right moment to ask is right after a win, while you're fresh in their mind. Offer to let them approve the exact wording, and keep the agreement in writing. Don't push, and above all don't invent anything to fill the page.

As for structure, a page that works gathers: a clear promise about the problem you solve, two or three anonymized case studies, a section on how you think, partial testimonials, and a single simple next step.

At MPO Web Studio we build exactly these kinds of pages, with a ready-made demo before you pay anything, delivered remotely across the country, with transparent pricing. If you'd like to see what yours could look like, message us on WhatsApp and let's talk.