The Anti-Portfolio: Show Proof When You Have Zero Clients
Duncan Rogoff July 9, 2026 6 min read- An Anti-Portfolio is proof you created without a client - demos, spec builds, and public experiments that show exactly what you can do.
- Buyers do not care whether the proof came from a paid project. They care whether it solves the problem they have.
- Three strong Anti-Portfolio pieces outperform a list of ten vague client references.
Why Zero Clients Does Not Mean Zero Proof
The traditional portfolio trap: you need clients to get proof, but you need proof to get clients. The Anti-Portfolio breaks this loop by redefining what proof means. Proof is not a client testimonial. Proof is evidence that you can solve the problem. That evidence can exist before any client ever pays you.
A buyer on a first call wants to answer one question: has this person solved something like my problem before? If you have a demo that shows exactly that, a live build that addresses their category of pain, or a public experiment with documented results - that is proof. The fact that no one paid you to make it is irrelevant to the buyer's question.
The Three Types of Anti-Portfolio Proof
There are three formats that work for pre-client proof. Each has a different effort level and a different buyer impact. Build at least one of each before you start active outreach.
- Spec builds: Build the solution to a real problem in your target niche, using publicly available information instead of a real client's data. A spec build for a recruiting agency might automate their candidate screening process using example data. Document the problem, the build, and the result.
- Public experiments: Run a real process using Claude Code and document what happens. 'I ran 30 LinkedIn outreach messages through a Claude Code template and got X replies' is public proof with real outcome data. You are the client for the experiment.
- Functional demos: A live, working tool or automation that any interested buyer can see in action. A short screen recording or a shared link that shows the mechanism working. The demo does not have to be polished - it has to work and show something specific.
How to Present Anti-Portfolio Proof to Buyers
The framing of Anti-Portfolio pieces matters as much as the quality. Present them as completed work with outcomes, not as practice projects or experiments. The distinction is in the language.
| Weak Framing | Strong Framing |
|---|---|
| 'This is something I built to practice' | 'I built an automated lead qualification system for a spec recruiting agency project' |
| 'I have not worked with real clients yet but...' | 'Here is a build I completed that addresses [specific problem]' |
| 'This is just a demo' | 'This is a working prototype of the automation I would build for your use case' |
| 'I am still learning but I wanted to show you...' | 'Here is how I approached [problem type] - this is the output' |
Confidence in presentation is itself a proof signal. A builder who presents their spec work as real, completed work is demonstrating the same posture they will have when delivering actual client projects.
From Anti-Portfolio to Real Client: The Bridge
The Anti-Portfolio is a starting position, not a permanent one. The goal is to convert one Anti-Portfolio piece into a real paid engagement so you have one authentic case study. After that, the Anti-Portfolio becomes a secondary proof layer rather than your primary one.
- Use Anti-Portfolio pieces in outreach as conversation starters: 'I built this for a spec project in your space - curious if this is a problem you are dealing with.'
- Offer to show the demo live on a short call rather than sending a document - interactive proof is more convincing.
- For your first real client, consider reducing your rate to get the authentic case study. Frame it internally as buying proof, not discounting your service.
- Once you have one real client result, lead with that and use the Anti-Portfolio pieces as supporting evidence, not the headline.
The Profit Room exists precisely for this transition. Share your Anti-Portfolio pieces with the community, get feedback, refine the framing, and let other members surface the connections that turn spec work into paid work.
Frequently asked
Is it dishonest to present spec work without telling buyers it is not from a real client?
No, as long as you do not claim it is from a client. 'I built this to demonstrate how I would solve [problem]' is completely honest and still compelling to buyers.
How many Anti-Portfolio pieces do I need before I start outreach?
Three is enough to start. One demo, one spec build document, and one public build post. More is better but not required to begin conversations.
What if my niche is too specialized for me to build a relevant spec project?
Find a public example of the problem type, anonymize it, and build a solution to it. You do not need real client data to build a real solution.
How do I build a functional demo if I do not have the real platform credentials?
Use sandbox environments, test accounts, or simulate the data inputs. Most platforms have developer or trial accounts. The demo does not need to be connected to production data.
Will buyers really care about spec work once I have real clients?
Less so. Once you have two or three authentic case studies, your Anti-Portfolio pieces become secondary. Keep them as supporting proof but lead with the real client results.
Last reviewed July 9, 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.