Not an email we send any more — it is what the update says

Open Collective sends the update email itself, to everyone who contributed. So this stops being an artefact we build and becomes the content and the tone for theirs: the words, the order, the bill, the call to action, and the rule at the bottom of this page. That rule is the most valuable thing here and it survives intact.

What is no longer ours: the wrapper. The from-address, the footer, the unsubscribe line and the "read in a browser" link belong to the platform. Design owns the body and the subject line, and nothing else.

One thing got easier and one got riskier. Easier: this page's open question — a permanent public web copy of each update — is answered by the public collective, so a forwarded reader lands on a real page rather than a locked door. Riskier: the personal-data rule below is now enforced by their email template, not ours. ⛔ Somebody must open one real update notification from the fork and check it carries no name, no amount and no sign-in token. If it does, the forwardable email is broken by the platform and nothing we write fixes it. That has not been checked.

Also stale: every raseed.in URL below. The address is doable.aikyam.fund, and the naming question is open — see naming.html. Nothing inside the email itself has been edited; it is kept as drawn.

The update email

Sent weeks after a gift, when something has actually been bought. It is the artefact in this product built to be forwarded, so it assumes the reader has never heard of Aikyam, of us, or of whoever sent it to them.

In the inbox

Aikyam (via raseed)

Six chenda drums arrived in Fort Kochi on Tuesday

Fourteen girls had one drum between them. Here is what six new ones cost, and who paid.

The email

Aikyam · Fort Kochi, Kerala

The drums arrived on Tuesday.

Six of them, for fourteen girls who had been sharing one.

Photograph: six chenda standing against the wall of the rented room in Amaravathi, Fort Kochi

Every Saturday morning, fourteen girls between nine and fourteen meet in a rented room in Amaravathi, Fort Kochi, to learn the chenda — the drum you hear at every temple festival in Kerala, and one that women were kept away from for a very long time.

Until last week they had one instrument between them. Thirteen of them watched while one played.

On 4 September, Aikyam bought six more from a shop in Peruvanam that has been making them for four generations. They were delivered on Tuesday. This is the bill.

Peruvanam Music House
Bill 2126 · 4 September 2026

Chenda, full set with kolu — 6 × ₹6,200

₹37,200

Delivery, Peruvanam to Fort Kochi

₹1,000

Total paid

₹38,200

Twelve people gave ₹23,900 of that online. Aikyam paid the remaining ₹14,300 out of its own funds, from its own bank account. Two people at Aikyam approved the purchase before the shop was paid.

The class runs until March.

Aikyam is raising ₹40,000 for the next term of classes A teacher for six months, the room, and repairs. ₹23,400 has come in so far, from 47 people.

Give to this →

No account needed. The money goes straight into Aikyam's own bank account.

Gave to this already? Your own page shows which of those twelve gifts was yours, and your receipt.

Somebody forwarded you this? Nothing in it says who, or what they gave. It is written to be passed on.

Aikyam, Fort Kochi, Kerala 682001. Registered in India as a not-for-profit, registration AIK/2019/0000. 80G registration on file. Aikyam holds its own bank account and its own payment account; no one else touches its money.

raseed is how Aikyam sends this and how people who gave can see what their money bought. It never holds anyone's money.

Aikyam sends these to people who have given to it. Stop these emails · Read this in a browser

Everyone and every organisation named here is invented for a design review. No real person or organisation is described.

The plain-text version

This is what a stripped client shows, and often what actually gets pasted into WhatsApp. It has to stand on its own, so it is written rather than generated.

THE DRUMS ARRIVED ON TUESDAY
Six of them, for fourteen girls who had been sharing one.

Every Saturday morning, fourteen girls between nine and fourteen
meet in a rented room in Amaravathi, Fort Kochi, to learn the
chenda -- the drum you hear at every temple festival in Kerala,
and one that women were kept away from for a very long time.

Until last week they had one instrument between them. Thirteen of
them watched while one played.

On 4 September, Aikyam bought six more from a shop in Peruvanam
that has been making them for four generations. They were
delivered on Tuesday. This is the bill.

  Peruvanam Music House -- Bill 2126, 4 September 2026
  Chenda, full set with kolu, 6 x Rs 6,200 ....... Rs 37,200
  Delivery, Peruvanam to Fort Kochi .............. Rs  1,000
  TOTAL PAID ..................................... Rs 38,200

Twelve people gave Rs 23,900 of that online. Aikyam paid the
remaining Rs 14,300 out of its own funds, from its own bank
account. Two people at Aikyam approved the purchase before the
shop was paid.

The class runs until March.

--------------------------------------------------------------
AIKYAM IS RAISING Rs 40,000 FOR THE NEXT TERM OF CLASSES
A teacher for six months, the room, and repairs. Rs 23,400 has
come in so far, from 47 people.

Give to this:  https://raseed.in/aikyam/chenda
No account needed. The money goes straight into Aikyam's own
bank account.
--------------------------------------------------------------

Gave to this already? Your own page shows which of those twelve
gifts was yours, and your receipt: https://raseed.in/you

Somebody forwarded you this? Nothing in it says who, or what
they gave. It is written to be passed on.

Aikyam, Fort Kochi, Kerala 682001. Registered in India as a
not-for-profit, registration AIK/2019/0000. Aikyam holds its own
bank account and its own payment account; no one else touches
its money.

raseed is how Aikyam sends this and how people who gave can see
what their money bought. It never holds anyone's money.

Aikyam sends these to people who have given to it.
Stop these emails: https://raseed.in/stop

Everyone and every organisation named here is invented for a
design review. No real person or organisation is described.

What is ours now, and what is theirs

Ours: the body. Headline, story, bill, who paid, what is needed next. Written by a person at the organisation, in the organisation's voice, every time. An update that sounds like a platform does not get forwarded.
Ours: the subject line, and it is still one guess rather than a tested set. Three worth trying against each other: the one here, "Fourteen girls, six drums, one bill", and "What ₹23,900 bought in Fort Kochi".
Theirs: everything around it. From-address, footer, unsubscribe, the browser link, the plain-text version. Do not design these; check them.
Theirs, and it needs checking: the personal-data rule. The rule below used to be ours to keep. It is now a property of somebody else's template. ⛔ Open one real update notification from the fork and confirm it carries no name, no amount and no sign-in token. Unchecked.

The decision this page now forces

An Open Collective update can go to contributors only or to everyone. That single switch decides whether this email is forwardable at all — a contributors-only update is a locked door to whoever Priya sends it to, which is the exact failure the public collective just removed.

Recommendation: the update carrying a bill is public. The collective's page, its balance, its expenses and the bill are already public, so restricting the update gates nothing that is not one tap away — while costing the forward, which is the only growth this product has.
Contributors-only is for the intimate material: photographs of children, video, names, the voice note. The money is public; the people are not.
This is decision 1 in the shaping document and it is the Builder's, not mine to close.

What changed inside the email

The call to action got better. "Give to this" pointed at a page of ours that had to explain itself from nothing. It now points at the collective's own public page, which carries the ledger, the past bills and the story. A forwarded stranger arrives somewhere that proves itself.
"Gave to this already? Your own page" is redundant — the platform's own email already links her account. The principle it protected is not redundant: no sign-in token in anything designed to travel.
Every raseed.in URL is stale. The address is doable.aikyam.fund, and whether anything of ours is named in the footer at all is an open question.
The invented-people line in the footer stays while these pages are published, and so does the one on the collective's public page. Public means public.

The original notes, kept as they were

Written before the reversal and left unedited. The rule below is the durable part of this whole page — it was true when we were sending the email and it is true now that we are only writing it.

The rule this email exists to protect

An email designed to be forwarded contains nothing personal. Ever. No amount given, no name, no receipt, no PAN, no yearly total, and no sign-in link that carries a token. The moment Priya forwards it she is sending whatever is in it to people she has not thought about, and she will not know she did. Everything personal lives behind her sign-in, on her own page.

The tempting line is "your ₹500 helped buy these". It is warmer, it is the sentence the product is built on, and it must not be in this email — it broadcasts what she gave to a WhatsApp group of forty. That sentence belongs on her own page, where it is written in full and nobody else can read it.

Why this is not a thank-you

Nobody forwards a thank-you. A thank-you is about the person who got it, so passing it on is boasting. This email is about fourteen girls and a shop in Peruvanam, so passing it on is telling somebody something.
It assumes no prior knowledge and no relationship. No "thanks for your support", no "as you know", no reference to an earlier email. It explains who Aikyam is, what a chenda is, and why any of it matters, in the first two paragraphs.
The receipt email is the opposite and is a different email — sent minutes after she gives, all about her, carrying her amount and her sign-in link, and never designed to travel. It is not drawn here.

Who the call to action is written for

The stranger, because they are the only reader with anything left to do. Priya has already given. "Give to this" is aimed past her, at whoever she sends it to.
You cannot tell which one opened it, so the email does not try. Both lines are on the page, and both are true whoever reads them. The line for people who already gave sits below the button, quiet, and asks a question rather than assuming an answer.
The link is just the link. The giving page is public to anyone who has the URL, so a forwarded reader taps once and is in the flow. No account, no request for access, nothing to explain.
"Your own page" carries no sign-in token. It goes to a page that asks for an email address and sends a fresh link. A magic link in a forwardable email is somebody else's account arriving in a stranger's inbox — the one genuinely dangerous thing this email could do.

Built for a hostile medium

Tables, inline styles, no stylesheet, no JavaScript, no web font. It links neither tokens.css nor faces-inter.css; the tokens are a reference here, not a stylesheet.
Colours are the sRGB hex of the same colours the tokens name. The token file writes them in oklch, which no mail client understands, and annotates each one with its Tailwind name — so --primary is blue-600 #2563eb, the brand navy is #0c2764, and so on. Nothing was picked by eye.
The photograph is drawn as its images-off state, because a large share of readers see exactly that. The sentence inside the grey block is the alt text, and it is written to be worth reading on its own.
Order survives stripping. Read this email with every style removed and it still runs headline, story, bill, who paid, what is needed next, link. Nothing important is carried by a background colour.
Body text is 17px. Mail clients on phones shrink aggressively and this is the one thing that cannot be fixed after sending.
The bill's amounts are table cells, not floated spans. The first draft floated them right; measured at 375px the description wrapped and the unit price ended up sitting on the same line as the total, two rupee figures side by side with no way to tell which was which. Floats are unreliable in Outlook as well, so this was wrong twice.
The outer table is width:100%; max-width:600px, not width:600px. Measured at 375px the fixed version pushed 281px of the page off the right edge.

Known gaps

Not tested in any mail client. Not Gmail, not Outlook, not Apple Mail. The rounded corners and the padded link button are the two things most likely to render badly in Outlook, which needs a VML fallback this file does not have.
No real photograph is embedded, and no image hosting is decided. A hosted JPEG needs a public URL that will outlive the email.
The subject line is one guess, not a tested set. Three worth trying against each other: the one here, "Fourteen girls, six drums, one bill", and "What ₹23,900 bought in Fort Kochi".
No dark-mode treatment. Several clients invert colours themselves and will do something unplanned with the pale blue block.
The "read this in a browser" link implies a permanent public web copy of this email. That is a small widening of what is public and it needs a yes — see the giving page's notes.
The receipt email, the "we could not take your money" email, and the 80G-certificate-ready email are all unwritten.