08/24/2026
What I learned from a summer cold...
The weekend before last, I listened to my husband cough his way through several days.
And congratulated myself for not catching it.
Yeah. That was premature.
By Wednesday, my head had socked in, sneezing fits were wracking my body, and it was pretty clear the thing had come to stay for a while.
Unfortunately, I'd also spent Tuesday trying to solve a problem in GoHighLevel.
I'd tried it three or four different ways before realizing that what I actually wanted wasn't another form or another clever workaround.
I needed to build an app.
Okay. I can do that.
So I grabbed a YouTube video.
I wasn't even searching for "low-tech" or "no-tech," but that's what the guy promised.
Then he started talking at approximately 35 miles per hour.
Unfortunately, my brain was set to Walk: 3 mph.
Somewhere between app registration and OAuth and APIs and where-the-hell-does-the-actual-application-live, I gave up.
But something interesting happened first.
For a little while, I got to experience what it feels like to approach technology without the language and framework to hold what you're being told.
Normally, I can build that framework pretty quickly.
I may not know this technology yet, but I know what a database is. I know what an API does. I know authentication has to happen somewhere. I understand data and presentation layers.
I have places in my head to put the new information while I figure out how the pieces connect.
Last week, my brain temporarily couldn't do that.
And without the framework, the words were just coming at me.
That's when I realized how ridiculous one of our expectations of coaches, consultants, healers and other small-business owners has become.
Somehow, because the software is marketed as "easy," we've decided that someone whose expertise is helping clients change their lives or businesses should also be able to figure out:
Websites.
Funnels.
Forms.
Calendars.
Automations.
CRM architecture.
Email deliverability.
DNS.
Integrations.
Payment systems.
Facebook tracking.
And whatever the software company changed last Tuesday.
And if they can't?
They assume they're bad at tech.
Maybe they're not.
Maybe somebody handed them a pile of tools without giving them the framework that makes any of those tools make sense.
Because here's what I discovered about "no-code":
No-code doesn't mean there's no technology.
Usually, it just means somebody hid the code.
You still have to understand what the pieces do, how they fit together, what should talk to what, and what you're trying to build in the first place.
And maybe we should stop pretending that's simply part of the job description for being a coach.
Your business needs technology.
That doesn't mean you need to become the tech department.