PitchLeaf › Guides › Proposal pricing

Proposal pricing: fixed fee vs hourly vs itemized (what to put in the quote)

The pricing section is the only part of a proposal every client reads twice. How you structure it changes what they compare you against, how much they push back, and whether a "no" to one line becomes a "no" to the whole job. Here are the three models, when each one wins, and what the quote section needs to contain.

The three models in one table

None of these is the "professional" choice. The professional choice is the one that matches how well the scope is defined and how the client wants to buy. Many freelance proposals end up using two of them on the same page.

Fixed fee: one number, clear scope

A fixed fee says: this defined work, for this price. The client can budget to the dollar, and they never have to wonder whether you are padding hours. In exchange you take the risk. If the job takes twice as long as you thought, that is your problem.

Fixed fees work when three things are true: you have done something similar before and know roughly how long it takes; the deliverables can be listed on one page without the word "etc."; and you have a written way to handle changes. That last one is where fixed pricing fails. The fee is only fixed for the scope you wrote down, so the scope has to be written down.

Notice the last sentence. Pricing the most likely additions in advance turns a scope argument into a menu. Without it, every "small extra" is a negotiation.

A fixed quote is generally treated as a firm offer for the stated scope, which is why clients like it and why the scope must be tight (see proposal vs quote vs estimate for how binding each document is).

Hourly: when the scope is not yours to define

Hourly pricing puts the risk of overruns on the client. That is fair when the client controls the scope: an ongoing retainer, a maintenance contract, a project where they will decide what to work on each week, or a rescue job where nobody knows what is inside the codebase until you open it.

The problem with a bare hourly rate in a proposal is that it gives the client no number to approve. "$95 per hour" is not a price; it is a formula. Turn it into something they can say yes to:

• An estimated range of hours. "Estimated 30 to 40 hours." The range is honest and shows you have thought about the job.
• A cap, or a check-in point. "Not to exceed 45 hours without written approval," or "I will report hours weekly and pause at 30 for a review." Caps are what let a client approve an hourly proposal internally.
• What an hour includes. Meetings? Email? Travel? Say so.
• Billing rhythm. Weekly, fortnightly, or monthly invoices, with a timesheet attached.

In a proposal builder that uses line items, hourly work is just a line where quantity is hours and unit price is your rate: "Maintenance and small changes, 8 hours at $95, $760." That gives the client a concrete figure to approve while keeping the hourly basis explicit.

Itemized: show the parts, let them trim

Itemized pricing lists each deliverable or phase with its own price and sums them. It is the most transparent of the three and the one that most often saves a proposal that would otherwise be rejected on total. A client who cannot afford $6,000 can often afford $4,800 if they can see which $1,200 line to drop.

That same transparency is the weakness. Some clients will go line by line asking why the logo costs $600 when the business card costs $150. Two defences:

1. Group, do not atomise. Six to ten lines is plenty. "Design system: colours, type, components" is one line, not three. A line the client can remove without breaking the project is a good line; a line that only makes sense with the other lines should be merged into them.
2. Price the outcome, not the hours. Each line should describe what the client gets, not what you do. "Homepage design, two concepts, one revision round" rather than "Design time, 8 hours."

Discovery call and written brief                       1    $350      $350
Homepage design (two concepts, one revision round)     1  $1,400    $1,400
Inner page template (about, services, contact)         3    $450    $1,350
Blog index and post template                           1    $600      $600
Build, launch and 5 days of post-launch support        1  $1,500    $1,500
                                                          Subtotal  $5,200
                                                          Tax (0%)      $0
                                                          Total     $5,200

If the client asks to drop the blog, you remove one line and the proposal still makes sense. That is the test.

Mixing models on one proposal

Real projects often have a defined build phase and an undefined ongoing phase. Price them differently and say so: a fixed fee or itemized table for the build, then a separate hourly or monthly line for what comes after. Keep them visually separate so the client does not add an ongoing monthly fee to the one-off total and get a fright.

What to put in the quote section, whichever model you use

The pricing table is the headline, but it is not the whole quote. The following belong in the same section, in this order:

1. The prices, in one of the three structures above, in a stated currency.
2. Tax. Whether the prices include or exclude sales tax, VAT or GST, at what rate, shown as its own line. Discovering tax at invoice time feels like a price rise even when it is not.
3. Discount, if any, as its own visible line with a reason ("returning client discount, 10%"). A discount buried in the prices is invisible; a discount on its own line is a favour the client can see.
4. Payment schedule. Deposit percentage, milestone payments, and when the balance is due. Payment terms belong in the proposal, not just the invoice, because this is where the client agrees to them. The same goes for any late-fee wording.
5. What is not included. Stock photos, hosting, copywriting, third-party fees, travel. Two or three bullets prevent most later disputes.
6. Valid-until date. Two to four weeks is typical. Your rates and your calendar both change; the date is how you say the offer is current rather than permanent.
7. How to accept. "Reply 'approved' to this email" or "sign the last page." A clear acceptance step is the difference between a proposal and a brochure.

Items 4 and 6 are the ones most freelancers leave out, and they are the two that most often cost money later. Our freelance proposal guide covers where this section sits relative to Overview, Scope and Timeline.

Choosing: three questions

1. Can I list every deliverable without "etc."? No: hourly with a cap, or an estimate with a range and a path to a fixed quote. Yes: continue.
2. Might the client need to trim to fit a budget? Yes: itemized. No: continue.
3. Have I done this kind of job before and know roughly what it takes? Yes: fixed fee, with the likely extras pre-priced. No: itemized anyway, so the risk is spread over lines rather than sitting in one number.

Frequently asked questions

Should a freelance proposal show hourly rates or a fixed price?

Fixed price when the scope is clear and you have done similar work before; hourly when the scope is open-ended or the client wants to steer week to week. If you quote hourly, include an estimated range of hours and a cap so the client has a number to approve.

What is itemized pricing in a proposal?

A pricing table with one line per deliverable or phase, each priced, adding up to a total. It shows what the client is paying for and lets them remove a line instead of rejecting the whole proposal.

Should I include tax in the proposal price?

State clearly whether prices include or exclude tax, at what rate, and show it as a separate line. The total may be the same either way; the surprise is what damages trust.

How long should a quoted price stay valid?

Two to four weeks is typical for freelance work. Put a valid-until date on the quote so old pricing cannot be accepted months later.