You have one client, an NDA, and a Canva file you made for yourself. That does not feel like a portfolio. So you mumble something about being new and the conversation quietly dies.
Here is what is actually true: a portfolio is not a gallery of pretty deliverables. It is proof that you understand a problem and know how to solve it. That reframe changes everything, because you do not need twenty clients to demonstrate that. You need one good piece of documentation and the discipline to write it down properly.
This post is for the VA who has a little work behind her and no idea how to show it. Let us fix that.
What a Portfolio Actually Needs to Do
Before you build anything, get clear on the job. A prospect looking at your portfolio is asking one question: "Can this person handle my specific mess?" They are not judging your color palette or your logo. They want evidence that you have encountered a real situation, done something deliberate, and produced a result that mattered.
That means your portfolio needs three things: context, action, and outcome. Not just screenshots. Not just a list of tasks you completed. Context, action, outcome. Keep that in mind for everything that follows.
Turn One Client Project Into a Real Case Study
If you have done any paid or volunteer work, you have the raw material for at least one case study. The format is simple: three paragraphs, written in plain language, with no jargon.
Paragraph one, the situation. Describe what the client was dealing with before you got involved. Be specific about the problem, not the person. "A small e-commerce brand was spending six hours a week manually tracking customer inquiries across three inboxes with no system in place" is far more useful than "my client was disorganized."
Paragraph two, what you did. Walk through your actual approach. Not a task list, a decision-making sequence. "I audited the three inboxes, identified the five most common query types, built a tagging system in Gmail, and wrote template responses for each category." That shows process, not just output.
Paragraph three, what changed. This is where numbers help if you have them, but they are not required. "Response time dropped from two days to four hours. The client spent forty minutes on inbox management by week two, down from six hours." If you do not have metrics, describe the qualitative shift. "She told me the following week she had not thought about email once."
That is a case study. It fits on one page. It answers the prospect's question before she even asks it.
Related: How to write a VA proposal that converts
When an NDA Means You Cannot Show the Actual Work
This is more common than you think and less fatal than it feels. An NDA restricts what you share, not what you describe. You can write a case study without naming the client, showing the actual document, or revealing any proprietary detail. Say "a confidential client in the wellness space" and focus entirely on the problem and your process.
What you cannot do is fabricate outcomes or imply permission you do not have. If the NDA is tight and you are unsure, describe the situation in genuinely generic terms and let the quality of your thinking carry the case study. A clear, honest account of your process is worth more than a blurry screenshot someone will not trust anyway.
Spec Work Is Legitimate When You Label It Clearly
If you do not have client work yet, you can create sample work specifically to demonstrate a skill. This is called spec work and it is a normal, accepted practice. The single rule: label it honestly. "Created as a sample to demonstrate inbox management process" or "spec project for portfolio purposes" tells the reader exactly what they are looking at and keeps your credibility intact.
Good spec work mirrors a real scenario. Pick a problem type you want to attract clients for, for example, social media scheduling for a small service business, and build out the actual process you would use. Document it the way you would for a paying client. That documentation becomes a portfolio piece.
This is also where transferable skills from previous work have real value. If you spent three years in customer service handling escalations, that is a process skill. Write it up the same way you would write a case study. The situation, what you did, what changed.
Social Proof When You Do Not Have Formal Testimonials
Testimonials from happy clients are the easiest social proof to collect and the most overlooked. If you have done any work for anyone, ask. One sentence from a real person who worked with you is worth more than three paragraphs you wrote about yourself.
If your only experience so far has been helping a friend, a volunteer organization, or a family business, ask those people too. Be transparent about the context. "I helped a local non-profit reorganize their volunteer communications over two weeks" with a quote from the coordinator is legitimate social proof.
What you should not do is write fictional testimonials or imply client relationships that did not exist. Prospects can sense that. Honest and sparse is better than polished and questionable.
Related: How to find your first VA client without a portfolio or a following
Where Your Portfolio Should Actually Live
Not in a Canva carousel buried in your Instagram highlights. That is where portfolios go to be ignored.
A simple one-page website or a clean PDF is enough. The page or document should have your name, the type of work you do, one to three case studies or samples (clearly labeled), a short line about your background if it is relevant, and a way to contact you. That is the whole thing.
If you want a free option, a Google Doc shared via link works. A Notion page works. A basic Carrd site costs almost nothing. The point is that the link opens, loads quickly, and does not make the prospect do any work to understand what you offer.
Your portfolio does not need to be impressive. It needs to be findable, legible, and honest.
A Realistic Next Step
Pick one piece of work you have done, paid or not, real client or not, and write the three paragraphs. Situation, what you did, what changed. Keep each paragraph under one hundred words. Do not edit for perfection on the first pass, just get the information down.
Then put it somewhere with a link. One case study on a Google Doc is a portfolio. It is more than most new VAs have and it gives you something to point to the next time a prospect asks.
Build from there. One more project, one more case study. The portfolio grows while you work, not before you start.