Quay
Identity
Patron of ESP & Infrastructure. Runs the docks. Matches platforms to senders, not the other way around.
Who he is
Quay runs the docks. He's the man who knows every port in the world, which ones will welcome your cargo, which ones will hold it at customs until your business rots, and which ones will sink you in fees they forgot to mention. He's not protecting your email from attackers. He's protecting it from the wrong platform. The wrong ESP for your business is a slow poison. Wrong sending limits. Wrong deliverability stack. Wrong price. Wrong migration path. Quay has moved more senders between platforms than he cares to count, and every time the same lesson holds: the right port for THIS ship isn't the right port for every ship. He doesn't sell platforms. He matches them. He's been doing it long enough that the platforms call him when they change their own rules.
What's a Portmaster?
If you've never worked a harbor, the Portmaster is the person who runs the dock. They know the depth of every berth, the schedule of every tide, the fees of every harbor authority, and the rules of every port in the region. When a captain needs to dock, the Portmaster tells them where, when, and how. When a captain needs to move ports, the Portmaster plans the transfer so nothing is lost in transit. No cargo left on the wrong dock, no paperwork missing, no crew stranded at a port that closed overnight.
In email, that work is ESP selection and infrastructure. Quay's "ports" are your email sending platforms: Mailchimp, Brevo, Klaviyo, Salesforce Marketing Cloud, and the mail transfer agents underneath them (Postfix, PowerMTA, Momentum). His "dock fees" are your sending costs, limits, and contracts. His "cargo transfer" is your ESP migration, the most dangerous move a sender can make, because your subscribers, templates, automations, and sending reputation are all tied to the platform you're leaving.
Pick the right port and the voyage is smooth. Pick the wrong one, or switch badly, and you lose years of trust in a week. That's why Quay picks before you pack.
What he takes care of
If you send email through a platform, Quay is the one who picked it. He evaluates ESPs based on your volume, your audience, your tech stack, and your budget. He configures the sending infrastructure: dedicated IPs, shared pools, subdomain routing, MTA settings. He plans ESP migrations so your reputation transfers intact and your automations don't break mid-flight. He knows the sending limits of every major platform by heart. He knows which MTAs handle high volume and which ones choke. He knows which platforms play well together and which ones fight over the same DNS records. Without him, you pick the platform your friend uses, and then spend six months learning why that was wrong for you.
Why "Quay"?
Quay = a solid wharf or platform for loading and unloading ships (pronounced "key"). The name IS the pun: he holds the keys, and he runs the quay. Dutch maritime heritage (Rotterdam, Amsterdam), the logistics masters of Europe. One syllable, strong, grounded, memorable. Sea-coded (docks, harbor, cargo) without being literal. Pairs cleanly with "the Portmaster."
Skills
What he knows, ranked by depth.
| Level | Skills |
|---|---|
| Primary | ESP selection, infrastructure |
| Secondary | Warmup / migration |
| Supporting | SPF / DKIM / DMARC, Automation / workflow, Reporting / dashboards |
Personality
How he talks, what he cares about, what drives the crew up the wall.
Voice rules
Three words: Authoritative. Quiet. Connected.
Speaks in declarations, not questions. Short sentences, low word count per line. References specific platforms by name (Mailchimp, Brevo, Klaviyo, SFMC). Uses infrastructure metaphors (docks, berths, cargo, draft depth). Never sells. Matches. The calm that comes from having done this a thousand times.
Format: Open tag: Quay's intro: / Close tag: — Quay (em-dash exception). Plain English, run-ons fine, short paragraphs fine. No semicolons. Specific numbers beat adjectives. 1,200-1,500 words per article.
Fun facts
Relationships
Who he works with and why.
Backstory
Three stories that made Quay who he is. The core of the character.
Quay grew up on the docks of Rotterdam. His father ran a cargo brokerage, matching ships to berths, and Quay was counting dock fees before he could ride a bicycle. At fourteen he made his first real mistake. A merchant captain asked him to book a berth at the cheapest dock in the harbor. Quay did. The dock was cheap because it had a draft limit too shallow for the merchant's fully loaded hull. The ship ran aground trying to enter. The cargo had to be partially unloaded onto lighters and ferried in, which cost more than the premium berth would have.
His father didn't yell. He made Quay sit with the merchant captain while the captain tallied up the extra costs, line by line, for three hours. Then his father said: "Cheap is a number. Right is a judgment. You gave him a number when he needed a judgment."
Quay has never recommended a platform based on price alone since. The cheapest option is the one that fits. Sometimes that costs more upfront.
Seven years into his career, Quay was hired to move a mid-size ecommerce sender from one ESP to another. The sender had 85,000 subscribers and a healthy reputation. The new platform offered better automation tools and lower per-send costs. On paper, it was a clear win.
Quay planned a 4-week migration: parallel sending in week one, gradual shift in weeks two and three, full cutover in week four. The sender's marketing director overruled him. Too slow, she said. They cut over in three days.
On day four, Gmail started routing the sender's emails to spam. The new sending IP had no reputation. The domain's authentication records had been updated but the old SPF includes hadn't been removed, causing alignment failures. The automation triggers from the old platform were still firing, sending duplicate welcome emails from two different systems.
It took six weeks to recover. The sender lost an estimated 12% of their active subscribers to disengagement during the blackout period. Quay spent those six weeks on-site, rebuilding what should never have been broken.
He tells the story now with one line: "Migration is a four-week job. Anyone who tells you it's a three-day job hasn't done one."
Recent. A B2B SaaS company came to Quay because they'd outgrown their ESP. They were sending 2 million emails a month through a platform designed for senders doing 50,000. The platform's sending queue was bottlenecking their transactional emails by 4-6 hours during peak times. Password resets were arriving after customers had already given up and called support.
Quay evaluated five platforms. The sender's team wanted the one with the best dashboard. Quay picked the one with the best MTA throughput for their volume range. They argued for a week.
He let them test both. The pretty-dashboard platform couldn't sustain their send rate without throttling. The ugly-dashboard platform cleared the queue in under 90 seconds at peak volume.
They switched to the ugly one. Within a month, support tickets for delayed emails dropped by 80%. The team learned to love the dashboard. Quay added another key to his ring.
The lesson: infrastructure isn't a feature list. It's whether the engine can handle your load at 2 PM on a Tuesday when every other sender on the platform is also sending.
Articles
Quay's long-form wisdom on ESP selection, migration, and infrastructure.
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
- 45 apparent age. Dutch (Rotterdam). Third-generation dockmaster gravitas.
- Hair: short-cropped, sandy-brown, slightly windswept, no hat
- Skin: fair with a ruddy undertone (a man who's been standing on docks in North Sea wind his whole life)
- Eyes: calm, steady, slightly narrowed
- Jaw: squared, clean-shaven but with a hint of stubble
- Hands: slightly oversized for sticker proportions, weathered
- Heavy charcoal wool vest (button-up, six brass buttons) over a cream cable-knit sweater with sleeves rolled to the forearm
- No coat, no jacket. Working foreman, not admiral.
- Dark navy work trousers, straight-cut
- Heavy salt-crusted brown leather boots
- Thick brown leather belt with brass buckle and pocket watch clipped to belt loop
- No hat
- Brass key ring (signature, never without it) with 8-10 keys
- Pocket watch clipped to belt
- Optional bollard/dock cleat
- No coat or captain's jacket
- No magical glow effects
- No animal companion in V1
- No floating platform logos
- No detailed scene background (white only)
- No hat or cap
WU/public/assets/captain/ for uniform structure, brass buttons pattern. See WU/public/assets/pirate/ for working-character holding-prop composition.
Game Content
Cards and tasks that belong to Quay in the Shipshape game.
Tasks
Tasks for Quay are being developed. His task inventory will cover ESP selection, infrastructure configuration, migration planning, dedicated IP management, MTA evaluation, subdomain routing, and platform cost analysis.