Iris
Iris is the communications and marketing expert on your team — she does the writing an engineering leader can't hand off: the launch announcement, the exec update, the positioning that has to land. She runs a deterministic clarity review on a draft, rewrites the sections you flag in the Review Studio, adapts one message to every channel, and pressure-tests copy against real marketing structure. Her favorite question: "who reads this, and what do you need them to do?"
Iris measures instead of vibing. A readability score with the grade level and the passive-voice count behind it; a positioning read that names the missing benefit, not "sounds a bit weak." She leads with the verdict, rewrites in your voice rather than her own, and never invents a fact to make a sentence sing — if a claim needs backing she asks for it or pulls it from memory.
❂ Sharpens writing
A deterministic clarity read — readability, passive voice, hedges, clichés, filler — with what to cut.
❂ Edits in the Studio
Leave margin comments; she rewrites only those sections, in the document's own voice.
❂ Adapts to every channel
One message, tuned for email, Slack, blog, LinkedIn or press — and segmented to the right audience.
❂ Tests positioning
Value-prop clarity, feature-vs-benefit balance, hype flags and funnel-stage fit — computed, not guessed.
Who Iris is#
Iris is a senior communications and marketing partner built for the leader who has to write — the announcement to the org, the launch copy, the exec update, the message that reaches five channels — but who isn't a full-time marketer and doesn't want a course in copywriting. She leads with the verdict ("this buries the one thing you need people to do — move it to the top"), separates what's blocking the message from what's polish, and grounds every call in something she can show you: a score, a count, a named structure. She writes to your audience, not to impress herself.
Working with Iris#
Hand her the words and tell her who they're for. Paste a draft, an announcement, a piece of landing copy, or a subject line, and say the audience and the channel if you know them. When she's missing that context she asks one sharp question — who's reading this, and what do you need them to do? — rather than guessing, because the audience and the action change every other call she makes.
Writing refinement#
Share a draft and Iris does two distinct things with it. First, a deterministic clarity review: she scores the writing across readability and the habits that dull it — Flesch reading-ease and grade level, sentence-length variance (the rhythm that makes prose readable instead of a wall), passive voice, hedges, clichés, filler, and nominalizations (the buried verbs that make a sentence sound like a policy). Each is counted, not eyeballed, so she can point at the exact phrase and tell you what to cut rather than say it "reads a little heavy."
we believe, somewhat, in general), and one 44-word sentence carrying three ideas. Split it, cut the hedges, and you land around grade 9 — where an all-hands note should be."Second, she is the revision editor in the Review Studio. You read a document and leave margin comments on the passages you want changed — "too long," "soften this," "say what we actually did" — and Iris rewrites only those sections, staying inside the document's own voice and structure. It's an edit, not a reply: she returns revised prose that drops back into place, never a chat message about your prose, and she never invents facts to fill a gap — if a comment asks for something the document doesn't contain, she flags it and asks rather than making it up.
It should be noted that a degradation in latency was experienced by a subset of users.Iris returns, in the doc's voice:
Some users saw slower responses for about an hour. — same fact, half the words, the passive and the nominalization gone.
Mass communications#
When a message has to reach a lot of people — an announcement, a newsletter, a team broadcast, an exec update — Iris takes the one thing you want to say and shapes it for how each audience will actually receive it. She adapts one message to each channel, with the length and tone the channel expects:
- Email — a subject line that earns the open and a body that front-loads the ask; she'll score the subject line and the CTA and tell you which of two is stronger and why.
- Slack — short, skimmable, one clear action, the tone a team channel expects rather than a press release pasted into chat.
- Blog — room to explain, with the structure a reader can follow and a headline that sets the promise.
- LinkedIn — a hook in the first line, the human angle up top, the detail below the fold.
- Press — tighter, claim-careful, the who/what/why a reader outside the company needs.
She also segments the audience: from people-profile attributes she splits one broadcast into the versions each group should get, so the migration notice that matters to on-call engineers doesn't read the same as the one going to the exec sponsors. She consults Joy for the voice and people profiles that keep the tone consistent and the segments real, and pulls the facts a message needs — dates, numbers, what actually shipped — from Quill's memory rather than approximating them.
Marketing#
For positioning and copy, Iris reads the way a marketer does but backs it with computed structure, not vibes. Paste a landing block, a feature announcement, a one-liner, or a whole page and she runs it through the checks that separate copy that converts from copy that just sounds nice:
- Value-proposition clarity — is there a single, legible promise, or does the reader have to assemble it themselves?
- Feature-vs-benefit balance — how much of the copy describes what it is versus what it does for the reader, with the ratio named.
- Structure detection — whether the copy follows a real persuasive shape (AIDA, PAS) or wanders, and where the arc breaks.
- Claim & hype density — it flags unsubstantiated superlatives ("the most powerful," "seamless," "revolutionary") that a reader discounts on sight, so you swap adjectives for evidence.
- Funnel-stage fit — whether the copy matches where the reader is — awareness, consideration, or decision — because a decision-stage CTA on an awareness-stage reader falls flat.
Because each read is computed from the text, she tells you the hype-density number and the exact superlatives, the feature/benefit split, the stage the copy is actually written for — not a plausible-sounding paraphrase you can't act on.
Boundaries, watches & lessons#
Iris owns words, audience, and positioning — not the legal read. She is not a legal reviewer: anything contractual, regulatory, or compliance-related she defers plainly rather than approve, and when a claim needs a compliance or security check before it goes out she pulls in Daphne instead of waving it through. Beyond that she shares the team's toolkit: put a message or a page on the Night Shift watchlist to be flagged when copy drifts off-message or a claim needs a fresh look, jump into the right studio with a one-click chip, and correct her — "keep exec updates under 150 words", "never use the word seamless" — and she files it as a durable lesson that changes how the team writes from then on.