How do I send a product update to the people who asked for one?

The list and the digest, in one step

Choosing Product updates from New email makes two things at once: the Product updates list, with the consent sentence people actually agree to — "Email me when there is something new" — and a template carrying one line, !items, that becomes what happened since the last send, oldest first.

What counts: deploys read from Vercel, each with its commit and pull request titles where GitHub is also connected, and your own website's changes. Nothing from an error tracker or a support inbox — a digest reads what shipped, not what broke.

It drafts itself on a rhythm you set — weekly, by default — and it never sends on its own. When it falls due, Kicklace drafts it and hands you a proposal with the whole rendered email on it, waiting for you. And where nothing happened in the window, nothing is drafted at all: no filler, no "quiet week" email.

Set it up

1. New email → Product updates. It lands paused, with a weekly schedule already chosen.
2. In the template's own band, press With last week's facts to see the real draft, rendered with the actual items, before it is ever due.
3. Set the day, the hour and the list, then switch the digest on.
4. When it falls due, open the proposal on Home or Approvals: read the rendered email and press Approve, or Reject.
5. People join by the form Kicklace hosts at https://www.kicklace.com/f/<your workspace>/product-updates, or by adding data-kl-list="product-updates" to a signup form already on your site.

What it does not do

It never sends a week's draft without you approving that exact rendered page first. It never invents an update — nothing happened, nothing goes out. And it never reads from an error tracker, a support message or anything else that is not a deploy, a code change or your website. Email has the whole of what a digest is.