Product launch campaign

Produces a dated launch sequence the person approves in one table, then written, checked and scheduled post by post, with the launch-day moment on an exact time. Without scheduling rights it produces the same sequence as drafts waiting in ProPost.

Before you start

1. get_account: time zone, AI drafts left, weekly cap, autonomy. A launch is dense; the weekly cap may be the binding limit.
2. list_channels: pick the channels that carry the launch; note max_length, image and video requirements, needs_reconnect, queue_paused. Google Business, Instagram, Pinterest and TikTok need media.
3. list_personas: the company voice should write launch copy. If the channels are not on it, suggest propost-company-brand-voice first.
4. list_posts with status: "scheduled" over the launch window (from and to): don't collide with what's already going out.
5. suggest_posting_times per main channel: the launch-day slot and the supporting slots.

Workflow

1. Pin the facts. Ask in one message: what launches, the exact launch date and time and time zone, the one-sentence promise, who it is for, the call to action and link, price or availability if public, what is embargoed until launch, real proof that exists (beta users who agreed to be named, a real number, a review that is public). Anything missing becomes a [placeholder], never an invention.
2. Draft the sequence as a table. Columns: when (date, time, offset), phase, channel(s), angle, media, AI draft or own text. Default shape for a 3-week launch (compress or stretch to fit; see references/launch-day-checklist.md for the day itself):

Say how many AI drafts the plan uses (one per distinct idea; channels sharing a voice share a draft). Mark which posts need a visual.

1. Get a yes on the table, including exact times. Convert dates to ISO with the time zone offset from get_account.
2. Write. Own text from the person: create_draft. Otherwise generate_draft with an idea that states the angle, the promise and one concrete detail. Put all channels for that beat in channel_ids so the versions are linked (same group). Use per_channel or update_post to tailor: LinkedIn gets the story and the "why", X the sharpest line plus link, Instagram a caption that works under the image, Google Business the practical "now available at...". Use copy_post_to_channel to carry a finished post to one more channel.
3. Visuals. Announcement and proof posts should have one. attach_image with image_svg (a designed card: 1200x627 for LinkedIn and X, 1080x1080 or 1080x1350 for Instagram, with the product name, one line, no tiny text) or image_url of the real product screenshot (preferred when it exists). apply_to_linked defaults to true; set it false when sizes differ per network. A video: attach_video with a public video_url, or start_video_upload then PUT then finish_video_upload.
4. Check every post with check_post; fix everything reported.
5. Schedule (schedule level and up): schedule_post with post_id and scheduled_at for fixed beats (teaser dates, L-day, the follow-ups). The launch-day post gets its exact time; use add_to_queue only for deep dives that have no fixed moment. Respect the weekly cap: schedule in priority order (announcement first, recap last) and leave the rest as drafts if weekly_limit hits.
6. Report as a timeline: what goes out when and where, what's still a draft, what needs the person (screenshots, embargo confirmation, a real quote). Never publish_now as part of a plan. If the person wants the announcement published at the moment of launch by hand, they or you (with an explicit yes and at publish level) do it from the checklist.

Drafts-only fallback

At drafts level, do steps 1-6 and stop. Create every post as a draft, put its intended time in your report, and tell the person the whole sequence is waiting in ProPost to approve and schedule. Don't call schedule_post. Offer a one-line table they can copy: time, channel, first line.

Writing guidance

• The teaser sells the problem, not the product. "Every Monday we spent two hours reconciling invoices. We were tired of it." is a teaser. "Big news coming!" is not.
• The announcement answers four things in the first screen: what it is, who it is for, what it does for them, where to get it. Link once.
• Deep dives teach one thing each, with a concrete before and after from the product itself. Don't repeat the announcement.
• Proof must be real: named only with consent, numbers only from the person, reviews quoted exactly and only if public. No "customers love it" without evidence.
• Follow-up posts quote actual questions or feedback, answered plainly. Admit what the product does not do yet.
• Don't announce what isn't shipped. If availability is staged, say who gets it when.

Guardrails

• Embargo: don't schedule any post that reveals the product before the agreed time; check the teaser copy against it.
• No invented numbers, testimonials, partner logos or comparisons to named competitors.
• Don't exceed the weekly cap or AI drafts left; plan inside them.
• Don't put the launch on a paused or reconnect-needed channel.
• Scheduling a table the person approved is fine; anything else is not.

If something fails

• quota_exceeded: write remaining posts with create_draft.
• weekly_limit: keep the lower-priority posts as drafts, say which.
• time_in_past / time_too_far: the launch date has passed or is over a year away; confirm the date.
• image_required: attach an image before scheduling.
• autonomy_limit: stay in drafts-only mode as above.
• Anything else: see ../CONVENTIONS.md.