The job of a proposal pricing table
A pricing table should answer three questions: what is being purchased, how much does each component cost, and what is the total investment? It should not attempt to expose every internal calculation. The right amount of detail is the amount that makes the price credible and reviewable.
Use meaningful line items
A line item should represent a useful unit of work or deliverable. "Miscellaneous - $400" creates questions. "Content migration for 30 existing pages - $400" creates understanding. If a line item contains several unrelated services, consider splitting it. If splitting it would create unnecessary noise, use a concise description that explains the combined deliverable.
Do not over-itemize
More detail is not always more transparent. A table with 47 tiny internal tasks can make a simple project look complicated and invite the client to negotiate every row. Group internal activities into client-relevant phases or deliverables. The table should be detailed enough to explain the price but not so detailed that it becomes a task-management export.
Make quantities meaningful
Quantity is useful when it reflects something the client understands: pages, hours, workshops, products, locations, campaigns, or units. Do not invent quantities simply because your template has a quantity column. For fixed-fee deliverables, a quantity of one may be less useful than a clear description and fixed amount.
Show discounts deliberately
If you offer a discount, make the original subtotal and discount visible where appropriate. A transparent discount communicates that there was a commercial decision rather than an unexplained price change. Avoid fake list prices or artificial urgency. The table should remain credible if the client forwards it internally.
Handle taxes and expenses clearly
If taxes apply, label them according to your business and local requirements. If expenses are estimated separately, say so. Third-party costs should not disappear inside a vague "project expenses" line. Clear treatment of costs reduces surprises later and makes your total easier to reconcile with the eventual invoice.
Use options carefully
Good-better-best pricing can help clients choose without forcing a binary yes/no decision. The options should differ in meaningful scope, support, speed, or deliverables. If all three options are nearly identical except for price, the client may assume the pricing is arbitrary. Explain the practical difference between each option.
Put the total where the eye expects it
The final investment should be visually easy to find. Use a clear subtotal, discount if applicable, taxes if applicable, and total. Avoid hiding the total in prose. A client should be able to screenshot the pricing section and send it to a colleague without needing additional explanation.
Keep the table aligned with the scope
Every pricing row should have a corresponding scope explanation somewhere in the proposal. Likewise, major scope commitments should have a commercial home. This alignment is one reason structured estimating is valuable. When line items are generated consistently, it becomes easier to keep the narrative and numbers synchronized. Docs Estimator can support that structured Google Docs workflow.
Test the table with a five-second scan
Show the pricing table to someone unfamiliar with the project and ask what they think the client is buying and paying. If they cannot answer quickly, simplify the descriptions or hierarchy. Client clarity is the real design metric - not how impressive the table looks.