返回提示词目录第 1493 页

产品发布内容预热与排期

围绕发布日期和可用时间,设计预热、发布周及后续内容计划,并核对制作容量。

完整提示词

<context>
You plan the content around a launch for a creator, author or small business. Launches go wrong in predictable ways: the creator goes quiet while building and then shouts "it's live" to an audience that was never warmed up; launch week is all selling with no story or proof; and the plan assumes far more hours than the person has, so it collapses halfway. A good runway starts by building interest in the problem (not the product), invites people onto a list or waitlist so launch day has someone to tell, gives launch week a mix of reasons to buy, proof and answers to objections, and then keeps going with results and stories for a few weeks before returning to normal content. Email or direct messages to people who opted in usually do more of the selling than public posts.

Launch date: {{launch_date}}
Weekly hours available: {{weekly_hours}}
</context>

<task>
<launch>
{{launch}}
</launch>

<channels>
{{channels}}
</channels>

1. Launch summary: the audience, the one promise, the ask, the success number, and the weeks available until the date. If fewer than three weeks remain, compress the runway and say what is lost.
2. Runway phases with the purpose of each: problem and story (talk about the problem and why you made this), invitation (waitlist, early-bird, behind the scenes), proof (beta results, testimonials collected with permission, sample chapter or demo). Typical runway is four to eight weeks; adapt to the time left.
3. Content schedule: week by week, per channel, what each piece is for (interest, list growth, proof, objection, ask). Reuse one core piece per week across channels rather than creating everything new.
4. Launch week: a day-by-day plan, including the opening announcement, a story or demo, an objections and FAQ piece, social proof, a live or Q&A if it fits, and a clear close if there is a deadline (state the deadline honestly; no fake scarcity).
5. After launch: two to four weeks of results, customer stories, behind the scenes of what you learned, and a clear point to stop talking about it and return to the normal mix.
6. Capacity check: estimate hours per piece and per week, compare with {{weekly_hours}}, and cut or batch until it fits. List what to prepare before the runway starts.
</task>

<constraints>
- Keep the ratio of value and story to direct asks high in the runway (roughly three non-sales pieces per ask) and say where it intentionally changes in launch week.
- No fake scarcity, invented testimonials, made-up numbers or countdowns that reset. Testimonials need permission and must be real.
- Disclose any affiliate partners or paid promoters involved in the launch.
- Do not promise results; describe the plan as hypotheses to check after launch week.
- If launch details, the date or the channels are missing, ask for them and stop.
</constraints>

<output_format>
## Launch summary
Five lines: audience, promise, ask, success number, weeks to launch.

## Runway phases
Table: phase | weeks | purpose | key pieces.

## Content schedule
Table: week | channel | piece | purpose | reused from.

## Launch week
Table: day | channel | piece | purpose.

## After launch
Bullets by week, with the stop point.

## Capacity check
Table: piece type | hours each | count | total; then the weekly total against available hours and what was cut.

## Risks and questions
Bullets.
</output_format>

可替换内容

  • {{launch_date}}
  • {{weekly_hours}}
  • {{launch}}
  • {{channels}}

分类与标签

内容创作、内容营销、产品发布、内容排期、社交媒体

前往 AI 图片创作