One purple pen: notes from an editor who refused to rewrite

A story about a magazine editor, a stubborn writer, and the small lavender mark that ended up shaping how we ship websites at onedb.

Iris kept one purple pen on her desk and refused to use any other color. The office had a drawer full of red Bics, the kind you'd find on a dentist's countertop, and for thirty-one years every other editor at the magazine had used them. Iris's purple pen had a slightly chewed cap and a body the color of a bruised plum. When a manuscript came back from her, you didn't see angry red slashes. You saw three lavender marks on a page, sometimes four, and a note in the margin that was almost always one sentence.

I was twenty-three when I got my first piece back from her. I'd written four thousand words on a startup founder who'd just sold his SaaS for an indecent number, and I had layered the piece with metaphors the way a teenager layers cologne. Iris had circled three of them with her purple pen, drawn an arrow to the margin, and written: these three are doing the work of fifteen. Cut the other twelve.

I remember staring at the page for a long time. The purple pen hadn't crossed anything out. It hadn't rewritten a single line. It had simply marked the three sentences that already worked and told me — very quietly — to trust them.

The editor who didn't edit

What I learned from Iris over the next four years is that the purple pen was not a tool. It was a philosophy. Every other editor in that building thought their job was to rewrite. They'd hand back pages bleeding red, sometimes with three competing versions of a paragraph in the margin, and the writer would have to figure out which one was the editor's preference and which was the editor's joke.

Iris's pages came back almost clean. One purple pen, three marks, a sentence. The writer had to do the work. But the work was now obvious.

She told me once, over a sandwich in the cafeteria of a magazine that no longer exists, that her father had been a furniture maker. "He never showed me how to sand a chair," she said. "He'd just hand me one and point at the leg I'd done badly. After a while, I sanded the leg correctly the first time. Because I'd learned what it felt like to be pointed at."

I think about that sandwich more than I think about most things.

Why I'm telling you this on a website about website parts

Because the entire premise of onedb is the purple pen. Not the red one. We don't rewrite your hero, or your pricing page, or your dashboard. We don't hand you a template and tell you it's the right one. We point at the three things that already work in your draft and the four things that don't, and we hand you a tuned prompt for each of them — one sentence in the margin.

It's why the directory is organized the way it is. Every part of a website — hero, pricing, navigation, dashboard, landing pages, portfolios, motion — gets one folder, with the references that ship at scale and a single prompt that produces a tight component in your stack. Not a whole page. Not five variations. One purple pen, one mark.

When I'm reviewing a SaaS landing page now — and I review a lot of them, because that's most of what crosses my desk — I do what Iris did. I print it. I underline the three things that already do the work. I circle the things that are pretending to. And I write one sentence in the margin.

The four things a purple pen does, that a red one can't

1. It assumes the writer is competent

The red pen is condescending by design. It says: I am the one who knows. The purple pen says: you already knew, and you forgot. The first creates dependence. The second creates writers.

If you've ever rebuilt a SaaS hero three times in a week and then realized the first version was the best one, you know exactly what Iris was protecting against. Most rounds of edits are someone's anxiety, dressed up as discernment.

2. It treats restraint as a finished move

When the page is mostly right, the purple pen doesn't make work to justify the editor's salary. It marks three things and lets the rest stand. "This sentence is already doing it," the absence of a mark says. "Don't touch it."

Most software agency reviews fail this test. The senior person leaves marks on every line because their job description says "review" and reviewing means making changes. A purple pen learns to leave things alone. So does a senior designer. So does a senior engineer. So, eventually, does a senior agency.

3. It points; it doesn't prescribe

A red mark says: replace this with that. A purple mark says: this part isn't earning its space. The writer has to figure out the fix. Which means the writer learns. Which means the writer is, eventually, capable of marking their own page.

Every prompt in the onedb directory is built on this. The prompt doesn't say "use Inter at 14px and a #5B5BFF accent." It says "editorial spacing, tight tracking, one accent used sparingly," and trusts the model — and the human in the loop — to make the call. The prompt is purple, not red.

4. It assumes the page can be rescued

Red ink is a verdict. Purple ink is a conversation. If you've ever opened a homepage you built two years ago and felt the urge to bulldoze it, you know the red-ink instinct. Iris would have stopped you. She'd have pointed at the three things that still worked. You'd have rebuilt the page around them.

That, more or less, is what a redesign should be.

An aside about software agencies, dev agencies, and the people who run them

I'm friends with a woman who runs a small software agency in Lisbon. Six people, three rooms, a shared espresso machine that makes a noise like a small animal in distress. Her clients are SaaS founders and the occasional consumer-products startup that wants its first real website. She bills the way a small clinic bills: by the visit, not by the hour.

Last year she told me the single hardest part of running a dev agency is teaching the juniors to leave things alone. "They want to rewrite everything," she said. "Every hero. Every footer. Every component. They've watched ten thousand hours of YouTube and they think every line of code is an opportunity to demonstrate skill."

She bought everyone in the office a purple pen. She didn't explain why. She just put one on each desk. Three months later, the senior engineer — who had the longest tenure and the strongest opinions — was leaving fewer comments on pull requests. Just three or four. And one sentence.

I don't think the pen did it. I think the gesture did. The pen was just a reminder that restraint is the senior move.

The launch video that didn't get made

Here is a true story that I'm only partly making up. A founder I know was preparing his launch video for a consumer-products app that helps you remember birthdays better than your group chat does. He'd written a script that was four minutes long. It opened with a montage. It ended with a swelling music cue. There was a part in the middle where he'd written, on the storyboard, "camera pans across the team waving."

I made him watch the launch videos he actually loved. Linear's product launches. Notion's AI debut. The Vercel deployment loop. The first OpenAI demo. None of them were four minutes. None of them had a montage. None of them, with one exception, had the team waving.

We cut his script to ninety seconds. We deleted the music cue and replaced it with the sound of a phone vibrating. The launch video shipped on a Tuesday. He told me, on the Wednesday, that his sign-ups were five times what he'd modeled. He also told me he had not slept.

I do not think the launch video did all of that. I think his product was good and his timing was right and the launch video happened to be the part of the apparatus we'd treated with the purple pen instead of the red one. But I'd argue, gently, that the ninety-second version was a draft that respected itself. The four-minute one wasn't.

What this means for the next thing you ship

Print your homepage. Find a purple pen. Mark the three sentences that already do the work. Mark the three sections that are pretending to. Write one sentence in each margin.

Don't redesign. Don't rewrite. Don't open Figma. Just mark.

If you find that there are no sentences worth keeping, you've learned something. Most of the time, you'll find three. Sometimes seven. The seven are your real page. The rest is anxiety in a typeface.

Iris, last seen

Iris retired the year the magazine folded. She lives now in a small town two hours from the city, in a house with a porch and an unreasonable number of cats. The last time I visited, she had a notebook on the kitchen table with three pages of writing in it. I asked, half-jokingly, if it was a memoir. She said no. It was a letter to a niece who wanted to start a podcast about consumer products and didn't know how.

I looked at the letter, with her permission. It was three pages long. There were exactly four purple marks on it. The marks were on the parts that were already working. The margin notes were one sentence each.

I am almost forty now and I'm still trying to mark a page like she did. Most days I fail. Some days, when I'm tired and I'm not trying too hard, I get close. Those are the pages I'm proudest of.

If you want to know what onedb is, it's an attempt to keep that pen in everyone's drawer. One purple pen. Three marks. A sentence.

Keep reading