You know the scene. It's 11pm, the tender's due in the morning, and someone's asking whether the day rate should come down again because procurement “needs more value”. The spreadsheet says one thing, the bid strategy says another, and nobody wants to be the person who wins the contract and then spends the next year regretting it.
That's why margin calculation matters before you price anything. If you don't know your floor, your target, and your risk, you're not pricing a bid. You're guessing and hoping the buyer doesn't notice. For teams that handle lots of UK public sector work, that guesswork gets expensive fast, especially when you're juggling lots of moving parts and trying to keep assumptions straight in software for managing construction finances or any other cost system that isn't built for bid work.
Bid managers who keep this under control treat margin as a bid discipline, not a finance clean-up exercise. That's the same mindset behind a clear bid process in Bidwell's bid manager guidance, because the job is to price with intent, then defend that price all the way through submission.
Why Margin Calculation Matters Before You Price a Tender
At 11pm, the spreadsheet looks tidy until you start separating what's direct cost, what's overhead, and what's just wishful thinking. That's where bids go wrong. A public sector buyer doesn't care that you were busy, only that your number is competitive and your delivery plan still works.
The UK public sector is price-sensitive, and framework rate cards can lock you in for a long stretch. If you underprice a call-off or a multi-year schedule, you don't get a second bite when costs rise or scope creeps. You live with the number you signed.
The bit most teams miss
Margin isn't just a finance ratio. In tendering, it's the difference between a contract that grows the business and one that keeps the lights on while draining cash. A thin first-year margin on a long contract can become a real problem when delivery gets harder, not easier.
Practical rule: if you can't say your target margin out loud before you price, you're not ready to submit.
That's why bid teams need a repeatable pricing habit, not a last-minute scramble. Keep the assumptions in one place, tie them to your costing history, and stop rebuilding the same logic every time. The obvious place to store that discipline is the knowledge base, because the AI response layer is only as good as the assumptions you feed it.
If you want the blunt version, this is a management issue, not a maths issue. The bid that wins at the wrong margin can hurt more than the one you lost.
The Four Margin Formulas You Need

Gross margin
Gross margin shows what is left after direct costs come out. Use margin % = (profit ÷ revenue) × 100, and keep the logic straight, margin is measured off price, not cost. A simple worked example with £200,000 revenue and £40,000 profit gives 20%, and the same percentage appears with £50,000 revenue and £10,000 profit.
That matters in bid reviews because two tenders can produce very different pounds of profit and still carry the same margin percentage. If you are comparing options for a UK public sector contract, that percentage is the number that tells you how hard the bid can be pushed before it stops making sense.
Contribution margin
Contribution margin is the cleaner test for variable-cost decisions. It shows what remains after variable costs are stripped out, so you can see whether the work contributes to fixed overhead and whether there is anything left to protect. If a bid looks tidy on paper but the delivery model eats the upside, the margin picture is weaker than the headline suggests.
Disciplined costing matters here, especially on framework rate cards and call-offs where the numbers need to stand up under scrutiny. Keep your assumptions in one place, and use cost calculation and cost monitoring so you are not rebuilding the same logic for every submission.
Operating margin
Operating margin looks at operating income divided by revenue. Use it when you want to know whether the business is profitable after the normal running costs of delivery, not just the direct job costs. That is a better review metric than a simple sales target when you are assessing performance across several contracts.
It also tells you whether a contract is carrying its share of management time, reporting, and overhead. Public sector pricing punishes vague assumptions, so this is the point where sloppy cost allocation starts to show up.
Net margin
Net margin is the final test. It asks what is left after all costs, including interest and taxes, have had their turn. If a bid only looks good before those costs, the price is too optimistic.

If you still mix up margin and mark-up, fix that now. Mark-up is added to cost, margin is taken from price. Mix them up and you can make a healthy-looking figure much thinner than it really is.
For a clean explanation of how gross margin sits alongside the broader commercial picture, how to impress investors with margins is a useful reference point, even if your real audience is a procurement panel rather than an investor deck. If your pricing logic needs to live somewhere reusable, keep it in the knowledge base so Bidwell can store the assumptions and pull the right wording the next time a tender asks how you calculate value for money.
A Worked Tender Calculation From First Number to Final Bid
A proper tender calculation starts with cost categories, not a hopeful final price. Suppose you're bidding for a £250,000 IT support contract over three years, and the buyer wants the price shown ex VAT. You split the job into direct costs, indirect costs, and the margin you need to protect.
Direct costs come first because they're tied to delivery. Labour sits there, software licences sit there, and subcontractor fees sit there. You don't hide those in overhead because they move with the contract and belong in the core price build-up.
Build the price in layers
Start with direct delivery costs. Add your indirect costs next, things like overhead share, management time, and travel. If your company uses a standard allocation method, keep it consistent so you can compare one bid with the next without fooling yourself.
Then apply the margin after the cost base is complete. If you apply margin too early, you end up compounding on the wrong number and making the tender harder to defend. That's especially dangerous on framework work, where you may be stuck with the rate card for years.
Keep VAT out of the contract price when the tender is quoted ex VAT. If you build it into the bid cost base, you'll distort the commercial picture and misread your own margin.
That separation matters because the public sector commonly evaluates tender values on a VAT-exclusive basis, while your actual cost stack still includes VAT-bearing inputs in parts of the business. Suppliers need to track the actual cash impact, not just the headline figure. For a practical angle on job costing discipline, AmbitionCFO on job costing is a solid read.
A simple worked outcome
If the direct and indirect costs together produce a base price that supports a 22% gross margin, that tells you the delivery model is sound before overhead pressure bites. If the same bid lands at 18% net margin after overheads, you've learned something different, that the contract still pays, but not as generously as the gross figure suggests.
Those two numbers are not interchangeable. Gross margin tells you what the work earns before the wider business burden lands. Net margin tells you what you keep.
For teams that want the calculation logic tied to live opportunities, the tender workflow in Bidwell's tender use case is the right place to keep the assumptions, cost headings, and response language aligned.
How Procurement Scoring Changes the Margin You Should Bid
A lot of bid teams chase the lowest possible number because they assume price wins everything. It doesn't. Buyers score quality and price together, so the scoring split changes the margin you can realistically protect.
Start from the buyer's scoring model
A 70/30 quality/price split gives you room to defend a stronger delivery model if your technical response is credible. A 50/50 split is harsher, because price pressure becomes much more direct and your commercial room narrows fast. That doesn't mean you should slash margin blindly, it means you should reverse-engineer the target from the scoring method instead of guessing.
Framework agreements make this even more unforgiving. If you set a rate card for future call-offs, the first calculation shapes the next several years of work. That's not a place for optimism.
Bid the score, not the fantasy
The right margin is the one that fits the buyer's evaluation logic and your delivery reality. If you know the buyer is rewarding quality, you can sometimes hold margin better by proving capability rather than shaving every pound off the price. If the weighting leans hard on price, you need to decide whether the work is worth chasing at all.
That's where tender monitoring earns its keep. Flag the weighting early, store the buyer's pricing assumptions in your knowledge base, and keep the AI response generator from rewriting the same commercial logic every time a similar opportunity appears.
The mistake is simple. Teams bid what they want to earn, not what the scoring structure will support.
Five Margin Mistakes That Quietly Kill Public Sector Contracts
The worst margin errors rarely look dramatic on the day. They show up later, when the delivery team is drowning and finance is asking why the contract is performing below plan. Most of them start with a small assumption error that nobody challenged.

1. Confusing mark-up with margin
If you add a mark-up to cost and call it margin, you'll misprice the job. The symptom is simple, the bid looks fine in the room, but the actual return is thinner than the team expected. Fix it by using margin against selling price, not against cost, every single time.
2. Leaving VAT in the wrong place
UK public-sector pricing is usually presented ex VAT, so a cost base that treats VAT as part of the price story will muddy the numbers. The symptom is a headline that doesn't match the commercial case. Keep VAT separate and make sure everyone knows whether the tender wants ex VAT or inclusive figures.
3. Under-allocating overhead
When buyers push for a low day rate, teams often shave overhead out of the calculation to stay competitive. That only works until the business has to absorb the missing cost somewhere else. Fix it by assigning overhead consistently, then deciding whether the contract still clears your floor.
4. Ignoring multi-year escalation
A rate card that looks acceptable in year one can become a problem when labour and supplier costs move but the price doesn't. The symptom is a contract that gets harder to deliver each year, not easier. Build escalation thinking into the model before you sign.
5. Letting scope creep eat the profit
Change requests and little extras can strip away the gain you thought you'd won. The symptom is a healthy award that turns into a tired contract because nobody priced change properly. Set a change-control margin and stop treating extras as favours.
Your knowledge base should store each of these failure points so the AI response layer doesn't repeat the same mistakes. If the system sees a bid assumption that clashes with your policy, it should be obvious before submission, not after award.
A Margin Protection Checklist for Every Submission
Once the price is built, protect it. A lot of bids lose margin after the first draft because internal reviewers push the number around without checking what that does to the commercial model. Don't let that happen.
- Confirm VAT treatment. Make sure the tender is being priced on the same VAT basis the buyer is using.
- Lock the overhead allocation method. Use the same approach every time so your comparisons stay honest.
- Document assumptions. Write down what's in scope, what's excluded, and what the pricing depends on.
- Set a floor margin. Decide the minimum you'll accept before the bid becomes a distraction.
- Benchmark against past wins. Check whether the number makes sense against previous work with a similar delivery shape.
- Factor in change request margin. Price the risk of scope movement instead of hoping it stays still.
- Escalate multi-year costs. If costs rise over time, the model needs to reflect that.
- Review evaluation weighting. Don't let the price line drift without checking what the buyer is scoring.
Practical rule: if the bid team can't explain why the final price still clears the floor margin, the draft isn't ready.
This is exactly the kind of material that belongs in the knowledge base. Once it's stored, the AI response generator can flag contradictions in wording, assumptions, or pricing logic before they become a submission problem. That makes protected margin repeatable margin.
Your Bid Margin Spreadsheet in 15 Minutes
Stop rebuilding the model from scratch. Use one sheet, one structure, and the same logic every time. That gives you a faster review cycle and fewer surprises when the pricing meeting turns awkward.
| Column | Purpose | Sample Value |
|---|---|---|
| Column A | Direct costs by category | Labour, software, subcontractors |
| Column B | Indirect costs | Overhead allocation, management time, travel |
| Column C | Subtotal cost | Sum of direct and indirect costs |
| Column D | Target margin percentage | Chosen from buyer scoring and risk |
| Column E | Bid price | Total cost divided by one minus target margin |
A sample row should be built from the categories you use, not a generic template. Put labour hours multiplied by rate in direct cost, licences where they belong, and overhead where it's consumed. Then set the margin after you've finished the cost base, not before.
The two formulas you need are straightforward. Bid price = total cost / (1 - target margin). Gross margin = (bid price - total cost) / bid price. Use the first to build the number, then use the second to check that the output really gives you the percentage you intended.
That sheet should sit beside your knowledge base, not replace it. The knowledge base stores the assumptions, and the spreadsheet turns them into a price. The AI layer can then pre-fill categories from past bids instead of making you type the same logic again at midnight.
When you're done, run this mental checklist. Define the margin formula you're using. Allocate direct and indirect costs fairly. Set the target margin from the scoring model, not your gut. Run the protection checklist. Store the logic so the next bid starts halfway done.
If you're tired of rebuilding pricing logic for every tender, Bidwell gives you a practical way to keep your cost assumptions, tender monitoring, and response drafting in one place. It helps you carry the same margin discipline from opportunity alert to final submission, so you're not starting from zero every time the next public sector bid lands.



