GoHighLevel AI Studio tutorial: build a site and wire it to your CRM (2026)

It's HighLevel's vibe coding tool, the same idea as Lovable or Bolt, built into the CRM. You type in plain English, it writes a real React app, and you get a live preview you can keep prompting. As I put it in my first video on it: "You do not need to worry about the code that it's writing. That's the whole point of AI."

It's not only websites. In that video I asked it to build a missed call text back ROI calculator, then a voice AI receptionist ROI calculator, with one sentence each. It built the sliders and the chart by itself. You can use those as a sales tool: pull it up on the demo, do the math with the business owner, and if their numbers show they don't need a receptionist, that's your signal to pivot to something they do need.

Don't mix it up with Agent Studio. HighLevel's own docs call them two separate products: AI Studio builds pages and apps, Agent Studio builds AI agents that act on events.

This is the part that trips people up. AI Studio will happily build a beautiful form that sends its data nowhere. HighLevel's docs say it plainly: forms and calendars are not connected automatically. Until you connect them, the form is a front-end layout.

Once connected, every submission creates or updates the contact in the sub-account. You'll see them under Contacts and under Sites > Forms > Submissions > External Forms, and the project's own More > Analytics tab shows views, opt-ins and opt-in rate.

For automations, use the AI Studio Form Submitted trigger. It needs the form connected, the project published, and one test submission before the filter options load. Older forms built on the External Tracking Event trigger keep working. If you want one of those on the new trigger, type "Re-trigger form integration" in the project chat, reconnect, republish and test again.

Then build the follow-up like any other lead source. Text them within a minute and notify the owner. The money is made in the follow-ups. The exact builds I use are in GoHighLevel workflows.

If the follow-up texts the lead, the form needs proper consent, because carriers check the opt-in on the business's website during A2P review. Ask AI Studio for a separate, unchecked, optional checkbox under the phone field that names the business, says what kind of texts they'll get and how often, says message and data rates may apply, and tells them to reply STOP to opt out. Have it build Privacy Policy and Terms pages and link both next to the box.

Then submit a test entry and check the contact record to make sure the fields landed where you expect. If they didn't, Settings > External Tracking has field mapping (it's in Labs as of October 2026). This is general guidance, not legal advice, so check the current carrier rules for the client's use case.

AI Studio spent most of 2026 in Labs. Since it went live for everyone, it's grown from a front-end builder into something closer to a full app platform. New projects run on TanStack Start with server rendering, which also helps SEO because Google gets real HTML. Older React projects have to go through Project Settings > Migrate to SSR to use payments or Cloud. That makes a copy and leaves the live site alone.

It depends on who's building. Agency admins and users on the $97, $297 and $497 plans build for free, subject to fair use. So if you build client sites yourself from the agency side, building costs you nothing extra.

Sub-account users pay per use unless the sub-account has an AI Employee plan. Usage is counted in rolling five-hour windows. When an allowance runs out, it pauses until the window resets unless Extra Usage is turned on in AI Suite, in which case it keeps going at pay-per-use rates.

HighLevel published three real builds: a one-page yoga lead-capture site for $0.60, an image-heavy fashion page for $1.30 and a seven-page travel site with a blog for $1.10. Generated images cost the most, so a page full of AI images can cost more than a bigger text site. You can check spend at the agency level in AI Suite, which breaks it down by product, model and sub-account. Pay-per-use users also get a heads-up for every $50 spent.

HighLevel doesn't list a separate fee for publishing a normal site. Cloud, the backend for apps with logins and a database, is billed separately from building and comes out of the wallet daily. Every project gets the smallest instance, 2 GB of database and 1 GB of file storage free, so a small member portal can run at no extra cost.

One thing to watch: database storage is billed on the size you reserve, the smallest bump is to 8 GB, and you can never shrink it again. It also keeps billing while Cloud is paused. Only increase it when you're close to the limit.

Yes, two ways. Download Codebase (under Code, or in Project Settings) gives you the whole project as a ZIP, and you can grab any older version from Version History the same way. HighLevel's docs say the code is yours to use, host elsewhere or use commercially. You can't upload a ZIP back in, though. You'd paste changes into the Code Editor.

Git Sync, since Oct 15, 2026, is the better option if you code. More > Git > GitHub creates a private repo, pushes every version you save, and pulls back every commit you make elsewhere, so you can work on it in Claude Code or Cursor and see the preview update in AI Studio. It scans pushes for API keys and blocks them. The permission is called Manage Git & download code, and it's on for every role by default, so turn it off for client users if you don't want them taking the code.

What you can't do is move a project into the regular Sites or Funnels builders. AI Studio projects stay in AI Studio. Also remember the form tracking, hosted checkout and Cloud backend are HighLevel services, so test all of them before you move a site off HighLevel hosting.

There's no excuse to have boring static websites anymore, and for anything custom or interactive AI Studio wins: quizzes, calculators, custom booking pages, storefronts and apps with logins. The plumber site I built had a pricing guide and a diagnostic quiz that captures the lead's details and gives them an estimate. Building that by hand in a drag and drop builder is a lot more work.

The classic Sites builder is still the better pick when the client wants to edit pages themselves by dragging blocks around, when you already have funnel snapshots you reuse across clients, or when a sub-account user does the building and you don't want usage charges. Funnel & Website AI in the classic builder is free for sub-account users, while AI Studio isn't.

This is one of the coolest things I've built. With Ask AI's browser control turned on, I gave it a prompt and the URL of an AI Studio site, and it opened AI Studio, audited the page, typed the fix into the AI Studio chat itself and checked the result. In the first round it spotted a broken image and made the second of two competing buttons smaller. In the next it added a trust badge it pulled from the business's real site.

I set mine to three rounds, but you can set it to more and let it run. Every round is a normal AI Studio message, so it counts toward usage.

Find businesses with a bad website or none at all. Go a few pages deep on Google for plumbers or roofers near you. Build them a site with a good prompt, change the business name, then call and say you built them a free website and want them to see it. That gets you the meeting.

Then sell what's connected to it: the form goes into their CRM, the missed lead gets a text in a minute, the booking lands on their calendar. You could build this for a local business and charge a setup fee plus a monthly fee you set. It's a real business model and I run my agency on it. The pitch is in Sell AI to local businesses.