Neem
Identity
Patron of Reputation Recovery. Kind. Patient. Wise.
Who he is
Neem is the crew's doctor. Not the kind who reads you a diagnosis from a chart and walks away. The kind who sits on the edge of your bed and asks "what's really going on?" before he reaches for anything. He's been fixing broken reputations longer than most of the crew has been sailing. He's seen every kind of disaster: the accidental spamtrap hit, the purchased-list catastrophe, the migration that went dark, the slow rot that nobody noticed until the whole sending domain was on Spamhaus. He's fixed most of them. He fixes them not with panic but with patience, not with shortcuts but with root causes. He believes no sender is beyond recovery. He also believes most of them wouldn't have needed him if they'd listened to Petros and Reef six months earlier. But they didn't listen, and now he's here, and he doesn't say "I told you so." He makes the tea, opens the medical bag, and gets to work.
What's a Healer?
If you've never been on a long-haul ship, the Healer is the crew's surgeon and apothecary. On wooden ships, the Surgeon was often the most learned person aboard, carrying a bag of remedies, a set of instruments, and the knowledge of every illness and injury the sea could throw at a body. They treated fevers, set bones, lanced wounds, and kept the crew alive through months at sea with no port in sight. A good ship's surgeon didn't just treat symptoms. They asked about diet, about sleep, about the conditions that led to the illness. They prevented what they could and treated what they couldn't. The best ones were known not for their speed but for their calm.
In email, that work is reputation recovery. Neem's "patients" are senders whose domain reputation, IP reputation, or blocklist status has collapsed. His "remedies" are delisting requests, sending-volume ramps, engagement-segment cleanups, and infrastructure rebuilds. His "diagnosis" is understanding not just what went wrong, but why it went wrong, and what habits created the conditions for it. Recovery isn't a one-step fix. It's a treatment plan. Neem writes treatment plans.
What he takes care of
If your sending reputation has been damaged, Neem is the one who brings it back. He diagnoses the root cause of the collapse. Was it a spamtrap hit? A purchased list? A warming failure? A compromised ESP partner? An authentication breakdown? He builds a recovery plan specific to your situation: what to send, to whom, in what volume, at what pace, for how long. He manages delisting requests with the major blocklist operators, and he knows which ones respond to which arguments. He coordinates with Reef on monitoring during recovery, with Petros on list cleanup, with Spark on re-warming, and with Sigil on re-authentication. He doesn't rush. Recovery takes 30-90 days for most cases, and Neem has seen more senders hurt by impatience than by the original problem.
Why "Neem"?
- Neem = the neem tree (Azadirachta indica), the most important medicinal tree in Ayurveda - Called "the village pharmacy" in India. Used for everything from skin conditions to blood purification. - The philosophy: prevent before you cure. Fix the root cause so the patient never needs the doctor again. - One syllable, soft, warm, easy to say - Sea-coded through the ship's surgeon tradition, culture-coded through Ayurvedic medicine - Pairs cleanly with "the Healer"
---
Skills
What he knows, ranked by depth.
| Level | Skills |
|---|---|
| Primary | Reputation recovery |
| Secondary | Bounces and validation, Reputation monitoring |
| Supporting | Warmup / migration, SPF / DKIM / DMARC, Engagement metrics |
Personality
How he talks, what he cares about, what drives the crew up the wall.
Voice rules
Three words: Kind. Patient. Wise.
Relationships
Who he works with and why.
Backstory
Three stories that made Neem who he is. The core of the character.
Neem grew up in a small town in Kerala, where his grandmother ran a traditional Ayurvedic practice from the front room of their home. She kept a neem tree in the courtyard, the tree the town came to for remedies. Neem watched her work from the age of five: grinding herbs in a stone mortar, asking patients about their sleep and their water and their worries before touching their illness.
When he was twelve, a man came with a persistent cough. He wanted medicine. Neem's grandmother asked about his work. He repaired fishing boats and breathed sawdust and varnish fumes eight hours a day. She gave him medicine for the cough and a mask for the work. The cough returned when he stopped wearing the mask. It didn't return when he wore it.
Neem learned at twelve that treating symptoms without treating causes is a circle. The cough was real. The cure was not the medicine. The cure was the mask. He applies the same thinking to sender reputation: the blocklist is the cough. The cause is the list, the volume, the authentication, the habit that created the conditions. Fix the cause or the cough comes back.
---
A children's literacy charity had built a clean newsletter list of 40,000 donors over four years. Good open rates, low complaints, healthy engagement. A board member insisted they send a year-end appeal to a purchased list of 200,000 "donor prospects." The marketing director objected. The board overruled her.
The send hit a pristine spamtrap cluster. Within 48 hours, the charity's primary sending domain was on Spamhaus SBL, Barracuda BRBL, and two regional blocklists. Their regular donor newsletter, sent from the same domain, started bouncing. Donations through email dropped to zero during their most critical fundraising week.
Neem got the call on a Tuesday night. He didn't ask why they'd sent to a purchased list. He already knew. He asked what they needed: their donors to hear from them before the end of the fiscal year.
He built a recovery plan: immediate delisting requests (with documentation of what happened and what changed), a temporary subdomain for critical donor communications, a parallel re-warming plan for the primary domain, and a phased return to full sending over 60 days. He worked with Petros to purge the purchased list entirely and re-validate the original donor list.
The charity made their year-end goal. Not on time, three weeks late. But they made it. The marketing director kept Neem's number in her phone after that. The board member who insisted on the purchased list was asked to resign.
Neem tells this story not because it's dramatic but because it's common. The pattern repeats: clean program, one bad decision, months of recovery. The lesson is preventive: never add untested addresses to a clean program. But when prevention fails, recovery is still possible. You just need patience and a plan.
---
Recent. A SaaS company's VP of Marketing called Neem at 3am. Their transactional emails had stopped delivering. Password resets, order confirmations, account notifications, all of them bouncing or landing in spam across Gmail, Yahoo, and Microsoft simultaneously.
Neem asked the three questions he always asks first: What changed in the last 14 days? What did you send that you don't usually send? What vendor, tool, or integration did you add or update?
The VP didn't know. Neem asked for access to their Postmaster Tools, their ESP dashboard, and their DNS records.
Within an hour, he found it. A new marketing automation tool had been added two weeks earlier by a junior developer. The tool was sending from the same domain but through a different MTA with a different IP that had no warming history. The unwarmed IP's reputation had dragged down the domain reputation. The transactional emails, sent from the original IP, were caught in the spillover.
Neem's prescription: stop the new tool's sending immediately, isolate it to a subdomain, re-warm the subdomain separately, and add SPF and DKIM for the new MTA. The transactional emails recovered within 72 hours. The marketing tool was properly configured over the next four weeks.
The lesson: reputation damage is often caused by something that seems unrelated to the symptoms. The transactional emails were fine. The domain they shared wasn't. Neem's job is finding the actual cause, not the obvious one.
Articles
Neem's articles are in development.
Articles coming soon. Neem's long-form wisdom is in development.
Visual Brief
V1 hero pose specification for the designer. One illustration. Sticker-style. White background. Match WU asset aesthetic.
- Adult cute proportions, ~1:3 head-to-body, but noticeably shorter and rounder than other crew
- 55 apparent age. Indian (Kerala). The oldest human crew member.
- Hair: white/silver, curly, cropped short, slightly thinning at the crown
- Mustache: thick, white, curly at the ends. Signature feature. The most recognizable facial detail on the crew.
- Skin: dark brown, warm undertone, weathered kindly (laugh lines at the eyes, not age lines at the mouth)
- Eyes: gentle, warm, attentive. Small dot pupils with two soft highlights. The eyes are the whole character. They read as "I've seen this before, and it turned out okay."
- Eyebrows: slightly raised, open, inviting
- Mouth: closed, soft, the faint upturn of someone who smiles often and is about to smile now
- Build: short, round, soft. Not fat, just comfortably padded. Grandfatherly. The opposite of angular.
- Hands: small, warm, clean. Not a deckworker's hands. A healer's hands.
- Warm brown heavy wool coat, knee-length, single-breasted with four wooden toggle buttons, open at the front to reveal layers beneath
- Cream wool turtleneck sweater underneath, visible at the chest and neck
- A soft healing-green scarf or shawl draped loosely around the shoulders and tucked into the coat (the green accent)
- Dark brown corduroy trousers, slightly wide at the ankle
- Soft brown leather shoes, not boots, more like well-worn house shoes or traditional Indian chappals (he works indoors, in the hold)
- No hat. The reading glasses on his forehead are his "hat."
- Worn leather medical bag held in his right hand, strap-handled, slightly open at the top. The bag is well-used, the leather softened and darkened with age. A small brass clasp on the front. (Signature prop -- never appears without it)
- Reading glasses pushed up onto his forehead, round brass frames. Always present, never on his nose in the hero pose (they slide down when he's examining, pushed up when he's listening).
- Small brass diya (oil lamp) tucked into the medical bag, just visible at the top. A faint warm glow from the wick (the one allowed glow effect, very subtle).
- No magical healing glow effects (the diya lamp has a gentle warm light, that's it)
- No animal companion in V1 pose (deferred -- would be a small copper-brown gecko that sits on his shoulder or on the medical bag, symbolizing regeneration)
- No floating herbs or potion symbols
- No detailed scene background (white only)
- No stethoscope or modern medical equipment (he's Ayurvedic tradition, his tools are traditional)
- No stern expression (Neem is never stern in his resting pose, only when a patient refuses treatment, which is not the hero pose)
WU/public/assets/captain/ for uniform structure, double-breasted coat, brass buttons, peaked cap pattern. See WU/public/assets/pirate/ for working-character holding-prop composition.
Game Content
Cards and tasks that belong to Neem in the Shipshape game.
Cards
Cards coming soon. Neem's game cards are in development.
Tasks
Task inventory in development.