A scoping call goes cold after the call, over the two weeks that follow. The call itself ends well. You both mean the warm things you say. Then the heat leaks away while each of you gets on with other work. So the work that saves it sits in the last five minutes of the conversation and the day after.
- Enthusiasm is a state somebody was in on a Tuesday afternoon. It decays on its own, while everyone keeps the opinion of you they had on the call.
- A proposal is the first object anyone inside the client can carry. Until one exists, the work sits outside every decision, every thread and every agenda.
- Most of what keeps a call warm is settled before you hang up: the next date, the shape, the number, and who else needs to be in the room.
- The gap between the call and the document loses more work at this stage than anything a competitor does. It’s also the one part entirely under your control.
Why a warm call cools
You spent an hour with a marketing director in the first week of the month. She described a problem properly. You asked the questions nobody had asked her. By the end she was talking about the work as though it were already underway. Send me something, she said, and she meant it. It’s three weeks later now. You’ve written twice, and her side has stayed quiet.
The temptation is to read that as a verdict. Usually it’s something duller. Six things cool a scoping call, and one of the six is a decision about you.
The problem changed places in the queue. It was the biggest thing in her working life at three o’clock, because you had spent an hour asking her about it. On Thursday a supplier failed, or somebody resigned, or the quarter closed. The problem is still real and still worth money. It’s the fifth item now rather than the first, and fifth items wait their turn.
The person you charmed cannot buy. A refusal needs a request, and the request is still in her own head. The internal conversation that comes before a yes is still ahead of her. Starting it costs her an hour of preparation, and her hours are spoken for.
The job grew while you talked. Scoping conversations expand the scope, which is largely the point of them. What arrived as two weeks of review is, by the end of the call, a piece of work about the operating model. It’s a better engagement. It also needs a decision one or two levels above the person who enjoyed the hour.
The number landed badly and nobody said so. Almost nobody tells a consultant the price is wrong. Going quiet is easier, kinder in intention, and it leaves you guessing.
The trigger got dealt with another way. The board paper was written internally. The interim they hired absorbed it. The deadline moved to the spring.
You were both waiting. This is the most common of the six and the least defensible. She thinks the proposal is coming. You think a proposal needs three uninterrupted hours, and those hours belong to whichever live client is waiting on something. Eleven days pass. What arrives lands on a person whose attention has moved on.
This is worth separating from an approval that has stalled, because the two take different advice and this collection treats them apart. An approval sits inside somebody else’s organization as a decision already asked for, stuck on a person or a calendar you can’t see. A cooled scoping call is loose rather than stuck. It sits outside every queue, every owner and every agenda. On a busy week it has stopped being anybody’s business, including yours.
So most of what follows is about the room rather than the follow-up. What moves this is what you leave behind before you hang up.
What to settle before you hang up
Four things, and each takes under a minute. They’re worth more than anything you write afterwards. Each one turns a feeling into an object that outlives the call.
A date on the calendar, now. The best single predictor of whether a scoping call becomes work is a second appointment already held when it ends. A real slot, with a day and a time on it. I’ll send something over and we can take it from there is an intention shared by two people who are about to get busy. Offer two windows and settle one while you’re still talking. Agreeing a time afterwards takes four or five messages and most of a week, and the week is the thing you’re protecting.
The shape and the size, out loud. Say back what you think the work is, in a sentence, with a duration attached. Something like six weeks, with two of those on site. Both of you stay free to change your minds. What you’re doing is checking that the picture in their head matches the one in yours, while somebody’s still on the line to correct you. A proposal is a bad instrument for discovering that the two of you imagined different jobs.
Who else has to be comfortable. Ask it as a practical question, because that’s what it is. When this gets to the point of a yes, who else is in that conversation? People answer it happily. You want the names because they’re the guest list for the second conversation, and a proposal written after two conversations is a different document. Learning how a client’s decisions actually get made, who signs at what level and through what, is worth doing at kickoff, and this collection has a piece on it.
The day the document arrives. Name a date, say it aloud rather than typing it later, and choose a close one. Three working days beats eleven, for reasons that sit well away from the quality of the document. A date said in a conversation is a commitment. A date typed into a note afterwards is an intention, and intentions lose to live clients every time.
One more question before you finish, if the hour has left it open. What happens if nothing gets done about this? The case for asking that of any inquiry is made in this collection’s guide to proposal requests. On a scoping call it does a second job. Their answer is the sentence you’ll put at the top of everything you write from here on.
Saying a number in the room
The most common omission from a scoping call is the price, and it’s an expensive one. Wait until the proposal and you learn over two weeks of silence what ten seconds of watching somebody’s face would have told you.
You’re checking the order of magnitude rather than quoting, and it belongs near the end, once you know roughly what the work is. Something in this shape is usually somewhere between eighteen and thirty thousand, depending on whether we do the second site. Is that the sort of range you had in mind?
Then read what comes back. The three reactions mean quite different things.
A level face and a move to the next question means the number sits inside what they expected, and the money is real. A pause, then a question about what’s included, puts you at the top of their range. The useful move there is to make the first piece smaller rather than to argue. And a straight that is more than we were thinking is the most valuable answer of the three. Thank them for it, and ask what they were thinking. You now have a conversation about shape, where the alternative was a lost bid you never knew you were in.
The rule about keeping a price out of your first written reply still holds, for a good reason. Before a call you’d be pricing a job you have yet to see, and the number would anchor everything afterwards. By the end of the hour you’ve seen it. This collection’s guide to proposal requests works through that first reply in full.
Saying the number early is also the cheapest disqualification available to an independent. A conversation that ends there costs you an hour. A proposal that ends there costs you a day, and the reason usually stays private.
How much to give away
Two ways to lose a scoping call in the room, and they point in opposite directions.
Give nothing and the call becomes an interview. You ask thirty good questions, they answer thirty times, and they finish the hour where they started it. Nothing warm gets carried into the internal conversation, because nothing happened worth repeating. Enthusiasm survives a call when somebody heard something new.
Give everything and you’ve solved it. Well enough, anyway, that it stops feeling like an emergency, and a problem that feels understood is much less urgent than a problem that feels confusing. This is the quiet way good consultants talk themselves out of work. They diagnose, then set out the sequence, then wonder why a person who was animated on Tuesday has gone flat by Friday.
The line that works sits between the two. Be generous with the diagnosis and precise about it. Tell them what’s actually wrong, including the part they’ve left unsaid. Tell them which of their worries they can drop. That’s what earns the work, and holding it back to protect it is a mistake.
What you keep is the order of operations. The sequence, the dependencies, what to do in which week and why that week. That’s the work itself, and it’s what the fee buys. Naming the disease is one job. Writing the course of treatment is another.
One thing to give deliberately is something they can act on next week on their own. It costs you nothing, it proves the hour was worth having, and it’s the thing that gets repeated to a colleague when your name comes up.
One case sits apart, where the request is shaped from the beginning so that answering it properly is the work. The tells for spotting that in the first message belong to this collection’s guide to proposal requests.
The note that goes out that day
Send it the same day, before their evening. It lands on somebody who can still hear the conversation. A week later it lands against a memory that has faded, and anything at odds with that memory reads as a misunderstanding.
This is something other than minutes. Capturing actions, decisions and open questions after a meeting is a separate discipline with its own guide in this collection, and most meeting notes exist to settle a later dispute. A scoping note is the first draft of the scope. It’s written for somebody who missed the call.
Three parts, and it fits on a phone screen.
Their problem, in their words. Use the sentence they said, in their vocabulary rather than yours. A person forwards a document that sounds like their problem. They hesitate over one that sounds like a consultant’s category, because forwarding it endorses a framing they’re still deciding about.
What you would do about it, as a shape. Three or four lines. The parts, roughly how long, roughly in what order. Leave out the method, the principles and the plan you’re keeping.
What happens next, with the date you named. The proposal on Thursday the eighteenth. The second conversation you agreed. Whatever you promised to look up.
Send it inside the thread the inquiry began in, under the subject line you set at the start. That habit is worth having for reasons this collection’s guide to proposal requests sets out at length. Send it from wherever you took the call, in the twenty minutes afterwards, rather than from your desk on a later day. The version written from a parking lot while it’s fresh beats the polished one that goes out on Monday. By a long way, it beats the one that never goes out at all.
The gap before the document
If you can get the proposal out in three days, get it out in three days and skip this section. For most consultants the week is spoken for, and a proposal is a piece of work. Where those hours actually go, and how to get some of them back, is a subject of its own in this collection.
Two moves help when the gap runs longer than you’d like.
Send less. Most proposals are long for reasons that serve the writer. Credentials nobody asked for, methodology nobody will read, an appendix that has never once caused a yes. A document a client can read in four minutes travels around an organization. One that takes forty minutes waits for a quieter day, and the quieter day is always next week. The short one has a second advantage. You can write it on a Thursday morning, where the long one wants a Thursday you have already spent.
Send an outline for comment first. One page, ahead of the priced document. The problem as you understand it, the three or four things you would do, and the order. Leave the price off. Ask them to tell you what’s wrong with it.
That last move is the strongest thing available in this whole window, and it does four jobs at once. It gives you a reason to be in touch that reads as work rather than a chase. It surfaces the objection while it’s still cheap to fix, before the number attaches and the objection hardens into a refusal. It turns the priced proposal into a formality, because they’ve already agreed the contents. And it hands your contact a page to show a colleague, which starts the internal conversation you can’t start yourself and can’t see.
One failure mode is worth naming. An outline can quietly become the unpaid work. Half a page of shape is one object, and a phased plan with day counts against each stage is another. Keep it on the near side of that line.
The second conversation
More scoping calls are converted by a second conversation than by any improvement to what you write, and the reason is plain.
A proposal written after one call is your understanding of one person’s account of a problem. Write it after a second call, with the operations manager who has to live with the answer, and it describes the thing itself. A second person inside the client has now spent forty minutes on it. The second conversation is worth having for what it teaches you. It’s worth having twice over for what it does to the internal politics you’ll never be shown.
Ask for it on the first call, while asking is easy and free. Before I put anything in writing, it would be worth twenty minutes with whoever runs the scheduling side. I’d rather write something that’s right than write it twice.
Two cautions. Buying time with it backfires, because a second conversation you didn’t need is a delay you invented, and the client can tell. And if another call would leave every word of your document the same, skip it.
Where the client keeps you away from everybody else, that’s information rather than an obstacle. It usually means your contact is still building the confidence to spend internal credit on you. The thing to work on is her confidence rather than the document.
When it has gone quiet
Some of them go quiet anyway. This silence sits differently from waiting on a decision inside a live engagement. Nobody has bought anything, nothing has been promised, and you have no obligation to lean on. That rules out most of what people send.
The ordinary chase goes first. Just following up on my email of the ninth carries no information, hands the reader the work of composing a reply, and reminds them of a thing they already know they have left. Sending it a second time is worse than sending it once, because the repeat shows that ignoring you is free. The relationship is the only asset in play, so a message that reads as pressure costs more than the silence does.
Three re-entries work, in rough order of how often.
Something they can use. An observation, a comparable, a short account of how another organization handled the same problem, with the name left out. It arrives as a gift rather than a request. It shows them exactly the thing they were thinking of buying. They can answer it in a single line, or leave it, and either way stays polite.
A question with a small answer. Something like: is this still something you’re hoping to do this year, or has it moved? A person whose priorities have shifted answers that honestly in six words, with no failure to report, and either answer is worth having. The version that asks whether they’ve had a chance to look at the proposal asks for a status report on something embarrassing.
An occasion. Wait for a real reason to write rather than inventing one. Their results, a change in their sector, a piece of regulation, a hire. The strongest of these by some distance is the person you met changing job, in either direction. Move internally and they take the problem with them. Move to another company and they’re a warm contact somewhere new, with a problem they already believe you understand.
Two or three of those over a couple of months is enough. After that, offering to take it off your list produces an answer far more often than another attempt does. How to do that kindly, along with what to do with the no, is set out in this collection’s guide to approvals that have gone quiet.
The ones that come back
A scoping call that cooled is a considerably better prospect than a stranger, and a fair number of them return. They’ve already described the problem out loud to somebody, which is most of the work. The problem is usually still there, and usually worse.
So spend the two minutes at the moment you stop, rather than on the morning eight months later when the phone rings. Five things are worth writing down.
The trigger in their own words, because that sentence is how you’ll tell in February whether anything has changed. The shape and size you discussed, so February starts from something. The objection you left open, which is the actual reason it stalled and the thing to deal with first next time. The name of the person who was keen, which matters more than the name of the person who was senior. And a date to come back, chosen from their calendar rather than your mood. After the planning round, after the year end, after the new director has had a term to find out what’s broken.
Keep the thread and the note, too. Two years on you hold what they tried, who was uneasy about it, and why the obvious answer is a poor fit there. Everybody else bidding starts cold, and reading back a long chain quickly is how you get it back before the call. Nobody at the client is keeping that history for you.
What to do with these in a quiet two weeks with no live work is a subject of its own. So is writing to somebody you last spoke to a year ago, in a way that reads as contact rather than a request. Both belong to a separate guide in this collection.
What Point holds before a yes
All of the above is a practice rather than software. The parts that matter most stay yours: the diagnosis, the number, the judgment about how much to give away. A tool changes one thing here, and that’s how much of the bookkeeping you carry alone while a live client waits on something else. Point is a full email client that sits over the Google or Microsoft 365 mailbox a practice already runs. Your mail stays where it is, and so does the address on your proposals.
What Point does here is turn the two days after a call from something you intend into something that exists. Tell the thread in plain words that the proposal goes out on Thursday. That becomes a dated item carrying the conversation with it, in the window you’re already in. Anything you asked for and are still waiting on is kept the same way, as something outstanding in your favor. It comes back on the date you picked rather than whenever it next crosses your mind. A question nobody has answered otherwise has a habit of feeling handled.
The evidence at this stage is absence rather than arrival, so the useful instrument is often a standing request left in plain words. Tell me when anybody from Hartley writes. Tell me when Priya replies. One alert arrives on the day it fires, and the quiet days stay quiet. That’s all setting a watch turns out to be in practice.
Two other parts land squarely on this window. Getting the second call onto the calendar while the heat is on is a job Point runs itself, working the back and forth against calendars Point has already reconciled. Or you hand over a link that only offers times you can actually keep. And a reply arrives already written in your own phrasing, to alter or to send as it stands. That matters most on the message this guide is about. The same-day note is the one skipped for want of twenty minutes, and having a version to amend is what decides whether it leaves the parking lot or waits until Monday.
Around that, the ordinary work of the mailbox. A message from a company with no history behind it can still rise above two weeks of delivery threads, because what it costs to be late and how much a thing matters are weighed as two separate questions. That split has a guide of its own. Every thread carries a plain summary before you open it, so you can see that the marketing director has replied while staying out of the conversation. A short brief gathers what you need before a call, so you arrive knowing what she said in April. And a search understands your description of a thread when the words that were in it have gone.
Each kind of action carries its own setting for how much Point does unaided. Every one of them starts with a piece of work readied and then held, waiting on you. Move one up, once that kind of task has proved itself to you often enough, and Point does it from then on. That’s what moving it up means. Acknowledging an inquiry is a fair candidate. The note after a scoping call stays yours at every setting, because that note is the work. Whatever has been done is listed in order with a time beside it, and that line is where you go to take it back. A message that has already reached another company’s server is the exception, and it sits beyond the reach of any mail software anywhere.
Telling you a deal is dying sits outside what Point does. Point holds no pipeline, no stages and no forecast, and the internal thread where your contact either made the case for you or let it go sits outside the mailbox. Whether this one was ever real is your call. The only evidence of a scoping call going cold is an absence, and you turn that absence into a dated thing yourself, at the moment you send. If the question you want answered is which conversations happened in the spring and what was said in them, the tool for that is a CRM rather than a mailbox, and this collection’s opening piece works that comparison through properly. The rest of what Point does is catalogued under benefits, while Point for consultants makes this case around a whole practice rather than a single inquiry.
Common questions
How long after a scoping call should I wait before following up?
For the first one, the same day. The note goes out that evening, and it’s the thing the call was for. After that the clock is set by whatever you promised. If you said the proposal arrives Thursday, Thursday is the only date that matters, and being early is worth more than being thorough. Once the document is with them, give it a week before the first re-entry, then leave two or three weeks between attempts, and stop after the third. The instinct to write on the fourth day comes from your anxiety rather than from anything happening at their end.
Should I give a price on the scoping call?
A range, yes, near the end, once you know roughly what the work is. Call it a range rather than a quote, which takes one clause. What it buys you is the reaction, and the reaction is information you can get no other way. Almost nobody will tell you in writing that a number was wrong. They go quiet instead. Give the range once you understand the job, which is why a price in your very first written reply is a different question with a different answer, taken up in this collection’s guide to proposal requests.
What do I send if the proposal is going to take two weeks?
An outline for comment, on one page, with the price left off. The problem as you understand it, three or four things you would do, and the order. Ask them what’s wrong with it. That gives you a reason to be in touch that reads as work rather than a chase. It gets the objection out while it’s still cheap, and it gives your contact something to show a colleague. Better still, use it to make the two weeks unnecessary. Most proposals are long for reasons that serve the writer rather than the reader, and a four-minute document travels around an organization where a forty-minute one sits still.
They said they would come back to me and never did. How many times should I write?
Two or three, spaced out over a couple of months, and each one carrying something the last one lacked. A repeat of the same message is the first one arriving again, and it teaches its reader that your mail can safely be left. When those are used up, offering to close it produces an answer more often than another attempt does. You want the answer more than you want the hope. A no in September on something budget-shaped is frequently a yes in February.
Is a scoping call just a free consultation?
It’s unpaid, and unpaid is a different thing. An hour spent understanding a problem well enough to price it is a normal cost of selling advice, and charging for it early in a relationship loses more work than it earns. What you’re watching for is the shape where the questions keep arriving, a meeting is never offered, and the real request is a short paper. The tells for that are readable in the first message, and this collection’s guide to proposal requests goes through them. Inside a genuine call, your protection is generosity with the diagnosis and keeping the sequence.
The person I spoke to has left the company. Is it dead?
Usually the opposite, if you move. The problem stayed behind, and whoever inherits it is new, under-briefed and looking for somebody who already understands the situation. That’s a description of you. Write to your old contact at their new employer, because they arrive with a mandate to change things and a problem they’ve already explained to you once. Then write to whoever picked up their work, referring to the conversation and offering the summary you wrote at the time. That note you sent on the day of the call, a year ago, is worth more this morning than anything else in the archive.
The short version
A scoping call cools for reasons that are mostly about their week. The problem lost its place in a queue. The person you spoke to has to ask somebody else. The job grew past their authority. The number landed badly. Or you were both waiting on each other. Nobody inside has asked for anything or is carrying it, which is why the rescue lives in the room rather than in the follow-up. Settle four things before you hang up. A second date on the calendar. The shape and size said out loud. The names of everybody who has to be comfortable. And the day your document arrives. Give a range in the room and watch the reaction. Be generous with the diagnosis and keep the sequence, because the sequence is what they’re buying. Send the note the same day, in their words, short enough to be forwarded. If the proposal will be slow, send a one-page outline for comment instead. That surfaces the objection early and gives your contact something to show a colleague. When it does go quiet, re-enter with information rather than a nudge, three times at most. Then offer to close it, and write down the trigger, the objection and a date to return. The inquiry that started it, the approval that stalls once you have won, and the scope that drifts after you start are each taken up on a page of their own here.