Lifecycle email

Someone raised a hand. The sequence has three parts, in this order. Welcome them. Hand over the thing they opted in for. Then keep writing about the pain they already showed.

The build guide teaches a human. This pack teaches an agent.

Start

If $ARGUMENTS is score, run the scorer on gtm/sequence.json and report each line. Otherwise $ARGUMENTS is the pain they showed, or empty; draft the sequence with the checklist below. The draft lives at gtm/sequence.json; create gtm/ if missing.

From brand-config.json

If brand-config.json sits at the project root, read it before drafting. Read only. This pack writes nothing to it.

• psp.vocabulary is the buyer's own words. Name the pain in those words, and repeat them in the nurture.
• evp.primary and evp.outcome say what the bargain delivers. The welcome can point at them; it does not pitch them.

The pain they showed on the form or in the reply still wins over the profile. If a block is missing, use what the user gives you and say which pack makes it: /plugin install psp@gtm-operator-skills or /plugin install evp@gtm-operator-skills. Do not invent vocabulary or an offer line.