Cost plus pricing example: product and service

Half the time someone asks me how I got to a quote, I'm trying to remember whether the number came from cost, from what the buyer would tolerate, or from gut feel. Cost-plus is the version you can defend out loud: total the cost of delivery, add a markup, send the number. It's easy to calculate and, when the cost base is sound, easy to explain to a procurement team.

The danger is treating the result as the final price. I use cost-plus as an audit benchmark. It tells me whether a quote covers the resources needed to deliver the work. It says nothing about what a buyer will pay, what competitors charge or how much the outcome is worth to them.

Cost-plus pricing is a formula with one trap

Cost-plus pricing sets a selling price by taking the unit cost and adding a stated markup:

Selling price = unit cost × (1 + markup rate)

Start with a cost line you can explain. Then say whether your percentage is a markup on cost or a margin on the selling price. They're different calculations, and pricing conversations get painful when finance means one and sales means the other.

The formula in a small product example

Suppose the unit cost is £40 and the markup is 25%:

£40 × 1.25 = £50

The £10 difference is the profit added to cost. That's a 25% markup on cost, but £10 is only 20% of the £50 selling price. Someone who asks for a "25% margin" does not want a £50 price. They want one around £53.

Before you type a percentage into a spreadsheet, label the denominator.

Practical rule: write "markup on cost" or "margin on price" beside every percentage in a pricing model.

The formula is simple. The cost line is where the work sits. A £40 unit cost that leaves out support, rework, software or shared admin gives you a precise answer to the wrong question. Ambition CFO makes the same point: costing sets your economic floor, and pricing is a separate decision made above it.

Worked example for a software product

Software businesses underestimate cost-plus because the cost of serving one account isn't just the hosting bill. A credible unit cost includes the work that keeps the product available, secure and supportable.

These numbers are invented to show the structure. They aren't LiveDocument's costs and you shouldn't price against them. Take a subscription product with 10,000 expected paid customer-years and an annual cost base of:

Cloud infrastructure: £120,000
Support and compliance operations: £80,000
Payment, storage and notification costs: £50,000
Allocated product and engineering overhead: £150,000

That's £400,000 in total, so the fully loaded cost is:

£400,000 ÷ 10,000 = £40 per customer-year

Apply a 75% markup:

£40 × 1.75 = £70 per customer-year

£70 is a defensible cost-recovery price for this model. It includes engineering and operations costs that vanish from a superficial calculation.

I'd split usage-sensitive costs from fixed platform overhead rather than spreading everything evenly. Storage, video processing, bandwidth and notifications can be allocated per active account. Core engineering and compliance get spread across expected paid accounts. The spreadsheet then shows which costs rise with usage and which need recovering across the whole base.

The £70 is a floor and an audit check. A buyer may value the software far above its delivery cost, or a competitor may offer something cheaper. Those questions belong in the commercial review that comes after the cost calculation, and the number can then feed into a sample sales proposal without pretending internal cost is the same thing as customer value.

Worked example for a service business

Service pricing is harder because the deliverable includes labour that never appears on an invoice. A narrated proposal package, for example, involves production, review, media processing, hosting and revisions before the client sees anything.

Assume a team produces 1,000 packages a year. The cost per package is:

Direct labour: £90
Media processing and hosting: £15
Allocated overhead: £45

The full cost is £150 per package. The team chooses a 40% markup on full cost:

£150 × 1.40 = £210

That leaves £60 above assigned cost, but £60 is only a 28.6% margin on the £210 selling price, not 40%.

The denominator changes the quote

If management wants a 40% margin on the selling price, the calculation changes:

£150 ÷ (1 − 0.40) = £250

The underlying cost hasn't moved. Only the percentage and its denominator have.

Target	Calculation	Quoted price	Implied profit
40% markup on full cost	£150 × 1.40	£210	£60
40% margin on selling price	£150 ÷ (1 − 0.40)	£250	£100

This is what bites when a finance director checks a quote after a salesperson has promised a margin. Put the basis in the pricing sheet and in the approval note.

The process is repeatable:

Build the full cost per deliverable.
State whether the target is markup or margin.
Calculate the quote.
Check the implied margin before sending it.
Add any unusual onboarding, template or regulated-workflow work to the cost base.

If billing is staged, the quote also needs a collection process. Teams obsess over the number and then lose weeks chasing payment, so it's worth knowing how to send an invoice via email before the first one goes out.

What belongs in the cost

The most common failure happens before the markup is chosen. The business calculates an incomplete cost, applies a sensible percentage and still loses money. Marketing spend, tooling, rework and shared admin end up costing nothing on paper.

Separate the cost buckets

For a service or project business I'd start with three buckets.

Variable costs rise with each unit or client: materials, subcontractor fees, payment fees, media processing, hosting, delivery. Order more units and these should move with volume.

Fixed costs don't change straight away when output changes: software subscriptions, support tools, insurance, compliance work, shared admin. They still need recovering even though they never show on a project invoice.

Capacity-dependent costs move with utilisation. Direct labour is the obvious one, but owner time, review work, revisions and rework belong here too. A team with spare capacity may price a job differently from a team already at full stretch, but it should understand both versions of the economics.

The items people leave out

Sales commissions reduce what's left after a deal closes. Warranty work and revisions eat delivery time. A founder who sells, scopes and delivers the work is using a scarce resource even if no payroll line records it. I've priced work while ignoring my own hours more than once, and the margin looked lovely right up until I counted them.

Match the allocation base to the cause of the cost. Allocate a processing expense by usage where usage drives it. Spread shared engineering or admin across the accounts or projects that benefit. SumUp's small-business pricing guide makes the basic point: materials, labour and overheads all go in before you apply the markup.

A price can be mathematically tidy and operationally loss-making.

For project work, write the assumptions down next to the quote. A service contract should say what happens when scope, review rounds or delivery requirements change, which stops the cost model quietly absorbing extra work.

When the formula gives you the wrong answer

Cost-plus is internally consistent and externally naive. It responds to your cost, not to demand, perceived value or the alternatives in front of the buyer. Competera's breakdown of cost-plus limits puts it plainly: the same cost and markup produce the same price whatever demand is doing, so strong demand may support a higher price and weak demand may call for a lower one. A price floor is useful. A floor shouldn't become a ceiling.

Three situations that justify an override

A competitor launches a cheaper alternative and buyers start comparing like for like. Your cost-plus number may now be too high. The answer isn't automatically to cut the markup. You might strip out lower-value features, create a narrower package or offer a defined segment a discount.

A strategic customer offers a large order that fills unused capacity. The relevant numbers may then be marginal delivery cost and the opportunity cost of taking the work. A quote below fully allocated cost can be rational for spare capacity, as long as the decision is deliberate and you know which fixed costs stay uncovered.

The opposite case is just as common. Automation cuts the effort needed to deliver a service, so the formula spits out a lower price. If the customer still gets the same valuable outcome, passing every efficiency gain straight through leaves money on the table.

A practical override test

Keep the cost-plus number when the market is stable, the cost base is reliable and the buyer expects transparent cost recovery. Add a premium when the outcome carries value your internal cost doesn't capture. Discount or restructure when competitor evidence or unused capacity makes the calculated price unrealistic.

My rule is simple:

Use cost-plus as a price floor or audit benchmark, then test willingness to pay, competitor pricing and account-level usage before you send the final number.

That gives finance a defensible base and gives sales room to price the result rather than the effort.

Pros, cons and three habits

Cost-plus earns its place because it's straightforward. You can show the cost pool, the allocation method and how the percentage produced the quote. Procurement teams often like that transparency, especially when costs have moved. It also gives you a warning line: if a proposed price sits below fully loaded cost, someone has to approve the commercial reason instead of discovering the problem after delivery.

The drawbacks are just as practical:

It ignores demand: the formula can price a weak offer too high or a valuable one too low.
It can preserve inefficiency: if your processes cost more than they should, the customer ends up funding the waste.
It can unsettle value-led buyers: buyers focused on outcomes may ask why your internal cost sets their price.

Three habits make the model usable:

Separate usage from platform overhead. Costs that rise with storage, processing, bandwidth or notifications shouldn't be buried in a fixed average if account usage varies a lot. Keep fixed compliance and core engineering visible as shared overhead.
Re-price the cost base during inflation. Don't leave a markup untouched while labour, tools, delivery or supplier costs change. Review the inputs at least quarterly when costs are moving quickly.
Explain surcharges with the same logic as the quote. If a temporary cost increase affects delivery, show the affected line and say whether the charge is temporary or permanent. A buyer may still reject it, but a vague explanation makes a reasonable change look arbitrary.

Common questions about cost plus pricing

How often should the cost base be reviewed during inflation?

Whenever major inputs change, with a regular quarterly check when costs are moving fast. Labour, supplier charges, software, hosting, payment fees and delivery costs usually deserve attention first.

Should I set a margin or a markup?

Decide which outcome finance wants before you calculate the quote. Markup is added to cost and margin is measured against the selling price, so the same percentage gives different prices.

Where does the owner's time belong?

In the cost base, when the owner sells, scopes, manages or delivers the work. Use a consistent internal rate, then test the resulting quote against market evidence rather than pretending unpaid time is free.

Can cost-plus pricing work in regulated contracts?

Yes, but the contract may add controls beyond a fixed percentage. In a cost-plus-incentive-fee contract under the US Federal Acquisition Regulation, the agreement sets a target cost, target fee, minimum and maximum fees and a fee-adjustment formula, and the final fee moves with allowable costs within those limits.

---

If your pricing documents need more than a static attachment, LiveDocument lets you add a short video walkthrough to a PDF or image, share one tracked link and see which pages a buyer viewed. One limit: it tells you what was viewed, not why. Use the cost-plus benchmark to defend the number, then use the walkthrough to explain the value behind it.