How to Build a Portfolio That Actually Gets You Clients (Not Just Compliments)

Industry & Career
1

Portfolio advice gets recycled so often I want to give the counter-intuitive version.

What actually gets attention in a portfolio review is not what most advice columns say:

More is not better: I’ve reviewed hundreds of portfolios. The ones that get remembered show 4-6 projects done exceptionally well. The ones that get forgotten show 15 projects at uneven quality. One weak project undermines five strong ones.

Process documentation is overrated when the process is obvious: showing 40 screenshots of Figma iterations for a simple UI change is padding. Process matters when the problem was genuinely complex and the solution required visible thinking.

The context sentence: one sentence explaining what problem this project solved and for whom. This is what I’m most often missing in portfolio reviews. Beautiful work without context is just pictures.

Awards and client names: useful signal but not a substitute for the work. Some of the best portfolios I’ve seen have no recognisable names. Some of the weakest have impressive client lists.

What you actually need: one project where the problem was difficult, you made a specific strategic decision, and the execution is flawless. Everything else is supporting evidence.

What’s the feedback that changed how you thought about your portfolio?

2

The context sentence is what’s missing from most junior portfolios. Beautiful execution, no problem statement. As a reviewer I’m left wondering what the actual brief was and whether the work addressed it.

3

Four to six projects well done is better than fifteen at varied quality - this is correct and I wish I’d understood it earlier. My first portfolio had everything in it. My current one has six things and gets better responses.

4

@JohnWillowdusk the one difficult project requirement is the differentiator. Anyone can show clean execution. Showing how you made a difficult strategic call and how that decision shaped the outcome is what separates senior-level portfolios.

5

Process documentation being overrated when the process is obvious is something more people need to hear. I’ve reviewed portfolios where 80% of the space is iterations and 20% is finished work. Invert that.