066
How to build a design portfolio that wins freelance clients
Stop forcing one generic design portfolio on every buyer. Create targeted mini ones per client type, so every pitch shows your most relevant work.
I've been a product designer for almost twenty years.
In that time I've worked across SaaS, ecommerce, small businesses, corporate product teams, and plenty of odd one-off briefs that don't fit a neat label.
I don't have a design portfolio with my "best" projects, because what's strong for a B2B SaaS founder is noise for a local retailer. What's convincing for a corporate stakeholder reads as overkill for a ten-person startup.
So I have several mini portfolios that showcase work from similar industries and similar product types.
When I pitch a company, the client sees the work closest to their world first. They are not scrolling past unrelated projects wondering if I can help solve their problem.
Most buyers prefer someone who looks like an expert in their problem: Their product type, their business context, their constraints, not a generalist.
This article shows you how to build that system without rebuilding your entire site.
If you are at the beginning of your freelance career, I recommend reading Freelance UX Design: Finding clients, setting rates, and staying sane as well.
Why one generic design portfolio loses freelance pitches
A portfolio designed to get a job is optimized for recruiters.
Freelance portfolios optimize for one specific buyer who has a specific problem to solve.
That buyer isn't grading your whole career.
They are looking for reassurance and relevant experience in their field. This person wants to know if you solved a similar problem to theirs before, if you understand their industry and product and business contexts.
When your portfolio tries to target everyone, it targets nobody.
The main issue isn't that you lack range.
It's that range without specificity reads as misalignment for the buyer.
What freelance clients want
The obvious ones are clarity, experience and professionalism.
They also want:
- Fit to their industry and product type before they read depth.
- Outcome language tied to their business goals and users.
- Confidence you are the right specialist: You know the scope and what to deliver.
They care less about:
- How many case studies you have in total.
- Whether you worked in other industries or other types of businesses they are not familiar with.
- Process jargon that doesn't map to their brief and needs.
Your goal should be to make it obvious you have done this kind of work before and you are the right person for them.
If you are interested in how to structure your portfolio, read how to build a UX portfolio website that works as hard as your best project.
The mini portfolios system
You need one website plus several mini portfolios per client type.
Step 1: Build one website
Your website is the URL you'd put on a business card or LinkedIn.
It should:
- Name what you do for UX and product design buyers.
- Show your strongest overall proof (3 to 4 projects).
- Include contact and a plain offer line.
This isn't where you dump every project you've ever touched. It is where strangers decide you are legitimate.
Structure beats decoration here so start with portfolio design templates: Start with structure, not style.
Step 2: Define your clients
For most freelance UX and product designers, four types of clients cover most outreach:
1: SaaS product
Buyers care about onboarding, retention flows, complex settings, B2B workflows, and evidence you understand product iteration.
2: Ecommerce
Buyers care about conversion paths, checkout friction, mobile shopping behavior, and merchandising clarity.
3: Marketing and standard websites for small business
Buyers care about fast clarity, lead capture, service positioning, and sites that look trustworthy without enterprise baggage.
4: Corporate product work
Buyers care about stakeholder alignment, accessibility and compliance subtext, design systems, and calm execution inside slower organizations.
Step 3: Build a mini portfolio per lane
A mini portfolio is a curated package for one type of client: Usually 3 to 4 projects from the most relevant industries, not your full archive.
Delivery format is flexible. Pick what you'll maintain:
- A private page on your website: A real URL on your site that isn't linked from your menu or homepage, so only clients you send it to will find it.
- A view-only deck link.
- A PDF for fast email attachments.
The format matters less than whether the work reads as a match in the first screen.
Be brutal when leaving out projects that look strong but fit the wrong client type or industry. A corporate buyer doesn't need your indie app concept first. An ecommerce founder doesn't need your enterprise admin redesign.
If you struggle to write what you did for each project, use writing a UX Design case study that shows thinking, not just pixels.
Step 4: Send only the right mini portfolio
Routing is the whole strategy.
When you do cold outreach to a SaaS founder, you send them the SaaS mini portfolio link, that's it. If a referral comes in from an agency contact who works in ecommerce, you drop the ecommerce one. For general networking, your website works just fine.
When you write proposals, open with relevance.
Tell them you pulled three projects closest to their product type and share the relevant mini portfolio. That one sentence does more positioning work than any generic portfolio your competitor sends over.
You aren't hiding your other work. You are simply respecting the client's time and their true interest.
What to lead with and what to avoid
Use these as defaults when you build each mini portfolio.
SaaS product lane
Lead with:
- A workflow or onboarding project with a clear before/after story.
- Evidence of iteration (what you tested, what you cut).
- Language your buyer uses: Activation, adoption, churn, time-to-value.
Avoid leading with:
- Consumer apps with no B2B parallel.
- Pure visual rebrands with no product behavior change.
Ecommerce lane
Lead with:
- Conversion or checkout improvements.
- Mobile shopping flows.
- Catalog or search clarity when that matches the brief.
Avoid leading with:
- Internal dashboards unless the buyer explicitly runs operations-heavy commerce.
Small business marketing site lane
Lead with:
- Fast clarity: What the business does, who it is for, how to contact or buy.
- Trust signals done simply (not over-designed).
- Projects where the owner could explain the outcome in one sentence.
Avoid leading with:
- Dense product case studies meant for VP-level product reviews.
Corporate lane
Lead with:
- Cross-functional work with constraints named early.
- System thinking, accessibility awareness, and rollout reality.
- Calm visual proof that reads as dependable.
Avoid leading with:
- Flashy Dribbble-style shots with no business context.
FAQs
Do I need separate websites for each client lane?
No. One website is enough. Mini portfolios can be private pages on that site, decks, or PDFs. The goal is curated relevance, not duplicate builds.
How many projects belong in a mini portfolio?
Usually 2 to 4. Enough to show pattern, not so many that buyers lose the thread. Lead with the closest match to their product type.
Should I still keep a general homepage?
Yes. Your website is for credibility and broad discovery. Mini portfolios are for targeted outreach and proposals where fit matters most.
How is this different from a recruiter-focused UX Design portfolio?
Recruiter portfolios optimize for role fit across many employers. Freelance portfolios optimize for one buyer's business problem. The structure overlaps; the lead project and framing changes.
Can I use the same project in multiple portfolios?
Sometimes, if the story changes. A checkout flow might lead an ecommerce lane and support a SaaS lane with a different outcome frame. Don't copy-paste identical blurbs. Tune language to the buyer.
What delivery format works best for mini portfolios?
Use what you will maintain. Site pages are easy to access. Decks and PDFs are fine for fast outreach. Avoid formats that feel broken on mobile or require passwords without context.
How often should I update my portfolios?
Review quarterly or when you shift target clients. Swap the lead project when you land stronger experience in that industry. Remove work that no longer represents your standard.
Final takeaway
Your portfolio has one job: Make the right buyer feel immediately understood.
A generic link forces potential clients to do mental work, connecting the dots between your past projects and their specific needs. Most won't bother.
After nearly twenty years freelancing, I learned that clients don't hire your entire career. They hire confidence that you understand their product, their context, their problem.
That's the difference between a portfolio targeting everyone and a set of mini portfolios built around the exact clients you want more of. One does the translation work for them. The other puts it on them.
Curate your projects by client type, send the link that matches, and you arrive at every conversation already positioned as the right choice, before you've said a word.
Positioning, relevant experience, and similar past projects will always beat volume.
If you want a clear system for building this, from curating your projects to turning outreach into real conversations, Zero to Pro is where to start.
Read next
Step-by-step guide to getting UX Design internships with no experience
UX Design salary explained: What's rising, what's flat, and why
From Designer to Design Manager: Climbing without losing your craft
Remote UX Design jobs: Where to find them and how to land one
Why your Web Design portfolio matters more than your case studies
Never miss an article
Get more actionable ideas for free in your inbox
Stay up to date with the latest AI & Design insights in the industry

