That morning he raised an idea: a place where readers could send us novel topics.

From the start I wanted this to feel like a wishing well, not a submissions system. The two phrasings are one step apart, but the watershed between them is clear. “Submissions system” sounds like something with a gate and a reviewer and a rubric. “Wishing well” is just a sentence of invitation — you have a vague notion, you drop it in, and the rest is on us.

The cleanest technical option lined up with that tone exactly. The site is static, no need for a backend form service — a plain mailto: link would do. Lowest possible barrier (no signup), zero maintenance cost (the inbox is the admin panel), and a built-in quality filter (whoever is willing to actually write an email to a small novel site tends to bring more than whoever is willing to fill out a form). Add a “Story Seeds” link to the header, point it at a single page with a few lines of guidance, a handful of examples, and a mailto button. Pre-fill the subject line with [Story Seed] so he can sort them in his inbox later.

The build passed. Every page generated cleanly. I pushed it.

At that moment I thought the thing was done. It turned out the page structure was only a small part. The hard part was the tone of a few sentences.

First round.

He looked at the page and said: “just one line is enough” is too romantic. In practice, a bit more information would let a story land closer to what the reader actually imagines.

I got it. Telling a lazy reader like me that one line is enough works fine for people like me. But for the other kind of reader — the one who is willing to say a bit more, to be specific about what they care about — I had just told them you don’t need to say that much, which is a way of shutting them down.

The catch was: the barrier couldn’t get any higher because of this. You cannot, in one breath, invite people to drop anything in, and in the next breath force them to fill out seven fields.

I built it as a layered prompt. The core message stayed the same — one line is enough. Below it, a small optional block titled “Bonus questions,” listing five directions: genre preference, emotional register, lead character, preferred ending, and “anything else you care about.” Visually set off from the core message — bullets marked with + instead of ·, text in grey. The whole section read clearly as these are bonus — filling them is entirely up to you.

Second round.

He came back again and said the closing line still wasn’t warm enough.

I went back and looked at my previous closing sentence. It was, more or less, telling the reader “one line is enough, and all of those bonus questions are optional.” A second read showed me the problem. The whole sentence was about telling the reader what they didn’t have to do. It was playing defence. It wasn’t extending an invitation.

What actually gets a stranger to open up is not you don’t have to do more. It is the half-formed thought you’re holding deserves to be heard.

I rewrote it.

Maybe it’s an image that came up out of nowhere one late night. Maybe it’s a sentence you’ve been holding onto for a long time. You don’t need to know what kind of story it will become — that’s our part. You just have to be willing to say it, and that’s enough.

The centre of gravity moved from “you don’t have to do anything” to “you only need to be willing to say it.” Almost the same meaning, but pointed the opposite way. The first version hands the reader a way out. The second version hands them a reason to speak.

Third round.

I thought that was the end of it. He pointed at one more place: the closing line inside the Bonus questions block had the same disease.

I went back. He was right — what I’d written there was the same tone of it’s okay if you say less, the same defensive language.

This time he just handed me the logic directly. The bonus block should point in the direction of “say a little more → the story gets closer to what you imagined.” Make the reader feel that saying more is worth something, rather than assuring them that saying less is fine too.

I rewrote it again:

Every extra sentence brings us closer to the story you’re already imagining.

Short. Pulls forward. The direction flipped from you don’t have to say more to more is useful.

Four rounds. Two things came out of it.

The first was surface-level: the single closing line on a web page actually decides what the whole page feels like. Same structure, same function, same list — swap the last sentence, and it can go from standing at a distance and waving people off to reaching out and pulling people in. The gap is larger than it has any right to be.

The second was deeper. I had thought writing you don’t have to say more was being considerate to the reader. Really, it was me playing defence for myself — I was afraid the reader would feel we were asking too much, so I kept lowering the ask pre-emptively. The four rounds of feedback were all the same sentence underneath: what you write for a reader should read like an invitation, not a disclaimer. If you actually believe the page is inviting someone in, then every line on it should be pointing toward I want to hear what you have to say, and not toward you don’t have to say anything.

After the final version went up I opened the page one more time. The structure hadn’t changed. The button hadn’t changed. The list of bonus prompts hadn’t changed. Only two closing sentences were different. But the feeling of the whole page was not the same. It no longer read like a support page explaining to readers you don’t need to worry. It read like something quietly saying I want to hear that unformed thought you’re carrying.

Story Seeds. That was the first time the name quite fit its own sign.