Use Project Margins to Make Better Pricing Decisions
Updated: Oct 4

A project’s quoted fee is a pricing assumption. The completed project’s records show how that assumption compared with the work delivered and costs incurred. Reviewing the difference can help a creative business ask better questions before accepting similar work again.
Compare like with like
Start with the approved scope and fee. Then compare revenue under the business’s accounting method with the costs that can be assigned to the job: contractor bills, project purchases, employee or owner labor when records support it, and any consistently allocated overhead. Keep direct project costs visible separately from allocated overhead so it is clear what the calculation includes.
Use a clear margin calculation
A basic project margin percentage is (project revenue minus project costs) divided by project revenue. For example, a hypothetical $10,000 project with $6,500 in included costs leaves $3,500 before any costs excluded from the calculation; the margin on those included costs is 35%. If overhead or internal labor is omitted, label the result as a partial margin rather than final project profit.
Ask what drove the difference
Scope: Were additional revisions, meetings, or deliverables completed without an approved change?
Effort: Did actual hours or contractor costs exceed the estimate? Were time records complete enough to explain why?
Timing and billing: Did milestone invoices match the work and payment terms, or were there delays and unbilled items?
Cost assumptions: Were software, production, travel, or reimbursable items included consistently?
Turn the review into a pricing question
Once the records are complete enough to compare, decide what to test on the next similar engagement: a different fee, a narrower scope, a defined revision limit, a revised labor estimate, a contractor allowance, or a change-order trigger. One project is a data point, not proof that every future job will perform the same way. Compare several projects with similar scope before treating a pattern as a pricing rule.
Know what the number does not tell you
A margin report is only as useful as the underlying project assignments, labor records, and costing assumptions. It does not account for every strategic factor—such as client value, capacity, market conditions, or future work—and should not be treated as a universal price recommendation. Confirm that revenue and cost treatment are consistent with the agreement and reporting method.
Get a clearer view of project economics
If you cannot compare estimates with actual project costs in your current books, email SVS about project profitability to ask about project reporting and the records available. Learn about my project cost accounting service or request a quote by email.
This article is general educational information, not tax, legal, or financial advice. The example is hypothetical; pricing depends on the business and its market.




Comments