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
Billy Morgan
November 160

Working Genius at Work

I’ve spent enough years leading teams to know this simple truth:

Most performance problems are not performance problems.

They’re fit problems. Role problems. Clarity problems. Energy problems.

That’s why the Working Genius framework resonates. It gives operators a practical language for something we’ve all seen but often fail to name: two capable people can look wildly different at work, not because one cares more, but because different stages of work give them energy and different stages drain them.

That distinction matters.

Too many leaders still make the same mistake: they assume if someone is competent at a task, they should keep doing more of it. That’s lazy management. A person can be very good at something and still be slowly burning out doing it.

I’ve seen this firsthand. In operating roles, people get rewarded for reliability, and before long they’re trapped in work that the business needs but that quietly kills their joy. Then the leader says, “I don’t understand, they’re great at the job, why are they disengaged?”

Because competence is not genius.

And if you miss that, you’ll misread the signal. You’ll call someone unmotivated when they’re actually misused.

What I like about this model is that it’s not another abstract personality exercise you do at an offsite and forget by Monday. It’s tangible. It answers a very practical question:

What kind of work actually gives this person energy?

That’s useful.

Not just for hiring.
Not just for team design.
Not just for meetings.

For retention.

One story that stuck with me was the idea that some people were heading toward the door—or toward being pushed out—not because they were wrong for the company, but because they were sitting in the wrong seat. Drucker said culture eats strategy for breakfast. I’d add this: role design eats a lot of culture before lunch.

If you have a good operator in the wrong kind of work, don’t be surprised when they get “cranky,” checked out, or flat. The problem may not be attitude. It may be sustained friction between what the work requires and how they’re wired to contribute.

That’s also why this lands so well in environments where leaders are dealing with burnout, turnover, and foggy accountability.

When teams don’t know what stage of work they’re actually in, they create avoidable friction. One person is trying to explore. Another is trying to decide. Another is trying to mobilize. Another is trying to finish. Then everybody gets frustrated with everybody else.

That’s not a personality clash.

That’s a workflow clarity issue.

Lencioni has always been strong at this. He doesn’t romanticize teamwork. He operationalizes it. Very The Five Dysfunctions of a Team: name the thing, remove the ambiguity, give people a shared language, and let the team function like adults.

The shared language here is the real unlock.

When a team can say, “We’re wondering right now,” or “This meeting is for invention,” or “We need tenacity in this stage,” the work gets cleaner. Expectations get cleaner. Meetings get shorter. Judgment goes down. Throughput goes up.

That’s the part many leaders miss.

The value isn’t just self-awareness.
The value is coordination.

And operators should care about that.

I also think there’s a leadership lesson here that has nothing to do with assessments and everything to do with humility. A good leader should be willing to say, plainly:

Here’s where I’m strong. Here’s where I’m not. Here’s the kind of work that drains me. Here’s where I need help.

That’s not weakness. That’s maturity.

In my experience, teams trust you more when you stop pretending to be universally gifted. Nobody believes that anyway. The minute a leader names their frustrations honestly, the team gets permission to be honest too. That’s when you stop managing theater and start managing reality.

And reality is where good operating happens.

One more point that matters: this framework doesn’t just reduce guilt; it reduces misplaced judgment.

A lot of tension on teams comes from people morally evaluating what is actually just a difference in genius. The person who loves brainstorming thinks the finisher is rigid. The finisher thinks the brainstormer is exhausting. The discerner sounds hesitant. The galvanizer sounds overly certain. Same team, same mission, different contribution pattern.

Once you understand that, you can stop pathologizing each other.

Lencioni’s work has always pushed leaders toward healthier teams, but this one is especially useful because it gets concrete fast. That’s why operators will use it. It doesn’t live in theory. It lives in calendars, meeting design, role design, and day-to-day collaboration.

If I were advising a leadership team on where to start, I’d keep it simple:

Don’t begin by rolling out another company-wide initiative.

Start with your own work.

Share where you do your best work. Share where you get drained. Then look at your team and ask one hard, operational question:

Do we have good people doing too much work outside their genius?

If the answer is yes—and on most teams it is—you probably just found a root cause of burnout, drag, and unnecessary turnover.

That’s worth fixing.

Because the goal isn’t to make work easy. Operators know better than that.

The goal is to align people to the kind of contribution where they can create disproportionate value without paying for it every day in frustration.

I’ve spent enough years leading teams to know this simple truth:

Most performance problems are not performance problems.

They’re fit problems. Role problems. Clarity problems. Energy problems.

That’s why the Working Genius framework resonates. It gives operators a practical language for something we’ve all seen but often fail to name: two capable people can look wildly different at work, not because one cares more, but because different stages of work give them energy and different stages drain them.

That distinction matters.

Too many leaders still make the same mistake: they assume if someone is competent at a task, they should keep doing more of it. That’s lazy management. A person can be very good at something and still be slowly burning out doing it.

I’ve seen this firsthand. In operating roles, people get rewarded for reliability, and before long they’re trapped in work that the business needs but that quietly kills their joy. Then the leader says, “I don’t understand, they’re great at the job, why are they disengaged?”

Because competence is not genius.

And if you miss that, you’ll misread the signal. You’ll call someone unmotivated when they’re actually misused.

What I like about this model is that it’s not another abstract personality exercise you do at an offsite and forget by Monday. It’s tangible. It answers a very practical question:

What kind of work actually gives this person energy?

That’s useful.

Not just for hiring.
Not just for team design.
Not just for meetings.

For retention.

One story that stuck with me was the idea that some people were heading toward the door—or toward being pushed out—not because they were wrong for the company, but because they were sitting in the wrong seat. Drucker said culture eats strategy for breakfast. I’d add this: role design eats a lot of culture before lunch.

If you have a good operator in the wrong kind of work, don’t be surprised when they get “cranky,” checked out, or flat. The problem may not be attitude. It may be sustained friction between what the work requires and how they’re wired to contribute.

That’s also why this lands so well in environments where leaders are dealing with burnout, turnover, and foggy accountability.

When teams don’t know what stage of work they’re actually in, they create avoidable friction. One person is trying to explore. Another is trying to decide. Another is trying to mobilize. Another is trying to finish. Then everybody gets frustrated with everybody else.

That’s not a personality clash.

That’s a workflow clarity issue.

Lencioni has always been strong at this. He doesn’t romanticize teamwork. He operationalizes it. Very The Five Dysfunctions of a Team: name the thing, remove the ambiguity, give people a shared language, and let the team function like adults.

The shared language here is the real unlock.

When a team can say, “We’re wondering right now,” or “This meeting is for invention,” or “We need tenacity in this stage,” the work gets cleaner. Expectations get cleaner. Meetings get shorter. Judgment goes down. Throughput goes up.

That’s the part many leaders miss.

The value isn’t just self-awareness.
The value is coordination.

And operators should care about that.

I also think there’s a leadership lesson here that has nothing to do with assessments and everything to do with humility. A good leader should be willing to say, plainly:

Here’s where I’m strong. Here’s where I’m not. Here’s the kind of work that drains me. Here’s where I need help.

That’s not weakness. That’s maturity.

In my experience, teams trust you more when you stop pretending to be universally gifted. Nobody believes that anyway. The minute a leader names their frustrations honestly, the team gets permission to be honest too. That’s when you stop managing theater and start managing reality.

And reality is where good operating happens.

One more point that matters: this framework doesn’t just reduce guilt; it reduces misplaced judgment.

A lot of tension on teams comes from people morally evaluating what is actually just a difference in genius. The person who loves brainstorming thinks the finisher is rigid. The finisher thinks the brainstormer is exhausting. The discerner sounds hesitant. The galvanizer sounds overly certain. Same team, same mission, different contribution pattern.

Once you understand that, you can stop pathologizing each other.

Lencioni’s work has always pushed leaders toward healthier teams, but this one is especially useful because it gets concrete fast. That’s why operators will use it. It doesn’t live in theory. It lives in calendars, meeting design, role design, and day-to-day collaboration.

If I were advising a leadership team on where to start, I’d keep it simple:

Don’t begin by rolling out another company-wide initiative.

Start with your own work.

Share where you do your best work. Share where you get drained. Then look at your team and ask one hard, operational question:

Do we have good people doing too much work outside their genius?

If the answer is yes—and on most teams it is—you probably just found a root cause of burnout, drag, and unnecessary turnover.

That’s worth fixing.

Because the goal isn’t to make work easy. Operators know better than that.

The goal is to align people to the kind of contribution where they can create disproportionate value without paying for it every day in frustration.

...
#leadership#productivity#teamwork#management#burnout#patricklencioni#workinggenius#operatingteams
#leadership#productivity#teamwork#management#burnout#patricklencioni#workinggenius#operatingteams
Like
Dislike

Add a comment...

User avatar
Stephen Williams
November 150

Smart routing beats bigger models

A lot of enterprise AI spend is self-inflicted.

I keep seeing teams wire everything to the most expensive frontier model they can get approved, then act surprised when the monthly bill starts looking like a procurement incident.

That approach was always lazy architecture. Now it’s becoming obviously unsustainable.

The practical move is a routing layer that decides which model should handle which task in real time.

Not every request needs frontier reasoning. In fact, most don’t.

A basic extraction job, internal FAQ lookup, email summarization, form classification, routine drafting—these are often getting massively over-served. Sending all of that to a premium model is like using a surgical robot to open Amazon boxes.

The framing I like is a simple 3-tier model setup:

  • Budget / sovereign tier for high-volume, repetitive, or sensitive workloads
  • Mid-tier for everyday business logic and agent workflows
  • Frontier tier for the genuinely hard reasoning, long-context, or complex coding cases

That’s the part too many “AI strategy” decks skip. They talk about capability in the abstract, but not workload segmentation, escalation logic, fallback behavior, or compliance routing. The real value is in orchestration.

And yes, this is where the economics get interesting.

If your router can correctly classify requests and only escalate when confidence drops or complexity spikes, the cost reduction can be dramatic. The 60–80% range is believable to me if you actually have a lot of high-volume commodity tasks in the mix—which most enterprises do.

The other half of the story is data control.

For regulated environments, the architecture decision is not just about price. It’s also about where the data is allowed to go. A lot of organizations should never have designed around “send everything to a public API” in the first place.

That’s why open-weight models and private hosting matter more than a lot of people want to admit. Not because open automatically wins, but because it gives you another routing option:

cheap when possible, private when necessary, powerful when justified.

That’s a much better design principle than vendor loyalty.

What I also think gets underappreciated: a smart router is not just a cost tool. It’s a reliability tool.

A production-grade setup should be able to:

  • downgrade gracefully when a premium endpoint is rate-limited
  • keep sensitive prompts on approved infrastructure
  • escalate only when the cheaper path fails
  • log routing decisions for auditing and optimization

That’s real systems thinking. Not “we picked the smartest model.”

My main takeaway is pretty simple:

The winning GenAI stack is increasingly about orchestration, not model worship.

By now, access to powerful models is getting commoditized. What actually differentiates teams is whether they can build a system that knows:

  • what kind of task is arriving
  • how much intelligence it truly needs
  • what it’s allowed to touch
  • what it should cost to answer

That’s the playbook.

If I were implementing this, I’d start with one blunt question: Which requests are we currently sending to an expensive model that absolutely do not need to be there?

That one audit usually reveals how much money is being burned in the name of simplicity.

And to be honest, “one model for everything” was never simplicity. It was just pushing architectural decisions downstream until finance noticed.

A lot of enterprise AI spend is self-inflicted.

I keep seeing teams wire everything to the most expensive frontier model they can get approved, then act surprised when the monthly bill starts looking like a procurement incident.

That approach was always lazy architecture. Now it’s becoming obviously unsustainable.

The practical move is a routing layer that decides which model should handle which task in real time.

Not every request needs frontier reasoning. In fact, most don’t.

A basic extraction job, internal FAQ lookup, email summarization, form classification, routine drafting—these are often getting massively over-served. Sending all of that to a premium model is like using a surgical robot to open Amazon boxes.

The framing I like is a simple 3-tier model setup:

  • Budget / sovereign tier for high-volume, repetitive, or sensitive workloads
  • Mid-tier for everyday business logic and agent workflows
  • Frontier tier for the genuinely hard reasoning, long-context, or complex coding cases

That’s the part too many “AI strategy” decks skip. They talk about capability in the abstract, but not workload segmentation, escalation logic, fallback behavior, or compliance routing. The real value is in orchestration.

And yes, this is where the economics get interesting.

If your router can correctly classify requests and only escalate when confidence drops or complexity spikes, the cost reduction can be dramatic. The 60–80% range is believable to me if you actually have a lot of high-volume commodity tasks in the mix—which most enterprises do.

The other half of the story is data control.

For regulated environments, the architecture decision is not just about price. It’s also about where the data is allowed to go. A lot of organizations should never have designed around “send everything to a public API” in the first place.

That’s why open-weight models and private hosting matter more than a lot of people want to admit. Not because open automatically wins, but because it gives you another routing option:

cheap when possible, private when necessary, powerful when justified.

That’s a much better design principle than vendor loyalty.

What I also think gets underappreciated: a smart router is not just a cost tool. It’s a reliability tool.

A production-grade setup should be able to:

  • downgrade gracefully when a premium endpoint is rate-limited
  • keep sensitive prompts on approved infrastructure
  • escalate only when the cheaper path fails
  • log routing decisions for auditing and optimization

That’s real systems thinking. Not “we picked the smartest model.”

My main takeaway is pretty simple:

The winning GenAI stack is increasingly about orchestration, not model worship.

By now, access to powerful models is getting commoditized. What actually differentiates teams is whether they can build a system that knows:

  • what kind of task is arriving
  • how much intelligence it truly needs
  • what it’s allowed to touch
  • what it should cost to answer

That’s the playbook.

If I were implementing this, I’d start with one blunt question: Which requests are we currently sending to an expensive model that absolutely do not need to be there?

That one audit usually reveals how much money is being burned in the name of simplicity.

And to be honest, “one model for everything” was never simplicity. It was just pushing architectural decisions downstream until finance noticed.

...
#generativeai#ai#costoptimization#aiarchitecture#enterpriseai#llmops#modelrouting
#generativeai#ai#costoptimization#aiarchitecture#enterpriseai#llmops#modelrouting
Like
Dislike

Add a comment...

User avatar
Catherine Myers
November 15147

Dynamic vs. Baked-In Ads

One of the more practical conversations in podcast monetization is also one of the least flashy: where the ad actually lives.

I’ve seen a lot of podcasters treat baked-in vs. dynamic insertion like a “which one wins?” debate. In reality, it’s more of a fit question. The right answer depends on your show, your back catalog, and how your audience actually listens.

A baked-in ad is the old-school version. The host reads it in the episode, it becomes part of the audio, and it stays there unless someone manually removes it later. There’s something very natural about that format. When it’s done well, it can feel seamless because it was recorded in the same session, in the same voice, with the same energy as the rest of the episode.

But there’s a tradeoff.

If an episode keeps getting downloads long after the first 30 days, that ad is still doing work while the show may no longer be earning against those later listens. Great value for the advertiser, not always great value for the publisher. And if the ad is time-sensitive — Black Friday, a limited launch, a seasonal promo — it can age badly fast.

That’s where dynamic ad insertion starts to make a lot of sense.

With dynamic, the ad is usually recorded separately and inserted at designated points in the episode. From the listener side, if the production is clean, they may not even notice. From the business side, it gives you control. You can run an ad for a set amount of time, for a set number of downloads, then swap it out.

That matters a lot if your catalog keeps working for you.

I’ve worked on shows where the real inventory wasn’t just the latest episode — it was the library. Older episodes kept pulling in listeners month after month. In those cases, dynamic insertion isn’t just a nice feature. It’s the difference between monetizing the full catalog and leaving a lot of value on the table.

That said, not every show benefits equally.

Some podcasts are of the moment. News-driven, trend-driven, reaction-based, timely commentary. Once the moment passes, the back catalog may still have brand value, but not much monetization depth. In that case, baked-in can still be perfectly reasonable, especially if the host read is strong and the campaign is built around freshness and trust.

So when I think about this, I don’t start with the ad format. I start with listener behavior.

Are people mostly listening in the first 30 days?
Or do episodes keep getting discovered for months?
Is the show evergreen enough that old inventory still matters?
Is the ad message timeless, or does it expire quickly?

That’s usually where the real answer is.

From a production perspective, I’ll add one more thing: dynamic only works well if the listening experience still feels intentional. I’m a perfectionist about audio, and listeners can absolutely hear when an ad break was jammed in without care. The transition, loudness, tone, and placement all matter. If you want the flexibility of dynamic, you still have to respect the craft.

So my takeaway is simple: don’t choose based on trend; choose based on consumption pattern.

Baked-in is still useful. Dynamic is incredibly powerful. Neither is automatically better.

The smart move is knowing whether your show lives in the moment, in the archive, or in both.

One of the more practical conversations in podcast monetization is also one of the least flashy: where the ad actually lives.

I’ve seen a lot of podcasters treat baked-in vs. dynamic insertion like a “which one wins?” debate. In reality, it’s more of a fit question. The right answer depends on your show, your back catalog, and how your audience actually listens.

A baked-in ad is the old-school version. The host reads it in the episode, it becomes part of the audio, and it stays there unless someone manually removes it later. There’s something very natural about that format. When it’s done well, it can feel seamless because it was recorded in the same session, in the same voice, with the same energy as the rest of the episode.

But there’s a tradeoff.

If an episode keeps getting downloads long after the first 30 days, that ad is still doing work while the show may no longer be earning against those later listens. Great value for the advertiser, not always great value for the publisher. And if the ad is time-sensitive — Black Friday, a limited launch, a seasonal promo — it can age badly fast.

That’s where dynamic ad insertion starts to make a lot of sense.

With dynamic, the ad is usually recorded separately and inserted at designated points in the episode. From the listener side, if the production is clean, they may not even notice. From the business side, it gives you control. You can run an ad for a set amount of time, for a set number of downloads, then swap it out.

That matters a lot if your catalog keeps working for you.

I’ve worked on shows where the real inventory wasn’t just the latest episode — it was the library. Older episodes kept pulling in listeners month after month. In those cases, dynamic insertion isn’t just a nice feature. It’s the difference between monetizing the full catalog and leaving a lot of value on the table.

That said, not every show benefits equally.

Some podcasts are of the moment. News-driven, trend-driven, reaction-based, timely commentary. Once the moment passes, the back catalog may still have brand value, but not much monetization depth. In that case, baked-in can still be perfectly reasonable, especially if the host read is strong and the campaign is built around freshness and trust.

So when I think about this, I don’t start with the ad format. I start with listener behavior.

Are people mostly listening in the first 30 days?
Or do episodes keep getting discovered for months?
Is the show evergreen enough that old inventory still matters?
Is the ad message timeless, or does it expire quickly?

That’s usually where the real answer is.

From a production perspective, I’ll add one more thing: dynamic only works well if the listening experience still feels intentional. I’m a perfectionist about audio, and listeners can absolutely hear when an ad break was jammed in without care. The transition, loudness, tone, and placement all matter. If you want the flexibility of dynamic, you still have to respect the craft.

So my takeaway is simple: don’t choose based on trend; choose based on consumption pattern.

Baked-in is still useful. Dynamic is incredibly powerful. Neither is automatically better.

The smart move is knowing whether your show lives in the moment, in the archive, or in both.

...
#podcasting#podcastgrowth#monetization#podcastads#podcasthosting
#podcasting#podcastgrowth#monetization#podcastads#podcasthosting
Like
Dislike

15

8

Timothy Nelson
Timothy Nelson

solid breakdown 👏👏👏👏📝

Dorothy Miller
Dorothy Miller

thanks! do you work with podcast ads at all?

Add a comment...

User avatar
Alan Morgan
November 15169

LinkedIn Featured Section That Gets Clicked

One of the most overlooked parts of a LinkedIn profile is the Featured section.

I used to review profiles all day as a recruiter, and this section often made the difference between “looks fine” and “I can immediately see this person’s value.”

That’s why I always tell candidates: don’t treat Featured like decoration. Treat it like your proof-of-work shelf.

If someone lands on your profile, they should not have to dig through your experience section, activity feed, or buried links to figure out what you actually do well.

The Featured section lets you surface that instantly.

A few things I’d be intentional about:

  • a strong portfolio sample
  • a case study with measurable results
  • a certification that matters for your target role
  • a slide deck, press mention, or project walkthrough
  • a top-performing post that reinforces your expertise

What matters most is not just adding something — it’s adding the right first item.

That first card becomes a visual signal. Recruiters skim fast. Hiring managers skim even faster. If your first Featured item clearly shows relevance, credibility, and outcomes, you’ve made their job easier.

And when you make their job easier, you increase your odds of being shortlisted.

A few practical mistakes I see all the time:

Vague titles.
If the title says something generic, it gets ignored. Be clear and specific.

No context.
Don’t assume people know what they’re looking at. A short description explaining the project, your role, and the outcome goes a long way.

Random uploads.
Just because something looks polished doesn’t mean it supports your target role.

Outdated content.
If your best work is from 3 years ago and nothing has been refreshed, it quietly signals stagnation.

If you’re job searching right now, I’d ask yourself:

If a recruiter only looked at my Featured section for 10 seconds, would they understand the kind of roles I should be considered for?

That’s the standard.

I’m a big believer in using LinkedIn real estate strategically. Your headline gets attention. Your About section builds the story. Your Featured section provides the evidence.

That combination is what turns a profile from informative into convincing.

If your Featured section is empty, this is an easy win. If it’s already there, audit it like a recruiter would:

Is it relevant?
Is it current?
Is it easy to understand in seconds?
Does it support the role you want next?

Most people don’t need a complete LinkedIn rewrite.

They need better positioning of the proof they already have.

One of the most overlooked parts of a LinkedIn profile is the Featured section.

I used to review profiles all day as a recruiter, and this section often made the difference between “looks fine” and “I can immediately see this person’s value.”

That’s why I always tell candidates: don’t treat Featured like decoration. Treat it like your proof-of-work shelf.

If someone lands on your profile, they should not have to dig through your experience section, activity feed, or buried links to figure out what you actually do well.

The Featured section lets you surface that instantly.

A few things I’d be intentional about:

  • a strong portfolio sample
  • a case study with measurable results
  • a certification that matters for your target role
  • a slide deck, press mention, or project walkthrough
  • a top-performing post that reinforces your expertise

What matters most is not just adding something — it’s adding the right first item.

That first card becomes a visual signal. Recruiters skim fast. Hiring managers skim even faster. If your first Featured item clearly shows relevance, credibility, and outcomes, you’ve made their job easier.

And when you make their job easier, you increase your odds of being shortlisted.

A few practical mistakes I see all the time:

Vague titles.
If the title says something generic, it gets ignored. Be clear and specific.

No context.
Don’t assume people know what they’re looking at. A short description explaining the project, your role, and the outcome goes a long way.

Random uploads.
Just because something looks polished doesn’t mean it supports your target role.

Outdated content.
If your best work is from 3 years ago and nothing has been refreshed, it quietly signals stagnation.

If you’re job searching right now, I’d ask yourself:

If a recruiter only looked at my Featured section for 10 seconds, would they understand the kind of roles I should be considered for?

That’s the standard.

I’m a big believer in using LinkedIn real estate strategically. Your headline gets attention. Your About section builds the story. Your Featured section provides the evidence.

That combination is what turns a profile from informative into convincing.

If your Featured section is empty, this is an easy win. If it’s already there, audit it like a recruiter would:

Is it relevant?
Is it current?
Is it easy to understand in seconds?
Does it support the role you want next?

Most people don’t need a complete LinkedIn rewrite.

They need better positioning of the proof they already have.

...
#jobsearch#careergrowth#portfoliotips#personalbranding#linkedinprofile#recruitingtips
#jobsearch#careergrowth#portfoliotips#personalbranding#linkedinprofile#recruitingtips
Like
Dislike

27

7

Juan Reyes
Juan Reyes

seen this exact post 100 times on linkedin already

Sophia Walker
Sophia Walker

have you actually updated yours based on any of them

Add a comment...

User avatar
Danielle Collins
November 15251

SPICED for Better ICPs

Most teams don’t actually have an ICP.

They have a list of firmographics.

“VP at a 200–1000 employee SaaS company.” “Uses Salesforce.” “Raised a Series A.”

That’s not an ICP. That’s a filtering layer.

What actually separates high-value customers from noise is whether you understand the buying context: what’s happening in their business, what pain is urgent enough to act on, what the cost of inaction is, and who can actually move budget.

That’s why I like the SPICED framework so much.

It forces a team to move from guessing to pattern recognition:

  • Situation — what’s true in their world today?
  • Pain — what is broken enough to matter?
  • Impact — what is that pain costing them?
  • Critical Event — why now?
  • Economic Buyer — who owns the budget?
  • Decision Criteria — how will they choose?

Simple framework. Big leverage.

What I’ve seen over and over is that most early-stage teams overweight the top of the funnel and underinvest in customer understanding. They’ll debate channels, outbound copy, SDR productivity, CAC, and conversion rates — all important — while still targeting an audience that doesn’t have enough pain to buy.

That’s a recipe for inflated pipeline and weak win rates.

If your ICP is real, it should improve the metrics that matter: win rate, sales cycle length, ACV, expansion potential, and retention.

If it doesn’t move those, it’s probably not an ICP. It’s just segmentation theater.

The part of SPICED that I think is most underused is Impact.

A lot of teams can identify pain at a surface level: “We waste time.” “Our process is manual.” “Reporting is hard.”

But pain without quantified impact rarely creates urgency.

The moment you can tie the problem to something economic — missed revenue, slower ramp, higher churn, more headcount, lower productivity, delayed launches — the conversation changes. You stop selling a “nice-to-have” and start mapping to a budgeted problem.

That matters even more in this SaaS market, where buyers are scrutinizing spend harder, CFOs are more involved, and every new tool gets compared against consolidation pressure. In a lower-multiple environment, efficient growth wins. And efficient growth starts with selling to customers who have a clear, expensive problem.

I’d also argue Critical Event is where a lot of pipeline forecasting breaks.

Teams ask, “Do they like the product?” They should be asking, “What event makes this a Q4 priority instead of a someday project?”

Budget cycle. Board pressure. New executive hire. Compliance deadline. A broken implementation. A competitor forcing a response.

Without a real trigger, deals stall. Not because the product is bad, but because the timing isn’t real.

And then there’s the classic trap: great champion, wrong buyer.

If you don’t identify the Economic Buyer early, you can have perfect demos, strong multi-threading, and still lose momentum the minute procurement or finance enters the picture. I’ve seen this especially with founder-led sales teams — they mistake enthusiasm for authority.

They’re not the same.

What I like most here is that SPICED isn’t just a sales qualification tool. It’s a company learning system.

When you capture this consistently in the CRM, you create a feedback loop across go-to-market:

Marketing gets sharper positioning. Sales qualifies faster. CS understands desired outcomes earlier. Product sees recurring pain patterns across segments. Leadership can refine the ICP based on actual conversion and retention data, not opinions.

That’s the unlock.

The best ICPs are not written in a Notion doc and forgotten. They’re continuously earned from closed-won, closed-lost, expansion, and churn data.

If I were tightening an ICP tomorrow, I’d ask:

  • Which customers have the strongest pain and highest measurable impact?
  • Which ones had a clear critical event when they bought?
  • Which buyer persona actually controlled budget?
  • Which deals closed fastest and expanded later?
  • Which “good-fit” accounts looked right on paper but never truly had urgency?

That exercise usually tells you more than another quarter of broad prospecting.

My bottom line:
Firmographics tell you who could buy. SPICED helps you understand who is most likely to buy now, buy big, and stay.

And in B2B SaaS, that difference is everything.

Most teams don’t actually have an ICP.

They have a list of firmographics.

“VP at a 200–1000 employee SaaS company.” “Uses Salesforce.” “Raised a Series A.”

That’s not an ICP. That’s a filtering layer.

What actually separates high-value customers from noise is whether you understand the buying context: what’s happening in their business, what pain is urgent enough to act on, what the cost of inaction is, and who can actually move budget.

That’s why I like the SPICED framework so much.

It forces a team to move from guessing to pattern recognition:

  • Situation — what’s true in their world today?
  • Pain — what is broken enough to matter?
  • Impact — what is that pain costing them?
  • Critical Event — why now?
  • Economic Buyer — who owns the budget?
  • Decision Criteria — how will they choose?

Simple framework. Big leverage.

What I’ve seen over and over is that most early-stage teams overweight the top of the funnel and underinvest in customer understanding. They’ll debate channels, outbound copy, SDR productivity, CAC, and conversion rates — all important — while still targeting an audience that doesn’t have enough pain to buy.

That’s a recipe for inflated pipeline and weak win rates.

If your ICP is real, it should improve the metrics that matter: win rate, sales cycle length, ACV, expansion potential, and retention.

If it doesn’t move those, it’s probably not an ICP. It’s just segmentation theater.

The part of SPICED that I think is most underused is Impact.

A lot of teams can identify pain at a surface level: “We waste time.” “Our process is manual.” “Reporting is hard.”

But pain without quantified impact rarely creates urgency.

The moment you can tie the problem to something economic — missed revenue, slower ramp, higher churn, more headcount, lower productivity, delayed launches — the conversation changes. You stop selling a “nice-to-have” and start mapping to a budgeted problem.

That matters even more in this SaaS market, where buyers are scrutinizing spend harder, CFOs are more involved, and every new tool gets compared against consolidation pressure. In a lower-multiple environment, efficient growth wins. And efficient growth starts with selling to customers who have a clear, expensive problem.

I’d also argue Critical Event is where a lot of pipeline forecasting breaks.

Teams ask, “Do they like the product?” They should be asking, “What event makes this a Q4 priority instead of a someday project?”

Budget cycle. Board pressure. New executive hire. Compliance deadline. A broken implementation. A competitor forcing a response.

Without a real trigger, deals stall. Not because the product is bad, but because the timing isn’t real.

And then there’s the classic trap: great champion, wrong buyer.

If you don’t identify the Economic Buyer early, you can have perfect demos, strong multi-threading, and still lose momentum the minute procurement or finance enters the picture. I’ve seen this especially with founder-led sales teams — they mistake enthusiasm for authority.

They’re not the same.

What I like most here is that SPICED isn’t just a sales qualification tool. It’s a company learning system.

When you capture this consistently in the CRM, you create a feedback loop across go-to-market:

Marketing gets sharper positioning. Sales qualifies faster. CS understands desired outcomes earlier. Product sees recurring pain patterns across segments. Leadership can refine the ICP based on actual conversion and retention data, not opinions.

That’s the unlock.

The best ICPs are not written in a Notion doc and forgotten. They’re continuously earned from closed-won, closed-lost, expansion, and churn data.

If I were tightening an ICP tomorrow, I’d ask:

  • Which customers have the strongest pain and highest measurable impact?
  • Which ones had a clear critical event when they bought?
  • Which buyer persona actually controlled budget?
  • Which deals closed fastest and expanded later?
  • Which “good-fit” accounts looked right on paper but never truly had urgency?

That exercise usually tells you more than another quarter of broad prospecting.

My bottom line:
Firmographics tell you who could buy. SPICED helps you understand who is most likely to buy now, buy big, and stay.

And in B2B SaaS, that difference is everything.

...
#growth#startups#sales#saas#spiced#icp#founders#revops#b2bsaas#gtmmarket
#growth#startups#sales#saas#spiced#icp#founders#revops#b2bsaas#gtmmarket
Like
Dislike

27

11

Gloria Sanders
Gloria Sanders

this is gold

Martha Mitchell
Martha Mitchell

any actual results to back this up though

Add a comment...

For you

Charles Ramos's post cover
Brandy Lampinen's post cover
Herbert Oliver's post cover
Eugene Hansen's post cover
Tracey Snyder's post cover
Raul Toro's post cover
Michelle King's post cover
Ben Black's post cover
Denise Fisher's post cover
Charles Ramos's post cover
Eugene Hansen's post cover
Herbert Oliver's post cover
Michelle King's post cover
Brandy Lampinen's post cover
Tracey Snyder's post cover
Ben Black's post cover
Charles Ramos's post cover
Michelle King's post cover
Herbert Oliver's post cover
Brandy Lampinen's post cover
Eugene Hansen's post cover
Brandy Lampinen's post cover
Charles Ramos's post cover
Herbert Oliver's post cover
Eugene Hansen's post cover