Skip to content

Discover creators and exclusive content on Sociala

User avatar
Sociala Team

Welcome to Sociala 🎉

Turn your expertise into clear, specific offers your audience can choose from — a detailed review, a focused consultation or a session to work through one particular problem. Help people understand what you can do for them and book the session that fits their needs.

Bring your offers together in your Sociala Widget

Your Widget puts your offers on one page, with one link to share in your bio, posts or messages. People can explore their options, choose what they need, and book and pay through that page.

Set up your Widget

Choose how you’ll deliver each offer

Paid calls let you work with someone directly — review their work, answer questions or help them decide on their next step. Clients can book, pay and join the call on Sociala. How paid calls work

Paid chats let you offer advice and feedback through messages when the question doesn’t need a scheduled call. How paid chats work

Add more ways to learn from you

Some of your knowledge can become something people can read, use or return to:

• Paid posts: Sell individual guides, tutorials, detailed breakdowns or other useful materials. How to create a paid post

• Paid channels: Bring your content and community together, with paid access to your materials and new posts. How to create a paid channel

• Donations: Let people support your work with a voluntary contribution. How donations work

You can also share free posts and build a free community to help your audience get to know your work.

You’re in the newsfeed, where you can discover posts from experts and creators. When you publish your own posts, they’ll appear here and on your profile.

🎁 Here to learn from other experts? Your first purchase from any expert comes with 50% cashback.

Invite friends and earn 10% of their purchases through our referral program.

For ideas and support, join Sociala for Creators.

📌 You can always find this welcome post in your profile whenever you need these guides.

Like
Dislike

24

2

User avatar
Isabella Morris
November 181

Multithreading Wins Deals

I’ve carried enough enterprise quota to tell you this plainly:

Deals don’t usually die because of product.
They die because you weren’t threaded deep enough.

Everybody says they’re “multi-threading.”

Cool.

You’ve got one champion, two friendly users, and a manager who nodded on a Zoom call. That’s not multithreading. That’s hope dressed up as strategy.

Real multithreading is simple:

Who are we talking to? What do they care about? Who’s missing? How do we fix it?

That’s the game.

And if you sell into enterprise, the problem is getting worse, not better. Buying committees are bigger. More people can stall a deal. More people can say “not now.” More people can quietly kill momentum while your CRM happily tells you the opp is “progressing.”

That’s why I keep coming back to this point:

Your CRM is usually a database. It is not a deal strategy.

You can log next steps until your fingers fall off.
That does not mean you understand the relationship map.

And enterprise sales is a relationship map.

Not in the soft, motivational LinkedIn way. I mean literally:

  • who has power
  • who has influence
  • who has budget
  • who can block
  • who is one degree away from your internal network
  • who still hasn’t been engaged

That’s the part too many reps miss.

I’ve seen this movie a hundred times. End of quarter. Forecast call. Rep says, “We have strong support.” Translation: they’ve built a nice relationship with the people who can say yes.

Then the person who can say no shows up late and nukes the deal.

That isn’t bad luck.
That’s weak account strategy.

This is where I think AI actually gets interesting for sales.

Not for writing another mediocre outbound email.

For helping teams understand relationship complexity at scale.

If one enterprise rep is working 40 accounts and needs to navigate even 20 stakeholders per account, that’s 800 people they need to track, understand, and message correctly. Then a manager inherits that across a whole team. Then a CRO is supposed to somehow understand sentiment across thousands of humans.

That’s not a “work harder” problem.
That’s a systems problem.

And the best use of AI here is not replacing the rep. It’s helping the rep walk into the call already knowing:

Here’s who matters. Here’s their context. Here’s what they care about. Here’s the white space. Here’s where we’re exposed.

That’s useful.

Because let’s be honest: most internal deal reviews are a mess. Half the time, the rep is spending 30 minutes recapping who Jill is, who Jack is, what they said three calls ago, and whether procurement has even been looped in.

That friction kills speed.

A strong sales org should be able to answer, fast:

Who are we selling to, and do we have enough coverage to win?

If not, don’t tell me the deal is in commit.

This also ties back to something I believe hard:

Selling is still trust. Always will be.

Automation matters. Data matters. Clean systems matter.

But the closer we get to automating everything around go-to-market, the more obvious the truth becomes:

The advantage is still in the relationship.

Can you earn trust with the champion?
Can you build credibility with leadership?
Can you get access to the people your competitor hasn’t reached?
Can you tailor the message to the individual, not just the account?

That’s enterprise selling.

Not charisma. Not “natural talent.” Not some rep saying, “I just know how to work a room.”

No. It’s process. It’s discipline. It’s pattern recognition.

It’s MEDDIC with actual teeth.
It’s Challenger with better stakeholder mapping.
It’s Sandler without the amateur hour optimism.

If I were coaching a team on this tomorrow, I’d ask one question in every deal review:

Show me the org, show me the relationships, and show me the gaps.

Not “How did the last call go?”

That’s too shallow.

I want to know whether you’ve built a case across the buying committee or whether you’re still relying on one enthusiastic contact to drag the deal over the line.

Because one-threaded deals feel good right up until they don’t.

And if you’re a leader, this is the part you can’t ignore: reps should not be manually stitching together email history, call notes, LinkedIn context, and CRM fields just to understand where they stand in an account.

That’s wasted effort.

The job is to move the deal.
Not play detective in six different tools.

Bottom line:

Multithreading is no longer a nice-to-have enterprise skill. It’s survival.

If your team can’t clearly see: who they know, what those people care about, who’s missing, and how to get there—

you don’t have pipeline coverage.

You have pipeline fiction.

And fiction doesn’t close seven-figure deals.

I’ve carried enough enterprise quota to tell you this plainly:

Deals don’t usually die because of product.
They die because you weren’t threaded deep enough.

Everybody says they’re “multi-threading.”

Cool.

You’ve got one champion, two friendly users, and a manager who nodded on a Zoom call. That’s not multithreading. That’s hope dressed up as strategy.

Real multithreading is simple:

Who are we talking to? What do they care about? Who’s missing? How do we fix it?

That’s the game.

And if you sell into enterprise, the problem is getting worse, not better. Buying committees are bigger. More people can stall a deal. More people can say “not now.” More people can quietly kill momentum while your CRM happily tells you the opp is “progressing.”

That’s why I keep coming back to this point:

Your CRM is usually a database. It is not a deal strategy.

You can log next steps until your fingers fall off.
That does not mean you understand the relationship map.

And enterprise sales is a relationship map.

Not in the soft, motivational LinkedIn way. I mean literally:

  • who has power
  • who has influence
  • who has budget
  • who can block
  • who is one degree away from your internal network
  • who still hasn’t been engaged

That’s the part too many reps miss.

I’ve seen this movie a hundred times. End of quarter. Forecast call. Rep says, “We have strong support.” Translation: they’ve built a nice relationship with the people who can say yes.

Then the person who can say no shows up late and nukes the deal.

That isn’t bad luck.
That’s weak account strategy.

This is where I think AI actually gets interesting for sales.

Not for writing another mediocre outbound email.

For helping teams understand relationship complexity at scale.

If one enterprise rep is working 40 accounts and needs to navigate even 20 stakeholders per account, that’s 800 people they need to track, understand, and message correctly. Then a manager inherits that across a whole team. Then a CRO is supposed to somehow understand sentiment across thousands of humans.

That’s not a “work harder” problem.
That’s a systems problem.

And the best use of AI here is not replacing the rep. It’s helping the rep walk into the call already knowing:

Here’s who matters. Here’s their context. Here’s what they care about. Here’s the white space. Here’s where we’re exposed.

That’s useful.

Because let’s be honest: most internal deal reviews are a mess. Half the time, the rep is spending 30 minutes recapping who Jill is, who Jack is, what they said three calls ago, and whether procurement has even been looped in.

That friction kills speed.

A strong sales org should be able to answer, fast:

Who are we selling to, and do we have enough coverage to win?

If not, don’t tell me the deal is in commit.

This also ties back to something I believe hard:

Selling is still trust. Always will be.

Automation matters. Data matters. Clean systems matter.

But the closer we get to automating everything around go-to-market, the more obvious the truth becomes:

The advantage is still in the relationship.

Can you earn trust with the champion?
Can you build credibility with leadership?
Can you get access to the people your competitor hasn’t reached?
Can you tailor the message to the individual, not just the account?

That’s enterprise selling.

Not charisma. Not “natural talent.” Not some rep saying, “I just know how to work a room.”

No. It’s process. It’s discipline. It’s pattern recognition.

It’s MEDDIC with actual teeth.
It’s Challenger with better stakeholder mapping.
It’s Sandler without the amateur hour optimism.

If I were coaching a team on this tomorrow, I’d ask one question in every deal review:

Show me the org, show me the relationships, and show me the gaps.

Not “How did the last call go?”

That’s too shallow.

I want to know whether you’ve built a case across the buying committee or whether you’re still relying on one enthusiastic contact to drag the deal over the line.

Because one-threaded deals feel good right up until they don’t.

And if you’re a leader, this is the part you can’t ignore: reps should not be manually stitching together email history, call notes, LinkedIn context, and CRM fields just to understand where they stand in an account.

That’s wasted effort.

The job is to move the deal.
Not play detective in six different tools.

Bottom line:

Multithreading is no longer a nice-to-have enterprise skill. It’s survival.

If your team can’t clearly see: who they know, what those people care about, who’s missing, and how to get there—

you don’t have pipeline coverage.

You have pipeline fiction.

And fiction doesn’t close seven-figure deals.

...
#crm#salesstrategy#multithreading#b2bsales#salesleadership#aiinsales#revops#enterprisesales
#crm#salesstrategy#multithreading#b2bsales#salesleadership#aiinsales#revops#enterprisesales
Like
Dislike

Add a comment...

User avatar
Stephen Williams
November 180

Picking the Right Agent Framework

I keep seeing teams ask the wrong question about agentic AI:

“What’s the best framework?”

Usually that’s the moment when someone has 12 GitHub tabs open, three half-read blog posts, and a vague plan to “build agents.” I’ve been there. It’s a fast way to burn a week and still have no architecture.

The more useful question is:

What kind of system am I actually building?

That distinction matters because most of these frameworks are not interchangeable. They overlap, sure, but they’re optimized for different shapes of work.

For simple, predictable flows, I still think in terms of workflows first. If the system is basically:

user input → retrieve context → run logic → generate response → maybe trigger an action

…then I probably don’t need a swarm of agents debating with each other. I need something reliable, inspectable, and easy to control. That’s where tools like LangChain, LlamaIndex, or LangGraph can make sense depending on how much state and branching I need.

On the other hand, if I’m giving the system an open-ended goal and expecting it to figure out the path, that’s a different beast. Now I’m in autonomous or multi-agent territory. Think planner/coder/reviewer loops, where agents collaborate toward a goal. Tools like AutoGen and CrewAI fit that mental model better.

And there’s an important nuance here: not all multi-agent systems are the same.

Some are loosely autonomous. Others are more like a team with job descriptions. That role-based setup is often more practical in the real world because constraints are your friend. A researcher agent researches. A writer writes. An editor edits. Cleaner boundaries usually mean less chaos, easier debugging, and better odds of getting something production-worthy.

That’s why I’m generally skeptical when people jump straight to “multi-agent” because it sounds advanced. In practice, a lot of these systems collapse back into one of two things:

either a workflow with extra marketing
or an orchestration problem with bad observability

That brings me to the part people tend to underestimate: production.

A demo agent that looks smart in a notebook is not the same thing as a production system that has to deal with APIs, retries, permissions, monitoring, cost controls, tool failures, and business logic that was written five years ago by someone who already left the company.

Once you cross that line, framework choice becomes less about clever prompting patterns and more about:

  • orchestration
  • integration
  • state management
  • guardrails
  • monitoring
  • recovery when things break

That’s where a framework like LangGraph starts to look more attractive than “just let the agents talk,” and where Semantic Kernel / AutoGen-style stacks can be useful if they fit your ecosystem.

Then there’s the very real category that gets ignored in a lot of AI strategy decks: rapid prototyping.

Sometimes I do not need a perfect architecture. I need to answer one question fast:

Does this idea work well enough to deserve engineering time?

That’s where tools like LangFlow or Flowise are useful. Not because drag-and-drop is magic, but because speed matters. If I can validate a flow in a day instead of arguing about abstractions for a week, that’s a win.

My practical takeaway is pretty simple:

If the path is known, use a workflow.
If the goal is open-ended, consider autonomous agents.
If collaboration needs boundaries, use role-based agents.
If it has to survive contact with reality, optimize for orchestration.
If you’re still testing the idea, prototype fast and keep your ego out of it.

I like this framing because it cuts through a lot of the noise. Too much agent discourse treats frameworks like they’re a personality test. They’re not. They’re implementation choices tied to system design.

And honestly, most teams should start simpler than they think.

Not every problem needs a multi-agent architecture. A lot of “agentic AI” use cases are just structured pipelines with tool use, retrieval, and a bit of state. That’s fine. In fact, that’s often the right call.

I’d rather ship a boring workflow that works than a dazzling agent demo that can’t survive production traffic.

I keep seeing teams ask the wrong question about agentic AI:

“What’s the best framework?”

Usually that’s the moment when someone has 12 GitHub tabs open, three half-read blog posts, and a vague plan to “build agents.” I’ve been there. It’s a fast way to burn a week and still have no architecture.

The more useful question is:

What kind of system am I actually building?

That distinction matters because most of these frameworks are not interchangeable. They overlap, sure, but they’re optimized for different shapes of work.

For simple, predictable flows, I still think in terms of workflows first. If the system is basically:

user input → retrieve context → run logic → generate response → maybe trigger an action

…then I probably don’t need a swarm of agents debating with each other. I need something reliable, inspectable, and easy to control. That’s where tools like LangChain, LlamaIndex, or LangGraph can make sense depending on how much state and branching I need.

On the other hand, if I’m giving the system an open-ended goal and expecting it to figure out the path, that’s a different beast. Now I’m in autonomous or multi-agent territory. Think planner/coder/reviewer loops, where agents collaborate toward a goal. Tools like AutoGen and CrewAI fit that mental model better.

And there’s an important nuance here: not all multi-agent systems are the same.

Some are loosely autonomous. Others are more like a team with job descriptions. That role-based setup is often more practical in the real world because constraints are your friend. A researcher agent researches. A writer writes. An editor edits. Cleaner boundaries usually mean less chaos, easier debugging, and better odds of getting something production-worthy.

That’s why I’m generally skeptical when people jump straight to “multi-agent” because it sounds advanced. In practice, a lot of these systems collapse back into one of two things:

either a workflow with extra marketing
or an orchestration problem with bad observability

That brings me to the part people tend to underestimate: production.

A demo agent that looks smart in a notebook is not the same thing as a production system that has to deal with APIs, retries, permissions, monitoring, cost controls, tool failures, and business logic that was written five years ago by someone who already left the company.

Once you cross that line, framework choice becomes less about clever prompting patterns and more about:

  • orchestration
  • integration
  • state management
  • guardrails
  • monitoring
  • recovery when things break

That’s where a framework like LangGraph starts to look more attractive than “just let the agents talk,” and where Semantic Kernel / AutoGen-style stacks can be useful if they fit your ecosystem.

Then there’s the very real category that gets ignored in a lot of AI strategy decks: rapid prototyping.

Sometimes I do not need a perfect architecture. I need to answer one question fast:

Does this idea work well enough to deserve engineering time?

That’s where tools like LangFlow or Flowise are useful. Not because drag-and-drop is magic, but because speed matters. If I can validate a flow in a day instead of arguing about abstractions for a week, that’s a win.

My practical takeaway is pretty simple:

If the path is known, use a workflow.
If the goal is open-ended, consider autonomous agents.
If collaboration needs boundaries, use role-based agents.
If it has to survive contact with reality, optimize for orchestration.
If you’re still testing the idea, prototype fast and keep your ego out of it.

I like this framing because it cuts through a lot of the noise. Too much agent discourse treats frameworks like they’re a personality test. They’re not. They’re implementation choices tied to system design.

And honestly, most teams should start simpler than they think.

Not every problem needs a multi-agent architecture. A lot of “agentic AI” use cases are just structured pipelines with tool use, retrieval, and a bit of state. That’s fine. In fact, that’s often the right call.

I’d rather ship a boring workflow that works than a dazzling agent demo that can’t survive production traffic.

...
#aiagents#langchain#mlengineering#agenticai#langgraph#autogen#crewai#semantickernel
#aiagents#langchain#mlengineering#agenticai#langgraph#autogen#crewai#semantickernel
Like
Dislike

Add a comment...

User avatar
Billy Morgan
November 18137

Visionaries, Operators, and Time

I’ve sat in this movie a hundred times.

A visionary walks into a meeting with a new idea, lays it on the table, and then asks, “So where are we at with that?”

My answer is usually the same: we’re at the part where you said it out loud for the first time 90 seconds ago.

That tension is real. And if you run a growing business, you need to understand it.

The visionary and the operator live in completely different relationships with time.

The visionary is moving at idea speed. They’ve been turning it over all weekend. In their mind, it’s already half-built, sold, and scaling.

The operator is moving at execution speed. They’re thinking:

What does this affect? Who owns it? What gets delayed? What breaks if we rush it? What does this cost in team energy, brand trust, and opportunity cost?

Neither person is wrong.

But if you don’t respect the difference, you get chaos.

I saw this for years as a CEO, and I see it now coaching operators inside founder-led companies. The pattern is predictable: the visionary wants momentum, the operator wants coherence. The business needs both.

Drucker said culture eats strategy for breakfast. I’d add this: in founder-led companies, execution dies when speed outruns clarity.

The online education world is the cleanest example. A founder can wake up with an idea and be taking payments by dinner. That feels efficient. Sometimes it even works.

But a fast launch without enough operational scrutiny usually creates one of three problems:

  • you burn out the team
  • you confuse the market
  • you damage the brand

Just because you can launch today doesn’t mean you should.

Operators know this intuitively. Visionaries often experience that caution as resistance.

That’s where the relationship either matures or starts to rot.

If you’re the operator, your job is not to be the department of “no.” Nobody follows the person who kills energy for a living. You have to learn to say:

That’s a strong idea. Here’s the constraint. Here’s the cost. Here’s what we’d need to pause to do it well.

That is a very different posture than dumping a wall of objections on the table.

And if you’re the visionary, stop asking your operator to react at your speed. They are not behind. They are processing risk, sequence, resources, dependencies, and tradeoffs. That’s the job.

Lencioni has been right about this for years: healthy teams can engage in conflict without becoming dysfunctional. This is one of those places. The friction between visionary and operator is not the problem. Unmanaged friction is the problem.

A few practical things I’d push any team to do:

If you’re a visionary, bring the idea in simple form. Bullet points, not speeches. Then give your operator 24 hours to think.

If you’re an operator, bring back the response in a format the visionary can actually consume. Short. Clear. Prioritized. Not a memo.

And the single best question in these conversations is still:

What should we stop doing to make room for this?

That question forces reality into the room.

Because every “yes” lives on top of a dozen hidden “no’s.” Team capacity is finite. Attention is finite. Strategic focus is finite.

Operators understand this. Visionaries need to be reminded of it.

I also think some companies need a legitimate rapid-response lane. Call it a SWAT team, call it a sprint pod, I don’t care. If the founder is always going to generate high-velocity opportunities, then build a structure that can absorb that without setting the core operation on fire.

That’s not indulgence. That’s design.

The real issue is not whether visionaries move too fast or operators move too slow.

The real issue is whether the company has built a way for bold ideas and disciplined execution to work together.

Because vision without execution is theater.

Execution without vision is maintenance.

And if you want to scale, you need both.

I’ve sat in this movie a hundred times.

A visionary walks into a meeting with a new idea, lays it on the table, and then asks, “So where are we at with that?”

My answer is usually the same: we’re at the part where you said it out loud for the first time 90 seconds ago.

That tension is real. And if you run a growing business, you need to understand it.

The visionary and the operator live in completely different relationships with time.

The visionary is moving at idea speed. They’ve been turning it over all weekend. In their mind, it’s already half-built, sold, and scaling.

The operator is moving at execution speed. They’re thinking:

What does this affect? Who owns it? What gets delayed? What breaks if we rush it? What does this cost in team energy, brand trust, and opportunity cost?

Neither person is wrong.

But if you don’t respect the difference, you get chaos.

I saw this for years as a CEO, and I see it now coaching operators inside founder-led companies. The pattern is predictable: the visionary wants momentum, the operator wants coherence. The business needs both.

Drucker said culture eats strategy for breakfast. I’d add this: in founder-led companies, execution dies when speed outruns clarity.

The online education world is the cleanest example. A founder can wake up with an idea and be taking payments by dinner. That feels efficient. Sometimes it even works.

But a fast launch without enough operational scrutiny usually creates one of three problems:

  • you burn out the team
  • you confuse the market
  • you damage the brand

Just because you can launch today doesn’t mean you should.

Operators know this intuitively. Visionaries often experience that caution as resistance.

That’s where the relationship either matures or starts to rot.

If you’re the operator, your job is not to be the department of “no.” Nobody follows the person who kills energy for a living. You have to learn to say:

That’s a strong idea. Here’s the constraint. Here’s the cost. Here’s what we’d need to pause to do it well.

That is a very different posture than dumping a wall of objections on the table.

And if you’re the visionary, stop asking your operator to react at your speed. They are not behind. They are processing risk, sequence, resources, dependencies, and tradeoffs. That’s the job.

Lencioni has been right about this for years: healthy teams can engage in conflict without becoming dysfunctional. This is one of those places. The friction between visionary and operator is not the problem. Unmanaged friction is the problem.

A few practical things I’d push any team to do:

If you’re a visionary, bring the idea in simple form. Bullet points, not speeches. Then give your operator 24 hours to think.

If you’re an operator, bring back the response in a format the visionary can actually consume. Short. Clear. Prioritized. Not a memo.

And the single best question in these conversations is still:

What should we stop doing to make room for this?

That question forces reality into the room.

Because every “yes” lives on top of a dozen hidden “no’s.” Team capacity is finite. Attention is finite. Strategic focus is finite.

Operators understand this. Visionaries need to be reminded of it.

I also think some companies need a legitimate rapid-response lane. Call it a SWAT team, call it a sprint pod, I don’t care. If the founder is always going to generate high-velocity opportunities, then build a structure that can absorb that without setting the core operation on fire.

That’s not indulgence. That’s design.

The real issue is not whether visionaries move too fast or operators move too slow.

The real issue is whether the company has built a way for bold ideas and disciplined execution to work together.

Because vision without execution is theater.

Execution without vision is maintenance.

And if you want to scale, you need both.

...
#leadership#entrepreneurship#visionary#scaling#execution#operations#integrator#teams
#leadership#entrepreneurship#visionary#scaling#execution#operations#integrator#teams
Like
Dislike

12

3

Elizabeth Phillips
Elizabeth Phillips

this is SO real 🔥 the "what should we stop doing" question is actual gold fr

Add a comment...

User avatar
Elizabeth Morgan
November 18278

Gary Halbert on the Phone

I love finding old copy lessons that still embarrass modern marketing advice.

This one does.

Back in 2005, Gary Halbert got on a phone call with Michel Fortin and proceeded to do what Gary always did best: cut through the nonsense and get back to what actually sells.

And right out of the gate, he made the point most people still miss:

The real wealth is between your ears.

Money can disappear. Markets can shift. Platforms can die. But if I can write a sales message that makes people act, I’m never truly broke for long.

That idea alone is worth more than most $997 copy courses.

What hit me hardest was how ruthless Gary was about the power of words.

He used that brutal example of two letters to your mother. Same envelope. Same stamp. Same paper. Same effort. Totally different outcome.

His point was simple:

The words are the variable.

That’s copywriting in one line. Not branding decks. Not funnel maps. Not color psychology threads from people who’ve never sold a thing.

Words change behavior.

Another lesson I loved: great copy isn’t about being a great writer as much as being a great knower.

That’s vintage Halbert, and he was dead right.

Most weak copy sounds weak because the writer doesn’t know enough. They don’t know the market. They don’t know the buyer. They don’t know the product deeply enough to say something sharp, specific, and true.

So they reach for fluff.

They pile on adjectives.

They write “amazing,” “incredible,” “revolutionary,” and every other crutch word people use when they have no substance.

Gary’s answer was cleaner: if I know something my prospect cares about, I have leverage. If I don’t, I’m just making noise.

That’s also why his section on “hypey” copy still matters.

He basically said hype is what people use when they haven’t done the homework.

Exactly.

The best sales copy can be dramatic, punchy, emotional, even aggressive. But it should still be anchored in truth, detail, and discovery. Real facts beat fake intensity every time.

One of the biggest takeaways for me was his obsession with specific tested behavior over theory.

Not opinions. Not “best practices.” Not what sounds reasonable in a Slack thread.

What actually pulls.

For example, he talked about how a phone-only response option could dramatically outpull giving people multiple ways to respond. Why? Because delay kills action. If people can “do it later,” a huge chunk of them never do it.

That’s such a Halbert insight because it forces me to think less about convenience and more about momentum.

He also made a distinction more marketers need tattooed on their forehead:

Don’t confuse efficiency with effectiveness.

That part was brutal and true.

A lot of online marketing is built around what feels efficient for the business. Automate this. Remove friction there. Push everyone through the same sterile flow.

But efficient doesn’t mean persuasive.

A system can be beautifully streamlined and still lose money.

Gary’s point was that I should care first about what gets the sale. Efficiency is nice after that. Not before.

Then he got into one of my favorite topics: long copy.

And he answered the “does long copy still work?” question the same way I’d want it answered — with contempt for the question itself.

Because it’s the wrong question.

The real question is: is the reader interested?

If they are, they’ll read a ton.

If they aren’t, they won’t read a sentence.

That’s it.

People don’t avoid long copy. They avoid boring copy, vague copy, self-centered copy, and copy that says nothing they care about.

A prospect who wants the outcome will gladly read every word that feels like progress toward that outcome.

The other part that stood out was his advice on bullets.

He and John Carlton both pushed the same idea: write the bullets first.

Smart.

Because bullets force me to identify the real payload of the offer. They sharpen curiosity. They dramatize value. They help me find what the market actually wants, not what I want to say.

And when Gary read those bullets, the thing that stood out wasn’t “hype.”

It was specific intrigue.

That’s the game.

Not screaming louder.

Not adding more exclamation points.

Not trying to sound like a carnival barker with a ClickFunnels account.

Just taking something true, desirable, and not fully revealed — then packaging it so the right person has to know more.

He also said something I wish more copywriters would hear:

A good copywriter doesn’t worry much about finding clients.

That stings a little, but it’s true.

If I can produce sales, clients don’t feel hard to find for very long. The market has a way of locating people who can make cash registers ring.

That doesn’t mean skill alone removes every business problem. But it does mean the fastest path to being in demand is getting undeniable at the thing that matters.

Results.

And maybe my favorite Halbertism from the whole thing was about personality.

He had zero interest in trying to please everyone. Zero.

That matters because bland copy is usually written by people terrified of rejection. They want universal approval, so they sand off every edge. Then they wonder why nobody responds.

But strong copy gives the market something to react to.

Some people lean in. Some people lean out.

Good.

That’s healthier than being ignored.

If I had to boil the whole call down, it would be this:

Learn human behavior. Know more than other people know. Use words that move action. Test what works. Stop worshipping efficiency. Stop writing vague fluff.

That’s the post.

Not “delight your audience.” Not “build authentic synergy.” Not any of the usual beige nonsense.

Just write something people care enough to act on.

That’s still the job.

I love finding old copy lessons that still embarrass modern marketing advice.

This one does.

Back in 2005, Gary Halbert got on a phone call with Michel Fortin and proceeded to do what Gary always did best: cut through the nonsense and get back to what actually sells.

And right out of the gate, he made the point most people still miss:

The real wealth is between your ears.

Money can disappear. Markets can shift. Platforms can die. But if I can write a sales message that makes people act, I’m never truly broke for long.

That idea alone is worth more than most $997 copy courses.

What hit me hardest was how ruthless Gary was about the power of words.

He used that brutal example of two letters to your mother. Same envelope. Same stamp. Same paper. Same effort. Totally different outcome.

His point was simple:

The words are the variable.

That’s copywriting in one line. Not branding decks. Not funnel maps. Not color psychology threads from people who’ve never sold a thing.

Words change behavior.

Another lesson I loved: great copy isn’t about being a great writer as much as being a great knower.

That’s vintage Halbert, and he was dead right.

Most weak copy sounds weak because the writer doesn’t know enough. They don’t know the market. They don’t know the buyer. They don’t know the product deeply enough to say something sharp, specific, and true.

So they reach for fluff.

They pile on adjectives.

They write “amazing,” “incredible,” “revolutionary,” and every other crutch word people use when they have no substance.

Gary’s answer was cleaner: if I know something my prospect cares about, I have leverage. If I don’t, I’m just making noise.

That’s also why his section on “hypey” copy still matters.

He basically said hype is what people use when they haven’t done the homework.

Exactly.

The best sales copy can be dramatic, punchy, emotional, even aggressive. But it should still be anchored in truth, detail, and discovery. Real facts beat fake intensity every time.

One of the biggest takeaways for me was his obsession with specific tested behavior over theory.

Not opinions. Not “best practices.” Not what sounds reasonable in a Slack thread.

What actually pulls.

For example, he talked about how a phone-only response option could dramatically outpull giving people multiple ways to respond. Why? Because delay kills action. If people can “do it later,” a huge chunk of them never do it.

That’s such a Halbert insight because it forces me to think less about convenience and more about momentum.

He also made a distinction more marketers need tattooed on their forehead:

Don’t confuse efficiency with effectiveness.

That part was brutal and true.

A lot of online marketing is built around what feels efficient for the business. Automate this. Remove friction there. Push everyone through the same sterile flow.

But efficient doesn’t mean persuasive.

A system can be beautifully streamlined and still lose money.

Gary’s point was that I should care first about what gets the sale. Efficiency is nice after that. Not before.

Then he got into one of my favorite topics: long copy.

And he answered the “does long copy still work?” question the same way I’d want it answered — with contempt for the question itself.

Because it’s the wrong question.

The real question is: is the reader interested?

If they are, they’ll read a ton.

If they aren’t, they won’t read a sentence.

That’s it.

People don’t avoid long copy. They avoid boring copy, vague copy, self-centered copy, and copy that says nothing they care about.

A prospect who wants the outcome will gladly read every word that feels like progress toward that outcome.

The other part that stood out was his advice on bullets.

He and John Carlton both pushed the same idea: write the bullets first.

Smart.

Because bullets force me to identify the real payload of the offer. They sharpen curiosity. They dramatize value. They help me find what the market actually wants, not what I want to say.

And when Gary read those bullets, the thing that stood out wasn’t “hype.”

It was specific intrigue.

That’s the game.

Not screaming louder.

Not adding more exclamation points.

Not trying to sound like a carnival barker with a ClickFunnels account.

Just taking something true, desirable, and not fully revealed — then packaging it so the right person has to know more.

He also said something I wish more copywriters would hear:

A good copywriter doesn’t worry much about finding clients.

That stings a little, but it’s true.

If I can produce sales, clients don’t feel hard to find for very long. The market has a way of locating people who can make cash registers ring.

That doesn’t mean skill alone removes every business problem. But it does mean the fastest path to being in demand is getting undeniable at the thing that matters.

Results.

And maybe my favorite Halbertism from the whole thing was about personality.

He had zero interest in trying to please everyone. Zero.

That matters because bland copy is usually written by people terrified of rejection. They want universal approval, so they sand off every edge. Then they wonder why nobody responds.

But strong copy gives the market something to react to.

Some people lean in. Some people lean out.

Good.

That’s healthier than being ignored.

If I had to boil the whole call down, it would be this:

Learn human behavior. Know more than other people know. Use words that move action. Test what works. Stop worshipping efficiency. Stop writing vague fluff.

That’s the post.

Not “delight your audience.” Not “build authentic synergy.” Not any of the usual beige nonsense.

Just write something people care enough to act on.

That’s still the job.

...
#copywriting#marketing#persuasion#salescopy#directresponse#garyhalbert
#copywriting#marketing#persuasion#salescopy#directresponse#garyhalbert
Like
Dislike

27

4

Joan Kim
Joan Kim

so you write bullets before the headline??

Ann Long
Ann Long

yeah apparently halbert would knock out bullets first to find the strongest angles then build the headline from those

Add a comment...

User avatar
Gabriel Chavez
November 18298

Entra ID Governance and the JML Problem

I spend a lot of time with companies that think they have onboarding and offboarding under control.

Then I look closer.

What they usually have is a mix of HR emails, IT tickets, spreadsheets, tribal knowledge, and a manager who vaguely remembers what happened the last time someone joined or left six months ago. It works right up until it doesn’t.

And when it fails, it fails in the places that matter:

  • accounts enabled too early or too late
  • access granted inconsistently
  • old group memberships hanging around after role changes
  • SaaS access never removed after termination
  • no reliable proof that the process actually happened

That’s why identity lifecycle automation matters more than most organizations think.

What stood out to me is that the real problem isn’t “creating a user.” The real problem is the full joiner / mover / leaver cycle.

A new hire needs the right access at the right time.
A role change needs access adjusted without carrying old privileges forward.
A departing employee needs more than a disabled AD account — they need to be removed from groups, Teams, apps, and anything else the business forgot it connected over the last few years.

That last part is where I see real risk every week.

A lot of offboarding processes still assume disabling the main identity is enough. In practice, users are often still present in downstream SaaS platforms, old distribution groups, collaboration spaces, external tools, and line-of-business systems. That’s not just messy administration. It’s unnecessary exposure.

What I like about Entra ID Governance is that it gives organizations a structured way to automate the repetitive identity work they keep handling manually.

Not just “create account, send password.”

I’m talking about practical workflow steps like:

  • triggering actions based on hire date or leave date
  • scoping workflows by department or user attributes
  • enabling accounts when they should become active
  • adding users to the right groups or Teams
  • assigning access packages
  • removing access during offboarding
  • extending workflows into non-Microsoft systems through custom tasks and Logic Apps

That last piece matters. Most environments I walk into are hybrid by default, even if they don’t call themselves that. Identity starts in HR or Entra, but access sprawls across multiple SaaS platforms. If your automation stops at Microsoft 365, you’ve only solved part of the problem.

From a security standpoint, the biggest win is consistency.

Manual processes create drift. Drift creates exceptions. Exceptions become standing access, orphaned accounts, and audit findings. If I can reduce the number of humans who need to remember every step in every handoff, I reduce the chance of a preventable miss.

There’s also an operational truth here that security teams understand and finance teams often overlook: manual identity processes are expensive. Not just in licensing terms, but in payroll hours, ticket queues, follow-ups, escalations, and rework.

If HR, IT, managers, and security all have to coordinate by email every time someone joins, moves, or leaves, that cost adds up fast.

That said, I wouldn’t oversell this as “turn it on and you’re done.”

The hard part is not the feature. The hard part is the process design.

Before anyone automates onboarding/offboarding, I usually tell them to answer a few plain questions:

What should happen on day -7, day 1, day 3, and day 30?
Which access is role-based, and which is manager-approved?
What systems fall outside M365 but still need lifecycle actions?
What gets disabled, what gets removed, and what gets retained for legal/compliance reasons?
Who owns each exception path?

If you don’t answer those first, automation just makes a bad process run faster.

The other point worth calling out is licensing. A lot of teams get excited about governance features and then discover they’re not included where they assumed they were. That’s not a reason to dismiss it, but it is a reason to build the business case properly. In many environments, the people-cost of manual JML work is already higher than the technology cost to streamline it.

My practical takeaway:

Identity lifecycle management is one of the highest-value low-drama improvements most organizations can make.

It improves security.
It improves user experience.
It improves auditability.
And it reduces the dependence on memory, heroics, and checklists no one really trusts.

If your onboarding and offboarding process still depends on someone chasing a spreadsheet and sending reminder emails, you don’t have a process. You have a vulnerability with good intentions.

I spend a lot of time with companies that think they have onboarding and offboarding under control.

Then I look closer.

What they usually have is a mix of HR emails, IT tickets, spreadsheets, tribal knowledge, and a manager who vaguely remembers what happened the last time someone joined or left six months ago. It works right up until it doesn’t.

And when it fails, it fails in the places that matter:

  • accounts enabled too early or too late
  • access granted inconsistently
  • old group memberships hanging around after role changes
  • SaaS access never removed after termination
  • no reliable proof that the process actually happened

That’s why identity lifecycle automation matters more than most organizations think.

What stood out to me is that the real problem isn’t “creating a user.” The real problem is the full joiner / mover / leaver cycle.

A new hire needs the right access at the right time.
A role change needs access adjusted without carrying old privileges forward.
A departing employee needs more than a disabled AD account — they need to be removed from groups, Teams, apps, and anything else the business forgot it connected over the last few years.

That last part is where I see real risk every week.

A lot of offboarding processes still assume disabling the main identity is enough. In practice, users are often still present in downstream SaaS platforms, old distribution groups, collaboration spaces, external tools, and line-of-business systems. That’s not just messy administration. It’s unnecessary exposure.

What I like about Entra ID Governance is that it gives organizations a structured way to automate the repetitive identity work they keep handling manually.

Not just “create account, send password.”

I’m talking about practical workflow steps like:

  • triggering actions based on hire date or leave date
  • scoping workflows by department or user attributes
  • enabling accounts when they should become active
  • adding users to the right groups or Teams
  • assigning access packages
  • removing access during offboarding
  • extending workflows into non-Microsoft systems through custom tasks and Logic Apps

That last piece matters. Most environments I walk into are hybrid by default, even if they don’t call themselves that. Identity starts in HR or Entra, but access sprawls across multiple SaaS platforms. If your automation stops at Microsoft 365, you’ve only solved part of the problem.

From a security standpoint, the biggest win is consistency.

Manual processes create drift. Drift creates exceptions. Exceptions become standing access, orphaned accounts, and audit findings. If I can reduce the number of humans who need to remember every step in every handoff, I reduce the chance of a preventable miss.

There’s also an operational truth here that security teams understand and finance teams often overlook: manual identity processes are expensive. Not just in licensing terms, but in payroll hours, ticket queues, follow-ups, escalations, and rework.

If HR, IT, managers, and security all have to coordinate by email every time someone joins, moves, or leaves, that cost adds up fast.

That said, I wouldn’t oversell this as “turn it on and you’re done.”

The hard part is not the feature. The hard part is the process design.

Before anyone automates onboarding/offboarding, I usually tell them to answer a few plain questions:

What should happen on day -7, day 1, day 3, and day 30?
Which access is role-based, and which is manager-approved?
What systems fall outside M365 but still need lifecycle actions?
What gets disabled, what gets removed, and what gets retained for legal/compliance reasons?
Who owns each exception path?

If you don’t answer those first, automation just makes a bad process run faster.

The other point worth calling out is licensing. A lot of teams get excited about governance features and then discover they’re not included where they assumed they were. That’s not a reason to dismiss it, but it is a reason to build the business case properly. In many environments, the people-cost of manual JML work is already higher than the technology cost to streamline it.

My practical takeaway:

Identity lifecycle management is one of the highest-value low-drama improvements most organizations can make.

It improves security.
It improves user experience.
It improves auditability.
And it reduces the dependence on memory, heroics, and checklists no one really trusts.

If your onboarding and offboarding process still depends on someone chasing a spreadsheet and sending reminder emails, you don’t have a process. You have a vulnerability with good intentions.

...
#cybersecurity#infosec#compliance#iam#zerotrust#identitygovernance#itoperations#entraid#saassecurity
#cybersecurity#infosec#compliance#iam#zerotrust#identitygovernance#itoperations#entraid#saassecurity
Like
Dislike

27

13

James Jimenez
James Jimenez

offboarding is always where things fall apart

Susan Ramos
Susan Ramos

what's the most common offboarding miss you see

Add a comment...

For you

Clyde Webb's post cover
Danielle Peters's post cover
Mason Morris's post cover
Beth Cook's post cover
Elsa Slawa's post cover
Jennie Ward's post cover
Lucy Phillips's post cover
Florence Ross's post cover
Anthony Rodriquez's post cover
Clyde Webb's post cover
Lucy Phillips's post cover
Beth Cook's post cover
Florence Ross's post cover
Danielle Peters's post cover
Jennie Ward's post cover
Elsa Slawa's post cover
Beth Cook's post cover
Jennie Ward's post cover
Danielle Peters's post cover
Clyde Webb's post cover
Elsa Slawa's post cover
Jennie Ward's post cover
Clyde Webb's post cover
Beth Cook's post cover
Danielle Peters's post cover