The GoHighLevel Expert Checklist (24 Checks Before You Pay)

Score any GoHighLevel expert on 24 checks before you pay. Covers testing, account structure, A2P, workflow traps and terms, plus Upwork prices and a pass mark.

By Carlos Familia, CRM & AI automation expert. Updated October 14, 2026. 9 min.

A business owner in professional services posted on r/gohighlevel after spending $15,000 on GoHighLevel vendors. Several were GHL-certified, and all of those disappointed. Automations got switched on that emailed and texted the owner's clients, with emails that were not even the owner's. URLs behind paid ads changed without notice, so the ads sent people to 404 pages. The owner's summary: "the bar is set extremely low here."

The top reply gave the advice I would give: make each candidate open their own account on the call and show the work. Every failure in that story can be caught before you pay.

To hire a GoHighLevel expert, give each candidate one point for every check below that they pass with proof, before you pay anything. There are 24. A score of 21 or more means hire. A score of 16 to 20 means pay for one small test task first. Anything lower, keep looking.

For budget, Upwork's GoHighLevel hiring page lists $300 to $1,200 for an account setup or cleanup and $1,000 to $4,000 for a funnel and automation build (checked October 14, 2026). Run the checks in an interview, then send the follow-up questions in writing so you can compare answers side by side.

Where do you find a GoHighLevel expert to score?

Three places work. None of them replaces the checklist.

• Upwork. Freelancers show a public hourly rate, and the rate tells you little about skill. I wrote a separate guide to hiring a GoHighLevel freelancer on Upwork or Fiverr.
• HighLevel's admin directory. HighLevel runs an official directory, linked from its partner site. Admins are listed after passing a live proctored exam, and HighLevel reported 456 admins in the directory in November 2025. The exam shows platform knowledge. It does not show how someone tests, documents or repairs a workflow, so score people from the directory like everyone else.
• Referrals. Ask a business owner in your own industry who runs GoHighLevel. Then score the person they name.

If the job needs custom code, you want a GoHighLevel developer instead. The same partner site lists a Developer Partner Program for that.

Can they prove a workflow works?

Testing is the first group because every other check depends on it. On my eight niche demo accounts I ran 268 test journeys with fake do-not-disturb contacts before calling anything finished. The full method is in how I test GoHighLevel workflows.

• Check 1. They show an execution log of a test contact moving through a workflow, step by step. A screenshot of the builder does not count.
• Check 2. The test contact is isolated: do-not-disturb on, no real phone, no real email.
• Check 3. They run one journey per branch and per exit, not only the happy path.
• Check 4. They read each step's status and reason, not the newest log row. GoHighLevel keeps writing "condition: success" rows while a contact is still waiting, so the last row is not the state.

Two more things came out of those runs. Tag-triggered workflows can start late under load, so a slow start is not proof of failure. And publishing a workflow re-arms its triggers even if you saved them as inactive. A builder who has never been surprised by either has probably not run many tests.

Can someone else read their account?

A mortgage brokerage in Florida handed me an account that a previous agency had built. Before I changed anything, I counted: 281 workflows in 27 folders, only 95 of them active, and 186 old ones parked in draft. The question I put to every builder, myself included, comes from that count. Can you explain what each live workflow does, and why the old ones are still there?

Then I cloned the previous agency's 190 workflows into an archive folder and checked the copy. It came to 190 of 190 workflows, 1,559 actions with zero differences, and 257 of 257 triggers. A check like that only works when the structure is readable.

The Florida account had 27 stage triggers, and every one was filtered by pipeline and stage. Those filters matter. Ask a candidate how they scope an opportunity lookup. Without a pipeline filter, GoHighLevel returns the newest opportunity from any pipeline, and the next update can drag it into the wrong one.

• Check 5. Folders follow a logic you can state in one sentence, such as one folder per pipeline stage.
• Check 6. Workflows and waits have plain names. An HVAC owner in California was annoyed by waits named "1440 minutes". Write "Wait 1 day".
• Check 7. They keep a written map: which workflows exist, what triggers each, and what each one changes.
• Check 8. They know the clutter traps. GoHighLevel allows duplicate folder names, and a failed publish can leave a draft with the same name as the live workflow. Ask how they count copies after publishing.

Do they know the rules for texting?

On that HVAC build, the A2P registration came back rejected, with codes 30909 and 30891. Texting waited and email went first until approval. I wrote more about this in my guide to GoHighLevel A2P registration.

A candidate who says texting "works out of the box" has not been through a rejection. Registration is paperwork first and software second, and the paperwork has to match your public footprint. On a restaurant build, the business email domain did not match the website domain, which carriers reject.

• Check 9. They ask for your legal business name and the EIN from your IRS letter, not the name on your sign.
• Check 10. They ask for privacy and terms pages and an opt-in form that match how you really collect phone numbers.
• Check 11. They build while registration is pending and send email first, so no lead waits on a carrier.
• Check 12. They never ship "no reply, cancel the appointment" before approval. The text never arrives, so every booking cancels.

Do they know the traps that break workflows silently?

These six come from my own builds. Ask each one as a question and score the answer.

Here is an example of how a default can hide a trap. On the HVAC build, my own build tool defaulted to no re-entry. That is the kind of setting you only catch by checking it, and a builder who has not been burned by it will not think to ask.

• Check 13. Re-entry. A returning customer should get the confirmation again. With re-entry off, they never re-enter the workflow. A good builder checks the setting on every workflow.
• Check 14. Tag triggers. A tag trigger fires only when the tag is newly added. Adding a tag the contact already has does nothing, so the tag must be removed first.
• Check 15. Step order. Tag first, then move the stage. If the stage moves first, the next workflow can fire before the guard tag exists. In a wellness clinic funnel that race sent leads the same WhatsApp message two or three times, and I cleaned 31 contacts out of four workflows.
• Check 16. Opportunity context. A contact enrolled by hand or by API has no opportunity context. Stage conditions read false until the workflow looks the opportunity up.
• Check 17. One opportunity per pipeline. GoHighLevel refuses a second opportunity for the same contact in the same pipeline, even when the first is won or abandoned. In one account, the setting that allows it switched itself off within about two hours.
• Check 18. Silent skips. Premium actions such as a custom webhook cost $0.01 per execution and skip when the agency wallet is empty. The reason sits in the step detail. There is no banner.

I expand on these in GoHighLevel workflow mistakes.

What happens when they copy something from another account?

Snapshots and clones are where careful builders separate from fast ones. I learned what to check while cloning funnels for my niche packs, and each clone had to be verified before anyone trusted it.

• Check 19. They know that copied steps which add or remove a contact from another workflow keep the source account's workflow IDs and fail silently.
• Check 20. After cloning a funnel, they check the payment mode and the page schema. Payment mode is set per funnel, and my cloned funnels came up in live payment mode. Clones also carry hidden structured data from the source page.
• Check 21. They take an inventory of inherited triggers before anyone opens them. Saving a migrated trigger in the editor erases orphan IDs, which destroys the evidence of what was broken. When I migrated a portable storage company in Alabama into a fresh sub-account, an integrity scan found three real issues. All three were already broken in the source account.

Are the terms and the first two weeks clear?

• Check 22. Access is a user seat with the permissions the job needs, not the owner login. Upwork's own hiring advice says to share only what is needed to scope the work and to avoid sharing credentials before a contract exists.
• Check 23. The pricing model fits the job. Use fixed scope with milestones for a defined build, hourly for audits and cleanup, and a retainer after launch. Upwork lists ongoing optimization and support at $800 to $3,000 and says a typical GoHighLevel project runs one to eight weeks.
• Check 24. A first-two-weeks plan exists. Week one is access, inventory and a backup. Week two is the first workflow built and proven on a test contact, with the log in your hands.

Here is what that plan looks like in practice. In week one you grant a user seat, and the expert counts workflows by folder, separates active from draft, lists every trigger and pipeline, and takes a snapshot or other backup. Nothing gets edited yet.

In week two they pick the smallest workflow that matters, build it, and run a test contact through every path. You receive the log. If the first two weeks end without a log, the next two will too.

How do you score the checklist?

Give a point only when the answer is specific and the candidate can show proof. "I always test" earns nothing. A log earns the point.

What does a passing score mean?

A pass means the person can show their work. It does not mean they will finish yours. That is why even a 24 gets a paid first task, milestones and a plan.

For a score of 16 to 20, the paid test task does the rescoring. Pick one small workflow, such as a new form lead that gets a text, a task for a rep and a stage move. Ask for the build and the execution log of a test contact through each path. Then score checks 1 to 4 again from the evidence.

A low score is information too. "Good question, let me check" is a fine answer. A confident wrong answer on checks 13 to 18 is a reason to stop, because those are the mistakes that fail silently in a live account.

The same checklist works for someone from HighLevel's directory, a freelancer, an agency or me. If you want a second opinion on a builder's work or on your own account, the calendar below is open.

Your job also decides who you score. A GoHighLevel virtual assistant covers daily operations, not design. A build that talks to outside systems needs someone who understands GoHighLevel n8n as well. Prices and what moves them are in how much a GoHighLevel expert costs.

About the author

Carlos Familia, CRM & AI automation expert. GoHighLevel, n8n, AI agents, servers. Full-stack developer.

I build CRM systems in GoHighLevel, n8n automations on my own servers and AI voice and chat agents for service businesses. Full-stack developer: I write the workflow, the API integration, the database and the server it runs on, and I test every build with real journeys before handoff.