If you're a VA and you want to move into higher-ticket tech consulting but don't know where to start - this is exactly what to do, and how to get Claude to do most of it for you.

Because the thing I hear constantly is:

"I want to become a consultant, but I don't have consulting experience."

And sometimes that's genuinely true. But very often you do have the evidence that you can operate at a higher level. You just haven't learned to recognise it, so it's never made it onto your website, into a proposal, or out of your mouth on a sales call.

That's not a confidence problem. That's an evidence problem. And an evidence problem is much easier to fix.

What you're actually looking for

Go back through the clients you've worked with, and stop looking at the list of tasks you completed. Ask five different questions instead:

1. What decisions was I trusted to make?
2. What systems or processes did I improve?
3. What problems did I spot before the client realised there was a problem?
4. What did I recommend that they actually implemented?
5. What did I end up taking ownership of, because they trusted my judgement?

Because there's an enormous difference between these two sentences, and they can describe the same afternoon:

The first is execution. The second shows diagnosis, recommendation, ownership and problem solving - and that is what you build consultant positioning on.

The honest bit

This does not mean every task you've ever done as a VA is secretly consulting.

Some of your experience is genuinely just execution, and that's completely fine. The goal here isn't to relabel task work as strategy - if you do that, you'll get found out on the first call with someone who knows the difference.

And the exercise is just as useful for what it doesn't find, because that shows you the gaps:

• Maybe you're brilliant at implementing, but you've never been the person making the recommendation.
• Maybe you understand the systems but not the commercial side of the business.
• Maybe clients already lean on your judgement constantly and you've simply never thought to position or price yourself that way.

Those gaps are the actual plan for what to develop next.

---

The process

Two steps. Step one builds the evidence. Step two translates it.

Step 0 - Somewhere for it to live

Before anything, make a folder called Consulting Experience.

If you've got an AI brain set up, put it inside your workspace folder - mine lives in Samantha's Workroom. If you haven't, just make a folder on your desktop. Either is fine for now.

Everything you're about to produce goes in there, and by the end of step one you'll have one document per client.

Step 1 - One summary per client

This depends on whether you've already got your AI brain running. Both routes get you to the same place.

Path A - you have a vault, or a project per client

You've already done the hard part. Open a chat inside that client's project (or point Claude at their folder in your vault) and run this. Do it once per client, current and past.

You've got the full history for [CLIENT] in this project.

Write me a detailed summary of my work with them & save it as an md document.

Cover:
- what I actually do for them, task by task, including the small things
- what I've changed or improved since I started
- decisions I've been trusted to make without checking first
- problems I spotted before they did
- anything I recommended that they went ahead with
- anything I've ended up owning outright
- results & outcomes I can point to, with numbers where we have them
- what's gone well, & what hasn't

Then, separately: what do you notice about how this client treats me? Am I being
asked, or am I being told?

Be specific & factual. Don't flatter it - I'm going to use this as evidence &
it needs to be true.

"Am I being asked, or am I being told?" is the sharpest question in this whole post. It's the difference between an assistant and an adviser, and the answer is sitting in your email history whether you've noticed it or not.

Path B - you haven't got that set up yet

No problem, it just means you supply the raw material instead. Open a new chat and do one client at a time.

I'm auditing my client work to find the consultant-level experience hiding in it.

Here's a brain dump about [CLIENT]: [talk for as long as it takes. What you do
for them, how it started, what's changed since, what you've fixed, what you've
suggested, what you've quietly taken over, what's gone well & what hasn't. Don't
tidy it]

I've also attached [my proposal / our agreement / the original scope] so you can
see what I was actually hired to do.

Write me a detailed summary covering:
- what I was hired to do, versus what I actually do now
- decisions I've been trusted to make
- problems I spotted before they did
- anything I recommended that they implemented
- anything I've ended up owning
- results & outcomes, with numbers where I've given you them
- what's gone well, & what hasn't

Then tell me: what does the gap between what I was hired for & what I actually
do now say about how this client sees me?

Be specific & factual. Don't flatter it - this is evidence & it needs to be true.

That gap is usually the whole story. Almost nobody is still doing only what their original contract said. The distance between the two is scope creep - and scope creep upward, into judgement and decisions, is exactly the evidence you're hunting for.

Attaching the proposal or agreement matters, because it's the only fixed record of where you started.

Do this for every client, current and past. Then drop all of the summaries into your Consulting Experience folder.

Step 2 - Translate it

Now a fresh chat, with all of those documents available to it.

• Claude Projects person? Do this in your War Room chat and drop the documents into the project.
• Cowork person? Point it at the folder in your vault.
• Neither? Drag all the files into a new chat.

In this folder are summaries of my work with every client I've had.

Go through all of them & build me an evidence report.

PART 1 - THE CONSULTANT-LEVEL WORK
Pull out every instance, across all clients, where I was:
- trusted to make a decision rather than told what to do
- diagnosing a problem rather than executing a fix
- recommending something that then got implemented
- improving a system or a process, not just running it
- owning an area outright

Quote the actual example each time & name the client it came from. I want
specifics I could say out loud on a sales call, not categories.

PART 2 - WHAT'S JUST EXECUTION
Be honest with me. Which parts of my work are genuinely execution rather than
consulting? Do not relabel task work as strategy to make me feel better - I need
to know the difference.

PART 3 - THE PATTERN
Looking across all of it: what kind of problem do I keep being the person who
solves? Where do I create the most value?

PART 4 - MY GAPS
Where am I weak? Am I brilliant at implementing but never the one recommending?
Do I know the systems but not the commercial side? Do clients already lean on my
judgement in a way I've never priced for?

PART 5 - TRANSLATE IT
Take the strongest evidence & show me how to say it as consulting instead of as
VA work. For each one, give me:
- the VA version - how I'd have described it before
- the consulting version - problem, what I did, outcome

Then give me 3-4 consulting pillars I could build my positioning on, each with
the real evidence from my own client work underneath it.

Don't invent anything. Every single thing in this report has to be traceable to
something in those files.

"Don't invent anything." Put that in and leave it in. This report is going to become things you say to prospects, and you cannot afford one impressive-sounding line you can't back up when someone asks a follow-up question.

What you should end up with

Three things:

A list of the consultant-level work you've already done, with real examples attached to real clients. That's your evidence bank, and it's what you draw on for proposals, sales calls, your website and your LinkedIn.

An honest picture of what's still execution. Useful, not depressing. It tells you what to stop leading with.

Three or four consulting pillars - the problems you solve, with proof underneath each one.

And that changes what your next offer looks like. Instead of building it around "here are the 17 tasks I can do for you", you build it around "here's the problem I can help you solve, and the outcome I can help you create."

What to do about the gaps

Don't skip Part 4.

If it tells you you've never been the one making the recommendation, that's your next ninety days - start making recommendations to the clients you've already got. If it says you don't know the commercial side, that's what to go and learn.

The gaps aren't a verdict on whether you're ready. They're a to-do list.

Start with one client

Don't try to do all of them tonight. Pick the client you've worked with longest - they'll have the richest history and the biggest gap between what you were hired for and what you actually do now.

Run the summary. Read it. I'd be surprised if there isn't at least one thing in there you'd forgotten you did, and would never have thought to mention.

You probably don't need to start from scratch to become a consultant. You need to learn to recognise the consulting experience you already have.

If you haven't got your AI brain set up yet, path A is much better than path B and it's a twenty minute job: start here.

And once you know what you're actually good at, working out what to call it is the next question - which is this one: The Claude Prompt I Used to Find My Niche.

Watch the free training →