Virtual Assistant Portfolio Examples: Three Case Studies You Can Model (and a One-Page Layout) | Virtueasy
Getting Started

Virtual Assistant Portfolio Examples: Three Case Studies You Can Model (and a One-Page Layout)

· Virtueasy · Portfolio & Proof · 7 min read

Every guide tells you to put case studies in your portfolio. Almost none shows you what a finished one looks like. Here are three, written out in full, plus the one-page layout to put them in.

A VA portfolio is three short case studies and a way to contact you. That is the whole thing. The reason most new VAs never finish one is not a lack of work to show. It is that nobody has shown them what done looks like, so they keep polishing a Canva cover page instead of writing the three paragraphs that matter.

Below are three complete portfolio entries, each in the situation, what I did, what changed format. One is written as an anonymized client result. One is a mock project built on fictional data. One is spec work built from skills carried over from a previous job. Those three labels cover every situation a new VA is in. Copy the structure, swap in your own work, and you have a portfolio by tonight.

Two things before you read them. Each entry is written in the first person, the way it would read on your own page. And the businesses in them are made up to show the format, with numbers that are illustrative. Your entries will use your own.

What Every Entry Needs Before You Write It

Each example has the same five parts: a title that names the task and the kind of client, a one-line label saying what kind of proof it is, a situation paragraph, a what-I-did paragraph, and a what-changed paragraph. Keep each entry under 250 words. If you cannot write one of the three paragraphs, that is a sign to pick a different project, not to pad the one you have.

The labels come from how to show VA work you cannot share: anonymized result, mock project, spec work. Use them exactly as written. A prospect who knows what she is looking at trusts it.

Example 1: Inbox Management for a Two-Person Bookkeeping Firm

Label: anonymized result. Written as it would read for real client work with the identifying details removed.

Situation. A two-person bookkeeping firm was running all client communication through one shared Gmail inbox. Around 60 new messages a day, no labels, and no agreement about who answered what. Client questions sat for two or three days, and the owners spent the first hour of every morning sorting instead of doing billable work.

What I did. I spent the first week reading, not changing anything, and logged every message by type. Five categories covered about 90 percent of the volume: document requests, invoice questions, scheduling, new client enquiries and vendor notices. I built a label and filter set for those five, wrote a template reply for each one, and set a rule that anything I had not answered within four business hours gets flagged to whichever owner is on duty. Then I documented all of it in a one-page SOP so the system does not depend on me being online.

What changed. Client reply time went from two or three days to the same business day. The owners stopped opening the inbox before 10 a.m. By week three I was handling it in about 45 minutes a day, down from the two hours the owners had been splitting between them.

Example 2: Social Media Scheduling for a Fictional Yoga Studio

Label: mock project. Built on made-up data for portfolio purposes.

Situation. For this sample I invented a single-location yoga studio with 30 classes a week, an Instagram account posting two or three times a month with no pattern, and an owner who wanted a consistent presence without doing it herself. Everything in this entry is a demonstration, including the studio.

What I did. I built a four-week content calendar in a spreadsheet: three posts a week, each tied to a purpose (a class spotlight, a student question answered, a schedule reminder). I wrote the 12 captions, picked a free scheduling tool, loaded the first two weeks, and wrote a half-page handover note explaining how the owner reviews the queue in ten minutes on a Friday. The calendar, the captions and the handover note are the deliverables, and all three are linked from this entry.

What changed. Nothing yet, because the studio is not real, and I am not going to invent a result. What the sample shows is the system: a cadence that holds without the owner thinking about it, captions in one consistent voice, and a review step that takes minutes. That is the thing a studio owner would be paying for.

That last paragraph is the honest way to end a mock project. Do not write a fake outcome. Describe what the system does and let the prospect judge the work.

Example 3: Customer Escalations, Rewritten as VA Experience

Label: spec work from a previous role. No VA client involved.

Situation. Before going freelance I spent three years on a customer service team at a regional internet provider, handling escalated complaints: the calls where the customer had already been passed around twice. Around 25 escalations a week, most of them angry on arrival, each needing a resolution within 48 hours.

What I did. I kept a personal tracker of every escalation and what resolved it. After two months I could see that about half came from the same three billing problems, so I wrote a plain-language reply for each, got the team lead to approve them, and shared them with the floor. I also started sending a short follow-up message 48 hours after each resolution, which nobody on the team had been doing.

What changed. My own resolution time dropped from about three days to a day and a half. Repeat contacts on my cases roughly halved. The three replies were still in use when I left. For a VA client this is the same skill as customer support or inbox management: find the pattern, write the response once, and stop solving the same problem from scratch.

If your experience is from a job rather than a client, this is the format. Write it like a case study, say plainly where it came from, and finish with the sentence that connects it to the work you want now.

The One-Page Layout

Now the page to put them on. Top to bottom:

  1. One line about you. Your name, the type of work, the kind of client. "Inbox and calendar management for small service businesses." No paragraph about your journey.
  2. Services, as three to five short lines. Not a menu with prices. Prices belong in the proposal, and the free Pricing Tool will work them out when you get there.
  3. The three entries, each with its label, each under 250 words. Link a redacted screenshot or the actual deliverable wherever you have one.
  4. One or two quotes from anyone you have worked with, with the context stated honestly. If you have none yet, here is how to ask.
  5. How to reach you. An email address and nothing else. No form that goes to a folder you forget to check.

A Google Doc with view access, a Notion page or a one-page Carrd site all work. The test is whether the link opens on a phone and the first entry is readable without scrolling past a hero image.

What to Do If You Only Have One

Publish it. One finished entry on a page you can link is a portfolio. Two of the three examples above did not come from VA clients at all, which is the point: most new VAs have more to show than they think once the format is clear. Write the one you have today, add the second when you finish the next project, and send the link the next time a prospect asks.

For the full walkthrough of turning a project into a case study, this guide goes deeper on each paragraph. If you do not have a client yet, start here.

Ready to build your VA business?

The VA Starter Kit

Step-by-step guidance for landing your first high-ticket client. No experience required.

Get the VA Starter Kit
Free. No spam.

Get the next guide in your inbox

New guides for virtual assistants, current job leads, and the free tools as they go live. One click to unsubscribe.

No spam. Unsubscribe anytime. A Virtueasy product.