The “no clients, no portfolio; no portfolio, no clients” trap is real — but it’s breakable. Portfolio pieces don’t require paying clients. They require evidence that you can do the work. Here’s how to build that evidence from scratch.
When a potential client looks at your portfolio, they’re asking one question: “Can this person do what I need?” The answer to that question doesn’t require that someone else has already paid you. It requires samples that demonstrate your skill and your process.
Portfolio type 1: Spec projects
A spec project is work you create for an imaginary or existing client without being commissioned to do so. You identify a problem, define a brief, and execute it as if it were a real engagement.
A copywriter might write a homepage for a fictional SaaS startup. A designer might brand a fictional coffee shop from concept through logo to packaging. A developer might build a functional app that solves a problem they personally have.
Spec work is credible because it shows intentional creative decisions. The key is to document your thinking: what problem were you solving, what constraints did you give yourself, and what decisions did you make along the way? A spec piece with a one-paragraph brief and a short explanation of your choices is worth more than a polished deliverable with no context.
Portfolio type 2: Personal projects
Personal projects are specs where you’re the client. If you’re a developer who built a tool to track your own freelance expenses, that’s a portfolio piece. If you’re a writer who runs a newsletter on your area of expertise, those articles are portfolio pieces. If you’re a photographer who shot your city for a personal project, those images are portfolio pieces.
Personal projects have an advantage: you can speak about them with genuine enthusiasm. Clients often find authentic personal projects more compelling than polished spec work because they reveal what you find worth making.
Portfolio type 3: Redesigns and reconstructions
Redesigning or reconstructing something that already exists is a legitimate portfolio entry, as long as you’re clear it’s a conceptual exercise.
A UX designer might redesign a confusing checkout flow they encountered, documenting the original problem and their proposed solution. A copywriter might rewrite a weak landing page to show what they’d do differently. A developer might refactor a poorly structured open-source project and document the improvement.
Redesign portfolios often show more analytical skill than original work because they require articulating what’s wrong with something first, then fixing it.
Label these clearly: “Conceptual redesign — not affiliated with [Company].” Clients appreciate the transparency and understand the format.
Portfolio type 4: Contributions and collaborations
Open-source contributions (for developers), co-authored articles, collaborative design projects, or volunteer work for nonprofits all produce real-world deliverables that belong in a portfolio.
Contributing to an open-source project puts your code in front of real users and maintainers. Writing a guest post for an industry blog gives you published clips with a real publication. Doing pro bono work for a nonprofit gives you actual client work — a real brief, a real feedback process, a real outcome.
These contributions carry more weight than spec work because they were reviewed by someone outside yourself. That external validation matters to clients who are trying to assess quality.
Portfolio type 5: Work from past employment (with permission)
If your past job involved creating work that’s now public, you may be able to include it in your portfolio with appropriate framing. A marketing manager who wrote blog posts that were published under the company name can link to those posts. A developer who built a feature that shipped can describe the project in their portfolio.
Get explicit permission before including work that belongs to a former employer, and be precise about your specific contribution. “I designed the checkout flow” is more credible and appropriate than implying you were solely responsible for a product built by a team.
How to document any portfolio piece
The deliverable is only half the value. The documentation is the other half.
For each piece, write a brief that includes:
- The problem or goal: What were you trying to achieve?
- Your approach: What decisions did you make and why?
- The outcome: What resulted, or what would have resulted in a real engagement?
This process description shows clients how you think — which is often what they’re really evaluating. Two designers might produce similar visual work, but the one who can articulate their reasoning clearly is the one who will be easier to work with.
Building toward paid work
Once you have three to five pieces, the portfolio is sufficient to start pitching. Don’t wait until you have ten. Don’t wait until the website is perfect.
When you send your first proposals, the portfolio link is one piece of the package. The cover message, the proposed scope, and the clarity of your proposal matter just as much. Tools like Waco3 let you include your portfolio link and service description in a single professional document — so the whole package lands well, not just the work samples.
Build the minimum viable portfolio and start sending proposals. The portfolio improves fastest when you’re actively pitching, because you learn quickly what clients actually want to see.
Ready to send stronger proposals?
Build, send, and track proposals in one place so follow-up is easier.
Start your free trial →
