What the Buyer Sees When Your Proposal Lands

How a Proposal Travels Inside a Buying Organisation

A proposal does not land on one desk. It lands on several, in order, and each reader has a different question. The person you met wants to know whether you understood the problem. The owner or senior manager wants to know what it costs and what changes. The purchase department wants to know whether the document can become a work order. Finance wants to know when the money goes out.

In a family-run company the chain is shorter, but it is still there. The son may have met you, the father may approve the spend, and the accountant who has worked with the family for twenty years may read the payment terms. In institutional and defence buying the chain is longer and every step is written down. Either way, your proposal must answer each reader without you in the room to explain.

When I led a retail operation of over Rs 1,000 crore and its online operation across India, I saw this every week. A good meeting created interest. The paper decided whether that interest became an order. A proposal that answered the purchase team's questions on the first reading moved in days. One that raised questions went back down the chain, and some never came back up.

The lesson is simple. Before you write, list every person who will read the proposal and the one question each will ask. Then check that the document answers each question in the place that reader will look. Most consultants write only for the first reader, because that is the person they met and liked, and the rest of the chain is left to guess.

Why Most Proposals Go to the Bottom of the Pile

The most common fault is that the proposal describes the consultant, not the work. It opens with two pages of background, a list of past roles and a view on change. The buyer has to reach page four to find what will be done and what it costs. A busy reader stops before that, sets it aside to read properly later, and later rarely comes.

The second fault is a scope that cannot be checked. "Support on process improvement" or "strategic guidance for growth" means nothing to a purchase officer. They cannot write it into a work order, and at the end they cannot confirm whether it was delivered. A scope that cannot be verified is a risk, and a buyer is paid to reduce risk, not to take it on trust.

The third fault is a price that moves. A consultant quotes one figure in the meeting, another in the proposal and a discount on the phone. To the buyer this does not look flexible. It looks as if the first figure was never real, and it invites the purchase department to push again. The proposals I saw hold their price were the ones that explained it once, clearly.

None of these faults is about competence. I saw excellent people lose work to average ones because the average ones wrote a proposal that a purchase department could process without a single phone call. The good news is that this is the easiest part of a practice to fix. It needs an afternoon and an honest reading, not a new skill.

The Five Lines a Purchase Department Reads

A purchase officer does not read a proposal from front to back. They look for five things, and if any one is missing the file stops. Put each where it can be found in a few seconds, ideally together on a single page headed "Commercial Terms", so that nobody has to hunt through your method section for a date or a figure.

• Who you are, legally: the exact name of your firm, PAN, GST number or a line saying you are not registered under GST, your Udyam registration number if you have one, and the registered address. All of it must match your invoice.
• What you will deliver: a numbered list of outputs a person can check, each with a date. Write "a costing model for 12 product lines, delivered as an Excel file with a one-hour handover", not "costing support".
• The total price: one figure, with tax shown separately or a clear statement that no GST applies. No ranges and no "approximately".
• When you will be paid: the advance, the milestones and the number of days allowed for each invoice.
• Start, validity and exit: when work begins, how long the offer holds, and how either side can end the engagement.

The One Page the Owner Reads

The owner, or the senior person who approves the spend, will read one page at most. Make it the first page. In plain words it should say what problem you are solving, what will be different when you finish, how long it takes and what it costs. If the owner reads nothing else, they should still be able to say yes with confidence.

Write that page in the owner's language, not yours. If the owner talks about dispatch delays and stock that never moves, use those words. Do not translate their problem into consulting terms. When I read a summary that used my own words back to me, I knew the consultant had listened. When it used words from a textbook, I wondered whose problem it was describing.

Keep everything else behind that page: the method, the team, your background, examples of past work. Those pages matter, but they are read by the person who wants detail, usually the one you met. They are evidence, not the argument. A proposal that puts evidence first and the argument last asks the busiest reader to do the most work.

Getting this order right is a skill, and it can be learned. Building a proposal a purchase department can sign is part of the Pricing pillar of the Buyer-Side Method, because a fee is only real once the paper behind it has been approved. A proposal that is easy to approve protects your price better than any argument made on the phone.

What Makes a Buyer Hesitate

Some signals made me slow down as a buyer, even when I liked the consultant and wanted the work done. They are small, they are common, and every one of them can be avoided with a careful reading before the proposal goes out.

• A name that does not match: the proposal comes from a person, the invoice will come from a firm, and the bank account is in a third name.
• No end date: an engagement with no finish line looks like a cost that will never stop.
• An advance with no milestone: asking for money up front is fair, but the buyer needs to see what the advance pays for.
• Promises of results you cannot control: "we will double your sales" tells a buyer you will either fail or argue later about why.
• A generic document: another company's name left in a heading tells the buyer this was not written for them.

The last point catches more consultants than it should. A buyer who finds another client's name in your proposal will assume you will treat their information with the same care. It takes ten minutes to read your document as a stranger would before you send it. Do it every time, and ideally ask someone who was not in the meeting to read it too.

Hesitation is expensive for you because it is silent. A buyer with doubts rarely calls to raise them. They move your file down and pick up the next one. You will hear "we are still evaluating" for weeks, and you will not know why. The only defence is a proposal that leaves no doubt to raise.

Rewrite Your Proposal This Week

Take your last proposal, the one you felt most confident about, and read it as each reader in the chain would. Time how long the owner would take to find the problem, the result and the price. Then check whether a purchase officer could find all five commercial lines on one page. You will probably find at least two gaps worth fixing.

Fix the order first: one page for the owner, then the commercial terms, then the evidence. Then fix the scope, turning every vague phrase into an output someone can check. Finally, write the price once and decide in advance what you will say if asked for a discount. Offering a smaller scope, calmly, is better than a quick concession you regret.

A proposal is the only part of your practice that speaks for you when you are not there. It deserves the same care you give the work itself. From the buyer's side, a clear proposal is a relief. It tells the reader, before a single day of work, that the engagement will be handled the same way.