How to build a design portfolio when you have no clients
You build a portfolio without clients by giving yourself the briefs a client would. Design real solutions to real problems, present the thinking behind them, and keep six to ten pieces you would defend. Here is the method.
The short answer
You build a portfolio with no clients by giving yourself the briefs a client would. Pick real problems (a local cafe that needs a menu, a podcast that needs cover art, an app idea that needs a screen), design solutions for them, and present them as finished projects. Nobody looking at your work cares whether the client was real. They care whether the thinking and the craft are.
The goal is six to ten strong pieces that show range and judgment, not a folder of forty half-finished experiments. A portfolio is an argument that you can solve a design problem. Every weak piece weakens the argument.
Reviewers spend seconds on a first pass. Your weakest piece sets your ceiling, so it is better to cut it than to pad the count.
Give yourself real briefs
Self-assigned briefs beat aimless practice
Open-ended practice ('I'll just design something') tends to stall, because there's no problem to solve and no way to know when you're done. A brief fixes that. Give yourself constraints: who is this for, what does it need to do, where will it appear. Constraints are what make design decisions possible.
Good sources of realistic briefs:
- Redesign something that exists. Take a real product's poster, menu, or app screen and redesign it. State the problem you saw and what you changed. Redesigns show judgment, which is the thing clients actually buy.
- Design for a fictional but plausible business. A neighborhood bakery, an indie game studio, a running club. Give it a name, a brief, and a full set of pieces (logo, social, one printed item).
- Solve your own problems. The event you are organizing, the newsletter you send, the side project you are building. Real needs make honest projects.
One caution: if you redesign a real brand, label it clearly as an unofficial concept so nobody mistakes it for client work. Honesty is part of the craft.
What to put in (and leave out)
Show the thinking, not just the final image
A pretty final image tells a reviewer you can push pixels. The story around it tells them you can think, and thinking is what gets you hired. For each project, include a short line on the problem, a couple of process shots or drafts, and the final result. You don't need essays. Three sentences of 'here's the brief, here's the key decision, here's the outcome' does more than a paragraph of adjectives.
- Range: show a few different types of work (layout, type, brand, maybe one UI piece) so a reviewer can see where your strengths sit.
- Consistent quality: every piece should be one you'd defend. Cut the rest.
- Real constraints: pieces that respect a format (print sizes, safe zones, a real aspect ratio) read as professional. The tool guides help here, whether you work in Photoshop, Illustrator, or Figma.
If you are aiming at UX or product roles specifically, the expectation shifts toward case studies: the problem, your process, the decisions, and the result. That format is built into the Figma path more than the print ones.
Where to host it
You need somewhere to send people. Three reliable options, in rough order of effort:
- A profile on a design community like Behance or Dribbble. Fast to set up, built-in audience, good enough to start applying with.
- A simple personal site. More work, more control, and the version reviewers respect most for senior roles. You can start on a community profile and graduate to this.
- A clean PDF. Underrated for sending directly to a specific person. Easy to tailor, easy to attach, no login wall between the reviewer and your work.
Whichever you pick, keep it fast to load and easy to skim. If a reviewer has to hunt for your best piece, the best piece isn't doing its job.
When not to worry about a portfolio yet
Don't build a giant portfolio before you can make one strong piece. If you're brand new, learn the fundamentals first and let the portfolio grow out of the coursework, one finished piece at a time. A rushed portfolio of weak work is worse than no portfolio, because it argues against you.
And don't wait for the portfolio to be 'perfect' before you show it. Perfect is a moving target that mostly keeps you from applying. Get to six pieces you're proud of, publish, and improve it while it's live. Enroll in a course when you want a structured way to produce those pieces instead of guessing what to make next.
Common questions
How many pieces should a design portfolio have?
Roughly six to ten strong pieces. Quality decides more than quantity, and reviewers judge you by your weakest included work as much as your best. When in doubt, cut the weakest piece rather than add a filler one.
Can I get hired with a portfolio of personal projects?
Yes. Self-assigned and concept projects are common and respected, as long as the work is strong and you present the thinking behind it. Reviewers care about your judgment and craft, not whether an invoice was involved.
Where should I host my design portfolio?
Start on a community like Behance or Dribbble for speed, and move to a simple personal site as you get more serious. A tailored PDF is great for sending directly to a specific person or role.
Should I include client work if I have some?
Yes, real client work is worth showing, but only the strong pieces. One weak client project can pull your portfolio down more than a strong concept project lifts it. Curate ruthlessly either way.
Do I need a portfolio for a UX or UI job?
Yes, and it should lean toward case studies: the problem, your process, the decisions, and the outcome. That storytelling matters more in product roles than a gallery of polished screens. The Figma course is built around that workflow.