When a Client Won't Let You Show Their Project in Your Portfolio
- A client saying no to your portfolio is usually saying no to one specific thing: their name, their data, their screens, or customers finding out they use AI. Find out which, because the answer is rarely no to everything.
- Use the Profit Room's Proof Ladder: ask for the most visible proof first, and step down one rung at a time - a named case study, an anonymous case study, results only, a private demo you rebuild with sample data, or a reference call. Most clients say yes somewhere on the ladder.
- Fix it for next time with a short portfolio clause in your agreement that the client can strike or narrow before signing. Never show anything they have not approved, and never use their real data in a demo.
The Short Answer
When a client won't let you show their project, say yes to their request first. Then ask one question: 'Totally understood. Can I ask what you would want kept private, so I make sure I respect it?' The answer usually narrows a blanket no into something specific, like 'do not use our name' or 'do not show our customer data.' Once you know the real concern, you can offer a version of proof that avoids it.
That is the Proof Ladder. The mistake is treating the first no as the final answer, or worse, quietly posting the work anyway. The opposite mistake is giving up on proof from that project entirely. I think almost every finished build can produce some proof the client is comfortable with. You just have to ask for the right rung.
Why Clients Say No
Clients rarely refuse out of spite. The common reasons are simpler. They do not want competitors to see how they run things. The build touches customer data, and they do not want screens of it anywhere public. They signed something with their own customers or partners that limits what they can share. Or they have not told their customers that part of the service runs on AI, and they would rather keep it that way for now. [Should you tell clients you use AI](/blog/should-you-tell-clients-you-use-ai) covers the other side of that question.
Each of those worries has a different fix. A competitor worry is solved by removing the name. A data worry is solved by never showing their real data. A contract worry means you need to know what their contract actually says. An AI worry may mean results-only proof, with no mention of how it was built. Asking 'what would you want kept private?' gets you to the right fix without guessing.
Climb Down the Proof Ladder
Start at the top and step down one rung at a time. Stop at the first one the client agrees to, and get that agreement in writing, even if it is a one-line email.
- Named case study: their name, the problem, what you built, and the result, with screenshots they have approved. The strongest proof, and the one [writing a case study that wins clients](/blog/write-a-case-study-that-wins-clients) is built around.
- Anonymous case study: the same story with the name removed and the business described by type and size, such as 'a family-owned property management company.' Remove anything that would identify them, including their logo, colors, and screens.
- Results only: one or two outcomes they are happy to have shared, with no screens and no name, in a sentence like 'cut the time to answer a new inquiry from next morning to a few minutes.' Use only numbers the client confirms.
- Private demo: a version you rebuild from scratch with sample data, shown only on sales calls, never posted. Check your agreement first, because [who owns the code you build for a client](/blog/who-owns-the-code-you-build-for-a-client) decides what you are allowed to reuse.
- Reference call: no public proof at all, but they agree to take a short call from a serious prospect. For some buyers this is worth more than any portfolio page.
| Rung | What a prospect sees | What the client keeps private |
|---|---|---|
| Named case study | Name, problem, build, result, approved screens | Only what they asked you to leave out |
| Anonymous case study | Business type, problem, build, result | Their name, logo, and screens |
| Results only | One or two confirmed outcomes | Everything except those outcomes |
| Private demo | A rebuilt version with sample data, on calls only | All of their real data and branding |
| Reference call | A conversation with a happy client | Everything public |
The Proof Ladder: what each rung shows and what it protects
What Not to Do
Do not post the work and hope they do not notice. Even blurred screenshots can give away a client through their layout, their wording, or a stray detail. If you signed a confidentiality agreement, sharing could be a breach, and [when a client asks you to sign an NDA](/blog/client-wants-you-to-sign-an-nda) covers what those usually restrict. Never use their real customer data in a demo, even privately. And do not offer a discount in exchange for portfolio rights after the fact. It turns a favor into a negotiation and makes the client wonder what else is for sale.
If the client says no to every rung, accept it gracefully. A happy client who refers you quietly is still worth more than a portfolio piece, and [how to get referrals from clients](/blog/how-to-get-referrals-from-clients) works without any public proof. In the meantime, the [anti-portfolio](/blog/the-anti-portfolio-proof-with-no-clients) approach shows how to build proof from your own builds instead.
Stop It From Surprising You Next Time
Add a short portfolio clause to your agreement. Something like: 'The builder may describe this project in a portfolio or case study. Before anything is published, the client will see and approve it, and no client data will be shown. The client may ask for the project to be shared anonymously or not at all.' Clients can strike or narrow it before signing, which means you find out where they stand on day one instead of after launch. Have a lawyer look at your agreement, since this is not legal advice.
Then ask for proof at the right moment. The best time is right after a visible win, when the client is happiest, which is the same timing [getting your first client testimonial](/blog/get-your-first-client-testimonial) recommends. Bring it up in your [expectations conversation](/blog/set-client-expectations-before-a-claude-code-build) at the start, so the request at the end is never a surprise.
Short, practical drops on offers, outreach, pricing, and closing clients with Claude Code. No spam, unsubscribe anytime.
Frequently asked
Can I put a client project in my portfolio without permission?
Do not. Even if your agreement does not forbid it, posting work a client asked you to keep private damages trust and can breach a confidentiality agreement. Ask for approval, and offer an anonymous version if they hesitate.
How do I write an anonymous case study?
Describe the business by type and size instead of by name, explain the problem, what you built, and the result, and remove anything identifying, including logos, colors, screenshots, and real data. Send the client the exact text for approval before you use it.
Should I add a portfolio clause to my client agreement?
Yes. A short clause saying you may describe the project after the client approves it, with no client data shown, lets them strike or narrow it before signing so you know where you stand from the start. Have a lawyer review it, since this is not legal advice.
Can I rebuild a client project as a demo?
Only if your agreement allows you to reuse the work, and only with sample data, never the client's real data. Check who owns the code before you rebuild anything, and keep the demo private to sales calls.
What if the client says no to every kind of proof?
Accept it gracefully. Ask whether they would be willing to refer you or take an occasional call from a prospect, and build public proof from your other projects or your own builds instead.
Last reviewed November 2, 2026.
Co-founder of the Claude Code Profit Room. Built and sold AI services to real clients; writes about offers, pricing, outreach, and closing with receipts.
More from Duncan Rogoff →