Guide

How to price a service proposal

Pricing a proposal is the part most service businesses get wrong. They quote what feels reasonable, then discover six weeks in that the work was twice the size they thought. The fix is not a magic number — it is a structure that ties price to scope, time, and risk before the proposal goes out.

Proposals & Quotes 8 min readUpdated Oct 22, 2025
SMBHelper editorial teamLast updated Oct 22, 2025Reviewed for clarityEditorial standards

Start with the scope, not the number

Every well-priced proposal starts with a clear scope. List the deliverables in plain language, then estimate the time each deliverable takes — including review cycles, project management, and the small admin work that always shows up.

If you cannot describe the work as a list of deliverables, you are not ready to price it. Go back and ask the buyer one more round of questions before you commit to a number.

Pick a pricing model that matches the work

There are three pricing models that cover almost all service work. Each has a sweet spot.

  • Project pricing: a fixed total for a defined scope. Best when the deliverable is well understood and the buyer wants budget certainty.
  • Hourly pricing: time spent at an agreed rate. Best for open-ended discovery, support work, or when the scope is genuinely impossible to define up front.
  • Retainer: a recurring monthly amount for an agreed bucket of work. Best for ongoing services where capacity matters more than discrete deliverables.

Anchor the value before the price

A price feels expensive when it appears before the buyer understands the value. The same price feels reasonable when it appears after a clear summary of the outcome.

Lead the proposal with the outcome the buyer cares about — revenue lifted, hours saved, risk removed — then introduce the price. The price has not changed, but the framing has.

Build in a margin for risk

Most service projects run 20–40 percent longer than the original estimate. Build that margin into the price, not into the timeline. A 10,000 project that takes 30 percent longer than expected is still profitable at 10,000 if you priced for 30 percent slippage.

If you priced exactly to your time estimate, you are losing money on every project that runs over — which is most of them.

Show optional add-ons separately

Optional add-ons (extra revisions, an extra deliverable, a rush option) belong in their own section, not buried in the main scope. The buyer can say yes to them or skip them without renegotiating the whole price.

Optional items also signal flexibility — you have a way to scale the engagement up or down, which buyers find reassuring.

Stop discounting on instinct

Discounting because the buyer hesitated is the most expensive habit in service pricing. Every percent off comes straight out of margin. If a discount is genuinely warranted (volume, long-term commitment, marquee logo), tie it to something the buyer gives in return — not to the silence in their reply.

Frequently asked questions

Should I show my hourly rate in a project proposal?
Generally no. Showing the rate invites the buyer to argue about the hours. Show the project price and the deliverables; keep the internal time estimate to yourself.
What if the buyer asks for a discount?
Trade, do not give. Reduce the scope, lengthen the timeline, or remove a deliverable. A free discount tells the buyer your original price was inflated.
How do I price something I have never done before?
Estimate the time as honestly as you can, then add a 30–50 percent risk premium. The first project of any new type is always the most expensive to deliver.

Related tools

Related reading

Read next