Proposals, Pricing & Contracts
The brief is agreed and everybody is enthusiastic. Now somebody has to say a number out loud, and that's the part designers dread most.
Every unclear proposal costs you money. Hear how to price and write one while you travel.
Listen to the full Proposals, Pricing & Contracts course on DesignPath
Pricing goes wrong in a predictable direction. You quote low out of fear, win the work, and spend three months resenting a project you chose. Or the scope drifts by a screen a week, nobody records any of it, and the fee that was fair in January is an insult by March.
This module is the money half of a freelance engagement. Turning agreed work into a proposal, a price, a scope with edges, and a contract that means somebody gets paid.
Write a Winning Proposal
After a good first conversation, the client asks you to "send something over". What you send is a proposal - and most freelancers treat it as a price tag with a few lines of fluff on top. That's a missed chance. A proposal is a sales document. Its job is to leave the client confident that you understood their problem, that you have a plan, and that you're the right person to trust with it. Done well, it doesn't just quote the work - it closes it.
Open on Their Problem
Open the proposal by showing you understood what they actually need. Restate their problem and goal in your own words: "You're launching a new product and need a checkout flow that converts and feels trustworthy." This does two things - it proves you listened, and it frames everything that follows as the solution to their problem, not a generic service. (The goal-first principle from presenting applies here too: context before craft.)
A Structure That Sells
A clear proposal usually runs one to three pages with these parts:
- Introduction: a short, warm recap of the project and their goal.
- Scope: what you'll deliver, in plain terms - and, just as important, what's not included.
- Approach: how you'll work - your process and the rough phases. This is where you show expertise.
- Timeline: realistic phases and milestones.
- Pricing: the investment, ideally as options (next article).
- Next steps: exactly how they say yes and what happens then.
The structure itself signals professionalism. A clear, well-organized proposal tells the client you'll be clear and organized to work with.
Show What the Deliverables Are Worth
A list of deliverables invites the client to price-shop each item. Framing the value keeps them focused on the outcome. "A redesigned checkout flow built to lift conversion" lands better than "12 screens in Figma". Tie the work back to what they care about - revenue, trust, time saved - the same translation skill from earlier in this theme, now selling your services.
Where the Proposal Stops
One important distinction: a proposal sells the work; a contract protects it. They often travel together, but they're different documents with different jobs. The proposal persuades and outlines; the contract (a few articles on) makes it legally binding - milestones, payment terms, what happens if things change. Don't rely on a proposal alone to protect you. Send a confident proposal to win the yes, then a contract to make it real.
Pro tip: Keep a proposal template with your standard sections, approach, and terms, then tailor the problem, scope, and price per client. AI can draft the first tailored pass from your notes - you make it specific and true before it goes out.
