A proposal request arrives while somebody is comparing you with other people, and nothing in it says so. It’s the only message in your inbox that works that way. What it asks of you on the day it lands is smaller than it looks. An ordinary reply, sent quickly. And a decision about whether this one is worth a proposal at all.
- The formal ones are unmistakable, and they’re often the least likely to become work. The ones worth having arrive as four lines from a name you half recognize.
- What the message leaves out tells you more than what it says. The most useful blank is why this is happening now.
- Waiting until you can do it justice is what loses it. The fast reply exists to win a conversation, and you write the proposal once you know something.
- A fair share of these should be declined, and the tells sit in the first message rather than at the end of a week of unpaid work.
The requests that arrive in disguise
A mailbox sorts by how much a message looks like it matters. On this one subject, that instinct runs backwards.
The unmistakable ones announce themselves. A procurement portal generates a notification with a reference number. A pack arrives called request for proposal, phase two. There’s a deadline, a document set and a named contact who isn’t the person who’ll do the work. You’ll spot it straight away. On honest numbers it’s among the least likely things in your week to become an engagement. You’re one of six, and two of them have been talking to this client since spring.
The ones that convert look like nothing at all.
A referral runs to four lines with no attachment and a throwaway subject. Somebody you worked for two years ago mentioned your name over lunch, and this is the result. In the list it looks less pressing than a newsletter.
A past client coming back is the highest value message a consultant receives. It’s also the one most often read as a friendly catch up. We were talking about you the other day is business, and it’s business because the company has already paid you once.
A form fill from your site or a professional profile is terse by construction. The form gave them three boxes, and one of those was for a phone number.
An intermediary is two conversations at once. A peer, a broker or a small firm has won something and needs a pair of hands. The client you’d actually be working for stays out of sight, and out of reach of your questions.
And then there’s the one that arrives inside another conversation. Halfway down a delivery thread on live work, a client mentions that the board has asked for something else. Or that the finance team has the same problem. Or that they’ve been wondering what to do about the second site. That sentence is a proposal request. It converts better than anything else on this list, because the trust is already paid for. It’s also the one you’re most likely to answer with a single line about the thing you were actually discussing. The general problem of live work drowning out everything quieter belongs to the piece that opens this collection. The narrower fact worth carrying away is this. The best new business a consultant gets often arrives inside the mail of the work already sold.
So the habit that helps is a question, put once a day to the mail you’ve already read. Did anybody just describe a problem they haven’t asked me to solve. You can ask that of a whole morning without opening a single thread, because every thread carries a plain summary.
Read it for what is missing
A proposal request is defined by its blanks, and there are six of them. A first message gives you two or three at most. That’s ordinary, and the person writing is being perfectly polite.
The outcome. What good looks like to them, said as a result rather than an activity. A review of our operating model is an activity. We cannot open the third site until somebody tells us how the second one should have been run is an outcome. Nearly every request arrives in the first form. The activity is what the client has been calling it internally for a month.
The person who decides. Usually somebody other than the person writing to you, and often somebody your contact names only when you ask.
The date that forces it. Something happens on a particular date if the work hasn’t been done. That’s a different date from the one they’d like it by.
Why now. The strongest single signal in the whole message, and the one most often missing. Something changed: a new finance director, a system that failed, a board paper due in November, an acquisition, a letter from a regulator, a resignation. A request with a trigger has money somewhere behind it. Somebody has already had to explain the problem upwards to get permission to ask you. A request with no trigger is a person thinking, and thinking has no budget. If you learn one thing about an inquiry, learn this one.
The size in their head. A shape rather than a number, and whether it’s two weeks or two quarters in their imagination. The distance between their shape and yours is why proposals come back declined, with no counter offer and no explanation.
Who else is being asked. And how far along those conversations already are.
You ask two of these in the reply and get the rest on a call. A list of six questions reads as an intake form, and it puts you straight back among the vendors. If you only get two, ask what happens if this doesn’t get done, and who else needs to be comfortable before it does. The first tells you whether the work is real. The second tells you who you’re actually writing for.
One of the blanks deserves a gentler reading than it usually gets. A client who names no budget is almost always being honest. They genuinely don’t know, and any number they guessed at would be wrong in both directions. A client who can’t name a decision maker is usually describing an organization that has yet to decide to decide. That’s a useful thing to learn in the first week rather than the sixth. What to do about a decision sitting inside somebody else’s company is its own subject, and this collection takes it separately.
Answer today and propose later
The most expensive mistake with a proposal request is treating it as a piece of work. Work needs three uninterrupted hours, so it goes on Thursday. Thursday belongs to whichever client is waiting. Then it’s the weekend, then it’s Monday, and the request is nine days old. The person who sent it has spent one of those days on a call with somebody who replied the same afternoon.
The general case for giving new business the fastest answer in your week is made in the piece that opens this collection. What belongs here is what that fast answer is for.
It’s there to become a conversation, and that’s the whole of what it can do. Reach for more in it and you can lose the work.
Four things go in it and nothing else. One sentence that proves you read the message, written in their words, naming the outcome rather than the activity. Whether you can help, said plainly, or what you’d need to know before you could say. Two questions, taken from the six above. And a next step with real times in it, rather than an invitation to tell you what suits.
Your method, a price, a capability deck, a client list and three paragraphs of background all wait. Each one is a thing to discuss once you know what the job is. Send them on day one and you’re interchangeable with everybody else who attached theirs.
One mechanical habit here pays out for the next six months. Rewrite the subject line to the outcome, in the words they used, and leave it that way. Reply inside that thread for everything until the work is signed or lost. The proposal, the revised price, the introduction to the third stakeholder and the eventual yes all end up in one place under one name. You’ll find it in a minute a year and a half later. Consultants who do this have an archive. Consultants who start a fresh message each time have a search problem instead.
There’s a second gap in the same shape, further along, and it loses more bids than slowness at the front ever does. Between the call and the proposal arriving, eleven days pass. The proposal is a piece of work again, and Thursday is still Thursday. It closes the same way. On the call, name the day the document will arrive. Then treat that date as something you owe a client. A proposal that lands on the day you said it would is evidence about how you work, delivered before anybody has bought anything.
The ones worth turning down
A good number of these requests are somebody else’s internal process wearing your name. Recognizing them early is worth more than any improvement to how you write, because the cost of the others is measured in days.
The third quote. Their policy requires three bids, and they already have a supplier. The tells are short notice against a large scope, a specification unusually complete for a first contact, and a reluctance to talk before you price. The scope reads as though it was written with one particular firm in mind, because it was. The test is a call. If a conversation stays unavailable on any terms, you’re supplying paperwork.
The free consultation. The request is shaped so that answering it properly is the work. Send us your view of how you would approach this, with an outline of the first phase. The tells are that they want the approach in the document more than the price, that questions keep arriving while a meeting stays off the table, and that what they’re asking for reads like a short paper. What a client buys from an independent is the thinking, and this shape of request asks you to hand the thinking over unpaid. That argument is made at length in the piece that opens this collection.
The internal build. A team that could do the work themselves wants a shape and a number to size their own effort against. The tells are that the inquiry comes from the function rather than from anybody sponsoring it, and that the questions are about method and day counts rather than availability. The date you could start has yet to come up.
The bid you can’t win. Read the mandatory requirements before you write a word. A turnover threshold, an insurance level, a named team of four, references from a sector you’ve never worked in: any one of them ends it, and ten minutes of reading has just saved a week.
And a fifth that’s nobody’s fault, which is work you can do and should turn down anyway. Below your rate, outside the patch you want to be known for, or from somebody who has already shown you across two emails exactly how the engagement is going to go.
Declining is cheap and fast and worth doing well. A good no arrives the same day, keeps its reason clear of anything worth arguing with, and offers a name where you have one. That’s why the person calls you first about the next thing, and why the person you named returns the favor. The one real difficulty is that these requests look their best when the calendar looks its worst. So set the rule in a busy month, and let the quiet morning follow it. What to do with the quiet months is a subject of its own and this collection has a piece on it.
When it is a formal RFP
A procurement process changes the mechanics enough to be worth handling as a different animal. Four of the changes sit squarely in your mailbox.
The deadlines live outside the email. They sit inside a document, or on a portal page, or in an addendum published after you downloaded the pack. The one that binds first is the clarification window, usually a week or two ahead of the submission date. Once it closes, questions are over. Miss it and you’re bidding against your own guesses about what they meant. That date goes on the calendar the day the pack arrives, before you’ve read any of it.
The portal sends machine mail. Notification of an addendum, notification of a message, notification that your registration succeeded: one sender, one subject shape, one tone. One of them changes the specification and the rest are noise. They arrive in the middle of a week that already belongs to a client. This is the most common way a serious bidder ends up submitting against the wrong version of a document.
Your questions are published. Most processes restrict you to the named contact, and answers to clarifications go out to every bidder. The questions you’d have asked on a call are closed to you, and the ones you do ask tell the field what you’re thinking. Ask what you genuinely need in order to bid, and stop there.
The file they score is the one on the portal. Not the one attached to your last email, and not the copy in your downloads folder. Keep one working version in one place. Upload with hours to spare, because a portal closes on its own clock, and a failed upload at 11:55 is a bid that never existed.
Underneath the mechanics is the question of whether to answer at all. For an independent the arithmetic is harsher than it first looks. A serious response is several days of unpaid work against a field that includes firms employing people whose entire job is writing them. Two questions settle it. Do you meet every mandatory requirement without a caveat. And is there a reason this client would choose you specifically over a larger supplier, which in practice means an existing relationship, a named specialism they can only get from you, or somebody inside who already wants you. Answer the second one first, because a blank there ends the matter.
What to write down the day it lands
A proposal request creates a short chain of dated obligations, and every one of them lives outside your mailbox. Why that’s the general condition of consulting, and why silence is the hardest thing in an inbox to see, is set out in the piece that opens this collection. The chain itself is specific, and it’s always the same five items.
The reply you sent, and what you promised inside it, which is usually a date. The call, and the questions still open when it ended. The day you said the proposal would arrive, which is the one date in the whole sequence you control absolutely, and so the one that says most about you. The day you sent it, and which version went. And the date you’ll come back to it if the reply stays quiet. Pick that date at the moment you press send, because a question nobody has answered has a habit of feeling handled.
Two facts about the opportunity belong beside that list, because both decay. Who else is bidding, if you ever find out. And the trigger, written down in the client’s own words. Six weeks later that sentence gives you something to say beyond checking in. Eight months later it’s how you know the problem is still there.
Keep the ones you lost. A bid that went nowhere, together with what you sent and whatever you learned about why, is worth more than most consultants assume. Keep it for the day they call back, because a good share of them do. A proposal you can produce in a minute is a running start on a conversation everybody else in the field is having from nothing. The wider case for keeping rather than clearing, and for treating the mailbox as the only engagement file an independent has, is made in this collection’s opening piece.
Sending it so it survives a forward
Almost every proposal is read by somebody who was never on the call.
Your contact forwards it, sometimes with a line of their own and often with the file alone. The person who opens it next has your document and nothing else. They were somewhere else when the problem was described, and they’re weighing what you wrote against a number already in their head. Write for that person and the proposal works in both places at once.
That puts real weight on the covering message, because the covering message is what gets forwarded with it. Two or three sentences: what the document is, what it costs, and what decision you’re asking somebody to make. A note that says as discussed, please find attached, arrives at the other end meaning nothing at all.
Four things follow from that, and they’re small.
Put the price where it can be found rather than where it feels comfortable. Everybody looks for it first. Making them hunt adds an irritation to the reaction and leaves the reaction exactly where it was.
Name the decision, and name one. Whether to go ahead with the first phase, starting in the week of the ninth. Asking for their thoughts on the below leaves them nothing to decide.
Give it a date after which something changes, and be straight about what changes: your availability, the price, or the start. A consultant has to invent their own deadlines, because the client’s organization will supply none. That’s argued in the piece that opens this collection, and it applies here as squarely as anywhere.
Offer options where the work allows it. A single price is a yes or a no. Two or three shapes at different sizes turn the reply into a question about which one, and that’s a far easier message for a person to send. It’s a habit rather than a rule. A formal RFP that demands one figure rules it out, and so does a job with one honest shape.
Then send it in the thread you’ve been using, under the subject you set in the first week, and stop. What happens between sending and hearing, and how to come back without becoming somebody who chases, is a separate craft. What the proposal turns into once somebody says yes, and how the agreed scope is kept from quietly drifting apart from the work, is the next guide in this collection.
The parts Point can carry
Everything above is a practice, and consultants ran it on a card index for decades before software offered to help. The job itself stays as it is. What a tool changes is which parts of the job you hold in your head on a Tuesday, while a client waits for something else. The split is clean: the judgment stays entirely yours, and Point carries the bookkeeping.
Start with the ranking, because this subject depends on it most. Point weighs your mail before you reach it, on two questions kept apart. What it costs you to be late, and how much the thing actually matters. So four lines from an address with no history behind it get the same weighing as two weeks of delivery threads. That’s the whole difficulty with an inquiry. The one most likely to convert carries no attachment, no urgency marker and no past correspondence, which is exactly what every other kind of sorting rewards. Important and urgent as two different measurements is a subject in itself. You can also mark the people who count, so a message from a company that has already paid you rises on the strength of who sent it rather than what it happens to say.
Then the reading. Every thread arrives with a summary of a line or two, which makes this piece’s daily question cheap to ask. Did anybody in a morning’s mail describe a problem they haven’t asked you to solve.
An ask inside a message becomes a dated item of its own, with the thread attached to it. Nobody typed it into a list. The questions you sent out in your first reply sit there too, as debts owed to you. They come back on a date you picked, rather than on whichever morning they cross your mind. You can leave a standing request in plain words as well. The answer you’re waiting on from one particular company then reaches you once, at the moment it lands. Setting a watch is what that looks like on an ordinary week.
A reply arrives already written in your own way of putting things. You change it or send it as it stands, and that counts for most on the exact message this guide is about. The same day answer is the one skipped for want of ten minutes. Starting with something to correct is the difference between sending it this afternoon and sending it on Thursday. Once a call is agreed, Point runs the scheduling back and forth against calendars already reconciled. Two offered windows stay two offered windows, rather than a chain of five messages in the one week where tempo is the only advantage you have.
For a document pack, attachments gather into a list of their own, each one still joined to the message it arrived on. That’s where an RFP and its three addenda stay together. You can put a question to one of those documents, and the answer comes back naming the page it came off. That’s a reasonable way to find out whether a forty page pack demands a level of professional indemnity cover you don’t hold. You find that out before the week of work rather than after it.
Each kind of task holds its own setting for how far Point goes without you, and every one of them opens in the same place. A piece of work is prepared and then held, with your yes as the last step. Watch a kind of task enough times, raise its setting, and Point gets on with it from then on, because that’s what raising it means. The dial is the proper account of that. Acknowledging an inquiry is a fair candidate for moving up. A proposal stays at the bottom of the dial, and it stays there for good. Whatever gets done for you appears in a list with a time against each entry, and most entries can be taken back from there. The one exception is a message that has already arrived on somebody else’s server, which no mail software can reach.
Everything stays where it is. Point sits over the Google or Microsoft 365 account the practice already has, so the address at the top of the proposal is the address it has always been.
Qualifying stays with you. Point holds no view on whether a request is real, no sight of the other four people bidding, no opinion about your win rate, and no way of telling you that the scope was written around a competitor. Point holds no pipeline stages and writes no proposals. Those are the parts that are actually the work, and they’re why the client is talking to an independent rather than to a firm. The benefits page is the full inventory, Point for consultants tells the same argument through a practice, and Point is the whole of it on one page.
Common questions
How fast does a proposal request really need an answer?
The same day, and the reason is narrower than general advice about responsiveness. The first reply competes on one thing: being the conversation that starts. The person who books a call on Tuesday is discussing the actual problem while everybody else is still composing. Quality has nothing to do with it, so waiting until you can do it justice buys you nothing. If the day is genuinely gone, four lines will hold the position. Name the outcome in their words and offer two windows. The considered part happens once you know what the job is.
Should I put a price in the first reply?
Almost never, and the reason is the missing information rather than negotiating posture. Until you know the outcome, the trigger and who decides, any number you give is a guess at a job you haven’t seen. That guess becomes the anchor for everything afterwards. One exception is worth naming. When somebody is plainly collecting three quotes and will take no call, a price is all they’re ever going to get from you. So the choice is between sending one quickly and declining, and both are cheap. Writing a full proposal for that request is the expensive option.
How do I tell a real inquiry from somebody collecting quotes?
Ask why now, and read what comes back. A request with a trigger behind it has a person attached who has already had to justify the problem to somebody above them. At that stage, that justification is what a budget actually is. A request with no trigger, an unusually complete specification, a tight deadline and a reluctance to talk is a procurement exercise you’re furnishing. The single test that separates them is whether a call is available. Anybody seriously considering hiring an independent consultant will give you twenty minutes.
Is it worth an independent responding to formal RFPs at all?
Sometimes, and the decision takes ten minutes rather than a week. Read the mandatory requirements first, because a turnover threshold or an insurance level ends it before any writing starts. Then ask whether there’s a reason this buyer would choose you specifically over a larger supplier. That usually means an existing relationship, a specialism they can only get from you, or somebody inside who already wants you there. With no answer to that, a serious response is several days of unpaid work against firms who employ people to write them. With an answer, the process is paperwork around a decision that has already half been made.
A client mentioned new work in the middle of a delivery thread. What now?
Treat it as the proposal request it is, that week, and separately from the thread it arrived in. It has a better chance of becoming work than anything else in your inbox, because the trust is already bought and paid for. It’s also the one most often lost, because answering the delivery question in front of you feels like answering the message. A single line back is enough to open it: name what they mentioned, say it sounds like a separate piece of work, and offer a short conversation about it. Everything in this guide then applies as normal, with two of the six blanks already filled in.
The short version
A proposal request is the one message that arrives while you’re being compared, and it rarely looks the part. The formal pack you can’t miss is the least likely to convert. The referral, the returning client and the sentence buried in a delivery thread are the ones that do. Read the message for its blanks rather than its contents. If you learn only one thing about an inquiry, learn why it’s happening now, because a trigger is what a budget looks like before anybody has approved it. Answer the same day, in four short parts, to win a conversation rather than the work. Decline the third quote, the free consultation and the bid you fail on a mandatory requirement, quickly and warmly, because a good no is worth a call next year. Put the clarification deadline on the calendar the day a pack arrives, because that’s the one that binds first. Write down the five dates the request creates, because your mailbox holds none of them. And send the document so it survives the forward to somebody who was never on the call. Every stage after this one gets a guide to itself elsewhere in this collection, and the same argument written around a whole practice rather than a single inquiry is the piece this collection opens with.