How to price services from actual delivery cost

Service prices need a defensible delivery floor, not just an estimate carried forward from the last proposal. Combine actual hours, loaded labor cost, and comparable revenue to see which service lines need a different scope, staffing mix, or price, while keeping payroll details restricted and decisions at client and team level.

By SIGNLD Editorial · · 7 min read · Playbooks
Payroll, time and accounting records compared to examine pricing services based on cost.

What is covered?

What does actual delivery cost tell you?

A proposal can look profitable because its estimate leaves out the work that makes delivery possible. Discovery runs longer. Reviews multiply. A specialist joins late. The invoice stays the same while the cost of fulfilling the promise grows.

Pricing services based on cost starts by replacing that estimate with a reconciled history of comparable work. It asks what the service normally consumes, which costs belong to delivery, and whether the current fee leaves enough room for overhead and profit.

That is a pricing and staffing question, not a reason to rank employees. Differences in assignments, seniority, training, and client complexity make individual comparisons misleading. Keep the working view at service, client, and team level. The broader framework in what each employee's time actually earns explains why paid time, delivery time, and revenue need separate definitions.

Which records belong in the calculation?

Start with completed engagements that resemble the service you sell today. Bring together approved time entries, project or service codes, payroll cost records, and accounting records for the matching work. Include credits and adjustments, not just the original invoice.

Loaded labor cost needs an explicit definition. It may include employer payroll taxes and employer benefit contributions alongside wages or salary. Decide whether leave belongs in the paid-hours denominator or an allocation, and do not count it twice. Document any delivery overhead included separately.

Use paid hours to establish an hourly labor cost, then apply that cost to attributable delivery hours. Salaried teams still need a consistent paid-hours convention. Contractor delivery belongs in the cost base too, using approved supplier bills rather than pretending it appears in employee payroll.

The connector directory lists QuickBooks, Harvest, Xero, HubSpot, Salesforce, and Stripe. Gusto and ADP are not listed; use approved payroll exports or files and confirm their handling route rather than assuming a direct connector. Confirm the fields available from each selected source before choosing the calculation.

Match service codes and customers carefully. A renamed package or an invoice that covers several services can otherwise put cost and revenue in different buckets. Preserve an unmatched category until someone resolves it instead of quietly excluding inconvenient records.

How do you turn cost into a pricing floor?

Use a simple sequence that someone outside finance can inspect:

  1. Define the service and delivery period.
  2. Multiply attributable hours by the relevant loaded hourly costs.
  3. Add direct nonlabor delivery costs.
  4. Divide by completed service units to establish cost per unit.
  5. Test a fee against the margin needed to cover the rest of the business.

Illustrative example: a service uses 40 delivery hours at a loaded labor cost of $60 per hour, plus $300 in direct external costs. Its delivery cost is $2,700. At a $4,500 fee, the delivery margin is 40%, before any overhead not included in that cost definition.

Those figures are illustrative, not recommended rates or benchmark margins. A target margin calculation divides delivery cost by one minus the target margin. It is different from adding a markup to cost, and confusing the two can leave a proposal short of its intended return.

Check the result against scope and customer value. A sustainable floor does not establish market willingness to pay. If the floor exceeds the accepted fee, the answer may be a narrower offer, a different delivery model, or declining work that cannot support its demands.

Also inspect variation. A typical engagement can hide a costly tail of revisions or handovers. Show ordinary delivery alongside clearly identified exceptions so that a single unusually difficult client does not define every future quote.

What should change before the price?

Separate pricing problems from delivery problems. A low fee is different from unclear acceptance criteria, missing client inputs, or repeated internal rework. Raising the rate without addressing those issues can preserve the same weak economics at a higher headline price.

Review the service promise with delivery leads. Specify included revisions, response expectations, dependencies, and the point at which new work becomes a change request. Put those boundaries into future proposals and discuss existing agreements before changing anything midstream.

Then test staffing at an aggregate level. Could planned specialist involvement reduce avoidable handoffs? Is routine work being assigned to an expensive role because scheduling is late? These are process questions. Do not publish individual wage details or produce employee profitability rankings.

Keep a short decision record: the observed cost pattern, the likely cause, the proposed change, and what would make you reconsider. That makes the next review a comparison against an explicit hypothesis rather than a debate about whose memory is right.

How often should you reprice?

Choose a review rhythm that fits your contract cycle and delivery volume. Review sooner when compensation changes, supplier costs rise, scope expands, or the service mix shifts materially. An isolated overrun warrants investigation, not an automatic increase across the client base.

For recurring work, compare consistent periods and account for seasonal workload. For project services, wait for enough comparable completions to distinguish a repeatable pattern from an unusual engagement. Keep the observation window visible so that older, differently scoped work does not dictate today's offer.

Separate the internal review date from the date a client receives a new price. Renewal terms, notice requirements, and commercial relationships matter. Give account owners a clear explanation of what changed and what customers receive, rather than presenting an unexplained rate adjustment.

How can SIGNLD support the review?

SIGNLD's Knowledge Graph builds automatically from connected sources, with no data engineering required. Confirm entity matches and the definitions behind your question, especially where payroll files and service codes use different identifiers. Automatic construction does not remove the need to resolve missing or ambiguous business records.

Create a Decision Topic for service pricing. Keep the Topic focused on aggregate delivery economics, and use a Decision Brief to explain the evidence, assumptions, and proposed commercial response. Restrict payroll fields to authorized users and share only the aggregate detail needed for the review.

Your data stays yours: read-only connections, a private LLM powered by AWS Bedrock on a single-tenant instance, and we never train on it.

Key takeaways

  • Actual delivery cost establishes a pricing floor, not the price a customer will accept.
  • Compare matched service periods and separate repeatable delivery from exceptional work.
  • Restrict payroll details and use aggregate service, client, and team views for pricing discussions.
  • Reprice when sustained cost or scope changes justify a review, rather than reacting to one difficult project.

FAQ

Is delivery cost the same as the price floor?

Delivery cost is the starting point, not necessarily the full sustainable floor. You may still need to cover sales, administration, facilities, and other overhead that your delivery definition excludes. State those exclusions clearly. A fee that covers direct labor can still leave the business short, even when the project appears to have a positive delivery margin.

Should we include nonbillable hours?

Include nonbillable work that is genuinely required to deliver the service, such as preparation or internal quality review. Treat general business development and unrelated administration separately unless your allocation policy explicitly includes them. The important distinction is attributable delivery effort versus broader operating cost, not whether someone marked an entry billable in the time tracker.

What if our time records are incomplete?

Treat the calculated cost as incomplete too. Show the affected coverage, identify missing assignments, and resolve gaps before using the result to justify a rate change. An explicit estimate may help planning, but label it as an estimate and keep it separate from recorded hours. Missing time should not silently become apparent profit.

Does the ROI calculator calculate service prices?

No. The SIGNLD ROI calculator is a business value estimator, not a service pricing calculator. Use it to explore the potential value of improving the decision process, with assumptions you can explain. Establish delivery costs, overhead treatment, and commercial pricing separately using your records and review process rather than treating an estimator result as a recommended client fee.

Related reading

Compare early project budget warnings and pipeline-based hiring. For additional context, read why utilization can miss client margin, project hours versus budget, and billing and payroll reconciliation.

Try SIGNLD free

Explore the business value estimator without treating it as a pricing calculator. Start with the Free Forever plan or a 14-day Growth trial, no credit card. Register for SIGNLD and begin with a clearly defined service-cost question.