Most freelance proposals are not lost because the work is weak. They are lost because the proposal is slow, vague, or difficult to approve.
Here is a small system you can use in any text editor. It takes six inputs and produces a proposal that answers the questions a client actually has:
- Do you understand the outcome?
- What exactly will I receive?
- How long will it take?
- What will it cost?
- What happens next?
No account, CRM, or elaborate deck is required.
Try the interactive builder
Open PitchMint — the free, no-signup proposal builder
Your brief stays in your browser. The interactive version is carried in the link itself and opens in result-only mode.
The six-input brief
Before writing, collect only these fields:
- Client — the person or company receiving the proposal.
- Project — a result-oriented project name.
- Outcome — the business change the client wants.
- Scope — four to six concrete deliverables.
- Timeline — one clear duration or date range.
- Investment — one price, unless options are genuinely useful.
The useful constraint is that every sentence must help the client decide. If a paragraph only proves how clever you are, remove it.
Copy-paste proposal template
PROPOSAL FOR [CLIENT]
[PROJECT NAME]
This engagement is designed to [DESIRED CLIENT OUTCOME].
WHAT IS INCLUDED
• [Deliverable 1]
• [Deliverable 2]
• [Deliverable 3]
• [Deliverable 4]
WHY THIS APPROACH
[One relevant proof point, case-study result, or sentence explaining why this scope fits the outcome.]
TIMELINE
[Duration or date range]
INVESTMENT
[Currency and price]
NEXT STEP
Approve this proposal and we will confirm kickoff details, milestones, and the first working session.
Prepared by [YOUR NAME]
A filled example
PROPOSAL FOR NORTHSTAR STUDIO
Website conversion refresh
This engagement is designed to turn more qualified visitors into booked discovery calls with a clearer story and a faster path to action.
WHAT IS INCLUDED
• Conversion-focused homepage redesign
• Responsive design system
• Booking flow optimization
• Launch-ready handoff
WHY THIS APPROACH
This scope connects message clarity, responsive design, and the booking path to one conversion goal.
TIMELINE
3 weeks
INVESTMENT
$4,800
NEXT STEP
Approve this proposal and we will confirm kickoff details, milestones, and the first working session.
Prepared by Alex Morgan
Three edits that improve almost every proposal
1. Name the outcome before the deliverables
“Redesign five pages” describes labor. “Turn more qualified visitors into booked calls” describes value. The deliverables still matter, but the outcome gives them a reason to exist.
2. Replace fuzzy scope with countable nouns
Avoid phrases like “ongoing support” or “brand improvements” unless you define them. Prefer “two feedback rounds,” “five responsive page designs,” or “a 60-minute handoff call.” Clarity protects both sides.
3. End with one low-friction action
Do not make the client invent the next step. State it. “Approve this proposal and we will schedule kickoff” is better than a general “Let me know what you think.”
The final 60-second check
Before sending, verify that:
- the project title names a result, not just a task;
- the outcome uses the client’s language;
- every scope item is observable;
- the timeline and price are unambiguous;
- the next step asks for one action;
- the proposal is readable on a phone.
That is enough. A proposal should reduce uncertainty, not demonstrate document-making endurance.
If this template saves you time, pass it to another independent worker. If you want to support more free, privacy-first tools, an optional SOL tip can be sent to:
DCQuYw28yGLv8H1wacfi5fBpfE3AcXSNiom9pDenWDen
Suggested amount: 0.01 SOL. The template is fully free either way.
Top comments (1)
Two feedback rounds" and "five responsive page designs" do more than improve readability-they turn scope into something both sides can verify. The six-input constraint is strong too, especially pairing a result-oriented project name with one clear timeline and price so the client has fewer decisions to make. I'd treat the seven-minute proposal as the decision layer, then carry exclusions, dependencies, and acceptance criteria into the contract or statement of work; speed keeps the sale moving, but those details keep a quick yes from becoming a slow dispute.