skills/customer-launch-kit/SKILL.mdView on GitHub
This applies in the weeks before a launch. It produces customer voices on launch day without a single uncleared name.
Before you start
This skill works on its own. If the person has their own marketing brain (or any folder of context files about their company), read the files listed under reads in the header first and cite them for every fact. If they do not have one, do not look for one: ask for the two or three facts this play needs and go on. Never invent a fact; a blank is a question for the person.
Tools: this play speaks in verbs (check the CRM, pull the call, schedule the post). TOOLS.md at the root of this repo lists the tools recommended for each verb. The company’s own 1-context/stack.md wins when it exists. No tool is required; a spreadsheet and a mail client cover most of it.
The play
- Read the context (see Before you start). Pull the customer list from the CRM with health status; ask success to mark who is in a good place to be asked.
- Run
permission-checkon each candidate for the pieces planned (a post, a quote, a logo, a video clip). Keep only cleared or clearable customers. - Write the ask in the success owner’s voice: what is launching, what we are asking (share a post, give a quote, be named), what they get (early access, a feature in our channels), and the date. One ask per customer, sent by the person who owns the relationship.
- Draft the ready-to-post copy per customer so saying yes costs them nothing. Keep it in their voice, not the company’s; make it easy to edit.
- Collect quotes with
proof-captureso they enter the tracker with their permission status the day they arrive. - Build the day-of schedule: who posts when, who reshares, who thanks them.
- After launch day, send the thank-you and log which customers took part, for the next ask.
What good looks like
- The best operator asks fewer customers with a specific, easy request than many customers with a vague one. A customer who gets a drafted post and a date usually says yes.
- The mediocre version blasts the base with “please share our news” and gets nothing.
- Good output is a short list of customers, each cleared, each with a draft, each asked by the person they know.
Rules
- MUST clear every customer through
permission-checkfor each piece and channel before the ask. - MUST route every ask through the relationship owner in success.
- NEVER draft a customer’s post with a claim they did not state.
- NEVER ask a churn-risk or churning customer.