Pillar guide · 8 min read

Buyers block pitches. They save teachers.

Nobody wakes up wanting a demo. They wake up wanting the problem to go away. Teach them how the problem works — and you become the person they call when they're ready to fix it. This is the playbook.

Chapter 01

The pitch tax

very time a buyer sees your name attached to a pitch, they pay a small tax — attention spent on a message they didn't ask for. Do it enough times and they stop opening. Do it once with real value and they save the post, screenshot it to their team, and remember your name the next time they need what you sell.

Sales orgs love to talk about "trust." Trust is not a vibe. It's the sum of every free thing a buyer got from you before they gave you anything back.

A pitch withdraws from the trust account. Teaching deposits. Most reps run overdrawn.
Chapter 02

Why teaching converts (and pitching doesn't)

A buyer visits LinkedIn to feel smarter, not to feel sold to. When your post makes them nod, screenshot, or forward, three things happen without you doing anything else:

  • Your name becomes 'the person who explained X well,' not 'that AE who won't leave me alone.'
  • The algorithm rewards saves and long dwell-time, so more of the RIGHT people see the post.
  • The DM you eventually send lands in an inbox that already trusts your judgement.
What teaching actually earns you
0–5×
Reply rate on earned DMs vs cold
0s
Avg dwell on a good teach post
0
Buyers who blocked you for teaching
Chapter 03

The 4 teach-formats you'll rotate forever

You don't need 50 post ideas. You need 4 formats and one specific buyer to write for. Rotate these and you'll never stare at a blank composer again.

01

The framework

What it is: A repeatable way you think about a problem — named and numbered.

"The 3 questions I ask before I send a proposal: 1) Who signs the invoice? 2) What breaks if this doesn't ship in Q1? 3) Who loses budget if it does?"

Why it works: Frameworks travel. Someone screenshots yours, sends it in Slack, and now three buyers have your name in their heads.

02

The teardown

What it is: You pick a common thing — a cold email, a demo, a pricing page — and show what's broken and why.

"I got this cold email yesterday. Here's the line that killed it, and the rewrite that would've made me reply."

Why it works: Concrete beats abstract. Teardowns get saved because they teach a rule the reader can apply on Monday.

03

The contrarian take

What it is: Something 'everyone knows' — but you disagree, and you can prove it.

"'Always be closing' is the reason your win rate is dropping. Buyers don't need urgency, they need certainty. Here's what to say instead."

Why it works: Agreement is invisible. Disagreement — backed with a reason — is what gets shared, argued with, and remembered.

04

The receipt

What it is: A real result, real numbers, real conversation. No screenshots of Stripe.

"A prospect ghosted me for 6 weeks. I sent one voice note referencing what she said on our first call. She replied in 14 minutes. Here's the note."

Why it works: Buyers trust stories with texture. 'We increased pipeline 40%' means nothing; 'she replied in 14 minutes' means everything.

Chapter 04

The one-useful-idea rule

Every post gets ONE useful idea. Not three. Not "here are 7 things I learned." One. If the reader can walk away and do exactly one different thing on their next call, the post earned its space in the feed.

This sounds obvious. It isn't. The reason most sales posts feel like corporate blog vomit is that reps try to prove they know a lot, instead of proving they can help with one thing. A specialist is memorable. A generalist is background noise.

If I remove the last three sentences of this post, does it still teach the one thing? If yes, remove them.
The 10-second post editor's rule
Chapter 05

When to actually pitch — the earned ask

Teaching without ever asking is a hobby, not a job. The move is the earned ask: a specific, low-friction invite, placed at a moment when you've clearly delivered value first.

In-post

One line at the bottom, and only sometimes: 'This is exactly what SelloWise automates — link in comments.'

In-DM

After a comment they left: 'Loved your take on X. If it's useful, I put together a 1-pager on how we solved Y — want me to send it?'

In-profile

Your headline and About do the pitching 24/7 so your posts don't have to.

Chapter 06

A weekly template you can copy today

Not a content calendar. A rhythm. Do this for four weeks and you'll have 12 posts, 40+ comments, and at least one inbound conversation you didn't have to cold-open.

When
What to do
Mon
Framework post. Name it. Number it.
Format 01
Wed
Teardown or contrarian take. Pick a fight worth having.
Format 02 / 03
Fri
A receipt. One real story from your week, with texture.
Format 04
Daily
5 substantive comments on ICP posts. 'Great post!' does not count.
The habit
Chapter 07

Frequently asked questions

If I'm not pitching, how do I get pipeline from LinkedIn?
The pitch happens in the DM, not the post. Teaching posts drive profile views and replies from your ICP; those become 1:1 conversations where you can ask a real qualifying question. The rule: earn the ask before you make it.
How often can I mention my product?
A rough 4:1 ratio works — four teaching posts for every one that mentions your product, and even that mention should be embedded inside a story or teardown, not a feature list. If your last five posts all name your company, buyers will scroll past the sixth.
Won't 'teaching' just help my competitors?
Only if what you teach is generic. Teach the way YOU solve a specific problem for a specific buyer, and the post becomes your unfair advantage — competitors either ignore it or badly copy it, and either way your name is on the original.
What if I'm not an expert yet?
You don't need to be the expert. You need to be a step ahead of your buyer. Every discovery call you took last week made you one step ahead of the next buyer with the same problem — write that down.
How long should a teaching post be?
Long enough to teach one thing, short enough that a busy VP finishes it in 45 seconds. Usually 900–1,300 characters. One idea, one example, one 'so what.'
How does SelloWise help?
It turns the notes from your calls, objections, and wins into teaching posts you'd have written yourself — if you had time. The blank composer is why most reps quit. SelloWise removes it.

Teaching posts, without the blank composer.

SelloWise turns your calls, objections, and hot takes into teaching posts you'd have written yourself — if you had time.

More short lessons in the SelloWise learning library.