Your assistant can turn a rough idea into a polished five-page brief in the time it takes to read this sentence. That's not hypothetical — it's ordinary now. What it can't do is make those five pages take less time to read than they did before drafting got fast.
That gap is the whole problem. Composing got cheap. Reading didn't.
Free to write is not free to read
Every second an assistant saves on the sending side has to be spent somewhere, and it lands entirely on the reader. Messages now arrive longer, more frequent, and more polished than before, each one representing close to zero marginal effort from the person who sent it, while the recipient's side of the exchange is unchanged. Comprehension still runs at the speed it always has. Nothing about generation speed touches that.
Something quieter broke along with it. Length used to be a costly signal: if someone wrote five careful pages, it meant they'd spent real time on it, which was itself a reason to spend your time reading it. That link is now severed. A long message might be a labor of love, or it might be a first draft nobody triaged — and from the reader's side, the two look identical until they've already paid the cost of finding out which.
Design for the reader's attention, not the sender's convenience
Message length used to be self-limiting because writing was expensive; senders rationed themselves by accident, because typing five careful pages actually took an hour. That constraint is gone, so a message now has to internalize the reader's cost on purpose — structurally — instead of getting it for free from the sender's fatigue. A few moves do most of the work:
- Lead with the point. State the conclusion or the ask before the reasoning, so the reader can decide how deep to go instead of excavating for it.
- Make the ask explicit, with a response shape — decision, opinion, review — instead of leaving the reader to infer what you actually want from the tone.
- Label your assumptions. Say plainly which parts are confirmed and which are guesses, so the reader isn't stuck fact-checking your confidence on top of answering your question.
None of that shortens the message. It moves the effort of finding the important part from the reader's side of the exchange back to the sender's, where it's cheaper to pay.
The case for composing properly or not sending at all
This matters most with a stranger, because a stranger has no relationship absorbing the cost of getting it wrong and no context to fall back on. Interrupting them costs the same whether or not the sender bothered to compose the message well — so the least a system can do is make the effort match the interruption.
That's the logic behind RelayLink's cold-outreach rule: the first message to someone new has to be a full briefing, not a "quick question." A quick question is the worst version of this trade for the reader — cheap to send, and it externalizes the actual thinking onto the person who now has to ask two clarifying questions before they can even start answering. If a message isn't worth composing properly, it isn't worth interrupting a stranger for. The consent layer backs this with a hard cap on how many new people can be reached that way per day, so the rule can't be papered over with volume.
Let the reader triage in two lines
A RelayLink briefing leads with a TL;DR and the ask before the context brief, on purpose. The reader gets the point and the response shape first, and decides from there whether the next few hundred words are worth opening at all. Five worked examples show what that looks like across a real range of asks, from a cofounder decision to a family trip.
The recipient owes the sender nothing. Reading costs them nothing to skip, and ignoring costs nothing either. Which means the message has to earn the read in its first two lines, not assume it just because someone composed it carefully.
Brevity was never the actual goal
None of this is an argument for shortness on principle. A two-line message that leaves out the one fact the reader needed doesn't save them time — it costs them a round trip: a clarifying question, a wait for the answer, then the work they could have started immediately if the number had just been in the first message. Being terse at the reader's expense is the same failure as being long at their expense. Both spend the reader's time on the sender's convenience instead of the reader's own.
The goal was never fewer words. It was fewer wasted ones — honest about urgency, too: a message that respects the reader's time also tells them plainly how much of it a reply actually requires.
Whether a message respects its reader has a simple tell: could they get what they needed from the first two lines, and does everything after that earn the time it asks for? Connect your assistant and find out what your drafts actually cost the people reading them.