The message arrives at 8:14 on a Tuesday morning. Four lines from somebody whose name you half know, under a subject line typed in ten seconds. It describes a job, and the work you end up doing will be a different one. What it needs before lunch is about a hundred and thirty words, a subject line you can live with until March, and a time on the calendar. That’s the whole morning.
Subject: Quick question
Hi. Marcus Halloway gave me your name. We run two warehouses off one site in Sparks and we have been asked to look at whether the way we run them is right before we take on a lot more volume next year. Ray wants an outside view rather than ours. Is this the kind of thing you do, and roughly what does it cost?
Dana Whitfield Operations manager, Northgate
The reply you send this morning is a working message, and that’s all it’s meant to be. It has four jobs. Two of them are finished by Friday. Two of them you’ll still be living with in March.
It has been through two people already
Somebody described a problem in a meeting. Somebody else said they should get an outside view. Dana was asked to go and find one. What’s in your inbox is that conversation, heard once and passed on by the person who was sent to find you.
That’s the normal condition of a first contact. It decides what you can take from the message.
The words are reliable. “Whether the way we run them is right” is how Northgate has been describing the problem to each other for a month. Your trade has other words for it. Northgate’s words are the most useful thing in the four lines, and they’re the reason the subject line below is written in Dana’s language.
That somebody asked for it is reliable. A request written on instruction behaves differently from one written on an impulse, because a person senior enough to be quoted has already said the words out loud. Who Ray is and how firmly he said it are open questions. That the sentence about Ray came from a real meeting is settled.
The names are reliable, and so is the fact that there are two of them in four lines.
The shape of the work is still open, and so are the size and the date. Dana is describing a job nobody has scoped, in the terms of a meeting somebody else sat in. What the work turns out to be gets settled at the call and not before. A fourth read gets you the same four lines. Read it twice, once for what they’re asking and once for who made them ask, then put it down.
The five minute rule is about somebody else’s business
Somebody will tell you this week that a lead has to be answered in five minutes. The research they’re reaching for is a Harvard Business Review article from March 2011, “The Short Life of Online Sales Leads,” by James B. Oldroyd, Kristina McElheran and David Elkington. It’s worth knowing what it measured before you take a rule from it.
There are two pieces of work in it. In one, the authors audited 2,241 US companies by sending each a web-generated test lead and timing the answer. Among the companies that replied inside 30 days the average response time was 42 hours, and 23% of the companies never responded at all. The other covered 1.25 million sales leads at 29 business-to-consumer and 13 business-to-business companies in the US. There, a firm that tried to reach a potential customer within an hour of the query was nearly seven times as likely to qualify the lead as one that tried an hour afterward. Against a firm that waited a day or more, it was more than 60 times as likely. Qualifying, to the authors, meant having a meaningful conversation with a key decision maker.
Read the second one closely and it’s a study about catching a stranger on the phone. Somebody who filled in a form on a website and now sits in four other pipelines. Most of that multiplier is the distance between reaching a person and missing them entirely. It is not your Tuesday. Dana has your name, got it from somebody you both trust, and is still reachable at lunchtime.
The first study is the one that transfers, and it’s the more encouraging of the two. The field you’re standing in answers in 42 hours on average, and a quarter of it never answers at all. The bar you’re clearing sits somewhere around Thursday.
So today is enough, and today is also the last cheap day. A reply sent this morning buys a time on a calendar. A reply sent Thursday buys a reply on Friday. The wider case for giving new work the fastest answer in your week is made elsewhere.
The subject line you are stuck with until March
At the moment this conversation is called Quick question.
In seven months it holds the proposal, four versions of a statement of work, a lawyer’s markup, an approval from an address you haven’t seen yet, and a question about an invoice. It’s still called Quick question. In February you’ll go looking for it with none of those words in your head.
So rename it, once, on your reply, and then leave it alone for the life of the deal. What actually keeps a thread together after that is a subject of its own. The part belonging to this morning is simple. Today is the only day the rename is free.
Three things go in it. The client’s name, first, because in February you’ll search for Northgate. Their words for what they want. And enough of this particular job that you can tell it apart from the next piece of work you do for them.
Northgate: the two Sparks buildings before next year’s volume
Leave out the words for the transaction and keep the words for the work. Proposal, quote, inquiry, RFP, and anything carrying a version number. Each of them is true for a stretch of the next seven months. A subject line earns its keep by surviving all seven.
The cost is real and worth stating. Google’s own help page for Gmail says a Gmail conversation “breaks off into a new conversation when the subject line changes” (checked September 6, 2026). Change the subject on your first reply and everything from your reply onward gathers under the new name, while Dana’s original message sits by itself. Today that costs you exactly one message, and a ten second forward puts it in the new thread if you want it there. On day forty the same move costs you the whole history. That’s the argument for doing it this morning, while it’s still one message.
One exception. If the request came out of a procurement system and the subject carries a reference number, leave it exactly as it is. That number is what their side searches on. It’s what makes your mail findable to the people who will be deciding.
Three questions and the reason for numbering them
Two or three questions, and three is the ceiling. A first reply carrying six reads as an intake form, and the person filling it in is doing unpaid work for a supplier nobody has hired.
Choosing them is easier than it looks. Scoping happens at the call. This morning you’re finding out whether there’s work here and what it would have to be worth. For this message, that is:
- What is the extra volume, and when does it start arriving?
- If nothing changes before then, what goes wrong first?
- Is Ray picturing something like a couple of weeks of work, or something like a couple of quarters?
The first turns “next year” into a date, and a date is most of what tells you whether this is real. The second separates a problem from a preference. The third is the only one about money, and it asks for a size rather than a number, on purpose. Nobody in Dana’s position can name a figure. Everybody in Dana’s position knows roughly whether their boss is imagining a short piece of work or a program.
The test for a question is whether it can be answered in one line, from memory, without a meeting. “Who asked for this to be looked at” passes. “What does your current picking process look like” belongs on the call, because that one takes an hour, and you’re about to book an hour.
Then number them, and use the numbers. This looks like formatting, and it does more than that.
The small benefit is that a numbered question comes back as a numbered answer, or at least as a paragraph that works through them in order. The large one shows up when a question goes unanswered. Three numbered lines produce a reply with a visible gap in it. Fold the same three into a friendly paragraph and the reply reads as an answer. A well meaning person moves past one of them, and the two of you find out at the call, or at the proposal, or in March.
You want to know which one they skipped. It’s often the most informative thing in the reply, and the numbering is what makes it visible.
Two times instead of your availability
“Let me know what works for you” hands the work back to the person who wrote to you first. It’s the most common way a warm reply turns into a four message chain.
Offer two specific times. Both real, both an hour. One sentence saying either is fine, so that Dana’s entire job is to type a day.
A week out is about right here. Sooner and Dana arrives with whatever she can relay of a meeting she half remembers, because she’s had no chance to ask Ray anything. Much later and you’re trusting that a person who wrote to you on Tuesday is still interested the following Monday. That usually holds. A week out means you never have to find out.
Say the length out loud and make it an hour. Half an hour buys you time to describe yourself, which is the least useful thing that can happen in a first meeting. An hour buys a scoping conversation.
Offer the second chair rather than requiring it. If Ray wants to be on the call, better this one than the one after. Requiring him hands Dana a scheduling problem inside her own company and a reason to come back to you next week. Offering costs you a sentence. Now and then it puts the person who holds the money in the room a month early.
A booking link is the wrong instrument this morning. What a link is good and bad at is worth reading once, and it settles the general case rather than this one. What settles this one is that Dana wrote to a stranger on Marcus’s word. A reply that comes back with a link asks her to go and do a small task before you have done anything for her at all. Two times in the body of the message are warmer, and today they’re faster. Send the invitation yourself once she picks, without the chain of messages that normally costs.
The reply itself
Subject: Northgate: the two Sparks buildings before next year’s volume
Dana, thanks, and thanks to Marcus.
Yes, this is what I do. Most of my work is this exact question: whether a site is set up for the volume it is about to get rather than the volume it has.
Three questions before I can say anything useful about cost.
- What is the extra volume, and when does it start arriving?
- If nothing changes before then, what goes wrong first?
- Is Ray picturing something like a couple of weeks of work, or something like a couple of quarters?
I have Tuesday, September 8, at 9:00 a.m. and Thursday, September 10, at 2:00 p.m., an hour either way. Tell me which one and I will send an invitation. If Ray wants to be on it, I would rather have him on this one than the next one.
A hundred and thirty words, and four things in it are load bearing.
The answer to Dana’s actual question comes before the questions of your own. She asked whether this is the kind of thing you do. Answer her first and then ask, and the message reads as a conversation. Open with three questions and it reads as a screening process. The sentence that answers her borrows her frame, volume and the site, instead of naming a service.
She also asked what it costs. The reply gives her the reason for the wait instead of a figure, and the reason is standing in plain sight: three numbered questions.
The one commitment in the whole message is an invitation. That matters more than it sounds. It’s the promise you can keep by Thursday, and it’s the first evidence Northgate will ever have about whether you do what you say you will.
And there’s no closing line asking whether she has any questions. You just asked three.
Three of these do not get this reply
Three other things arrive looking close enough to this to get the same morning. Each of them takes a different one.
A procurement pack, or a notification from a portal. Different mechanics and a different clock, and the deadline that binds first usually sits somewhere inside the pack rather than on its cover. The formal version of this morning covers what to do with it. One thing above carries over, which is the part about leaving their reference number alone.
One you are going to turn down. A same day no is cheap and worth writing well, and deciding it on Tuesday is what saves the week. The tells sit in the first message, and they’re set out in the same place. The speed stays the same. A no goes out today too.
A current client, mid thread, in passing. Halfway down a delivery thread, Dana mentions that Reno has the same problem. That’s a proposal request, it converts better than anything else you’ll see this year, and most of this page can stay in the drawer, because the apparatus already exists. You have the relationship, the subject line convention and two of the three answers. It needs one thing. Start it as its own thread, the same day, under its own name. Six months from now the second engagement has a record of its own. Noticing it at all is the part that fails, and it fails quietly.
The part of Tuesday morning that is not judgment
Whether this is real work, whether Northgate can pay for it, which three questions are the right three. That’s the job, and it stays yours. What moves is the part that decides whether the reply goes out at 8:33 or on Thursday.
Start with whether you see it at all. Four lines, no attachment, no history, no urgent word, no thread behind them. That’s precisely the profile that automatic sorting pushes down. Point weighs what it costs to be late on something apart from how much the thing matters, so four lines from an address with nothing behind them stay in front of you, above a week of delivery mail. Two measurements instead of one is the whole of that idea.
Then the writing. A reply is waiting when you open the message, in the way you write rather than in a house style, and on this particular message that’s most of the difference between sending it before lunch and sending it on Thursday. What comes back is a draft to correct. The three questions stay yours to choose, as they should be, and correcting a draft at 8:20 is a different act from composing one.
Once Dana picks a time, Point runs the back and forth and writes the meeting into the calendar with both of you on it. That’s the one piece of this morning that is pure administration.
Then the waiting, which is where the morning usually leaks. You’ve just asked three questions, and that’s a debt owed to you rather than a message you’ve dealt with. It comes back when the wait has run past what you allowed for, rather than on whichever morning you happen to think of it, and where that debt actually lives is worth reading once. If you’d rather hear about one specific thing the moment it lands, say so in a sentence. Tell me when anything arrives from Northgate. A standing request is the plainest instrument in the whole week.
And in February, when what you remember is two buildings and more volume, with the name and the month long gone, describing what you do remember is enough to find it again.
Point keeps a separate setting for how much it does without you on each kind of action, and every one of them begins at review, which means the work is made ready and then left alone until you look at it. Sending a short acknowledgment is one of the safer things to move up the dial, once you’ve read a few and liked them. The reply on this page stays at review, probably for good, because it’s the first thing a stranger will ever read from you and every sentence in it is a choice. What Point does for you goes into a log with the time on it, and what it did can be undone from there. The one thing no mail software can take back is a message that has already landed on the other person’s server.
All of this runs on the mailbox you already keep, whether that’s Google or Microsoft 365, so the address at the top of that reply is the one Marcus gave Dana.
Qualifying stays with you. Whether Northgate has money, who else Dana wrote to, what Ray said in the meeting, the wording of the proposal. Point forms no view on any of them, and they’re the parts you’re about to be hired for. The benefits page sets out the rest of it flat, Point for consultants takes the same argument across a practice instead of one morning, and Point is the product itself.
Nineteen minutes
Reading it twice, four. Deciding the subject line, two, most of which went on keeping the word proposal out of it. Writing three questions and cutting a fourth, six. Looking at the calendar for two hours you’d genuinely be glad to spend on this, three. Writing the rest and sending it, four.
The reply left at 8:33. Every sentence in it was plain, and plain was all it needed to be.
Wednesday afternoon, Dana comes back. She takes Tuesday and says Ray will try to join for the first half. Her answers to the first two questions arrive in a single paragraph. The volume is a contract starting in March that roughly doubles what goes through the Sparks buildings. What goes wrong first is receiving backing up into the aisles, which she says happened for two weeks last November.
Question three is not in the reply.
No refusal, no deferral, no mention of it at all. There’s a paragraph where two answers are, and then there’s a line about Tuesday.
Which is a piece of information, and the first one this week that arrived without your asking.