Skip to content
Vanthis

ResourcesContent

Founder-Led Content to Pipeline

Turn lessons from real work into posts on LinkedIn and X that start conversations with buyers, and route the qualified ones to meetings.

Use in Vanthis

19 steps3 decisions+1

Knowledge baseKnowledge baseKnowledge baseClaudeKnowledge baseLinkedInX (Twitter)LinkedInHubSpotHubSpotLinkedInHubSpotKnowledge base
Shown with

This playbook turns the lessons from your real work into posts on LinkedIn and X, and the people who engage with them into conversations and booked meetings, with a record of which post started each one.

Who does what

  • Author the founder or expert, owns the point of view, approves every post, replies and holds the conversations.
  • Content Editor a marketer, editor or ghostwriter, runs the weekly interview, shapes the drafts, schedules the posts and records the signals.
  • GTM Lead owns the pillars against the ICP, the fit rules and the cycle review.
  • Sales Owner the founder, an AE or an SDR, takes the meeting and owns the CRM record.
  • Agent Claude or ChatGPT, drafts the cycle's posts from the idea bank with the founder-post-drafting skill. It never publishes or schedules a post.

What you need

In a solo founder team, the Author, the GTM Lead and the Sales Owner are the same person. Bring:

  • An author with weekly time for capture, replies and conversations.
  • ICP personas, and ideally a TAM map with tiers from ICP & TAM Mapping.
  • A knowledge base for notes and drafts, such as Obsidian, Notion or Google Drive.
  • A CRM, HubSpot or Salesforce, and a booking form that can ask a required free text question.
  • A scheduler, Buffer or Typefully, or LinkedIn's own scheduler, and an agent for the drafts.

Some answers are yours to set before the first cycle:

  • How many posts per cycle the author can sustain with a real source behind each.
  • LinkedIn, X or both, depending on where your buyers read and comment.
  • Who writes: the author, an editor from interviews, or AI from transcripts, with the author approving.
  • Which engagement counts as a signal, and how long unconverted signals are kept.

1Choose topics

  • Weekly content cycle starts
  • Turn buyer pains into topics

Each cycle starts with its period, its author and the platforms it covers. Notes and drafts stay in your knowledge base. Last cycle's review is open, and the time for capture, writing and daily replies is in the author's calendar.

The GTM Lead and the Author then turn buyer problems into three or four pillars:

  • Each pain is written in the buyer's own words, from a call, a ticket or a loss reason.
  • Each pillar has a stance a reasonable person could disagree with, backed by evidence.
  • One pillar says plainly what the company does, for whom and how to start.
  • Topics that started conversations last cycle stay, and topics that drew only non fit engagement go.

2Write from real work

  • Capture material from real work
  • Idea bank
  • Draft posts in your voice
  • Post drafts
  • Ready to publish?

Posts come from real work. The Author collects stories, questions and evidence from the week's calls, decisions and mistakes in one shared bank, often as a short voice memo right after a call, or in a weekly interview with the editor. Customer names, numbers and deal details are flagged when they need permission or anonymising.

The Content Editor drafts the cycle's posts in one session. Each post carries one idea, one buyer pain and one story, leads with the hook and the stance, and usually ends with a question or a view to react to. X gets a shorter version or a thread, and LinkedIn a single post. AI can turn transcripts into outlines, while the wording and the stories stay the author's.

Before anything is scheduled, the Author reads each draft aloud and approves it:

  • Every number or claim links to its source, or it goes.
  • Flagged customer details have permission or are anonymised.
  • Employees posting about the product state their relationship in the post.
  • Synthetic or manipulated images and video are labelled.

3Publish and reply

  • Publish on LinkedIn
  • Publish on X
  • Reply to comments and join threads

Posts go out from the author's personal profile, at times the author can reply in the hours after. LinkedIn's own scheduler works 10 minutes to 3 months ahead. Buffer or Typefully keep one queue for LinkedIn and X, with limits to check:

  • Buffer cannot post PDF documents to LinkedIn personal profiles.
  • Buffer warns that LinkedIn may suspend accounts that share duplicate content.
  • Typefully merges an X thread into one LinkedIn post and does not support mentions of people.

The Author then answers every real comment personally, with something specific, and asks a follow up question where a commenter describes their situation. The Author also comments on relevant threads by buyers and peers, found with saved searches or X Lists. LinkedIn bans bots, auto replies and engagement pods, and on X an automated reply needs the user to engage first.

4Start conversations

  • Note engaged buyers as signals
  • Signal list
  • Does the person fit?
  • Start a genuine conversation
  • Is there a real need?

The Content Editor notes the people whose engagement shows real interest: comments that describe a problem, questions, inbound DMs and repeated engagement count before single likes. Signals are recorded by hand, from notifications, the post's own lists or Sales Navigator alerts, and never scraped. Each signal keeps only the name, profile link, company, what they said, when, the account's tier and a deletion date.

The first decision asks whether the person fits:

  • The company passes the ICP hard filters or is in the TAM map.
  • The role matches a target persona or is close to one.
  • The account is no current customer or open deal owned by someone else.
  • An unknown role or company counts as not a fit for now, and the public thread goes on.

For a fit, the Author continues privately with one specific question that refers to what the person said, with no pitch and no meeting request in the first message. In Germany a DM counts as electronic mail, so advertising waits until the person asks. Every message is written and sent by hand, and a no ends the conversation at once.

The second decision asks whether there is a real need: the person describes the problem in their own words, works on it now or soon, can decide or influence, and agrees to or asks for a call. A conversation without a current need stays open, with no follow up pitch.

5Book and learn

  • Book the meeting and log source
  • Content-sourced meeting booked
  • Review which topics start conversations
  • Cycle reviewed

The Sales Owner books the meeting in the thread the person already uses and records on the CRM opportunity which post and pillar started it. The booking form asks where the person heard of you, as a required free text field, because a CRM's original source misses deals that began in a feed or a DM.

At the end of each cycle the GTM Lead reviews the posts by the conversations and meetings they started, with reach only as a tie breaker:

  • Native metrics: LinkedIn keeps post demographics for 180 days, and X shows non public metrics for the author's own posts of the last 30 days.
  • The free text answers: how many name the author or a post, and which topics they name.
  • Next topics: what to keep, change or drop.
  • Expired signals that never became conversations are deleted.

Both early exits, not a fit and not now, lead to this review, so every cycle closes with one, with or without a meeting.

Compliance checks

The playbook carries checks for LinkedIn's and X's terms and for the EU, Germany and the US. Three examples:

  • Recording a named engager is processing personal data: keep only what the next steps need, set a deletion date and send the privacy notice at first contact or within one month.
  • In Germany, OLG Hamm treats messages via LinkedIn and similar services as electronic mail, so advertising by DM needs prior express consent.
  • In the US, employees posting about their employer's product disclose the relationship in the post.

They are checks for whoever owns privacy on your team and no legal advice.

Run it in Vanthis

Pick your CRM, scheduler and agent above the Canvas, and the steps and guides on this page follow your choice. In Vanthis the playbook becomes your own Motion with that stack. Your agent, Claude or ChatGPT, asks which tools your team uses, then works through it step by step, and the Author approves every post before it goes out. To run it somewhere else, download it as Markdown or as an agent skill.

Use in Vanthis