Skip to content
Imagine

Launch week: posts from the whole team, then the engagers

Plan a post from each person on the team for launch week, each from their own angle: the founder's why, the engineer's how, the customer's result. After the posts are live, match the engagers across all of them to your ICP and CRM, and message the buyers with a question about their situation. The Imagine AI agent drafts every post in each person's voice, with the graphic, and the follow-ups for approval.

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're about to launch.

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're launching a product, a feature or a raise.
  • Only the founder posts about launches today.
  • Launch posts get likes but no conversations.
Launch week
Fig. 01: Launch week, then the engagers, 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

Engages for you

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

[04]Used in this play

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.

[05]Used in this play

Works from your content filesystem

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

[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]On

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.

[08]On

Turns what you have into posts

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

[09]On

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.

[10]On

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.

[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
  • The launch brief or doc.
  • Who on the team posts, and their angle.
  • Your ICP and CRM, for the follow-ups.
Files/Imagine AISend to agent

launch-week-engagers.md

Save

Step 1 · Pick an angle per person

  • The founder's why, the builder's how, the customer's result. Different angles reach different networks.

Step 2 · Draft every post

  • Each post in that person's voice with its graphic, spread across the week so they don't compete.

Step 3 · Approve and publish

  • Each person approves their own post before it goes out.

Step 4 · Message the engagers

  • After the posts are live, ICP engagers across every post matched to your CRM and messaged with a question.

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

Anatomy of a launch post

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

Files/Imagine AISend to agent

launch-post.md

Save

Outline

  • 1The problem, from this person's seat.
  • 2What shipped, in one line.
  • 3One image or a short multi-image post that shows it.
  • 4A question for the reader, not a link in the post.

Example from the run above

  • Monday, founder: Why we built this. We kept seeing teams post every day and still not know which posts brought in deals...
  • Tuesday, engineering: How the agent decides what to post, in 4 images. The hard part wasn't the writing...
  • Wednesday, customer: "We went from 2 posts a month to 3 a week." What changed for one team, in their words...

Avoid

  • Everyone resharing the company post with "so proud".
  • All posts on the same day.
  • No follow-up with the people who engaged.

Measure

  • Reach across all team posts, not just the company page.
  • ICP engagers across the week.
  • Conversations started from the follow-ups.

Fig. 03: The outline, part by part.

Join the high-growth companies already building with Imagine AI

Questions teams ask first.