An email to send a proposal to a client should identify the project, point to the document, explain how to approve it, and set the next contact. Keep the scope, price, and terms inside the proposal. Repeating them in the email creates another version that can drift out of date.
Proposal email subject lines
Use a subject line the client can find again:
- [Your company] proposal for [project]
- [Project] proposal Q-2026-041
- As discussed: proposal for [project]
- [Project] proposal ready for review
“Proposal attached” gives the recipient little context. Avoid urgency words unless the proposal has a real deadline or a start date that genuinely depends on availability.
What the email needs to say
Cover four points:
- Context: name the conversation, brief, or request.
- Access: provide the proposal link or name the attachment.
- Decision: give the client one way to approve.
- Next contact: suggest or confirm a review date.
The email is a handoff, so a few well-chosen lines are usually enough. Any term that affects the purchase belongs in the proposal too. Do not use the email to add a deposit, shorten the timeline, or change the scope without updating the document.
Share one clear version
Want to send professional proposals in less time?
Try Proposa for free and reuse templates designed to speed up prep and increase approvals.
Should you send a link or attach a PDF?
A secure client link gives the client one place to review the current proposal, ask a question, and record a decision. It also avoids a thread full of files called proposal-final-v3.pdf.
Some procurement teams still need a PDF for an approval system or internal archive. Ask what their process requires. If you send both formats, identify the version that controls:
The review link below and attached PDF both contain proposal Q-2026-041, revision 2. Please use the link to record the decision; the PDF is included for your procurement file.
Test the link in a private browser window and open the attachment before sending. The client should not need your account or special instructions to read the proposal.
Sample 1: after a discovery call
Subject: North Street website proposal
Hi Sam,
As agreed on today's call, here is the proposal for the North Street website: [proposal link]. It includes the agreed scope, proposed dates, and payment terms.
You can approve it from the link. Would Thursday, 20 August work for a short review of any questions?
Best, Alex
The message confirms delivery and the next contact. It does not claim that a proposed start date is already reserved.
Sample 2: an existing client
Subject: Member portal proposal
Hi Priya,
I have prepared the proposal for the member portal we discussed yesterday: [proposal link]. The core build and the two optional integrations are separated so you can review the costs independently.
Approve from the link if the scope is right, or reply with any point you want to discuss. I am available Tuesday afternoon if a call is easier.
Thanks, Alex
An established relationship may suit a warmer, shorter message. Keep the instruction as precise as it would be in a formal email.
Sample 3: procurement or several reviewers
Subject: Reporting project proposal Q-2026-041
Hi Morgan,
Here is proposal Q-2026-041 for the reporting project: [proposal link]. It covers the two requested phases and includes the supplier details your finance team requested.
You may share the same link with the review group; I have also attached a matching PDF for your procurement record. Who should receive technical questions, and who will record the final decision?
Regards, Alex Morgan
This wording recognises that the recipient may coordinate the process without having authority to approve the purchase.
What to leave out
- A second copy of the proposal. Do not paste every deliverable and price into the email.
- An unrequested discount. Send the agreed offer and wait for a real budget conversation.
- Unsupported outcome claims. Keep the message tied to the work you can deliver.
- Several competing actions. Choose one approval route.
- False urgency. Use only dates and availability stated in the proposal.
- Ambiguous files. A name such as
proposal-Q-2026-041-north-street.pdfis easier to trace.
Before you send
- Do the client, project, and proposal number match?
- Does the link work without your login?
- Does the PDF match the online revision?
- Is there one approval route?
- Is the next contact clear?
- Are the recipients and copied stakeholders correct?
- Are all deadlines and availability statements accurate?
With Proposa proposal software for freelancers, you can publish a proposal and copy its secure client link into your own email. Proposa does not send the client email; it keeps the proposal, opens, messages, and decision attached to the same link. The proposal tracking software page explains how those client signals appear after you send it.
If the document is not ready yet, start with the guide to writing a freelance proposal. Once the proposal is out, follow the date you agreed with the client. The proposal follow-up guide covers the later message without mixing it into the initial delivery email.
From proposal to decision
Want to send professional proposals in less time?
Try Proposa for free and reuse templates designed to speed up prep and increase approvals.