The salesperson attaches the PDF, writes "here is the proposal, any questions I’m available," and disappears. The client opens it, doesn’t understand half, has no one to ask at that moment, and postpones. Two weeks later, no one knows if it turned into a deal. This article shows how to send it in a way that generates a response.
In this article
- Sending is not presenting
- PDF, message or link: when to use each
- The seven parts of a proposal that closes
- The sending script, message by message
- Validity and condition: what makes you decide today
- The 48 hours that follow
- When the proposal should not be sent by message
- Mistakes that kill the proposal on delivery
- Frequently asked questions
Sending is not presenting
On WhatsApp, the proposal arrives in the middle of the person’s day — between a meeting and lunch, with the phone in hand and thirty seconds of attention. It will be opened under these conditions, not calmly in front of a computer. Whoever writes thinking about the second scene misses the first.
This changes the purpose of sending. It’s not about delivering the document: it’s about making the person understand, within the first twenty seconds, three things — what they get, how much it costs, and what the next step is. Everything else is detail that can wait for the conversation.
See the effect in numbers. A company sends 180 proposals per month, average ticket of R$ 2,400. When the proposal goes "raw" — file plus a generic phrase — suppose 46% of clients respond with something within 48 hours: 83 conversations resumed. With a structured presentation and a closed question at the end, this rate rises to 71%: 128 conversations.
If 20% of resumed conversations turn into sales, that’s 16.6 sales versus 25.6 — R$ 21,600 more per month, with the same 180 proposals, the same price, and the same team. What changed was the sending format and an agreed next step.
Note that this happens before any follow-up: a well-sent proposal needs fewer follow-ups to be answered, freeing the salesperson to work on more negotiations simultaneously.
PDF, message or link: when to use each
All three formats work — for different things. Choosing wrong is the first mistake in the process.
Message in the WhatsApp body. Ideal for simple values, one or two options, smaller ticket, and a single decision-maker. Advantage: no need to open anything, it’s read immediately, can be answered with one word. Limit: long text on WhatsApp becomes a wall and no one reads it. If it exceeds ten lines, change the format.
PDF. Ideal when there is a detailed scope, more than one decision-maker, or need to circulate internally. Advantage: looks official and survives forwarding. Care: maximum two pages, value and scope on the first fold, file name with client name and date — Proposal-Builder-Alfa-13-08.pdf instead of final_budget_v3.pdf. File name is the first thing the client sees, and "v3" communicates exactly what you don’t want.
Link (page or online document). Ideal for high ticket, proposals with configurable options, or when you want to know if the client opened it. Advantage: updates without resending and allows tracking opening. Limit: link requires prior trust — on first contact, many people don’t open it.
Practical rule: message for simple, PDF for formal, link for expensive. And, in any of the three, the text summary goes along in the conversation body. The file never travels alone.
Keep reading for free
Fill out once and unlock this and all other blog articles. We don’t charge anything — we just want to know who we’re writing for.
Takes 20 seconds. Prefer to talk directly on WhatsApp?
The seven parts of a proposal that closes
Regardless of format, seven blocks need to exist — in this order, from most decisive to most detailed.
1. The problem, in the client’s words. A sentence that reflects what they told you: "Today you lose about 30% of budgets due to delayed responses." This proves you listened and frames the value before the price.
2. What they get. Deliverables in three to five lines, without jargon. It’s not a list of everything you do: it’s what they receive.
3. The price, clearly. Total value, payment terms, and what is included. Price hidden in the footer of the second page increases distrust, not closing.
4. What is not included. The block that most avoids conflict afterward. Two or three lines of exclusions are worth more than ten of guarantees.
5. Execution time and first steps. When it starts, how long it lasts, what happens in the first week. Reduces the sense of risk.
6. Proposal validity. A real date. Without it, there is no reason to decide today.
7. The next step, written by you. "If it makes sense, reply here and I’ll reserve the schedule for 22." The client shouldn’t have to invent what to do next.
Two pages cover all this comfortably. An eight-page proposal is not more complete: it’s less read.
The sending script, message by message
Order matters as much as content. Send like this:
Message 1 — the context (before the file).
"[Name], I prepared the proposal considering what you told me: [problem in one sentence]. There are two options, and the difference between them is [variable]. I’m sending it below."
Message 2 — the file or link. Alone, without attached text.
Message 3 — the three-line summary.
"In summary: option A at R$ X, with [delivery], starting on [date]. Option B at R$ Y, which includes [difference]. Both with payment terms [condition] and validity until [date]."
Message 4 — the next step, in a closed question.
"Does A or B make more sense? If you prefer, I can call you tomorrow at 10h and we can decide in five minutes."
Four short messages, sent in sequence, take less than a minute to write with saved templates — and completely change the chance of response, because the client can decide without opening anything if they’re in a hurry.
Two useful variations. For high ticket, replace message 3 with an audio of 40 to 60 seconds explaining the difference between options: voice creates context that text doesn’t, as long as it’s short. And, when there is more than one decision-maker, add: "If it helps, I can prepare a half-page summary for you to take to [partner/director]" — material made to circulate without you is what supports the sale inside the client’s company.
Validity and condition: what makes you decide today
Proposal without a deadline invites postponement. But a made-up deadline, like "only until tomorrow" repeated every month, destroys the credibility of everything you say afterward. The solution is to use real conditions — and there are more than it seems:
Price validity. Input cost, exchange rate, and price list really change. State the date and reason.
Schedule reservation. "I can start on 22 if we close by Thursday; after that, the next start is 5 September." It’s honest and moves those with deadlines.
Payment condition. Extended installment or cash discount with a defined date. Here the bargaining chip is clear.
Batch or real availability. Only use if true and verifiable.
And keep the validity visible on both ends: in the document and in the summary message. A client who has to look for the date won’t find it.
The 48 hours that follow
The most decisive negotiation period starts the moment you hit send. Three moves organize this window:
Record the proposal as a stage, not a state of mind. "Proposal sent" needs to exist in the funnel, with date and value. Without this, no one knows how many proposals are waiting for a response now — and that number predicts next month’s revenue.
Arrange the next contact while sending. "I’ll call you Thursday at 10h" turns follow-up into a commitment and removes any feeling of pressure.
Watch for signals. A client who opens and asks about payment terms is advancing; a client who asks to "resend by email" is usually circulating internally — it’s worth asking who else will see it and offering material for that person.
If the response doesn’t come, the follow-up cadence kicks in: increasing intervals, new content at each touch, and a graceful closure at the end. The step-by-step is in follow-up on WhatsApp.
One operational note: if you use the official API, remember that after 24 hours without a message from the client, follow-up requires an approved template. Having a ready follow-up template before sending proposals avoids discovering this at the worst moment.
When the proposal should not be sent by message
There are three situations where sending the document first reduces the chance of closing, and the way is to reverse the order: schedule fifteen minutes and present before sending.
When the value is above what the client expected. If in conversation they mentioned a range and the proposal is well above, sending the number alone guarantees a definitive "thanks, I’ll evaluate." Presenting allows explaining the difference before it becomes an objection.
When there are more than two options. Three or four scenarios per message confuse, and a confused client doesn’t decide. Present, choose the path with them, and send the proposal already reduced to two options.
When the decision-maker did not participate in any conversation. A document that arrives cold to someone who never spoke with you is read as a price list, and compared as a price list.
In all three cases the message is the same: "Before sending, I prefer to show you in fifteen minutes how I arrived at these numbers — so you decide with the full context. Does tomorrow at 10h work?"
Mistakes that kill the proposal on delivery
Sending the file without context. "Attached" transfers the work of understanding to the client.
Proposal too long. Eight pages become zero pages read.
Careless file name. final_budget_v3_new.pdf tells a story you don’t want to tell.
Price at the end, hidden. Every client looks for the value first. Make it easy.
No validity. Without a date, there is no reason to respond today.
No next step. "Any questions I’m available" is the most polite and most useless closing in commerce.
Sending without qualifying. Proposal to someone without deadline or budget clogs the funnel and consumes follow-ups — hence the importance of qualifying first.
The proposal is the most expensive piece of your sales process: it carries the salesperson’s time, the lead cost, and the real chance of revenue. Sending it with context, summary, and next step costs one more minute — and is the difference between a document that generates conversation and a file that dies in WhatsApp scrolling.
Frequently asked questions
Is it better to send the proposal as a PDF or in the message body?
It depends on complexity and how many people decide. Simple values, one or two options, and a single decision-maker work better written in the conversation body because they are read immediately. Detailed scope or proposals that will circulate internally require a PDF of no more than two pages, with value and scope on the first fold. High ticket and configurable options favor a link, which allows updating without resending. In any case, the text summary goes along in the conversation.
What to write when sending a proposal via WhatsApp?
Four short messages in sequence: the context before the file ("I prepared considering what you told me..."), the file alone, a three-line summary with value, delivery, and validity, and a closed next step question ("Does A or B make more sense? If you prefer, I can call you tomorrow at 10h"). This way the client can decide even without opening the attachment.
Should I put a validity deadline on the proposal?
Yes, with a real date and a true reason — price validity due to input cost, schedule reservation for execution, or payment condition with a defined date. Made-up urgency, like "only until tomorrow" repeated every month, destroys the credibility of the rest of the negotiation. Keep the validity visible both in the document and in the summary message.
Centralize service without changing your number
Connection via QR or official API, single queue with defined responsible, client history that stays in the company, and sales funnel on the same WhatsApp panel.