Skip to content
Imagine

The ICP list post loop

Pick 5 to 10 people in your ICP, connect with them, publish a positive list post that features each one with a number, comment on their posts that week, then message them with something useful about their own data and a short call ask. The Imagine AI agent runs every step on LinkedIn with your approval and matches everyone who engages to your CRM.

Last updated
Oct 20, 2026
Written by
Sky Yang, Co-founder and CEO
How we wrote this
Written from how the Imagine AI agent runs this play on LinkedIn, with approval.
When it runs

You want conversations with 5 to 10 specific accounts.

One prompt. The agent runs the play.

The agent has its own computer and browser, so it finds the people and the news itself. It drafts every comment, connection note and message, and you approve what goes out. Use it when:

  • You want conversations with specific accounts, not just reach.
  • You have data or a point of view that makes people look good.
  • Cold messages to the same people are getting ignored.
Fintech founders list post
Fig. 01: The ICP list post loop, run by the agent. You approve before anything goes out.

The skills behind this play.

The agent has its own computer and browser, so it does the legwork itself. Every skill is on for every play; these are the ones this play leans on.

[01]Used in this play

Writes in each person's voice

Drafts for the company page, founders, executives and employees from each person's best posts. Imagine AI started as the operating system for ghostwriting teams, so sounding like you is the core of the product.

[02]Used in this play

Designs the graphics

Multi-image posts, infographics and visuals from your brand kit, made in its own sandbox, with the right people and companies tagged.

[03]Used in this play

Has its own computer and browser

It does the legwork itself: finds the people, checks job changes, launches and funding news, reads the sources and fact-checks claims before anything ships.

[04]Used in this play

Engages for you

Comments, connection requests and messages on LinkedIn, aimed at the people your posts pull in who match your ICP.

[05]Used in this play

Knows what works

Reads the public benchmark of 1,000+ B2B companies and tracks your competitors, so post types and formats follow your industry's data.

[06]Used in this play

Finds the buyers in your audience

Matches everyone who engages to your ICP and hands sales a worked list every week.

[07]Used in this play

Maps content to revenue

Connects to HubSpot or Salesforce and traces each closed deal back to its first content touch: post, person, deal stage moves.

[08]On

Runs one calendar for the team

Plan launches, sequence posts, schedule comments and edit together. Approvals sit with each person or route through one owner.

[09]On

Works from your content filesystem

Positioning, brand kit, decks, campaigns and compliance rules in one place it reads before every draft, remembered across threads.

[10]On

Turns what you have into posts

Events, podcast episodes, videos, decks and call notes become a week of posts across the team.

[11]On

Plugs into your stack

Engager data over API and webhooks, and the benchmark over MCP for your own agents.

What the data says

Across the whole benchmark, as a multiple of the account's own typical post.

  • Multi-image1,115 posts2.1x
  • Image2,984 posts1.43x
  • Video1,603 posts1.18x
  • Document324 posts0.89x
  • Text Only3,192 posts0.71x
Fig. 02: Formats, dashed line at 1x. Source: Imagine AI Benchmark (benchmark.useimagine.ai), public aggregates, data through Oct 20, 2026. Lift = a post type's reactions as a multiple of each author's own typical post (geometric mean), so big accounts do not skew it. CC BY 4.0.

Step by step

The playbook lives as a file the agent reads. Edit it once and every run follows it.

What you need
  • Your ICP: industries, roles, company size.
  • A source of numbers, like the benchmark or your own research.
  • Your CRM, so engagers are matched to accounts.
Files/Imagine AISend to agent

icp-list-post-loop.md

Save

Step 1 · Pick the list

  • 5 to 10 people your buyers already follow. The agent finds them and pulls company, role and one number for each, and can use your own tools, like Clay, through their API.

Step 2 · Connect first

  • Connection requests go out a few days before the post, with a one-line note about them, not you.

Step 3 · Post the list

  • A positive list post that features each person with one number and tags them. Only positive or neutral facts; never compare anyone down.

Step 4 · Comment where they are

  • That week, a specific comment on each person's latest post, so your name is familiar before you ask for anything.

Step 5 · Message with value

  • Once the post is live, a note with their own number, one question and a short call ask. No pitch. Everyone who engaged is matched to your CRM.

Fig. 02: The playbook as a file in your workspace.

Anatomy of the list post

The outline, what to avoid and how to measure it, in the file the agent drafts from.

Files/Imagine AISend to agent

list-post.md

Save

Outline

  • 1Hook: the most surprising line in the list.
  • 2One line per person: name, tag, one number.
  • 3What the people on the list have in common.
  • 4Where the numbers come from, in the first comment.

Example from the run above

  • 8 fintech founders who post every week, and the one number that stands out for each. @Sarah Chen: 3x her typical reach on hiring posts...
  • The part about pricing pages doing the selling is the one most teams skip. Saving this.
  • Hey Priya! You made the list this week. Your launch posts get 2x your usual reach, curious what you changed?

Avoid

  • Naming people to call them out.
  • A pitch in the first message.
  • Messaging before the post is live.

Measure

  • Accepted connection requests.
  • Comments and reshares from the people on the list.
  • Replies and calls booked from the notes.
  • Engagers matched to accounts in your CRM.

Fig. 03: The outline, part by part.

Join the high-growth companies already building with Imagine AI

Questions teams ask first.