Nabil Asofi

Library / LLM API

Launch Asset Kit

One launch input, every asset out — announcement, changelog, email, social variants, and the sales one-liner.

Setup time
35 min
Stack
LLM APIGoogle Sheetsn8n
Replaces
writing the same launch five times in five registers and getting it slightly different each time

What it does, in order

Launch Asset Kit — pipeline of 5 steps Pipeline of 5 steps: 1. Take the launch input (Google Sheets); 2. Fix the core claim (LLM API); 3. Generate the asset set (LLM API); 4. Check cross-asset consistency (LLM API); 5. Queue for approval (n8n). 01 Take the launch input Google Sheets 02 Fix the core claim LLM API 03 Generate the asset set LLM API 04 Check cross-asset consistency LLM API 05 Queue for approval n8n Launch Asset Kit — pipeline of 5 steps Pipeline of 5 steps: 1. Take the launch input (Google Sheets); 2. Fix the core claim (LLM API); 3. Generate the asset set (LLM API); 4. Check cross-asset consistency (LLM API); 5. Queue for approval (n8n). 01 Take the launch input Google Sheets 02 Fix the core claim LLM API 03 Generate the asset set LLM API 04 Check cross-asset consistency LLM API 05 Queue for approval n8n
5 steps. The final node is the artifact you end up with.

What this does

You write the launch once — what changed, who it is for, what it makes possible — and the workflow produces the set: announcement post, changelog entry, launch email, three social variants, and the single sentence a salesperson would actually say.

Every asset comes from the same input and the same product context, so the claim does not drift between the blog post and the email. Drift is what makes a launch feel bigger than the product.

What you get

  • The generator config and the per-asset prompts
  • The shared-claim rule, enforced in the prompt: one core promise, restated at different lengths
  • A consistency check that compares the generated assets against each other and flags contradictions
  • Output shaped for Google Sheets, so each asset is a row you can edit and approve

What it replaces

Writing the announcement, then the changelog, then the email, then three social posts — five passes over one idea, each pass slightly less accurate than the last.

Honest limits

It will not make a small change sound important, and it should not. If the honest version is “we fixed the export bug”, the assets will say that. Ship that rather than asking the workflow to dress it up.

It cannot know what you have not told it. A launch email that promises something the product does not do is a support ticket with a subject line.