Here's how to present a proposal to a client: don't just send it. Book a 20 to 30 minute call, share your screen, and walk them from their problem to your price in order. Pause at the sections that matter, stay quiet after the number, and don't hang up without a next step and a date attached to it.
You can write a great proposal, with a tight scope, a fair price and a clear plan, and still lose the project because of how it reached the client. Most freelancers and small firms treat the proposal as something to email. They attach it, write "Let me know if you have any questions," and wait.
Emailing a link leaves the client to interpret every section on their own. Presenting it lets you make the argument yourself, all the way to the decision.
What does the flow look like from first call to signed proposal?
It starts with the discovery call. That's where you hear the real problem, the goal behind it, the budget range and who else gets a say. Skip that listening and the proposal comes out generic. If you're not sure the lead has budget and urgency yet, sort that out before you write a word.
With that in hand, you write the proposal. Not a template with the name swapped, but an answer to this client: their problem, an approach that fits their situation, and an investment tied to the outcome they want.
When it's ready, you don't send it cold. You send a two-line email saying it's ready and proposing a time to go through it together, on Zoom, Google Meet or in person. What matters is that you're there to run it.
That flow, discovery call then tailored proposal then live walkthrough, is what separates people who close consistently from people waiting on replies that never come.
Why does presenting it live matter?
When the client reads alone, they decide what each section means. They may jump to the price before they've seen the value. They may not connect your diagnosis to your approach. They may hit a question halfway through and close the tab.
When you present, you set the pace. You take them through the story in the right order, slow down where it counts, answer questions as they come up and arrive at the investment with the groundwork laid.
It also shows commitment. The client sees that you prepared, that you understand the project and that you care how it turns out. That takes some of the pressure off the price before you even get there.
How do you run the call?
Start by confirming the problem. Before you share your screen, ask one quick question to check that nothing has changed since the discovery call. Priorities shift, budgets move, a new stakeholder appears. The question shows you were listening and puts the client in listening mode too.
Walk through it as a story, not a reading. Don't read the proposal aloud. Take them through it the way you'd tell it: the problem they have, what you found, the logic of your approach, what you'll deliver, and the investment that makes it happen. Each section sets up the next.
Share the link on screen. Open the proposal and scroll through it together. The document stops being something they file and becomes something you're showing them. They see what you see and follow your reasoning in real time.
Pause at the sections that matter. Don't present everything and ask "Thoughts?" at the end. Stop after the diagnosis and check that it rings true. Stop after the approach and ask whether it matches what they had in mind. Those pauses turn a pitch into a conversation.
Present the price and stop talking. When you reach the number, say it, then give them a few seconds of silence. The urge to fill that gap with justifications is strong, and it almost always hurts. If the earlier sections did their job, the number already has its context.
If the client pushes back on price, don't reach for a discount first. Ask a question: what specifically about the number concerns you? The answer tells you whether it's a real budget limit or a value gap, and each one needs a different response.
In Nepfy, the shortest way to present is Present: it opens the same proposal as 16:9 slides, with no second deck to build. One section per screen, in the order you drag them into, with a control pill that fades on its own after three seconds. Presenter notes open in a separate window marked "Only you see this", with Up next showing what comes after. You present and send one proposal, from draft to accepted.
How do you close at the end of the call?
The most common mistake after a good presentation is ending without a next step. The client says they'll think it over, you say thanks, the call ends. Interest cools, the week gets busy and the project stalls.
Before you hang up, agree on a next step with a date.
"Makes sense. Could you get back to me by Thursday? That way I can hold the start date we talked about."
That creates a commitment with a date on it and reminds the client that the start depends on their decision. It adds real urgency without manufactured pressure.
If they want to accept on the call, even better. With a proposal sent as a link, they can accept right there, with their name and signature, without leaving the page.
What do you do after the presentation?
The call is over, but the process isn't. The client will reread the proposal, maybe forward it to a partner or their boss, maybe compare it with another quote.
If you sent a proposal you can track, you know when it was opened again after the call. Opens spread over several days are a strong sign of active interest and a good moment to reach out with something useful.
Without tracking, you follow up blind. With it, you follow up on something that actually happened.
What are the most common mistakes when presenting a proposal?
Sending the link and waiting. On mid-size and large projects, sending without presenting wastes the work you put in. The client reads every section their own way, with nobody there to make the case.
Presenting before you confirm the problem. If you don't check that the situation is still the same, you risk pitching the wrong solution. One question at the start prevents it.
Defending the price before anyone questions it. Piling on justifications before the client reacts reads as nerves. State the number plainly and wait.
Ending without a next step. Every presentation should end with a concrete action: a date, a decision, a commitment to reply. Without one, the proposal sits there and interest fades.
Frequently asked questions
Should I send the proposal before the presentation?
Send it during or right after. If the client reads it first, they tend to go straight to the price without the context you'd give them on the call.
How long should the presentation be?
Plan for 20 to 30 minutes. That's enough to confirm the problem, walk through the proposal and agree on a next step without turning it into a second discovery call.
What if the client can't make a live call?
Record a five-minute screen walkthrough and send it with the link. It's not as good as a conversation, but it keeps you in control of the order.
In Nepfy, the same proposal turns into slides for the meeting with no second deck to build, with presenter notes only you see, and then stays with the client as a live page to reread and accept. For a call-by-call script, see these proposal presentation tips.
Start free: 14 days of Pro, no credit card.
