GoHighLevel Virtual Assistant or Developer: Which Do You Need?

A GoHighLevel virtual assistant runs an account that already works: the inbox, the pipeline, the appointment confirmations, the review replies, the small edits. A GoHighLevel developer makes the account work in the first place: the sub-account, the phone and texting setup, the pipeline, the pages and the workflows that follow up on their own. Most businesses that ask for one actually need the other first, and the ones that run smoothly have both, in that order.

I am the developer in that pair. I build the system, hand it over with a walkthrough, and the owner or a VA runs it from then on, with a care plan for the fixes. This guide is the conversation I have with every client who asks whether to hire a VA, and the prices in it come from the VA agencies’ own pricing pages and from my pricing page as they read on 3 November 2026.

Key takeaways

• A VA operates; a developer builds. If the account has no working pipeline, phone, A2P registration or workflows yet, a VA has nothing to operate.
• VA staffing runs from about $8.50 an hour at the cheapest agencies to $399 or $449 a month for a 20 to 40 hour block. A developer charges per job: my sub-account setup starts at $497, an automation install at $397, custom code at $297, and fixes run at $50 an hour.
• The order that works: developer builds and documents, VA runs from the documentation, developer stays on a care plan or an hourly line for anything that breaks.
• Five signs you need a developer: texts not sending, duplicate or missing follow-ups, a pipeline that does not match how you sell, an integration that silently fails, an agency snapshot that has never been tested.
• Five signs you need a VA: leads waiting in the inbox, appointments not confirmed, reviews not answered, pipeline stages out of date, posts and campaigns not going out.

What a GoHighLevel virtual assistant does

A GoHighLevel VA works inside an account every day. The job list on most VA agency pages is the same: answer and route conversations in the unified inbox, confirm and reschedule appointments, move contacts between pipeline stages and add notes, send review requests and reply to reviews, schedule social posts, build simple email campaigns from a template, update custom values and calendars when hours change, and report the week’s numbers. Good VAs also make small workflow edits, such as changing the wording of a reminder or adding a tag, and they notice when a workflow stops firing, which is worth more than it sounds.

What a VA does not do, and should not be asked to do, is design the system: decide the pipeline stages, configure the phone system and A2P 10DLC registration, set up the email sending domain, build the funnel pages, write the workflow logic with its waits and conditions, or connect Stripe and the third-party tools. Those are one-time build decisions with consequences that last for years, and a VA billed by the hour to figure them out is the most expensive way to get them wrong.

What a GoHighLevel developer does

A developer builds the account once and leaves it documented. In my sub-account setup that means the pipeline shaped around how the business actually sells, custom fields and tags, calendars with confirmations and reminders, the phone number with A2P registration filed on day one, the email sending domain, a booking or quote page in the builder, and the four workflows every local business needs: instant lead reply, missed-call text-back, appointment reminders and review requests. It ends with a Loom walkthrough, a written workflow list and 30 days of fixes.

Developers also do the work a VA cannot: custom code on pages, API and webhook integrations, snapshots and SaaS mode for agencies, and migrations from ClickFunnels or another platform. The GoHighLevel developer page covers that side. The test of a good developer is simple: after the handover, a VA or the owner can run the account without calling the developer every week.

What each one costs

Two things the table hides. A VA at $8.50 an hour who spends a month learning HighLevel on your account costs more than the $497 setup, with a worse result. And a developer who charges $497 to build but is not available afterwards leaves you paying the VA to guess, which is why the handover documentation and the 30 days of fixes matter as much as the build.

The order that works

Build first, then run, then maintain. The developer sets the account up and records the walkthrough. The VA, or the owner for the first few months, runs the account from that recording and the workflow list. The developer stays reachable on an hourly line or a care plan for the things that break: a workflow that stopped firing after a HighLevel update, a new integration, a second location. In the accounts I support, the VA sends me a Loom of the problem, I fix it in an hour or two, and the VA goes back to the inbox.

Agencies run the same model at scale: I build the snapshot and the per-client checklist, their VAs load it and run each client account, and I take the custom work and the rescues. The white-label page describes that arrangement.

Five signs you need a developer, not a VA

1. Texts are not sending, or they send but nobody receives them. That is A2P 10DLC registration, a sending-number problem or a workflow fault, and none of them is an inbox task.
2. Leads get two welcome messages, or none. Duplicate triggers and half-built workflows need to be merged by someone who understands the logic.
3. The pipeline stages do not match how you sell, so the dashboard numbers mean nothing. Rebuilding stages and moving contacts safely is build work.
4. An integration fails silently: Stripe, a calendar, Zapier, a lead form. Finding the broken step is debugging, not administration.
5. You bought a snapshot or inherited an agency account and nothing has been tested with a real lead. Testing and fixing a whole account is a developer’s job and usually takes less time than the VA has already spent on it.

Five signs you need a VA, not a developer

1. Leads sit in the conversations inbox for hours because nobody owns it.
2. Appointments are booked but not confirmed, and no-shows are climbing.
3. Reviews arrive and go unanswered; review requests only go out when someone remembers.
4. The pipeline is right but stale, because nobody moves cards or adds notes.
5. Campaigns, posts and newsletters are planned and never sent.

If the system works and the gap is daily attention, a VA is the right hire and a developer is a waste of money. If the system does not work, hire the developer first and give the VA a working account.

How to brief each one

Brief a developer with how a lead becomes a customer today: who answers the phone, how quotes go out, what counts as won, and the tools already in use. That becomes the pipeline and the workflows. Brief a VA with the workflow list and the walkthrough the developer left, the response times you expect, the tone for replies, and the one number you want reported each week.

The red flags are the same for both. A VA agency that promises to "set up your whole account" for an hourly rate with no scope. A developer who will not show live accounts or verifiable reviews. Anyone who wants your HighLevel login instead of a user seat of their own. And anyone who cannot explain A2P 10DLC in two sentences.

What I do, and what I do not

I build and I fix. I do not provide VA staffing, and I say so when a client needs one. My care plan at $149 a month covers updates, backups, security and two hours of edits, which is enough for a business whose owner runs the inbox; a business with hundreds of conversations a week needs a VA as well. Every build I hand over is documented for exactly that person, whoever they turn out to be.

Frequently asked questions

Can a GoHighLevel VA set up the account from scratch?

Some can, but you are paying an hourly rate for build decisions that a developer makes once and documents. The cheapest route that works is a fixed-price setup, then a VA to run it. If a VA agency offers setup, ask for the written scope, the workflow list and the A2P registration as deliverables, and ask to see an account they finished.

Can a developer run my account every month instead of a VA?

A developer on a care plan handles updates, checks and a couple of hours of edits a month. Daily inbox work, appointment confirmations and review replies need hours every day, which is VA work at VA prices. Paying developer rates for inbox work is the most common way these accounts get expensive.

How many hours a week does a GoHighLevel VA need?

For a single-location service business with working automations, most of the daily work fits in one to two hours a day, which is why 20-hour-a-month blocks exist. Agencies managing several client accounts need a full-time VA per ten to fifteen accounts, depending on how much conversation volume each one has.

Where do you find a GoHighLevel VA?

VA agencies that specialise in HighLevel list hourly and monthly prices on their sites, the HighLevel community and Facebook groups carry referrals, and Upwork has individual VAs with HighLevel in their profile. Whoever you choose, give them a user seat in your account, not your login, and start them on the walkthrough your developer recorded.

Should the VA or the developer be HighLevel certified?

Certification shows someone passed HighLevel’s course and exam; it does not show they have built or run an account like yours. For a developer, ask for live accounts and reviews on the platform they were earned on. For a VA, ask for a reference from an account they ran for at least six months.