I became the project manager of my own marketing once. A writer, a designer, a VA, and me in the middle forwarding things.
It looked like a team. It felt like progress. What it actually was: 3 people each holding a piece of my standard in their head, and none of it written down anywhere I could point at.
So when a coach tells me "we're already using AI, my VA runs everything through ChatGPT," I know exactly what they have. They have a person with a login. That's not nothing. It's also not an AI system, and the difference shows up on the worst possible day.
TLDR
- A VA with ChatGPT is a person applying their own judgment to a blank prompt. The judgment leaves when they leave.
- Managing a writer, a designer, and a VA is renting output. It is not owning production.
- The test a coach I work with now sets copywriters starts with a machine draft. That tells you where the job moved.
- What your VA needs is not a better prompt. It's a reference library and a gate, and both should be yours.
- The uncomfortable part: if your VA leaves tomorrow, what do you actually keep?
What You Actually Have When Your VA Opens ChatGPT
Let me describe the setup plainly, because it's the same in almost every coaching and consulting business I look at.
The VA has a folder of prompts, some of which they wrote and some of which they found. They paste in a transcript or a topic. They read the output, fix the bits that sound wrong to them, and send it to you. You fix the bits that sound wrong to you. It goes out.
Where is your standard in that chain? It's in 2 places. In the VA's head, as a feel for what you'd reject. And in yours, as the final edit. Neither is written down. Neither is checked automatically. And the AI in the middle has nothing of yours to work from, which is why the VA has to fix so much. I've written about what an AI content system actually is, and the short version is that the layer between the tool and the output is the whole thing. In this setup that layer is a human being who might quit in March.
Renting Output vs Owning a System
Here's the frame I use now, and I use it on myself first.
When I was managing a writer, a designer, and a VA, I was renting output. Every week, money went out and assets came back. Fine. But nothing accumulated. The writer's sense of my voice was the writer's. The designer's sense of my layouts was the designer's. If any of them left, the next person started from zero, and I started from zero with them.
Owning a system means the standard lives outside any one person's head. A reference library of approved and rejected work. A verification loop that checks every draft against it. A gate that passes or fails before I look. When a person leaves, the system stays. When a new person joins, they inherit it in an afternoon.
That's the Standard Stack, and the reason I insist clients own every piece of it is that I've been on the other side. Renting felt cheaper right up until I counted what I'd lost every time someone moved on.
The Copywriter Test That Starts With a Machine Draft
Here's something that happened this month that made the point sharper than I could.
A coach I work with is hiring copywriters. His plan for the test: I run the skill to produce the brand documents for new clients, do a light pass for readability and factual errors, and then he sends those drafts to the candidates. Their test is to finish and polish what the skill wrote.
Read that again. The brief for the writing role is not "write the blueprint" anymore. It's "finish the blueprint." The system produces the first 80%. The human's job is the last 20%, and the human is being evaluated on exactly that.
Now think about your VA with ChatGPT. They're doing the first 80% and the last 20% with no system behind either. That's not a knock on VAs. Mine were good. It's that they're being asked to be the system, and a person cannot be a system. A person is what a system is for.
What to Give Your VA Instead of a Login
Practically, for coaches and consultants who already have a VA and don't want to blow anything up:
- A reference library they didn't build. 10 to 20 pieces across the 3 Sources, with 1 line on each saying why it's in there. Yours, not theirs. This is the single biggest upgrade and it takes an afternoon.
- Your rejections, written down. Every time you send something back, the reason goes in a file. Not a message to the VA. A file the AI reads before the next draft. That's the rule, not ticket idea, and it's what makes the second month better than the first.
- 3 questions every draft gets read through. Would I say this on a call? Have I actually seen this with a client? Would my best client recognize me here? The VA runs the questions. The VA does not invent them.
- A gate you audit. Instead of editing every draft, you spot-check the gate once a week. If the gate is letting bad work through, fix the gate. If it isn't, stop editing.
Do those 4 things and your VA goes from being the system to running the system. Same person. Different job. And now the job survives them.
The Uncomfortable Version of This
Ask yourself one question. If your VA gave notice tomorrow, what would you keep?
If the answer is a folder of prompts and a Notion board, you were renting. The prompts without the judgment are templates, and I've written about why templates fail at the edges. The judgment walked out the door.
If the answer is a reference library, a rules file, a set of verification questions, and 6 months of approved work with the comments still on it, you own production. The next person picks it up and the output barely wobbles. I've watched it happen. The wobble was 1 week.
I'm not telling you to fire anyone. I'm telling you that "my VA uses ChatGPT" is a sentence about a person, and the thing you want is a sentence about a system.
Look, you already know the current setup depends on 1 person's memory of what you like. You've known that for a while. The part you're stuck on is what the alternative looks like without a 3-month build.
That's the conversation I have with every client before we build anything. Or skip the conversation: send me 1 piece of your work and you get a finished asset back in your voice within 48 hours, produced by a system you'd own, not a person you'd rent.
FAQs about VAs and AI systems
Is a VA using ChatGPT the same as having an AI system?
No. A VA with ChatGPT is a person applying their own judgment to a blank prompt. An AI system holds your standard in a reference library, checks every draft against it automatically, and passes or fails work before a human sees it. The first depends on the person staying. The second survives them.
Should I replace my VA with an AI system?
Usually not. Give the VA a system to run instead of asking them to be one. A reference library of your work, a file of your written rejections, fixed verification questions, and a gate you audit weekly. The same person becomes far more consistent, and the standard stops living only in their head.
What do I lose when a VA who used AI leaves?
Everything that was never written down: their feel for your voice, the reasons behind past rejections, and the fixes they made by hand every week. A folder of prompts stays behind, but prompts without judgment are templates. The judgment is what leaves.
What is the difference between renting output and owning production?
Renting means paying for assets that arrive weekly with nothing accumulating. Owning means the standard, the rules, and the checks exist as files you control, so quality compounds and does not reset when a person changes. The Ownership Clause exists because I have been on the renting side and counted the cost.