How to build a freelance writing portfolio that gets clients

A freelance writing portfolio shouldn’t feel like a junk drawer full of random links, dead pages, and pieces with zero context. Clients are busy. They don’t want to dig around trying to work out what you wrote, why you wrote it, or whether you can do it again.

Most portfolios stop at the finished piece. But clients also want to know whether you understood the brief, made smart choices, and can get the work over the line without becoming another problem to manage.

Basically, they want to know: can you make them money?

This guide shows you how to build three proof packets that show you can nail the brief, make smart calls, and help bring in the cash.

Think of your portfolio as a work test you set for yourself. Instead of waiting for a client to invent an unpaid assignment, you can create the brief, do the work, and package the evidence before you apply.

Set a deadline and an approval standard before you start. Give yourself the limits a real client might. Come up with a fixed word count, required sources, and one revision round. You might want to give yourself a due date, too. Unlimited time can make almost any sample look incredible. A realistic process shows what you can produce under the assignment constraints.

The U.S. Office of Personnel Management says strong work samples mirror the tasks and environment of the job. Apply the same logic to your freelance writing portfolio. Show the type of constraints and delivery process a client can expect after hiring you.

Three complete client simulations can say far more than 30 unexplained links. Each one gives the client evidence that you can understand a brief, make decisions, and hand over something usable. 

It also gives you a sensible response when a prospect asks for a lengthy custom test. You can point them to comparable proof or offer a small paid pilot.

Creating samples before studying the market is how writers end up with five finished blog posts and no proof they can do the work employers keep requesting. Start with the jobs, then work backward.

Save five to ten listings that resemble the work you want, even if you aren’t ready to apply. Look for patterns across the industry, deliverable, audience, tools, and supporting skills. One listing may be oddly specific. Seven listings asking for the same thing are giving you a clue.

Pay close attention to the portfolio request. Employers may ask for one to three relevant samples rather than a tour of everything you’ve ever written. Recruiters may want case studies, landing pages, UX flows, or technical documentation. Some care about WordPress, SEO, analytics, interviews, or experience working with designers.

Put those recurring requirements in one working document. You’re building a picture of the writer these clients expect to hire. Your portfolio can then show that person already exists.

Compare the job requirements with the evidence you currently have. Mark each one as strong, weak, or missing. Look beyond the writing format. A client may need something concrete showing niche knowledge, research, publishing tools, or results.

If your target jobs repeatedly request B2B SaaS case studies, but your portfolio contains general marketing blogs, then create a case study. Make the sample around a believable customer story, business problem, and measurable result.

Choose three simulated assignments that cover the most common gaps. You don’t need a new project for every line in every job post. One strong case study, for example, can show niche knowledge, interviewing, strategy, writing, and professional delivery.

Look at what causes a client to buy the service. A fintech company may need emails for onboarding, retention, or a product launch, and each piece of content calls for different proof.

Choose a niche and service combination rather than a category. “Healthcare writer” gives a client very little to grab onto. “Patient education writer” or “healthtech case study writer” makes the offer easier to understand.

Before throwing yourself at the best-paying writing niches, use your career, education, and hobbies to choose assignments you can handle credibly. A former teacher who geeks out on software could have a real shot at the education technology space. 

Spec work doesn’t have to look like homework. Every project needs enough business context for a client to understand what you were trying to accomplish and judge the choices you made.

Start with a fictional company, a realistic audience, and a specific business objective. Define the deliverable, tone, sources, desired action, and publishing platform. Then add constraints taken from the jobs you studied. These could be expert interviews, brand guidelines, SEO requirements, or CMS publishing.

A portfolio brief could include:

The brief stops you from decorating the sample with random portfolio bait. The keyword, CTA, and sources should earn their place by serving the assignment.

Keep the company fictional unless you have permission to create a public spec project around a real brand. Label the work as simulated or self-directed. Pretending Microsoft hired you won’t make the sample stronger. It will make the rest of the portfolio harder to trust.

Treat the research as paid work. Use credible sources, study competing content, and fact-check every meaningful claim. If the real assignment would require an expert interview, write the questions and try to find someone qualified to answer them.

Keep a short record of what shaped the piece. That might include the search intent you found, a pattern in customer reviews, or a claim you removed because it didn’t fit the target audience’s pain point.

You don’t have to write a dissertation. Clients only need enough evidence to see that the final draft didn’t appear through luck and caffeine. Two or three decision notes can reveal far more judgment than a long research dump.

Present the sample in the format a client would receive or publish. Put a blog in WordPress, break up emails into sequences, and give your UX copy design notes or a low-fi mockup.

If you're trying to get freelance writing jobs with no experience, package your samples in a way a client would expect to see them. If the handoff would begin in a document, make that document easy to review. Don’t pile on extras to make the packet look busier than it needs to be.

You’re trying to show that you understand where the writing goes and what the next person needs from you, not win an award for pretending to have a client.

Find your next writing opportunity with Get That Money.

A bare link makes the client do too much guessing. Package the assignment, finished work, key decisions, handoff, and results together so they can see what hiring you would look like.

Together, those pieces form your case file. Put everything on one project page or use a short overview linking to the supporting pieces. 

People should get it at a glance

Put the finished piece somewhere easy to access. A client who came to judge your writing shouldn’t have to crawl through six paragraphs of process notes before seeing it.

Give each project a clear title and a short introduction covering the format, audience, objective, and your exact contribution. “SEO article for a fictional accounting platform targeting small business owners” gives the reader more context than a random brand name. 

Let people view the work in a browser whenever possible. Downloads mean steps, which is work. And permissions have a habit of breaking at the worst moment. If a PDF or Google Doc is necessary, label it clearly and make it one click away.

Your portfolio may pass through a recruiter, content lead, founder, and subject expert before anyone offers you money. They’re all looking for different information. 

A recruiter may just want to confirm you're familiar with the industry, though whoever manages the work cares more about your process, judgment, and ability to follow a brief. A subject expert usually skips straight to the sources to see if you know what you're talking about.

Structure each project package in layers. Lead with a short summary that covers the assignment, your contribution, and the result. Put the finished work right after that. Everything else, like your research, decisions, and performance, can come last for whoever wants to dig deeper. 

Explain one or two choices that shaped the work. You might discuss how customer interviews changed the message, why you targeted a particular search intent, or how a brand guideline affected the tone.

Focus on choices with consequences. Nobody needs a diary entry about deciding between two subheadings for 45 minutes. Show the moments that reveal how you think, especially when you had to balance competing goals or work around a constraint.

Be clear about your contribution on real projects. If an SEO strategist chose the keyword and an editor rewrote the CTA, say so. Taking credit for an entire team’s work can make you look like a fool when someone asks a follow-up question.

Once the work is finished, hand it over cleanly. Keep related files together, separate the final copy from background notes, and use names a human can understand. 

Add short instructions for anything the client would need to do next. A handoff can show where an image belongs, which claims need legal approval, or how the emails fit into a sequence. You’re proving that delivering the work won’t create a fresh administrative crisis.

Most clients won’t send you a victory spreadsheet after the work goes live. If the revenue, traffic, or conversion data never arrives, work your way down the evidence ladder instead of filling the gap with numbers you found in your imagination.

Look at what the client did with the work. Did they approve it, publish it, pass it to the sales team, or turn it into an email campaign? A case study that still appears in sales calls six months later gives you something useful to say, even if nobody handed you the conversion rate.

Repeat assignments, referrals, quick approvals, positive feedback, and requests for similar work count too. Put the strongest evidence beside the sample and say exactly what happened. “The client commissioned three more articles” is useful. “Drove major growth” is fog wearing a blazer.

Keep the claim proportionate to your contribution. A landing page result may depend on the offer, traffic source, design, and existing brand recognition.

Simulated projects won’t have real results, so provide a measurement plan instead. Explain what you would track after publication and why. An SEO article might be measured through impressions, rankings, organic visits, product-page clicks, and conversions. 

Writing rarely happens alone. Clients may need someone who can research a technical subject, interview experts, publish in a CMS, understand analytics, and work with a team without turning every round of feedback into a personal reckoning.

Put those surrounding skills on the page. Don't make the client guess at them from a finished piece.

Match the supporting artifact to the assignment. An SEO sample could include a one-page search-intent map, and a case study might pair interview questions with a then-and-now result summary. UX copy tends to need something different: an annotated flow showing what the user sees at each step.

Tell the reviewer what the artifact demonstrates. A keyword map should explain the thinking behind the structure, not sit there looking impressively spreadsheet-shaped. One clear artifact is usually enough.

Use materials you really created during the project. Building a giant strategy deck after the copy is finished may make the packet look fuller, but it doesn’t prove the strategy guided the work.

If you can work in WordPress, Webflow, HubSpot, or another CMS, show it. A clean preview with the fields filled in and the formatting intact proves a lot more than another software logo sitting in a skills section.

Show the checks you make once the copy is inside the CMS too. Review headings, links, mobile formatting, alt text, metadata, tracking links, and basic accessibility. A short QA checklist shows that you know publishing involves more than hitting paste and hoping for the best.

Only claim tools you can use without someone talking you through every click. Clients may ask how you work in an interview, and “I watched half a tutorial once” won’t carry you very far.

If analytics are part of the role, show what you’d do with the numbers. A low click-through rate might send you back to the CTA, while weak search visibility could mean rethinking the topic or metadata. Explain what you’d change next instead of dropping a screenshot into the packet and leaving the client to play detective.

Use a project note to explain how you worked with an editor, designer, marketer, or subject matter expert. Mention a piece of feedback that improved the work or a recommendation you successfully defended.

A good example shows that you can respond to feedback without folding instantly or declaring war in the comments. Good collaborators know when to change the draft, when to ask a question, and when to explain the reason behind a choice.

Show a small draft-to-final example when feedback changed the work. Include the request, the revision, and one sentence explaining why the new version was stronger. If you pushed back, explain the business or reader reason without turning the project note into courtroom testimony.

Employers can't agree on AI, and pretending you already know their stance is a bad first move. Some want to see your prompt systems and repeatable workflows laid out like a receipt. Others want AI nowhere near the draft. Guess wrong, and you've either shelved your best process or handed a client exactly what they said no to.

Check the job post and company site before you decide how to talk about your process, or which samples to send. Match their stated rules, and be straight about how each piece got made. "They'll never know" is a bet you'll eventually lose, not a process.

Take two real postings. Branch AI wants writers who can show off prompt systems, custom GPTs, and brand-voice workflows as part of the application.

Perfect Search Media wants the opposite. They want zero AI content generation, full stop, and professional samples only. Send Branch's favorite trick to Perfect Search, and you've disqualified yourself before anyone reads a word.

If AI touched the piece, show your fingerprints on top of it. Walk through the prompts, the guardrails, the source material, and the checks you ran after. A quick before-and-after (the raw output next to your edit) says more than any paragraph explaining your process ever could.

Own the split plainly. If the tool wrote the first pass, say so, then show the fact-checking, restructuring, and judgment calls that turned it into something you'd put your name on. A client needs proof you were driving, not just proof you know how to press a button.

Keep a fully human sample in your back pocket too, for the clients who don't want AI anywhere near the process. Being upfront about it is a much easier conversation than explaining it after someone's already asking questions.

Thirty generic articles built from the same prompt don't show range. They show you can copy and paste.

Pick one workflow that fixes a real, recurring headache, like turning interview transcripts into source-tagged outlines, or running every draft against a brand system before it goes anywhere. Show the inputs, the rules, and one output. Let the client watch the system work instead of taking your word for it.

Then add a scorecard that moves on a scale. Show what's good enough for a client paying bargain rates for mostly AI-generated copy, and what you'd edit for a big spender. 

Want ↓ better writing jobs in your inbox?

Experienced writers can have surprisingly thin public portfolios because their best work is ghostwritten, covered by an NDA, or tucked away inside a client account. Annoying for your portfolio, yes. Annoyance is not permission to publish it and hope nobody notices.

Ask before you share anything. Check your contract and confidentiality terms. Then get written permission spelling out what you can show, where you can show it, and whether access needs to stay restricted.

If the client approves, use a password-protected page, secure link, anonymized excerpt, or general project description. Strip out names, figures, strategy, and anything else the agreement says should stay private.

Can't share the work? Build proof instead. Create a simulated project that shows the same skill without touching anything confidential, and back it up with an approved testimonial or an anonymized project summary.

Reedsy’s writing portfolio examples show several ways ghostwriters can present credible experience without blowing up client confidentiality.

Protecting private work is part of looking professional. A prospect won’t be impressed by a confidential document if their first thought is, “Cool, would you break my NDA?”

A freelance writing portfolio doesn’t need an elaborate logo, custom color palette, or three-day argument about serif fonts. A simple portfolio that loads quickly and makes sense can beat an expensive website that smothers the work under decorative fog.

Beginners can use a Notion portfolio template, Clippings.me, Journo Portfolio, Authory, or even a basic WordPress site. Choose based on the sample formats you need, privacy options, backups, mobile usability, and ease of updating.

A custom domain can add shine, but it shouldn't delay the proof packets. Nobody has ever rejected a perfect-fit case study because the writer hadn’t spent six weeks choosing a brand shade called “confident terracotta.”

Google Drive or PDFs can work as a temporary setup. Keep the folder clean and make the final version obvious. A client shouldn’t have to decode a filename or sort through six drafts to find the piece you meant to send.

Give the homepage a clear scan path. Lead with what you write, then who you write it for, your strongest proof, and how to contact you. A first-time visitor should understand the offer before deciding which project to open.

Add categories or filters once your portfolio spans a few industries or services. Keep the list tight enough to help. A dropdown containing 19 content types is a filing system, not positioning.

Pull up the whole portfolio on your phone. Check the text size, the navigation, the links, the downloads, all of it. Plenty of clients will open your application between meetings, and they won't save a broken page for later out of respect for your potential.

Once someone likes what they see, hand them one clear way to reach you and tell them exactly what to send. Nobody needs a 14-question form before they're allowed to discuss an article.

Published work can disappear. Companies close, publications redesign their sites, staff remove author pages, and old URLs wander off without leaving a forwarding address.

Save a PDF or a screenshot the moment a piece goes live, assuming you've got permission to keep one. Journo Portfolio does that automatically, backups and password-protected private pages included. The Verge's guide covers the rest of your archiving options, for when you want a backup for your backup.

Check your links on a schedule. Nobody wants a client finding your 404 before you do. Swap in your backups and cut anything embarrassing. A dead link tells them you haven't looked at your own portfolio since spring.

Your full portfolio and the samples you send aren't the same thing. A portfolio is your life's work, and the samples are what get you a job. You want to keep the whole collection for yourself and create a shortlist for each role.

Keep a private library of everything you're proud of. Include your strongest samples, case files, testimonials, and performance notes. Organize your work by industry, deliverable, or service. Future you does not want to dig through six folders all named "Copy (3) FINAL" while a client waits on Slack.

There’s no reason to trash older work if it's excellent writing. A big client name won't save a weak sample forever, no matter how much you want it to.

Update the collection as your services change. Swap early simulations for real paid work the second you're allowed to show it off, and keep the public portfolio lean even as your private stash keeps growing behind the scenes.

Send one to three work sample bundles that most closely match the client's assignment, leading with your strongest match. You can add one sentence explaining why each project is relevant. Your samples don’t need to be the newest piece or the client with the fanciest logo.

Always send a direct link to a relevant project so they aren’t hunting for your work. Make the review painless so the right work doesn’t get buried.

If you don’t have an exact match, choose the closest proof in this order: 

Explain the overlap honestly. A relevant adjacent sample is stronger than pretending an unrelated piece is perfect.

You don’t need to wait for a client to hand you the perfect sample. Pick the work you want, create a realistic brief, and build proof around it.

Three strong work samples can show clients how you think, what you can deliver, and whether your work can help them make money.

Then don’t waste your shiny new portfolio on bullshit job postings. Spend time on the jobs that will value your hard work. Get That Money filters through the mess and finds writing jobs with real budgets attached.

Subscribe to our newsletter, pick a role worth chasing, and put your new proof packets to work. Then go get that money.

A freelance writing portfolio should include a small selection of relevant samples, a short brief for each project, your exact contribution, key decisions, and results or a measurement plan. Add supporting evidence only when it makes your role or the outcome easier to understand.

Three strong samples can be enough when they closely match the work you want. Keep a larger private collection, but send each client only the one to three projects most relevant to the assignment. Relevance will usually help more than volume.

Study real job posts, identify the work employers request, and create three simulated client assignments that fill your biggest proof gaps. Build each one around a realistic brief, complete the supporting work, and label it honestly as a spec or self-directed sample.

No. A clean Notion page, portfolio platform, or organized set of browser-friendly samples can work. A personal website becomes more useful when you want a custom domain, service pages, search traffic, or inbound leads, but it shouldn’t delay pitching.

Only when your agreement allows it and the client gives permission. You may be able to share an excerpt privately, anonymize the project, or describe your contribution without revealing protected information. If the work must remain confidential, create a new simulated sample that demonstrates the same skill.

Ready to spend less time searching and more time writing?

Get That Money brings together freelance writing, copywriting, content, SEO and marketing opportunities worth checking out.