A freelancer lands a call with a serious prospect, the kind of client who could actually move the business forward, and sends over the portfolio beforehand. The one project that would prove it — the largest budget, the most complicated build, the result that actually matters to someone deciding whether to trust real money to a stranger — isn’t in there. It sits behind an NDA signed eighteen months ago, and the five projects that are in there are the smaller, easier ones nobody minded being shown. The prospect sees a portfolio that undersells exactly what they need proof of.
In my experience, freelancers treat a portfolio as a complete record of everything they’ve built, when its actual job is closer to a curated highlight reel for one specific reader: the next client deciding whether to hire them. An NDA doesn’t block that job. It changes how the job gets done for one or two projects, not whether the portfolio can do its job at all — and most freelancers who assume otherwise have never actually tried the workaround, because the assumption feels safer than asking.
None of this is legal advice about what a specific NDA permits. Confidentiality agreements vary — some forbid naming a client but allow describing the work in general terms, others forbid any mention of the engagement at all, and violating one has real consequences beyond the immediate relationship: referrals dry up, and in the worst case there’s actual legal exposure. What follows is the general shape of how freelancers who regularly sign NDAs handle this, and the questions worth asking before writing a project off as permanently unshowable.
This guide covers two decisions that get bundled together but are genuinely separate: which projects earn a spot in a portfolio in the first place, and what to do with the ones that would make the strongest case for hiring you but can’t be shown as-is. It doesn’t cover building the page itself — the structure, layout, and WordPress mechanics are already covered in how to create a portfolio page. This is the layer before that: deciding what goes on it, and what to do when the strongest candidate can’t go on it in its raw form.
What Actually Earns a Spot
Four criteria decide whether a finished project belongs in the portfolio, and none of them is “I’m proud of it.” Pride is a reason to keep something in a private archive, not a reason to put it in front of a prospect.
- Recency. Work from the last twelve to eighteen months reflects current skill and current tools. A project from three years ago might still look fine, but it’s answering “what could you do a while back,” not “what can you do now” — and design trends, frameworks, and a freelancer’s own standards move fast enough that the gap shows.
- Target-client alignment. Feature the work that resembles the client you want next, not the work that’s most technically impressive to another designer. A beautifully over-engineered passion project for a friend’s hobby brand does less for a prospect who runs a mid-size ecommerce business than a plainer project that solved the same category of problem they have.
- Diversity within a focus. Show enough range to prove adaptability — different industries, different project sizes, a mix of formats — without scattering so widely that the portfolio stops signaling any actual specialty. A portfolio that jumps from a restaurant site to a SaaS dashboard to a nonprofit rebrand with nothing tying them together reads as “will take anything,” which is rarely the pitch a freelancer actually wants to make.
- Genuine quality, not just a client who was easy to please. Some of the smoothest client relationships produce forgettable outcomes, and some of the hardest projects produce the strongest work. Judge the finished result on its own, separate from how pleasant the process was.
On volume: three to five strong projects is the right starting range for a newer freelancer, which lines up with the guidance already covered in how to create a portfolio page. Once a freelancer has a few years of steady client work behind them, that range can reasonably stretch toward six to twelve — enough to demonstrate consistency across a real body of work — but going much past that tends to work against the portfolio rather than for it. A prospect skimming a portfolio with twenty entries reads none of them closely; a prospect looking at eight reads most of them. More entries is not the same as more proof.
Building the Shortlist
- List every project completed in the last two years, regardless of whether it feels portfolio-worthy yet. Cutting comes later — the first pass is just making sure nothing gets forgotten.
- Score each one against the client you want next, not the client you happened to have. A project for a client wildly unlike anyone in the target market gets scored down even if the work itself was strong.
- Cut anything visually weak, regardless of how satisfying the underlying problem-solving was. A prospect skimming a portfolio judges the screenshot first and reads the description second, if at all.
- Group what survives for range, not by whichever category happens to have the most entries. If four of the six strongest projects are ecommerce rebuilds, keep the two best and let the other two make room for something that shows a different kind of problem.
- Set aside anything under NDA in a separate list rather than dropping it. An NDA changes how a project gets shown, not whether it belongs on the shortlist — and for many freelancers, the NDA’d projects are disproportionately the strongest ones, precisely because bigger, higher-stakes clients are the ones most likely to require an NDA in the first place.
When the Client Says No: Working Around an NDA
Before assuming a project is off-limits, read what the agreement actually restricts. Some NDAs forbid using the client’s name or brand assets but say nothing about describing the work in general terms. Others are broader and forbid any acknowledgment that the engagement happened at all. The difference matters, and it’s worth the ten minutes it takes to reread the clause rather than guessing.
The first move, before anonymizing anything, is to ask. Most freelancers skip this step and assume the answer is no — but a specific, scoped request is much easier for a client to approve than a blanket one. Send an email that names exactly what’s being requested: which project, which images or screenshots, which numbers, and where it would appear. Offer to send the final write-up for approval before it goes live. Framed that way, a request to show a sanitized version is a much smaller ask than it sounds, and many clients say yes to it even when they’d have refused “can I put this in my portfolio” as an open-ended question.
If the client declines, or can’t be reached, three fallback approaches cover most situations:
- Anonymize the case study. Replace the client’s name and logo with a generic descriptor — “a Rotterdam-based B2B SaaS company” instead of the actual company name — and swap raw figures for percentages. “Increased signups by 12%” carries the same proof without exposing “signups went from 12,512 to 14,013,” a number specific enough to identify the company to anyone who knows the industry.
- Write a process-only case study. Describe the brief, the constraints, the decisions made, and the reasoning behind them, without including any client-identifying deliverable at all — no screenshots, no visuals. This is weaker proof than showing the actual work, but it still demonstrates how someone thinks through a problem, which is often what a prospect is actually trying to evaluate.
- Keep it private. Note the project’s existence briefly — industry, scope, general outcome — and offer to discuss the specifics in a call with serious prospects. Clients who won’t agree to public posting are frequently willing to let a freelancer describe the work verbally in a sales conversation, since that’s a controlled, one-off disclosure rather than something permanently published.
One instinct to resist: blurring or redacting a screenshot to show “something” from a restricted project. It looks worse than not showing it at all. A blurred image signals that there was something to hide rather than something handled professionally, and it does nothing to actually protect the client — anyone motivated enough can often still make out layout, colour palette, or partial text. A clean, honest, anonymized description reads as intentional. A blurred screenshot reads as a workaround that got caught halfway.
| Approach | What it proves | When it fits |
|---|---|---|
| Public, anonymized case study | Full proof of process and outcome, without identifying the client | Client agrees to a sanitized version, or the NDA only restricts naming, not describing |
| Process-only write-up | How you think and work, without visual proof of the result | Client won’t approve any visuals or specifics, but the engagement itself isn’t secret |
| Private walkthrough | Full detail, shown selectively | Client won’t allow public posting at all, but is comfortable with it being discussed one-on-one |
A Worked Example
Say the strongest project of the year was a full ecommerce rebuild for a mid-size retailer, under an NDA that forbids naming the company but doesn’t forbid describing the engagement. The raw version — the one that can’t be published — includes the client’s name, exact before-and-after screenshots, and a conversion lift from 2.1% to 2.48%. The publishable version keeps everything that actually proves the work and drops everything that identifies the client: “a mid-size European home goods retailer,” generalized product photography standing in for the client’s actual catalogue images, and “a 18% relative increase in conversion rate” instead of the two raw percentages. Nothing about the proof weakens. What disappears is only what a competitor or curious visitor could have used to identify the company.
Common Mistakes
- Assuming the whole project is untouchable without rereading the NDA. Many agreements restrict less than freelancers assume, and the only way to know is to actually check the clause rather than defaulting to silence.
- Blurring a screenshot instead of writing around it. It protects less than it looks like it does and reads as evasive rather than professional.
- Sharing precise numbers instead of percentages. A specific figure is often enough for someone in the client’s industry to identify them even without a name attached.
- Dropping the project from the shortlist entirely rather than adapting it. This is usually the costliest mistake, since NDA’d work is disproportionately the work from bigger, higher-stakes clients — exactly what a portfolio most needs to prove.
- Never revisiting old NDAs. Confidentiality restrictions are usually tied to a product launch or a competitive window, not permanent secrecy. A restriction that made sense at signing may no longer apply once the client’s product has shipped publicly — worth a quick check before assuming last year’s answer still holds.
Where This Connects
The easiest point to raise portfolio permission is during onboarding, not after the project wraps and the client has moved on to something else — see how to create a client onboarding process for where that conversation naturally fits alongside the rest of the kickoff. If a client won’t approve a full case study, asking for a short testimonial instead is often an easier yes, and it still gives a prospect third-party proof; how to collect testimonials and case studies covers how to ask for one and where to use it. And because confidentiality terms are usually set once, at the start of a project, it’s worth checking what your own freelance web design contract actually says about it rather than assuming — a contract that’s silent on confidentiality gives neither side a clear answer when this comes up later.
Which clients a portfolio is built to attract is the same decision that shapes how a freelancer prices their work — both come down to deciding who you actually want to hire you next, not who you’re willing to accept. How to price web design services covers the other half of that same positioning decision.
The Portfolio Keeps Changing
A portfolio built once and left alone slowly stops matching the freelancer who made it. Revisit the shortlist every few months: retire the oldest project once something stronger and more recent replaces it, recheck whether an NDA’d project’s restriction still applies, and rescore everything against whoever the target client is right now rather than who it was a year ago. The strongest portfolios aren’t the ones with the most projects in them — they’re the ones that get pruned as often as they get added to.
Etienne Basson works with website systems, SEO-driven site architecture, and technical implementation. He writes practical guides on building, structuring, and optimizing websites for long-term growth.