There was a moment while back, when I almost convinced myself to say yes.
Not because I was completely sure it was the right opportunity for me, but because I really wanted it to be.
I had been given the opportunity to become an appointment setter for an AI automation company serving automotive businesses. On paper, quite a few things about the role appealed to me. It was voice-only, there was no activity tracker, I would be getting more exposure to GoHighLevel, and there was the possibility of recurring commissions. More than anything, though, I saw it as a chance to finally experience appointment setting and develop my sales skills in a real environment.
So I gave it a genuine chance.
I attended the onboarding, studied the scripts, practiced handling objections, and went through mock calls. At one point, I even practiced with an AI voice simulation that completely caught me off guard when it asked, “Wait, is this a pitch? Am I talking to a bot?”
I had to laugh because, for a few seconds, I forgot I was supposed to be the one doing the questioning.
But those practice sessions also brought something else to the surface. The more I tried to understand the offer, the more I realized that I had questions of my own.
And one question kept coming back.
What exactly am I selling?
The company talked about missed calls. The scripts talked about missed calls. The training slides talked about missed calls, and the website used the same idea as a major part of its message.
I understood the problem. A business misses a call, the potential customer doesn’t get an immediate response, and there is a chance that customer simply calls another business instead.
That made sense.
What I couldn’t quite connect was what happened after that.
If the system recovered the missed lead, what happened next? How did the CRM fit into the client’s sales process? How were leads nurtured after the initial response? What happened after the appointment was booked? How did the system ultimately help the business beyond simply recovering a missed call?
I wasn’t asking these questions because I wanted to find something wrong with the opportunity. I was asking because I knew that if I were going to represent someone else’s product, I needed to understand the value behind it.
I don’t think I can confidently sell something I don’t fully understand.
And that realization was important.
The More I Learned, The More Things Clicked
Around the same time, I had been exploring GoHighLevel more deeply through an affiliate community and a bootcamp.
That experience gave me a very different perspective.
The more I explored the platform, the less interested I became in thinking about it as a collection of individual features. GoHighLevel can certainly handle missed-call text back, CRM management, appointment booking, AI conversations, workflows, messaging, funnels, and a long list of other functions.
But the real value isn’t any one of those features.
It’s what happens when they work together.
A business can have a system that captures a lead, follows up with them, moves them through a pipeline, books an appointment, sends reminders, requests a review, and continues nurturing the relationship afterward. Instead of asking a business owner or their team to remember every step, the system can carry much of that process for them.
That was the part that fascinated me.
I wasn’t getting excited about selling another piece of software. I was getting excited about what the software could help a business do differently.
And suddenly, something I’d been building for quite some time started making even more sense.
I Don’t Think I Want to Sell Software
I’ve been thinking a lot about this since then.
I don’t think I want my work to revolve around selling a particular platform or feature. I want to understand the problem first and then figure out what kind of system would actually solve it.
Maybe a founder is losing leads because inquiries aren’t being followed up quickly enough.
Maybe client onboarding is scattered across email, spreadsheets, forms, and several different subscriptions.
Maybe a team is spending hours doing something manually that could be automated.
Maybe the business has plenty of leads but no clear process for moving them from inquiry to appointment to customer.
Those are the problems that interest me.
The software is simply one of the tools that can help solve them.
That distinction may sound small, but for me, it changed the entire way I was looking at the opportunity.
I stopped asking myself, “How do I sell this?”
I started asking, “What changes in someone’s business after this system is in place?”
Those are two very different conversations.
I Wasn’t Afraid of Rejection
There was another realization that surprised me.
I thought I was hesitant because I wasn’t confident enough with sales. After all, I was preparing for cold calls, objections, interruptions, and the possibility of hearing “no” over and over again.
But the more I thought about it, the more I realized that rejection wasn’t really what bothered me.
Confusion did.
I could handle a business owner telling me, “No, we’re not interested.”
That’s part of sales.
What I didn’t want was to finish a call and have that person wondering what exactly I had been trying to sell them.
I’d rather hear a clear “No, thank you” from someone who understood the offer than get a “Yes” from someone who never really understood what they were agreeing to.
That probably says something about how I naturally approach business.
I need to believe in the value of what I’m putting in front of people.
So I Said No
Eventually, I made my decision.
I thanked the recruiter. I thanked my team leader. And I stepped away.
It wasn’t a dramatic exit. There was no big confrontation or disagreement. I simply realized that continuing would mean forcing myself into a role that wasn’t aligning with the direction I was beginning to see for myself.
The response I received was wonderfully simple:
“Noted.”
And honestly, that one word managed to make me feel both sad and relieved.
I felt sad because I never enjoy disappointing people, especially people who have already spent time training and preparing me.
But I was also relieved because I had finally stopped trying to convince myself that I needed to make an opportunity work simply because I needed an opportunity.
That distinction matters.
I Didn’t Lose the Opportunity
Looking back, I don’t think I lost an opportunity.
I gained clarity.
The experience confirmed something I’ve been slowly discovering over the past year: I don’t want to be known simply as someone who knows how to use software. I want to become someone who can look at a business, understand where things are getting stuck, design a better process, and then choose the right tools to support that process.
That’s a very different career path.
And it’s one I’m willing to spend years building.
I’m still learning GoHighLevel. I’m still exploring AI and automation. I’m still building workflows, testing systems, documenting what I learn in Notion, and occasionally breaking things before figuring out how to fix them.
I don’t need to pretend that I know everything.
What matters to me is becoming genuinely useful.
I want to be able to sit with a founder and ask better questions.
Where are leads falling through?
What’s taking too much manual effort?
Where is the customer journey breaking down?
What should be automated?
What needs to stay human?
Which tools are actually necessary?
And, perhaps most importantly, what would make this business easier to run?
That’s the kind of work that keeps me curious.
I Still Want to Learn Sales
Interestingly, walking away from this role didn’t make me lose interest in sales.
It actually made me more interested in learning it properly.
I still want to experience the uncomfortable part of sales. I want to get better at handling objections, asking discovery questions, listening for buying signals, and understanding what makes someone move from curiosity to action.
I even want to become comfortable with rejection.
Just not at the expense of understanding the value I’m representing.
I don’t want to become someone who is simply good at convincing people.
I want to become someone who is good at understanding people and solving the right problem.
That feels much more aligned with the kind of strategic partner I want to become.
The Yes Hidden Inside the No
Perhaps that’s why this decision has stayed with me.
I thought I was deciding whether to accept a job.
In reality, I was making a decision about the direction I want my career to take.
The opportunity gave me a chance to practice sales, explore a different side of GoHighLevel, and see what appointment setting actually feels like. Those are valuable experiences, even though I ultimately decided not to continue.
And I’m grateful for that.
Sometimes we only discover what fits after we’ve spent enough time inside something to understand what doesn’t.
For me, this wasn’t a wasted week.
It was a very useful one.
What I Know Now
I still have a lot to learn.
I haven’t mastered GoHighLevel, and I don’t intend to pretend that I have. There are hundreds of features I haven’t explored yet, and that’s actually part of what makes it interesting.
What has changed is that I now understand what I’m looking for.
I don’t want to collect tools just because they’re powerful.
I want to understand the business problem first.
Then I want to build the system around it.
That is much closer to the work I’ve been moving toward with The Mari Effect all along.
Calm operations. Clear systems. Confident visibility.
The tools may change. The platforms will evolve. AI will continue to develop.
But the need for businesses to have better systems isn’t going away.
And that’s where I want to be.
The Mari Effect Takeaway
I’ve learned that clarity doesn’t always arrive before we take an opportunity.
Sometimes we have to walk through the door, learn what we can, ask uncomfortable questions, and pay attention to what the experience is teaching us.
Walking away doesn’t necessarily mean an opportunity was bad, nor does it mean we failed.
Sometimes it simply means we finally have enough information to make a decision that feels honest.
For me, the biggest lesson was this:
I don’t want to sell tools. I want to build systems that solve real business problems.
And if a tool like GoHighLevel happens to be the right tool for the job, then that’s where it belongs—as part of the solution, not the solution itself.
A Note From Mari’s Desk
I almost said yes because I needed the opportunity to work.
I almost stayed because I wanted the experience.
And, if I’m being completely honest, I almost continued because I didn’t want to disappoint anyone.
Those are all understandable reasons. But they aren’t necessarily good enough reasons to keep moving in a direction that doesn’t feel right.
This experience reminded me that I don’t have to force every opportunity to become my opportunity.
I can learn from it, appreciate the people who opened the door, and still decide that another path makes more sense for me.
And perhaps that’s one of the most useful things I’m learning as I build The Mari Effect.
Clarity isn’t only something I want to create for the founders I hope to serve.
It’s something I owe myself, too.
So I’m taking this experience with me—not as a rejection, not as a failure, and not as a missed opportunity, but as another signpost along the way.
I thought I was going to learn appointment setting.
Instead, I learned a little more about the kind of professional I want to become.
And for that, I’m grateful.
About The Mari Effect
The Mari Effect exists to help founder-led businesses replace operational chaos with calm, clarity, and confidence through business systems, executive workflows, strategic websites, and CRM automation.
Because technology isn’t the goal.
Helping people work better is.