Everything In One Box

There's a category of software that gets recommended for the wrong reason, and Go High Level is the loudest example of it.

You'll hear it pitched as the thing that replaces nine subscriptions. CRM, email, SMS, funnels, booking, pipelines, forms, reputation, courses, all under one login for a flat monthly number. And that pitch is technically accurate, which is what makes it dangerous, because the number of subscriptions you carry is not actually your problem and consolidating them will not fix the thing that's broken.

I've watched three businesses migrate onto it. Two of them are still on it two years later and would fight you over it. One of them spent eleven weeks migrating, got about seventy percent moved, stalled, and now runs a genuinely worse operation than they had before across two systems instead of one.

The difference between those outcomes had almost nothing to do with the software. So let's do this one honestly.

Go High Level is a customer operations platform built originally for marketing agencies to run client campaigns, which later got adopted by the businesses those agencies served. That origin explains almost everything about how it feels to use.

The core is a CRM with pipelines. Bolted onto it, and I mean bolted in the descriptive sense rather than the pejorative one, are outbound email, two way SMS, a calendar and booking system, form and survey building, landing pages and funnels, a workflow automation builder, call tracking, review requests, and a course and membership area. Recent versions push hard on conversational AI that answers inbound messages and books appointments without a human touching it.

Pricing lands in two useful places. The entry tier runs about 97 a month for a single business. The agency tier runs about 297 and gives you unlimited sub accounts, which is the tier that matters if you have multiple locations or brands, and which is also why so many consultants push it, since it's the tier that makes reselling viable.

Messaging is metered on top. SMS and email and call minutes come out of a wallet you top up. That's the line item people forget when they do their savings math, and for a business doing real SMS volume it's not trivial.

Two way SMS that's actually wired into the CRM. This is the strongest single argument and it's underrated. Most stacks have SMS bolted on through a third service, which means the text conversation lives somewhere your customer record doesn't. Here the thread sits on the contact, your automations can branch on a reply, and anybody on your team can pick up a conversation somebody else started. For any business where the buying decision happens over text, home services, medical, fitness, automotive, real estate, this alone is most of the value.

Booking that knows the pipeline. The calendar isn't a separate product with an integration. A booked appointment is a pipeline event, so no show sequences, reminder cadences, and rebooking logic are one workflow instead of three tools duct taped together. If your business runs on appointments this removes a whole class of things that quietly break.

Sub accounts. If you run three locations or two brands, the agency tier gives each one its own isolated environment with shared templates and snapshots you can push across them. Standing up location four becomes an afternoon instead of a project. Almost nothing else at this price does that cleanly.

I'd be doing you a disservice to skip this part.

Email deliverability takes work. The built in sending is fine once it's warmed and configured, and it is not fine out of the box. You need to set up your own domain authentication properly, warm slowly, and watch your bounce rates for the first six weeks. Dedicated email platforms handle more of this for you. If email is your primary revenue channel rather than a supporting one, keep it where it is. This is precisely why I still run newsletter sending on Beehiiv rather than consolidating it, and I say that as someone who likes consolidation.

The interface is a lot. Every module is present at all times whether you use it or not. There is no meaningful way to hide the eleven things you'll never touch. For a team that is not particularly technical this is a real adoption tax and it shows up as people quietly reverting to their old habits in month two.

The workflow builder hits a ceiling. It handles linear sequences and simple branching well. Once you need multi step logic across external systems, data transformation, or anything involving arrays, you'll feel the walls. I run Make alongside it for exactly this reason and I'd recommend planning for that rather than discovering it in month three.

Support quality is inconsistent. This is the most common complaint and it's fair. Chat support ranges from genuinely good to a link to a help article that doesn't address what you asked. The community and the third party consultant ecosystem partly compensate, and you should factor into your decision that you may end up paying somebody to help you.

Exit is expensive. Everything is in one place, which is the pitch, and it means leaving is a real project rather than cancelling a subscription. Contacts export fine. Workflows, funnels, and message history are much stickier. Go in knowing that.

Three profiles, and I'd say yes without much hesitation to all three.

You run an appointment based local business doing meaningful SMS volume, and you're currently paying for a CRM, a scheduler, a texting tool, and a review request tool that don't talk to each other. This is the profile it was built for and the fit is excellent.

You run multiple locations or brands and you're rebuilding the same stack for each one. The sub account model solves a problem most tools at this price simply don't address.

You're an agency running campaigns on behalf of clients. This is the original use case and it's still the strongest.

You're a solo operator or a two person shop with a working stack. The consolidation savings are real but small, and the migration cost plus the learning curve will eat two months of your attention. Two months is a lot when you're two people.

Your business is primarily email and content. You'll be fighting the deliverability setup to replace something that already works, and giving up the analytics depth of a purpose built platform to do it.

You have complex product or inventory needs. It's a customer operations platform, not commerce. Don't ask it to be.

Nobody on your team owns tools. This is the one that decides the outcome more than any feature comparison. That business I mentioned that stalled at seventy percent had no named owner. The migration was everybody's job, which means it was nobody's job, and it died in the middle where migrations are most dangerous.

Every platform in this category is shipping conversational AI right now and the marketing is uniformly overheated, so let me be specific about what's actually useful here.

The inbound message responder works genuinely well for a narrow job, which is answering common questions and pushing toward a booking, over SMS, during hours you're closed. That's a real problem for appointment businesses and it solves it. Response time to inbound leads is the single highest leverage number most local businesses have, and a bot that answers at 11pm beats a human who answers at 9am the next day, even if the human is better.

Where it's oversold is anything requiring judgment about the customer's actual situation. It will confidently book the wrong service type. It will miss that somebody is describing an emergency. Set it up with a narrow scope and an aggressive escalation rule that hands off to a human on anything it hasn't seen before.

The practical setup I'd recommend: let it handle hours, pricing ranges, availability, and booking. Escalate everything else. Then read the transcripts weekly for the first month, because that's where you find out what it's been telling people.

One note on disclosure. If you have any customers in the EU, the transparency obligations that took effect in August require you to make clear that people are interacting with an AI system rather than a person. That's a one line change to your greeting message, and it's cheap to do now and expensive to retrofit.

If you're going to test it, don't test it the way the onboarding suggests. Do this instead.

Pick your single highest volume workflow. Just one. Probably inbound lead to booked appointment.

Build only that. Form, pipeline stage, confirmation text, reminder sequence, no show follow up. Ignore every other module completely.

Run real traffic through it for two weeks in parallel with your existing system. Not test traffic. Real leads, duplicated into both.

At two weeks, compare three numbers. Time from lead to first contact. Booking rate. And the one people forget, how many times somebody on your team had to ask how to do something.

That third number is your migration cost estimate. If it's high on one workflow, multiply it by nine and ask yourself honestly whether you have that.

This is a good piece of software aimed at a specific shape of business, sold as if it's aimed at everyone.

If you're appointment driven, text heavy, and juggling four tools that don't talk, it's one of the better buys available and the 97 tier is close to a no brainer. If you run multiple locations, the 297 tier does something almost nothing else does at that price.

If you're consolidating because nine subscriptions feels messy, understand that you're about to trade nine small problems for one large one, and the large one has your entire operation inside it.

The number of logins was never the constraint. The constraint was that nobody owns the system. One box doesn't fix that. It just makes it harder to see.

See you tomorrow.

Jordan Hale
The AI Newsroom