Article Proposals General

How to mention your portfolio in a proposal without sounding like a resume

Use portfolio links as proof, not decoration. Learn where to place them, what to say, and how to connect examples to the job.

Your portfolio should make your proposal stronger. Too often, it does the opposite.

Many freelancers drop a link and hope the client does the work:

Here is my portfolio: [link]

That is not enough. Clients are busy. They may not click. If they do click, they may not know which project matters. If the portfolio has ten unrelated examples, the client has to guess what proves you can do their job.

Your job is to connect the proof for them.

The rule

Do not mention your portfolio as a list of things you have done. Mention it as evidence for this specific project.

Weak:

You can check my portfolio here.

Stronger:

This project is closest to the second example in my portfolio, where I rebuilt a service landing page and simplified the booking flow.

The second version tells the client what to look at and why it matters.

Put the link after you show understanding, not before.

Use this order:

  1. Opening line about the client’s outcome.
  2. Short plan or first step.
  3. Relevant proof with portfolio link.
  4. Question or next step.

If you lead with the portfolio, the proposal can feel like a resume. If you place it after the plan, it supports your thinking.

Template: one relevant portfolio item

This reminds me of [portfolio project], where the main challenge was [similar problem]. The result was [specific outcome or deliverable].

Relevant example: [link]

Example:

This reminds me of a service website redesign I worked on where the main challenge was making the offer clear above the fold. The result was a cleaner homepage structure, stronger CTA, and simpler contact flow.

Relevant example: [link]

You do not need to write a case study inside the proposal. You just need enough context to make the link meaningful.

Template: multiple portfolio examples

Use this when the client might care about different parts of your work.

Two examples are most relevant:

  1. [Project name]: closest to your [design/functionality/content] goal.
  2. [Project name]: closest to your [industry/platform/technical] setup.

Example:

Two examples are most relevant:

  1. SaaS landing page redesign: closest to your goal of explaining the offer faster.
  2. Booking flow cleanup: closest to your need for a smoother contact path.

This is better than sending a full portfolio and saying “let me know what you think.”

What if your portfolio is not in the same niche?

You can still use it if you explain the transferable part.

I do not have an example in your exact niche, but this project is relevant because the challenge was similar: turning a vague service offer into a clear page structure with a strong CTA.

That is honest and useful.

Avoid pretending unrelated work is the same. A restaurant website is not the same as a SaaS dashboard, but both may involve mobile layout, speed, navigation, or conversion clarity.

What if you cannot share client work?

Sometimes you cannot share private client work. Say that plainly and use a sanitized explanation.

Some similar work is under NDA, but the closest project involved [type of project], where I handled [specific responsibility]. I can describe the approach and show public examples of similar UI/content patterns.

You can also use:

  • Personal projects.
  • Before and after screenshots with sensitive details removed.
  • Public demo pages.
  • Short Loom walkthroughs.
  • Written mini case studies.

Proof does not always have to be a perfect public portfolio page.

How much proof is enough?

For small jobs, one sentence and one link may be enough.

For larger jobs, use 2-3 proof points:

  • Similar project.
  • Similar platform.
  • Similar problem.

Do not attach six links unless the client asked. Too many links create work for the client.

Portfolio mistakes to avoid

  • Sending a generic portfolio link with no explanation.
  • Linking to old or weak work just because it exists.
  • Using examples that make the client question your fit.
  • Making the proposal mostly about you.
  • Saying “I have done many projects” without naming one relevant example.

These mistakes are part of why many proposals get ignored. See why clients ignore your freelance proposals for the broader checklist.

A complete portfolio paragraph

Your project is closest to a landing page redesign I handled for a service business, where the main issue was that visitors could not quickly understand the offer or next step. I simplified the page structure, tightened the CTA, and made the mobile layout easier to scan.

Relevant example: [link]

Then move on. The portfolio is proof, not the whole proposal.

Final checklist

  • Did you explain why the portfolio item is relevant?
  • Did you choose the strongest 1-2 examples?
  • Did you connect the example to the client’s outcome?
  • Did you avoid making the proposal read like a resume?
  • Did you include a next step after the proof?

If your proposal still feels too long, use freelance proposal opening lines to sharpen the start before adding portfolio proof.

Turn your portfolio proof into a focused proposal

Save your experience, wins, and positioning once in Lervos. For each new lead, paste the job post. Our curated proposal AI builds a structured draft that sounds like you, not a generic template. Edit what you want, send when you are ready.

Try it free