The message that opened it is already in your mailbox, and you read it four weeks ago.
On November 19 the Thursday update goes to Dana, Ray and Alex, the way it has every week since October. Next morning a reply comes back from an address you’re seeing for the first time. Two lines, Ray copied, from somebody called Priya. Did the picking route work cover the returns aisle? They’re looking at Reno in the new year.
You answer it in eleven minutes, accurately, and go back to the interim findings. It slides straight past you. The subject line is one you wrote yourself. It asks you for nothing. It’s really addressed to somebody else.
That’s the renewal conversation opening.
What the eight weeks of silence turned out to be about was a decision Northgate makes in January. People you’ve yet to meet make it, out of money that sits in a different queue from your fee. So here’s what a January decision sounds like in November, from outside the building. It sounds like a question about a site outside your contract. It comes from a name outside your distribution list, attached to a season rather than a date.
So this part is about noticing. At this stage, noticing is the whole of the skill. There’s nothing to ask for yet and nobody to ask. Here’s what the signals look like, how to tell a live one from a warm one, what to write back on the day one arrives, and what to do with all of it before your last day.
Six messages that are all the same message
None of them contains the word. Each one makes sense only if somebody at the client has been thinking about a stretch of time. That stretch starts after your engagement ends.
A question about a period beyond your contract. Priya’s question is about the new year. That’s the tell. It’s the only part of the message that matters. The subject of the question barely counts. The period attached to it is the signal.
A new name, reading your work. Somebody has moved your findings around inside the building. People rarely forward a supplier’s document to admire it. They forward it to make an argument with it. A new name on a thread you own means a conversation has been running for days out of your sight, and your document is in it. The names you cannot afford to miss get marked in advance, and this is the case that list handles worst. The person who matters most this month is a stranger to your mailbox.
A forward you were copied on, with an empty space above it. On November 10 Ray sends your interim findings to two addresses at Reno and adds no covering note. It looks like the least significant message of the week. A document that goes out bare is usually one the recipients were already expecting. Which means it was discussed before it was sent.
A request for the method rather than the answer. On December 2 Dana asks whether you can send the route timing spreadsheet in a form they can keep using. That’s a request for a tool, and it has two opposite meanings. One is that Northgate intends to do the next round themselves. The other is that Northgate intends to do the next round somewhere else, and is working out what that would take. Only one of those is a renewal. The message reads identically either way.
The thing you excluded, coming back as a question. The night shift was out of scope in September, and dead as a scoping decision by the end of the observation days. If it reappears in December, it’s a new piece of work wearing the old subject line. Somebody has read what the two-shift version told them, and now they’re asking.
A logistics question that only makes sense if you’re coming back. Facilities asks whether to deactivate your badges on the 18th or leave them until the end of the quarter. Somebody asks what February looks like for you, in the middle of a paragraph about something else. Somebody asks whether four observation days is a standard number, or whether it was specific to this job. Each is administrative on its face. Each is a scheduling question underneath.
None of these is an inquiry. Everybody involved is still thinking it over. Answer one as though a sale has started, and you close the channel that produced it.
Why it arrives sideways
Worth understanding once. It settles most of what follows, and it teaches you to take the quiet ones seriously.
At this stage you’re evidence in the conversation. Somebody inside the client has a problem for next year. They’re assembling a case for it, and they’ve reached for the most credible document within reach. That’s yours. What leaks out to you are the byproducts of that work: a fact-check, a scope question, a forward. They’re about their problem, so they’re addressed to whoever is working on it.
Which produces the thing that catches people out. The energy in a message runs independent of the size of what’s behind it. Four lines about the returns aisle can be a larger piece of work than the one you’re finishing. “We should absolutely keep this going,” said warmly at the closing lunch with a handshake, is usually nothing at all. Saying it is free, and afterward somebody has to carry it, and nobody does.
Energy is a fact about the sender’s afternoon. You’re reading for two things, the period and the person. A stretch of time after your last day. A name other than your day-to-day contact. Both are free to check, and between them they do most of the work.
There’s a second reason it comes sideways, and this engagement already taught it to you. The person who funds next year sits behind the person talking to you. Ray goes past somebody. That somebody hears from you once there’s a document to send, and stays silent until then. Everything before that reaches you through intermediaries. Which is exactly why it arrives as somebody else’s question.
Telling a live one from a warm one
Three tests, in the order of what they cost you.
Is a period attached? A period, rather than a date. In the new year. Before the Q1 count. When Reno kicks off. Next budget round. Somebody who attaches a stretch of time to a thing has at least imagined it happening. Somebody who leaves the time open is being friendly. This test is free. The answer is already in the message you have.
Is there a second person? An internal conversation involves more than one person, and it leaves marks. A cc that surprises you. A forward you were copied on. A question about something outside your contact’s own area. A contact who has said “I” for two months, starting to say “we.” One person interested is interest. Two people asking about the same period is a conversation.
Does it survive one concrete question? This is the only test that costs anything, and it costs very little. Ask something small and specific. Ask something only a person who has really thought about it can answer. Ask whether Reno is its own project with its own budget, or whether it comes out of the operations line. Ask whether the Q1 count is the first week of February or a moving date. Ask who is putting the Reno plan together. Asking whether they’d be interested in extending the work earns a polite yes that means nothing. It asks for a commitment nobody in the room can give.
Somebody in a live conversation answers those in one sentence, because they already know. Somebody being friendly says they’ll find out, and then it goes quiet.
There’s a fourth test, and it’s the one you already used before any of this was an engagement. Ask when it would be decided. If nobody can name a date, it’s still an idea in somebody’s head. What’s different now is that you’re inside the building, with a better way of finding out. That’s the subject of the previous part, and it works unchanged here. Ask about the client’s calendar, and leave anybody’s intentions alone.
The two calendars that decide the date
There are two, and most consultants track only one.
The calendar that funds the work. A fiscal year, a budget round, a capital cycle, a committee that sits monthly. It sets the earliest date money can exist, and it moves on its own schedule. At Northgate, anything with a number goes into a queue that restarts in January. So the best December work in the world still produces a January decision.
The calendar that creates the need. Their operating events: the Q1 count, peak season, an audit, a system cutover, a site opening, a reorganization. This is the more useful of the two, and almost nobody asks about it. It sounds like an operational question rather than a commercial one. Work attached to an event on this calendar has its own reason to happen at a particular time, and that reason stands apart from your availability. A reason of that kind survives conversations that your own arguments lose.
Then the arithmetic, and the reason to do it in the second week of December rather than the first week of February.
Work backward from the funding date to the last day it’s still useful to be talking. The queue restarts in January, and Priya wants Reno work in the new year. So the people who decide it need something written in front of them before they meet. Something written means a conversation in December. Which makes the useful window the two weeks you’re standing in. It’s the same shape as the last date on which a yes is still buildable, pointed at a different decision.
And be honest with yourself about what happens if you miss it. After the 18th you’re outside. Your access to Alex decays. So does your standing to ask Dana something in passing, and the way your name comes up in rooms down the hall. All of it decays quickly, and it stays gone. Two months after a well-delivered engagement you’re somebody who did good work once. Somebody standing in the aisle today holds a considerably stronger position.
What to write back on the day
Three jobs and one prohibition.
Answer the question completely, as though it were an ordinary question, because it is. Somebody wants to know whether returns was covered. Being useful in the four minutes available is what gets you included in whatever comes next.
Then name the shape of the larger thing, with no price and no ask. One sentence, describing what would be involved, in the units you actually work in. A statement about how long something takes.
Then leave the door visible once, and stop.
The prohibition is the one everybody breaks. Don’t answer a four-line question with a proposal. The person who asked is gathering material for somebody else, and has no authority to decide anything today. Send them a pitch and two things happen at once. The material they wanted is now inside a sales document they can’t forward to anyone. And the channel that produced the question closes, because next time they’ll ask somebody who answers questions with answers.
Yes and no, and the distinction matters if you are planning Reno. The routing analysis covers the returns aisle as part of the layout, but the timings behind it come from the three highest volume picking aisles, so anything I say about returns specifically is inference rather than measurement.
If returns is a real question at Reno, it is a measurable one: roughly two days of observation on the returns lanes and a day to work it up, and then you would have numbers instead of my inference. Happy to talk it through with whoever is putting the Reno plan together, before I finish here on the 18th or after.
That’s a hundred and twenty words, and it does four things.
It answers the question honestly, including the part that weakens your own work. The sentence admitting the timings are inference is what makes every other sentence in the message credible. It’s also the one most people cut.
It names a size and leaves out the price, so the message stays forwardable. Two days and a day is a fact somebody can put in an internal note. A number with a currency symbol turns the message into a commercial document. Commercial documents get handled differently by everyone who touches them.
It asks a question in the last line, quietly. Whoever is putting the Reno plan together is exactly the name you need. This is the cheapest way there is to ask for it.
And it puts the 18th in front of them as a fact about your calendar, and leaves it there.
Two small things around it. Reply to everyone who was on the message. Priya wrote with Ray copied, so Ray stays copied. A supplier who starts a side conversation with somebody at a client creates a problem for their contact, and that problem outlasts the engagement.
And write it down for yourself the same afternoon, in the note you started keeping after the scoping call. The exact words, the date, who was copied. Then the three things you have yet to learn: whether Reno has its own budget, who owns the plan, when it gets decided. In March that note is the one thing that will tell you why you’re writing to Priya at all.
Which recommendation is the one
The report is the last thing you make. It’s also the only thing still in the room in February. Its recommendations are where the open items end up, each with a size and a start date, and that’s worth doing either way.
What belongs here is the ordering. It takes ten seconds, and most people order it by instinct instead.
Put first the recommendation somebody has already asked about. The one with a question behind it, ahead of the largest, the most interesting, and the one that follows most naturally from section 6. It’s the only one that already has a person inside the building who wants it to exist. A recommendation with an internal sponsor is a different object from one you invented. The ones you invented can be technically better and still die on the page.
Describe it in the words the question used. If the question was about returns at Reno, the recommendation says returns and says Reno. The instinct is to generalize it into extending the routing method to other sites. A generalization is harder to fund, because its cost is a guess. It’s harder to recognize too, which matters more. The person reading in February has to find their own question in your document.
And keep it to a size one person can approve on their own. Two days of observation and a day of analysis is a decision one person makes. A twelve week program is a budget round. Both may be right eventually, and only one of them can start in February.
The ones that look live and are not
Five false positives. Knowing them saves a December.
Warmth at the closing readout. The room is pleased, the work landed, and somebody says you should definitely do more of this. No period, no second person. It fails both free tests. People say it when something has gone well, and they mean it kindly.
A champion who is leaving, or whose job is changing. The strongest signal in your mailbox depends on the person behind it still being there in March. Asking directly is awkward, and it shows anyway. Somebody on the way out asks about the future slightly at arm’s length. They hand things over. They stop committing to anything past a certain month. If that person is your only internal sponsor, the whole thing is standing on one leg.
An introduction with nothing attached. “You should talk to my counterpart at Reno” is a kindness, and on its own it converts badly. The counterpart has a full week and a problem of their own for next year. It becomes real when it carries a reason: a specific thing at Reno that your work says something about. When an introduction is offered, ask for the reason to be in it.
A rate question from somebody outside the buying seat. Occasionally a number is being checked against a competing bid, an internal estimate, or a headcount case. It’s ordinary, and there’s one thing to do about it, which is to notice it. A question about price with no period and no scope attached is rarely a purchase.
A request for your tools that is genuinely a handover. Sometimes Dana wants the spreadsheet because Northgate intends to run it themselves next quarter, and that’s a good outcome. A consultant who makes their method hard to hand over gets one engagement. One who hands it over cleanly gets asked back for the part the client needs help with. The way to find out which it is, is to ask. Are you planning to run this yourselves, or is somebody looking at doing it somewhere else? Both answers are useful, and both are easy to receive.
When this is a pipeline problem instead
Three cases where everything above is the wrong instrument.
The client buys through a procurement cycle. Maybe the next piece of work goes to competitive bid. Maybe it sits under a master agreement with a stated renewal date, or arrives through a vendor portal with a published calendar. Then the date is something to look up, and week two was the time to look it up. Signals still tell you whether anybody wants the work. The process stays the process, and a required tender stays a tender however much goodwill is in the room. Ask your contact plainly what would have to happen procedurally for a second piece of work to start. Ask well before the report.
You have more than a handful of clients renewing on fixed dates. Fifteen retainer clients on annual cycles is a pipeline with dates in it, and that’s what customer relationship software exists for. Everything on this page assumes two or three engagements at a time. At that size the live renewal conversations fit on a list you genuinely read. Past that, buy the thing built for it, and keep the mailbox for the conversations.
Nothing has been raised anywhere. No period, no second person, no answer to a concrete question. Then the conversation to spot is still months away, and the 18th arrives first. You’re fine, and knowing it early is worth a lot, because it changes what the closing weeks are for. The work becomes leaving a reason to come back, which is a different activity with a different shape.
What a mailbox can be made to notice
Nearly all of the above is judgment. Whether a returns question is a renewal or a pleasantry. Whether Priya matters. Whether Reno goes first in the recommendations. That’s the work, and it’s why somebody hired a person rather than a tool.
What software can do is the part that failed on November 20, which was mechanical all along. You read the message. Then the day carried it away, and it stayed away.
Being told when a new name appears. One sentence, and it’s the instrument that matters most on this page. Ask to be told when somebody outside your distribution list replies on a Northgate thread. Ask to hear when anything arrives from an address new to this engagement. You hear once, on the day. A standing request of that kind turns a forward you were copied on from something you skim into something you look at.
A name that becomes a person. Priya lands in your contacts with the messages attached. So the second time that name appears, you recognize it instead of squinting at an address. Deciding who is worth being interrupted for usually happens up front. This is the case where the list gets to grow in week nine.
Finding it again in March. By February you’ll remember that somebody asked about returns. The name, the date and the wording will be gone. Search on the fragment you kept, and the message comes back. That’s the difference between a note that refers to a message and a note that leads to one. It matters here more than in most places, because the whole value of the November email is that it’s dated and in their words rather than yours.
An item that outlives the engagement. Ask Priya about the Reno plan in the first week of February. That’s a dated item with a look date past your last day, and how the date gets attached is worth reading once. It’s the most reliably lost item in consulting, because it belongs to no engagement. The one you’re finishing is over. The one it belongs to is still hypothetical. A list held per person rather than per project keeps it, and whether it gets written down at all is mostly a question of what typing it costs.
Reading a thread you were dropped into. A forward arrives carrying eight messages of history, all of it new to you, usually on a morning with no room in it. A plain account of a long chain is the difference between reading it and meaning to.
How far Point goes on its own is set separately for each kind of action, starting at review. At review, Point prepares the thing and holds it for you. There’s a good case for leaving drafting right there through all of this. A reply to a person you’ve yet to meet, at a client you’d like to work for again, is exactly the message worth reading before it goes. Anything done on your behalf lands in a timestamped log, and you can reverse it afterward. The one exception is the one every mail system shares: a message sitting on somebody else’s server has arrived.
The limits are worth stating flatly, because this subject invites overclaiming more than anything else in the series. Point has no view on whether a question about returns is a renewal signal. Northgate’s fiscal year, the money sitting in a different queue from your fee, what a second engagement would be worth: all of that lives with you. So does the pipeline, the forecast, and the question of which recommendation belongs first. Point wasn’t at the readout. Every act of reading a situation on this page is yours. What changes is that the evidence is still in front of you at the moment you go to read it.
Everything else Point does is written out plainly on the benefits page. There’s also the consulting shaped version, which takes this across a practice rather than one client, and Point is the product itself.
The whole of it, in date order
Set it out in order. In order it’s obviously one conversation, and on no single morning did it look like one.
November 6, the interim findings go to Dana, Ray and Alex. November 10, Ray forwards them to two addresses at Reno and writes nothing above them. November 20, Priya asks about the returns aisle in the new year. December 2, Dana asks for the route timing spreadsheet in a form they can keep using. December 9, facilities asks whether the badges come off on the 18th. December 18, the report goes out with returns at Reno first in the recommendations, two days and a day, described in Priya’s words rather than yours.
Six messages over six weeks, and two of them you wrote yourself. Of the four that came in, one was addressed to somebody else entirely and two were administration. Not one contained the word renewal, or the word proposal, or a single question you were expected to answer commercially. By the 18th you know more about next year’s work than you knew about this year’s on the day the original request landed.
Which is where this ends, because what happens next is where it started. Some morning in February a message arrives. Four lines, a name you half recognize, a subject line somebody typed in ten seconds. And a description of the work that differs from the work you’d end up doing.
You already know what that message is. What’s different this time is that you know where it began. It began on November 20, in a question about a returns aisle. Everything you did between then and the 18th is the reason it’s sitting in your inbox rather than somebody else’s.