I can look at a portfolio and see things a client may not immediately see. That's partly because I'm a designer, but also because I spend my time helping designers and small agencies communicate their capability more effectively.
The client has a different responsibility.
They have to decide whether to trust these people with a real business problem. If they make the wrong choice, they don't just lose the project fee. They lose time, momentum and potentially business results.
So the burden is on the portfolio to make that decision easier.
It has to give the client enough relevant evidence to say, “Yes. These are the people I want working on this.”
That is where many portfolios go wrong.
They are built as collections of the designer's best work. The most beautiful screens. The most interesting projects. The case studies everyone in the studio is proud of.
There is nothing wrong with beautiful work. But there is a difference between treating your work as art and treating it as communication.
When you treat your portfolio as art, you are saying, “Look how good this is.”
When you treat it as communication, you are saying, “Here is the problem we solved, how we solved it, and what changed because of our work.”
Your client is not hiring your portfolio. They are hiring your ability to solve a problem.
Once you look at a portfolio that way, the way you create it changes.
1. Articulate the promise
Start by being clear about what you do, how you do it and why someone should believe you are good at it.
A portfolio shouldn't force the client to work this out by looking through a collection of screenshots.
If you say you improve complex enterprise applications, for example, make that capability clear. If you specialise in improving digital products, explain what that means in practice.
The promise gives the rest of the portfolio a purpose. It tells the client what your work is supposed to demonstrate.
And that promise needs to be more than a collection of adjectives. “Creative.” “Innovative.” “User-centred.” “Strategic.” Most agencies can say those things.
The useful question is: What do you actually help clients accomplish?
2. Prove the promise
Once you make a claim, give the client something to believe.
If you redesigned a checkout flow, what happened afterwards? If you optimised an enterprise application, did you reduce the time required to complete a task? If you worked on an app whose rating was a problem, did the rating improve?
Not everything that matters can be measured, and not everything that can be measured necessarily matters. But when credible evidence exists, it makes your claim much easier to trust.
A beautiful checkout redesign tells me that you can design a beautiful checkout.
A checkout redesign that reduced a significant drop-off tells me something much more useful: that you have experience solving a problem I may also have.
For smaller agencies, this is often difficult because the evidence may not appear immediately. A redesign can take months before its impact becomes visible. If nobody follows up, documents the outcome and preserves the evidence, that information disappears.
The answer isn't to invent numbers. It is to recognise that evidence is valuable and, whenever possible, make it part of the process.
Evidence does not replace good design. It gives the buyer a reason to believe that the design worked.
3. Build a master capability deck
Don't try to make one presentation do everything.
Build a master capability deck containing the complete picture: who you are, what you do, who you do it for, how you work, what capabilities you have and what evidence supports those capabilities.
Think of it as your source of truth.
The master deck isn't necessarily what you send to every client. Its purpose is to make sure you have the material available when you need it.
That distinction matters because a sales conversation rarely follows the neat structure of your website.
A client might ask about accessibility. Another might ask about AI. Someone else might be struggling with an enterprise workflow or an e-commerce conversion problem.
You should not have to start searching through old Figma files when the question comes up.
4. Research the prospective client
Before deciding what to show, understand who you are showing it to.
What industry are they in? What are they trying to accomplish? What problems might they be facing? What questions are they likely to ask? What would they need to believe before they feel comfortable trusting you?
Imagine you are meeting an e-commerce company.
You could walk into the meeting with your four favourite projects.
Or you could think about the problems that might actually matter to that business: product discovery, checkout, conversion, retention, account management or other parts of the customer journey.
Then you can prepare evidence that makes those connections visible.
That tells the client something before you have even started discussing the work:
We spent some time understanding your situation before asking you to spend time with us.
That builds confidence.
5. Maintain a master project library
Your projects shouldn't simply be an archive of everything you have ever done.
They should be searchable evidence.
Map projects against the things a future client might care about: problems solved, industries, capabilities, types of users and outcomes.
This changes the question from “Which are our best projects?” to “Which projects demonstrate that we have solved something relevant to this client?”
Those are not the same question.
Your most visually impressive project might have very little relevance to the conversation in front of you. A less glamorous project might demonstrate exactly the experience the client needs.
The best project in your portfolio isn't necessarily your best work. It is the best evidence for the conversation you are having.
6. Customize for each opportunity
This is where the master library becomes useful.
Don't take the same four projects into every meeting simply because they are the projects you have always shown.
Select the evidence based on the client's situation.
If the conversation is about introducing AI into an existing workflow, show relevant work. If it is about accessibility, show work that demonstrates your understanding of accessibility. If it is about a particular industry or business problem, bring evidence that makes that connection obvious.
You are not changing your capabilities for every client.
You are changing which evidence you put in front of them.
And that is more than a presentation technique. It demonstrates the same behaviour you are asking the client to hire you for: understanding a situation, identifying what matters and responding accordingly.
7. Keep the website broader
Your website has a different job.
It should establish your broader capability and give people enough context to understand who you are, what you do and the kinds of problems you solve.
The sales deck can be much more specific.
The website says, “This is what we are capable of.”
The client-specific deck says, “Here is why that capability is relevant to you.”
Trying to make the website perform the second job can result in an unwieldy collection of everything you have ever done. Trying to make the sales deck perform the first can make it too generic to be persuasive.
Give each one a job.
Your portfolio is part of a larger system
There is a bigger lesson here.
If you genuinely work this way, the thinking doesn't stop at the portfolio. It appears in your proposal, your presentation and every conversation you have with the client.
You begin with what the client is trying to accomplish. You anticipate the questions they will have. You select the evidence that is relevant to those questions. You make your reasoning visible.
The portfolio is simply one expression of that way of working.
And that is why I don't think the answer to a weak portfolio is necessarily another round of polishing the case studies.
The deeper problem is often that there is no system behind the portfolio.
Good agencies accumulate experience. But experience sitting in old project folders is not particularly useful when a new client is asking, “Have you solved this before?”
That experience becomes valuable when you can retrieve it, explain it and connect it to the problem in front of you.
So the next time you sit down to review your portfolio, don't ask:
“Which projects should we show?”
Ask:
“What does this client need to believe, and what evidence do we have that will help them believe it?”
That question changes the portfolio from a gallery of past work into something much more valuable: a tool that helps the right client make a confident decision.
