Free for 30 days on Scale.Start free
Run10 steps3-4 weeks of prep, 5 days live, 1 week of follow-up

Run a launch week (5 daily drops)

A 5-day launch week that drives 3-5x the press attention of a single-day launch, sustains audience engagement Mon-Fri, and ships 5 distinct content artifacts that feed your evergreen library for the next 6 months.

Open in DockSee every step →

A 5-day launch week that drives 3-5x the press attention of a single-day launch

A 5-day launch week that drives 3-5x the press attention of a single-day launch, sustains audience engagement Mon-Fri, and ships 5 distinct content artifacts that feed your evergreen library for the next 6 months.

Spin up an agent for the heavy lifting

Drafts the daily drop content: announcement post, X thread, LinkedIn post, email blast, press copy.

10 steps, 0 official links, 4 agent prompts

Every external doc the agent needs to cite is pre-loaded into the workspace's Pointers table. No hunting for the right URL mid-draft.

What's inside

Pre-loaded so day one is execution.

5Surfaces
10Steps
4Agent prompts
6Tools mapped
Surfaces
  • tableSteps
  • tableDrops calendar
  • docLaunch week plan
  • tableEngagement log
  • docStatus
See every step, link, and prompt
How the loop works

Your agent works. Dock shows you what happened.

Open this template and you get a workspace seeded with an agent prompt. Connect your agent — Claude via our MCP, Cursor, your own setup — and it reads, drafts, and posts updates as it goes. You watch Dock for the latest.

  1. 01

    Connect your agent

    Claim an agent invite at trydock.ai/agent-invites — your agent gets an API key scoped to this workspace. Paste the key into Claude Desktop, Cursor, or any MCP client.

  2. 02

    Your agent reads the workspace

    The agent prompt at the top of the workspace tells your agent its role, the cadence to follow, and the surfaces to update. No extra setup — open Dock and your agent already knows what to do.

  3. 03

    Watch Dock for the latest

    Your agent posts to the Status surface after every meaningful action — newest at top. Wire the workspace's webhooks to Slack or email to get pinged in real time.

Wire it up · Claude Desktop

Add Dock as an MCP server in 30 seconds.

{
  "mcpServers": {
    "dock": {
      "command": "npx",
      "args": ["-y", "@trydock/mcp"],
      "env": {
        "DOCK_API_KEY": "<paste from /agent-invites>"
      }
    }
  }
}

Drop into ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or the equivalent on Windows / Linux. Restart Claude Desktop. Ask Claude:“Read trydock.ai/<org>/run-a-launch-week and follow the agent prompt.”

Full MCP setup guideOther agent clients (Cursor, custom MCP)
FAQ

Common questions on this template.

Is a launch week worth the production cost?
It depends. Launch weeks are 4-5x the production cost of a single-day launch. They're worth it when: you have 5 distinct shippable things, your audience is 1000+ engaged people (otherwise the week reaches the same audience repeatedly), you have a narrative arc that connects the 5 days. Without all three, run a stronger single-day launch and save the production cost for the next quarter.
What if Day 3 or Day 4 underperforms? Do we course-correct or stay the course?
Stay the course on the calendar; course-correct on the copy. The audience has trained itself to expect today's drop; skipping or merging drops breaks the rhythm. But you can refine the day-of copy: tighten the value prop, lead with a stronger hook, lean into the format that worked yesterday. The biggest mistake is accelerating Day 4-5 desperately to recover Day 3's miss.
Should each day's drop have its own URL or share the launch-week URL?
Both. The canonical launch-week URL (e.g., /launch-week-2026-q2) shows today's drop above the fold and stays as the archive. Each individual drop also gets its own URL (e.g., /launch-week-2026-q2/day-3) for SEO + sharing. Schema each as Article with datePublished so each indexes separately for long-tail search.
Should I email my whole list daily for 5 days?
Only if they opted in to the launch-week list specifically. Daily emails to your full list for 5 days drives 5-10% unsubscribes — the cost is lasting. The pattern that works: a launch-week-specific opt-in form ('get every drop in your inbox'), and a single 'launch week recap' email to the full list at the end of the week.
Can my AI agents help with the launch week?
Yes, especially for: drafting the daily X / LinkedIn / Bluesky / email content per day, drafting the per-day blog post outline, tracking the daily engagement log, drafting the post-week analysis. Posting and replying stay human; the agents draft and the humans ship. The launch-week scale (35+ pieces of content across 5 days) is exactly where agents earn their keep.
What does a launch week cost?
Tooling: ~$50-100/mo across Buffer, Resend, Plausible, Loom (mostly stuff you already have). Production: 3-4 weeks of team time for a small team (2-3 people). Press budget: 0 if you're doing organic only, $5-20k if you're running ad amplification on top of the organic week. The biggest cost is the team's energy across 5 consecutive launch days; budget recovery time after.
Related templates

More from Run

RunMixed
Launch on Product Hunt the right way

12-step plan from picking the launch date to shipping the post-mortem. Your agents draft the assets + run the 24-hour hunt log + flag every converting comment in real time.

RunMixed
Launch on Hacker News (Show HN guide)

10-step plan for landing on the HN front page with a Show HN. Real title rules, real comment-thread tactics, real survival guide.

RunMixed
Automate Instagram posting with your agents

10-step plan for a posting pipeline that drafts, queues, and ships 6-12 Instagram posts a week with agents drafting and a human approving.

Browse all Run templates →
Used by these teams · 1

Teams that run this template, with their full setup.

MarketingUse case

Campaigns that ship + the metrics next to them.

Campaigns table, briefs per campaign, performance data on the same row. Agents draft briefs, pull performance numbers, surface what's resonating so the calendar can adjust.

Open the use case

Open it. Hand it to your agent. Ship.

One click mints a fresh workspace in your org with the template body seeded. Your agents, your team, your edits from there.

Open in DockBrowse all templates →

About this template

Curated by the Dock team at . Every template is a real shared workspace we run with our own agents before publishing.

Reviewed regularly by the Dock team. Each playbook step links to the upstream tool's official docs so we can re-verify the rules as platforms change.