Some of the best work freelancers do is invisible in their portfolio. Confidential client work, internal tools that never shipped publicly, campaign materials that ran under a client’s brand, design systems for companies that don’t want their infrastructure discussed, stays hidden because of the NDA or confidentiality expectation that protects the client relationship. Most freelancers handle this badly: they either violate the agreement accidentally or pretend the work doesn’t exist.
The First Question: What Are You Actually Restricted From Showing?
Most freelancers over-restrict themselves out of caution when the actual constraints are narrower. Before assuming you can’t show a project, read whatever agreement governs it, the contract, NDA, or master service agreement, and find the specific clause.
Standard NDAs restrict: proprietary information (source code, unreleased product details, financial data, internal processes), identification of the client in connection with specific information they’ve designated confidential, and sometimes the existence of the engagement itself. They rarely restrict: showing that you did work in a particular category, describing the general nature of a project, sharing publicly visible output that the client has already released.
The confusion usually comes from treating the NDA as a total gag order when it’s typically much more specific. If you built an internal dashboard and signed an NDA, you’re probably restricted from showing the actual dashboard or naming the client in connection with proprietary business data. You’re not necessarily restricted from saying “I designed an internal reporting tool for a logistics company”, depending on how the agreement is written.
When in doubt, read the agreement. If the language is ambiguous, ask. Most clients will tell you what you can reference. The worst outcome from asking is that they say no, which is the same position you’d be in if you didn’t ask.
Anonymizing Confidential Work for Your Freelance Portfolio
The goal of anonymizing is to keep enough context that the case study is persuasive while removing whatever the client has restricted. Often, more survives than people expect.
You can usually keep: the industry or sector, the company stage (startup, mid-market, enterprise), the nature of the problem, the approach you took, and the results framed without client-identifying specifics. “A Series B SaaS company with a non-technical buyer persona” is a recognizable type of client even without a name. “A retail chain expanding internationally” creates context without identifying anyone.
What to remove or generalize: the company name, any numbers or data that could identify the company, any internal processes or proprietary information specifically called out in the agreement, and any information the client has told you explicitly is off limits.
An anonymized case study written well is often only marginally less persuasive than a named one. Most clients evaluating you aren’t going to verify the case study against a named company anyway, they’re reading it to understand how you think and what kind of work you’ve done. The industry context and the problem-solving narrative are what carry the persuasion, not the name in the header.
Presenting Restricted Work in Client Conversations
There’s a category of work that can’t go on a public portfolio but can be shown under conditions, in a meeting, on a screenshare with an NDA in place, or as part of a formal proposal process. This is worth knowing about and worth asking clients for permission to do.
Many NDAs restrict public disclosure but not selective disclosure to parties who have also signed a confidentiality agreement. If you’re pitching a new client who’s willing to sign a basic NDA as part of the proposal process, you may be able to show them work that can’t appear on your public website. This is standard practice in some industries, legal, financial services, healthcare, where almost everything is confidential and freelancers routinely show work under mutual NDA.
The ask is simple: “I have several relevant projects I’d be happy to walk you through on a call, some are under NDA, so I’d show them on screen rather than sending files. Would that work?” This signals professionalism rather than evasion and gives the client the context they need to evaluate you.
Discussing Restricted Work Without Showing It
Even when you can’t show the work, you can usually describe it. The key is to separate what’s restricted (the actual work product, the client’s proprietary information, the client’s identity in connection with sensitive details) from what isn’t restricted (the existence of a project, the general nature of the problem, the skills and disciplines you applied).
“I spent 18 months as the primary content strategist for a mid-market professional services firm going through a complete rebrand. I can’t share the specifics under NDA, but I’m happy to talk through how I approach that kind of engagement” is a legitimate and useful thing to say in a client conversation. It tells the client what they need to know, that you’ve done this kind of work, at this scale, without disclosing anything restricted.
Prepare two or three narrative descriptions of your confidential projects that cover the type of work, the general challenge, and your role, without the client name or any proprietary details. These are for conversations, not for your website. Practice them until they flow naturally. A client who hears you describe your process coherently and specifically will often ask fewer follow-up questions about the portfolio they can’t see.
When the Agreement Prevents Almost Everything
Some engagements come with restrictions that are genuinely broad, covering even the existence of the relationship, the type of work, and anything that could identify the client or their industry. These are uncommon but real, particularly in sensitive sectors.
When this applies, the practical answer is to get written permission for an agreed-upon description before the project ends, while you still have the client’s attention. Ask: “I’d like to be able to reference this engagement in future proposals, can we agree on what I can say?” Most clients will work with you on a general description. The conversation is much easier during wrap-up than months later when they’ve moved on.
If you can’t reference the project at all, the next best thing is to ask for a private reference, someone at the client organization who has agreed to take a call from a prospective client if asked. This is also the moment to think about what your freelance social proof looks like across all channels, not just the portfolio itself. This bypasses the portfolio entirely and goes straight to the most persuasive form of social proof: a real person who can speak to the experience of working with you.
The Practical Takeaway on Freelance Portfolio Confidential Work
Confidential work doesn’t have to be invisible. Most restrictions are narrower than freelancers assume, most clients will work with you on what can be referenced, and most of what matters to a potential client, the type of problem, the nature of your approach, the outcome, can survive anonymization.
The pieces that genuinely can’t be shown publicly are worth describing in conversation and worth protecting a reference relationship for. A client who hires you after a thirty-minute conversation where you walked through three anonymized projects will be less bothered by the anonymization than you are.
For the broader picture of how case studies and portfolio pieces work together in client evaluation, see how to write a freelance case study. For what clients are actually looking for when they vet a freelancer, confidential work is just one of several signals they’re reading, and rarely the deciding one.
