How to reference past work without dumping ten links in the opening lines
Proof should feel curated, not noisy. Here is how to pick examples, describe outcomes, and link only what helps the client decide.
Clients do not hire your portfolio. They hire your judgment about their problem.
When you open with a pile of links, you outsource that judgment back to them. Many will not do the work. They skim, get overwhelmed, and move to the next freelancer who made the decision easy.
You already have a deeper guide in how to use your portfolio inside a proposal. Treat this article as the “first ten lines” specialization: how to prove skill without looking like spam.
The rule: two proofs max in the opener
In the opening section, aim for:
- One primary example that matches industry, stack, or deliverable type.
- One secondary example that shows range, scale, or a different risk you can handle.
Put everything else later, or offer it on request.
Replace links with outcomes
A link without context is decoration. A short outcome line is proof.
Weak:
Here is my portfolio: link link link link
Stronger:
Closest match: I built [deliverable] for [type of client] under [constraint]. Outcome: [metric, speed, quality signal]. Link: [one].
If you are newer and worried about proof, pair this approach with beginner proposals without case studies.
A simple opening pattern you can reuse
Use this shape:
- One sentence: what you understood about their job.
- “Closest match” proof: what you did, what was hard, what happened.
- Optional second proof: different angle (speed, complexity, regulated industry, multilingual, etc.).
- Plan + question.
Example (adapt freely):
I read your post and it looks like you need [deliverable] with [constraint], especially around [risk area].
Closest match: I shipped [similar deliverable] for [similar context]. The tricky part was [real challenge]. Result: [outcome in plain language]. Example: [one link]
Second related project: [one line + optional link]
If that direction matches what you want, my first step would be [milestone 1]. Two quick questions: [Q1] and [Q2].
This respects the reader’s time. It also shows you can narrate work, which matters for higher-trust buyers.
When to use screenshots instead of links
Some work is private. Some links rot. Sometimes a screenshot of UI, copy, or analytics blur is enough for step 1.
If you blur data, say so in one honest phrase. Clients respect confidentiality signals.
What to do if everything is under NDA
You do not need illegal leaks. You need category proof.
Describe:
- The type of system
- The type of constraint
- The type of decision you owned
Then offer a paid small milestone to demonstrate skill safely.
How this interacts with proposal openings
Your first lines should not be a directory. They should be a lens.
If you want alternate openers, browse freelance proposal opening lines and pick patterns that leave room for proof, not a link farm.
Mistakes that make portfolios feel cheap
Linking the homepage of ten companies without saying what you personally did.
Claiming “we” when you mean “I.” If you are solo, say so. Agencies pretending to be solo destroy trust. If the post says “no agencies,” you need clean language from job posts that say no agencies.
Proof that does not match the job. A beautiful poster portfolio does not help a backend API job.
FAQ
Should I include GitHub?
Only if it is relevant and tidy. Many buyers will not read code. Summarize what they should notice.
Should I attach PDFs?
Sometimes, if small and targeted. Huge decks often get ignored on mobile.
How many total links in the full proposal?
There is no universal number. Think in terms of decision friction. If you add a link, add one line that says why it matters.
Before you send
Run the proposal checklist and add:
- Does each link have a “why this matters to you” sentence?
- Did you remove proof that is impressive but irrelevant?
If you generate drafts with AI, do not let it invent projects. Keep a saved list of real wins and let tools like Lervos map them to each job post during drafting, then you verify every claim.
Bottom line: proof is not volume. Proof is relevance with receipts.
Turn scattered wins into one tight proof story per lead
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.