The Codex
How to build a freelance portfolio (even with no clients)
A portfolio is evidence, not an archive: three to six relevant case studies with the problem, your approach, the result, and proof.
A freelance portfolio that wins clients shows three to six pieces of work that match the service you sell, each presented as a short case study: the problem, your approach, the result, and proof. If you have no client work yet, build spec or self-initiated projects for the kind of client you want, label them honestly, and replace them with real work as it comes in.
This guide covers what to include, a case-study structure, how to show NDA work ethically, portfolio formats for design, writing, development, marketing, and consulting, where to host it, a copyable one-page case-study template, and a review checklist.
A portfolio does its best work when someone already has a reason to look. Pair it with a steady way to start conversations, such as the cold email templates for freelancers.
Codex summary
A freelance portfolio that wins clients shows three to six pieces that match the service you sell, each as a short case study: problem, approach, result, proof. With no client work yet, build labeled spec or self-initiated projects. Show NDA work only with written permission, anonymized properly, and never invent testimonials or results.
Who this is for
- New freelancers with little or no client work to show
- Experienced freelancers whose best work is under NDA
- Anyone whose portfolio gets views but doesn't turn into enquiries
If you only do 3 things
- Cut your portfolio to the three to six pieces that match the services you want to sell, most relevant first.
- Rewrite each piece as a case study: problem, your role and approach, result, and proof.
- Ask past clients in writing whether you can show their work named, anonymized, or not at all.
What a freelance portfolio is for
A prospect looking at your portfolio is trying to answer one question: "Can this person solve a problem like mine, and will working with them be safe?" Your portfolio is evidence for that decision. It is not an archive of everything you have made.
That changes what "good" means. A portfolio wins work when it is relevant (it shows the work you want more of), explained (each piece says what problem it solved and what you did), and credible (the proof is real and checkable). Visual polish matters, but a beautiful gallery with no context still leaves the prospect guessing.
What to include
- A one-line positioning statement: who you help and with what. For example, "I write help docs and onboarding emails for B2B software companies."
- Three to six case studies that match the services on your offer list. Put the most relevant one first.
- Proof: testimonials used with permission, links to live work, client names or logos where you're allowed to show them.
- How you work: a short process summary, typical timelines, and how projects start.
- A clear next step: an email address or short contact form, plus what to include in a first message.
- About: a few sentences on your background that are relevant to the buyer, and a real photo if you're comfortable with that.
Leave out work in services you no longer want to sell, very old pieces that no longer reflect your skill, and anything you don't have the right to show.
The case-study structure: problem, approach, result, proof
Problem
What was wrong or missing, for whom, and why it mattered. Use the client's language: "mobile visitors were abandoning the booking form", not "UX optimization".
Approach
What you investigated, the key decision you made, and the alternative you rejected. This is where prospects see how you think, which is what they are really buying.
Result
What changed. Use real numbers only if you measured them and are allowed to share them. Plain outcomes count: shipped on time, replaced a manual process, handed over so the team can update it.
Proof
Screenshots, before and after, a link to the live work, a permitted testimonial, or a process artifact such as a sketch, outline, or code sample.
Always state your role. If you worked in a team or through an agency, say what you did yourself. Overstating your part is the fastest way to lose trust in a reference check.
Turning NDA and confidential work into portfolio pieces
A lot of good freelance work is covered by an NDA or sits behind a login. You may still be able to use it, but only in ways the agreement and the client allow.
- Read the paperwork first. Check the NDA and your contract for confidentiality terms, who owns the work, and any portfolio or publicity clause. If you're drafting new contracts, add a portfolio permission clause; the guide to freelance contract clauses covers how it fits with intellectual property terms.
- Ask in writing. Offer clear options: named, anonymized, or not shown. Get the answer by email so you have a record.
- Anonymize properly if that's the deal. Remove names, logos, domains, product names, people, internal figures, and anything that would let a reader identify the client. Describe the client by type, such as "a 40-person logistics company".
- Rebuild instead of screenshotting when needed. Recreate the layout, flow, or document structure with invented sample content so you show your thinking without exposing real data.
- Send the draft for approval before it goes live, and take it down promptly if the client changes their mind.
Screenshots of dashboards, inboxes, CRMs, and spreadsheets often contain other people's personal data. Blur or replace it with sample data even when the client has approved the case study.
Template: asking a client for portfolio permission
Subject: Featuring [project] in my portfolio?
Hi [Name],
I'm updating my portfolio and would like to include a short case study about the [project] work, if you're comfortable with it.
Here's what I'd show:
- [Option A: named, with the live link and 2-3 screenshots]
- [Option B: anonymized, e.g. "a regional accounting firm", with no logos, names, or figures]
I'll leave out [anything confidential: revenue, internal tools, customer data] and send you the draft before it goes live.
Would either option work? A quick reply is all I need, and "no" is completely fine.
Thanks,
[Your name]Building a portfolio with no client work yet
Everyone starts with an empty portfolio. You can fill it honestly with three kinds of work.
Spec projects
A spec project is work you create, unpaid and unrequested, to show how you would solve a realistic problem. Choose a problem your target clients actually have, write a short brief for yourself, and produce the work to the standard you'd deliver for pay. Present it as a case study and label it "Spec project". If you redesign or rewrite something for a real company, make clear they didn't commission it, and don't use their logo in a way that suggests a relationship.
Self-initiated projects
These are projects you own: a tool you built, a newsletter you write, a template you sell, research you published. They are often stronger than spec work because they are real and live, and they show initiative.
Small real projects
Work for a nonprofit, a community group, or a friend's business at a fair introductory price or pro bono gives you a real client, real constraints, and possibly a testimonial. Keep these small and scoped in writing. Before you agree to underpriced work just for the portfolio, weigh it with the framework for choosing freelance projects.
A starter plan (hypothetical example)
A new freelance copywriter targeting independent fitness studios writes one spec case study (a rewritten class-booking page with the reasoning behind each change), one self-initiated piece (a three-email welcome sequence for an imaginary studio, labeled as such), and one small paid project for a local studio. That is three relevant pieces, each tied to a service she sells, with honest labels.
Portfolio formats by field
| Field | What to show | What buyers look for |
|---|---|---|
| Design (brand, UI, web) | Visual case studies with process: sketches, options considered, final work in context (on a device, on packaging) | Taste, problem framing, and whether the design worked for the business |
| Writing (copy, content, technical) | Links to published pieces or clean PDFs, grouped by type, with a line on the brief and audience for each | Range within their niche, clarity, and the ability to work from a brief |
| Development | Live demos, repositories with a clear README, short write-ups of architecture decisions and trade-offs | Code quality, reliability, communication, and whether you finish things |
| Marketing (ads, SEO, email, social) | Campaign case studies: goal, strategy, execution, and results you are allowed to share, with screenshots stripped of private data | Strategic thinking and honest reporting, not vanity metrics |
| Consulting and operations | Short engagement summaries, a sample deliverable (anonymized audit, roadmap, or framework), and a described method | How you diagnose problems and what a client gets at the end |
Where to host your portfolio
| Option | Good for | Watch out for |
|---|---|---|
| Your own website and domain | Control, a professional email address, linking from proposals and cold email | Needs upkeep; keep it simple so you actually update it |
| Portfolio platforms (for example Behance or Dribbble for design) | Fast setup, discovery within the platform's community | You follow their rules and layout; use them alongside your own site |
| Code hosting (for example GitHub) | Showing repositories and demos to technical buyers | GitHub says GitHub Pages isn't meant as free hosting to run an online business, so use it for project demos rather than your main business site [5] |
| PDF portfolio | Sending a tailored selection with a proposal | Keep the file small and the selection specific to the prospect |
| Freelance marketplace profiles | Proof inside a marketplace where buyers already search | Check each platform's rules on contact details and showing off-platform work |
One-page case-study template
Copy this, fill it in for each project, and keep each case study to roughly one screen or one page. Detail goes in the approach section, not in a long introduction.
Template: one-page case study
[PROJECT TITLE: outcome-led, e.g. "Rebuilt a booking flow so mobile visitors could finish in one step"]
Client: [Name, or anonymized description: industry, size, region]
My role: [What you did yourself; who else was involved]
Timeline: [e.g. 6 weeks] Type: [Client work / Spec project / Self-initiated]
1. PROBLEM (2-3 sentences)
What was wrong or missing, who it affected, and why it mattered to the business.
2. APPROACH (3-5 bullets)
- What you looked at first and what you found
- The key decision you made, and the option you rejected
- What you built, wrote, or changed
- How you worked with the client (reviews, handover)
3. RESULT (2-3 sentences or bullets)
What changed. Use numbers only if they are real and you have permission
to share them. Otherwise describe the change plainly: "launched on time",
"replaced three manual spreadsheets", "now updated by the client's team".
4. PROOF
- Visuals: [screenshots, before/after, link to the live work]
- Testimonial: [exact quote, name and role, used with written permission]
- Artifacts: [process sketch, outline, code sample, brief excerpt]
Next step: [one line, e.g. "Need something similar? Here's how I work."]Testimonials and proof: keep it real
Disclaimer: General information, not legal advice. Check the consumer protection rules in the countries where you market your services.
Never invent testimonials, results, or client logos. Beyond the trust problem, regulators in all four main markets treat fake or misleading reviews and testimonials as a legal issue:
- US: the FTC's rule on consumer reviews and testimonials took effect on October 21, 2024 and bans fake reviews and testimonials, with civil penalties available against knowing violators. [1]
- UK: fake reviews and concealed incentivised reviews became banned practices under the Digital Markets, Competition and Consumers Act 2024 from April 6, 2025, as explained in the CMA's fake reviews guidance. [2]
- Canada: section 74.02 of the Competition Act generally prohibits publishing a testimonial about a product's performance or effectiveness unless the person has already made it and you have their written approval, and the published version must match what they said. [3]
- Australia: the ACCC says it is against the law for a business to create fake or misleading reviews or to arrange for others to create them. [4]
In practice: quote clients word for word, get written permission to use their name and role, don't edit a testimonial's meaning, and disclose if you gave anything in exchange. The easiest time to ask is at the end of a successful project; the guide to onboarding, delivery, and retention shows where that request fits in your offboarding.
Portfolio review checklist
- The first screen says who you help and with what, in one sentence.
- Every piece matches a service you currently sell.
- The most relevant case study for your target client comes first.
- Each case study states the problem, your role, your approach, the result, and the proof.
- Spec and self-initiated work is labeled.
- You have written permission for every named client, logo, and testimonial.
- Screenshots contain no personal or confidential data.
- Every link works, and the pages load quickly on a phone.
- There is one clear way to contact you, and it works.
- You've reviewed the whole portfolio in the last three months.
Common portfolio mistakes
- Showing everything instead of the work you want more of.
- Images with no explanation of the problem or your role.
- Claiming team results as solo work.
- Inventing metrics or testimonials, or quoting clients without permission.
- Showing confidential client work because "it's been a while".
- Spending months perfecting the site instead of pitching with three good pieces.
- Letting it go stale: old work, dead links, outdated services.
Put the portfolio to work
A portfolio rarely brings clients on its own; it converts the attention you create elsewhere. Link one relevant case study in each outreach email, attach a tailored selection to proposals with the freelance proposal template, and use stronger proof to justify pricing above your floor, as covered in how to set freelance rates. For the wider system of lists, outreach, and follow-up, see finding clients without a big audience.
FAQ
How do I build a freelance portfolio with no clients?
Create two or three spec or self-initiated projects that solve a realistic problem for the kind of client you want, and present each one as a case study with the problem, your approach, and what you would measure. Label them honestly as self-initiated. Add volunteer or pro bono work for real organizations as soon as you can.
How many projects should a freelance portfolio include?
Three to six strong, relevant pieces are usually enough. Each one should match a service you sell to the clients you want. A few detailed case studies persuade better than a long gallery of thumbnails with no context.
Can I show work I did under an NDA?
Only with permission, or in a form the agreement allows. Read the NDA and your contract, then ask the client in writing whether you can show the work named, anonymized, or not at all. If the answer is no, describe your process with invented sample content instead of showing the real deliverable.
Do I need my own website for a portfolio?
Not at first. A platform profile or a simple PDF can get you started, but a site on your own domain gives you control, works well with cold email and proposals, and is not affected if a platform changes its rules. Many freelancers use both.
Should spec work be labeled in my portfolio?
Yes. Mark spec and self-initiated projects clearly, and never use a real company's name or logo in a way that suggests they hired you. Honest labeling protects your reputation and avoids misleading prospects.
Sources
Official sources referenced above (checked November 4, 2026)
Tools and templates
Freelance Proposal Template
A practical freelance proposal template with section prompts and follow-up email scripts so prospects move from call to clear yes/no decisions.
Open Freelance Proposal TemplateFirst 30 Days Freelancing Checklist
A week-by-week checklist for your first month freelancing: set up your offer, outreach, pricing, invoices, and scope documents without busywork.
Open First 30 Days Freelancing ChecklistClient Onboarding & Kickoff Checklist
A freelance client onboarding checklist: collect access and decisions, run the kickoff call, agree review windows, and send a written recap.
Open Client Onboarding & Kickoff ChecklistLoading comments…

Comments
Sign in to comment.