WEBVTT

00:00:00.256 --> 00:00:03.883
Start with one book one intended reader and one destination

00:00:04.096 --> 00:00:04.992
you want that reader to visit

00:00:05.547 --> 00:00:08.747
LaunchCommand is a browser app for planning a campaign and

00:00:08.789 --> 00:00:09.728
preparing channel copy

00:00:10.283 --> 00:00:12.075
It does not publish posts automatically

00:00:12.526 --> 00:00:15.811
This guide uses prepared workspace examples to show the decisions

00:00:15.982 --> 00:00:17.006
from brief to schedule

00:00:17.944 --> 00:00:19.267
Begin with a workload you can maintain

00:00:19.779 --> 00:00:21.571
rather than filling every possible channel

00:00:22.109 --> 00:00:22.962
Add the reader promise

00:00:23.517 --> 00:00:24.200
supported tropes

00:00:24.840 --> 00:00:25.394
important dates

00:00:25.992 --> 00:00:28.765
available artwork or excerpts and spoiler boundaries

00:00:29.320 --> 00:00:31.496
Use your real book page or signup destination

00:00:32.136 --> 00:00:34.738
Review the proposed strategy before asking for a large batch

00:00:34.781 --> 00:00:35.037
of content

00:00:35.946 --> 00:00:38.250
Confirm that the campaign describes the book you have written

00:00:38.506 --> 00:00:41.663
and that every claimed asset or offer actually exists

00:00:42.516 --> 00:00:44.863
Choose the channels and pieces per week you can produce

00:00:45.525 --> 00:00:48.426
Review the dated tasks against your release calendar and other

00:00:48.554 --> 00:00:48.938
commitments

00:00:49.578 --> 00:00:51.882
A task should tell you what to make whom it

00:00:51.925 --> 00:00:53.290
serves and where it leads

00:00:53.973 --> 00:00:56.704
If the schedule is too crowded reduce the workload before

00:00:56.874 --> 00:00:57.813
generating more copy

00:00:58.382 --> 00:01:00.772
Keep the useful sequence of work even when you shift

00:01:00.857 --> 00:01:01.113
the dates

00:01:02.094 --> 00:01:05.636
Generate or develop the channel specific content in manageable batches

00:01:06.259 --> 00:01:09.630
Check each piece against the approved brief then replace placeholders

00:01:09.800 --> 00:01:10.824
with real links and details

00:01:11.720 --> 00:01:14.920
Keep your voice consistent across the campaign without posting identical

00:01:15.048 --> 00:01:15.688
text everywhere

00:01:16.222 --> 00:01:17.160
If work is interrupted

00:01:17.630 --> 00:01:21.299
use the saved recovery workflow to continue unfinished content rather

00:01:21.384 --> 00:01:22.963
than starting another disconnected plan

00:01:23.603 --> 00:01:26.163
You can use LaunchCommand's copy and calendar on their own

00:01:26.784 --> 00:01:29.259
If a task needs a slideshow and you have TeaserPro

00:01:29.344 --> 00:01:29.515
access

00:01:30.155 --> 00:01:33.355
use the optional handoff to develop editable slides and visuals

00:01:33.483 --> 00:01:33.653
there

00:01:34.165 --> 00:01:37.792
Access and provider costs remain separate unless your membership includes

00:01:37.835 --> 00:01:38.475
the relevant tools

00:01:39.245 --> 00:01:42.999
Across different sites follow the file based handoff instructions instead

00:01:43.127 --> 00:01:45.175
of assuming the projects synchronize automatically

00:01:45.997 --> 00:01:47.448
Before scheduling in your own services

00:01:48.045 --> 00:01:48.514
check dates

00:01:49.026 --> 00:01:49.496
destinations

00:01:50.178 --> 00:01:51.031
required assets

00:01:51.501 --> 00:01:54.018
spoilers and the action requested in each post

00:01:54.701 --> 00:01:56.919
Save the plan and a recoverable project copy

00:01:57.457 --> 00:01:58.225
After publication

00:01:58.822 --> 00:02:01.724
keep actual results and observations so you can choose what

00:02:01.766 --> 00:02:02.662
to repeat or change

00:02:03.260 --> 00:02:05.820
The finished result is a manageable campaign you understand

00:02:06.289 --> 00:02:09.062
with reviewed copy and a clear next production step for

00:02:09.105 --> 00:02:09.617
every task