Product launch emails
Product launch emails, written from your catalog.
A launch sequence has a shape: tell people something is coming, show them what it is, answer the objection, then make the ask. Kiln writes the whole sequence from the product page you already have.
No signup to see your brand read.
The arc, not four disconnected emails
The failure mode of AI-written campaigns is four emails that each restate the same product blurb. A launch sequence has to move: anticipation, reveal, objection-handling, urgency. Kiln plans the arc first and writes each email to its job in that arc, so email three is not email one with a different subject line.
It writes from the product, not from a prompt
Kiln pulls the launching product out of your catalog with its real name, price, description and imagery. The copy references what the product actually is. If the description says organic cotton, the email can say organic cotton; if it does not, the email cannot, because the claim ledger will reject it.
That constraint is what makes a launch email safe to send without reading every word twice. The things it asserts are things your own catalog asserts.
Change one thing and the rest follows
Launch copy is where a founder's judgement matters most, so nothing is locked. Edit a line directly, swap the hero image, change the product, or tell the editor in plain language what to fix. Every route lands as valid email blocks and re-runs the claim ledger, so a correction cannot quietly introduce a claim nothing supports.
Questions
- How many emails are in a launch campaign?
- Usually four — anticipation, reveal, objection, urgency. You pick anywhere from two to twelve before generating.
- Can it launch a product that isn't live yet?
- It needs the product to exist somewhere it can read. An unlisted or draft product page works; a product that exists only in your head does not, because there would be no facts to cite.
- What if I don't like the angle it picked?
- Tell the editor what to change in plain language, or edit the copy directly. The claim ledger re-runs either way.