---
title: "How to price a tender when volumes are unknown"
description: "Separate fixed and variable cost, expose volume drivers, test scenarios and follow the buyer’s evaluation method without inventing demand."
canonical: "https://zephior.com/insights/price-a-tender-with-unknown-volumes"
last-updated: 2026-09-02
---

# How to price a tender when volumes are unknown

> Separate fixed and variable cost, expose volume drivers, test scenarios and follow the buyer’s evaluation method without inventing demand.

By [Tony Kim](https://zephior.com/authors/tony-kim). Published 2026-09-02; updated 2026-09-02. 11 minute read.

## Definition

Pricing a tender with unknown volumes means offering the required commercial structure without pretending to know the buyer’s future demand. The bidder identifies measurable volume drivers, separates fixed, variable and step costs, follows the buyer’s units and evaluation quantities, documents permitted assumptions and tests the economics across plausible scenarios. The submitted figure may be a rate card, evaluated model, banded price, minimum commitment, capped charge or another mechanism expressly allowed by the procurement. It is not a bidder-created forecast presented as a buyer commitment.

## Problem

When quantities are missing, teams commonly choose a convenient central estimate and divide total cost by it. The resulting unit rate looks precise but can fail at both ends. At low demand, fixed onboarding, governance, environments and minimum staffing are not recovered. At high demand, capacity arrives in steps, support effort changes or a third-party charge grows faster than the chosen unit. Another team may add a broad contingency, making the offer uncompetitive without showing what it covers. The worst answer hides the assumed demand inside a spreadsheet formula. Evaluators cannot compare it, approvers cannot see the exposure and delivery inherits an economic promise based on a number the buyer never supplied.

## Point of view

Start with the buyer’s pricing schedule and evaluation rule, not with the bidder’s preferred commercial model. Treat evaluation quantity, contractual commitment and planning scenario as three different concepts. Ask a focused clarification when a missing input prevents a compliant price. Where the rules permit assumptions or scenarios, show the demand driver, unit, period, included range and price behavior outside it. Model fixed, variable and step costs separately and test breakpoints. State what the customer pays, how usage is measured, which price changes are automatic and which require agreement. A transparent model is not a transfer of every risk to the buyer; it is a deliberate allocation that both parties can operate.

## Separate evaluation quantity, planning demand and contractual commitment

A tender can contain several quantities that do different jobs. The buyer may publish estimated quantities only to compare bids, provide historic demand for context, request a total against a notional scenario and reserve the right to order more or less. None of those figures necessarily guarantees revenue. Record each number with its source, period, unit, purpose and contractual status. If the pricing sheet asks for 100,000 transactions, state internally whether that is an evaluation multiplier, a forecast or a committed minimum. Do not let the workbook’s multiplication formula answer a legal or commercial question that belongs to the procurement documents.

Use the buyer’s method exactly. Some indefinite-quantity structures expressly use estimates for evaluation while contract obligations are bounded differently. United States FAR Part 16, for example, recognizes indefinite-quantity contracts where precise quantities cannot be predetermined above a stated minimum. A Department of Commerce clause separately explains that proposed rates may be applied to estimated quantities for evaluation. Those rules illustrate the distinction but do not govern another tender. For the live bid, read the actual schedule and contract. If a necessary quantity or status remains ambiguous, submit a clarification before inventing a demand promise.

**Volume evidence register**

| Number | Question to answer | Do not assume |
| --- | --- | --- |
| Historic volume | Period, scope and known change | Future demand |
| Buyer forecast | Confidence and purpose | Purchase commitment |
| Evaluation quantity | Comparison formula | Expected outturn |
| Minimum | Binding wording and period | Forecast accuracy |
| Maximum or cap | Order or price boundary | Likely consumption |
| Bidder scenario | Approved use and assumption | Buyer-provided fact |

## Build a cost curve before choosing a unit rate

Separate costs by behavior. Fixed costs include bid-specific transition, baseline governance, a dedicated environment or minimum on-call coverage. Variable costs may follow messages, cases, storage, payment events or delivery hours. Step costs arrive when one more team, tenant, region, appliance or license block is required. Time-dependent costs vary with contract duration even if usage is flat. Map each cost to a measurable driver and note whether the driver is controlled by the buyer, supplier or an external party. A blended unit rate is a presentation output, not the model itself.

Test several coherent scenarios rather than moving one arbitrary volume cell. The UK Infrastructure and Projects Authority’s cost-estimating guidance says estimates should connect scope, design, schedule and risk, document assumptions and exclusions, and test material uncertainty. For a bid, the analysis must also respect what the buyer permits the supplier to submit. Low demand tests fixed-cost recovery. The evaluation case reproduces the scoring method. An operational expectation supports capacity planning without becoming a buyer fact. High demand tests service limits and price behavior. Add threshold cases just below and above every band to expose cliffs, accidental discounts and stranded capacity.

- Do not allocate all fixed cost across a demand estimate without testing lower use.
- Keep third-party minimums, commitments and overages visible.
- Model the time at which cash is paid as well as total margin.
- Test the unit denominator for double counting and omitted activity.
- Review thresholds one unit below, at and one unit above the boundary.

## Define a unit that finance and operations can both recognize

“Per transaction” is incomplete. Say whether a transaction is initiated, completed, accepted, unique, retried, reversed or billed in batches. Define the measurement window, time zone, rounding, exclusions, free allowance, source system and responsible party. Explain how corrections are handled and how both parties inspect the record. The same discipline applies to users, cases, sites, devices, gigabytes and hours. A price based on registered users behaves differently from one based on active users, and neither is workable until “active” has a rule.

Where the tender permits a commercial mechanism, choose one that reflects the cost curve without creating a hidden commitment. A fixed base plus variable rate can recover standing capacity. Bands can reflect capacity steps but need unambiguous marginal or all-units treatment. A minimum charge can protect readiness but must be allowed and visible. A cap can offer budget certainty only if its scope, reset period and excluded services are clear. Do not insert these devices into a mandatory fixed-price cell if alternatives are prohibited. Either price the required risk with approval, seek clarification or make a deliberate bid decision.

**Operational definition of a billable unit**

| Field | Example question | Commercial consequence |
| --- | --- | --- |
| Event | What exactly creates one unit? | Sets the charge trigger |
| Population | Which customers, sites or records count? | Sets scope |
| Period | Monthly, annual or contract cumulative? | Changes band treatment |
| Source | Which system is authoritative? | Controls invoicing evidence |
| Correction | How are retries and reversals treated? | Prevents double charge |
| Dispute | Who can inspect and challenge? | Makes the mechanism governable |

## Submit one commercial story across model, narrative and contract

Prepare an approval view that shows the required submitted price beside the internal economics. Include source volumes, uncommitted assumptions, fixed and variable cost, scenario revenue, gross margin, cash exposure, third-party commitments, capacity thresholds and the proposed treatment of residual risk. The approval should identify the exact workbook version and the assumptions that would reopen it. Do not conceal a weak case in a single weighted average. Decision-makers need to know which demand movement changes the outcome and whether the contract allows any corresponding price response.

Reconcile the commercial model with every buyer-facing component. The technical answer must not promise unlimited scale while price assumes a narrow range. Service levels must remain feasible at high use. The contract response must match minimums, caps, measurement, invoicing, indexation and change control. The portal total must equal the approved evaluation calculation. The UK government’s service-costing guidance emphasizes a controlled assumptions register, consistent denominators, source-to-output traceability and clear explanation of uncertainty. Those are useful assurance tests here. They do not authorize additional tender caveats, so disclosure still has to fit the buyer’s rules.

- Tie every submitted price cell to an approved model output.
- Separate the scoreable total from internal expected revenue.
- Confirm that scope and service capacity match each tested scenario.
- Put permitted assumptions in every place the buyer requires them.
- Archive the final model, approval, schedule and portal reconciliation together.

## Useful outcomes

- The submitted price uses the buyer’s required units, quantities and evaluation method.
- Planning assumptions are not mistaken for minimum orders or demand guarantees.
- Fixed, variable and capacity-step costs remain visible to commercial approvers.
- Unit definitions and measurement rules are operationally testable.
- Low, expected and high demand scenarios reveal margin and delivery breakpoints.
- Contract, price schedule and technical response describe the same volume mechanics.

## Workflow

1. **Read the commercial instruction literally.** Identify required units, periods, evaluation quantities, mandatory totals, permitted assumptions, minimums, caps, indexation and rules for blanks or alternative prices.
2. **Build the demand-driver map.** Trace each cost to users, transactions, sites, cases, hours, storage, environments or another measurable driver. Separate buyer data from bidder assumptions.
3. **Design a permitted price structure.** Allocate fixed, variable and step costs to the required schedule. Use bands, rates, minimums or caps only when the buyer’s rules allow them.
4. **Test scenarios and breakpoints.** Run low, evaluation, expected and high scenarios. Inspect margin, cash, service capacity, third-party exposure and discontinuities at every threshold.
5. **Approve and reconcile the offer.** Secure finance, delivery, tax and legal review as appropriate. Match price mechanics to scope, service levels, contract terms and portal values before submission.

## Key decisions

- Which quantity does the buyer use for evaluation, and does it create any purchase commitment?
- What event or measure defines one billable unit?
- Which costs exist before the first unit is consumed?
- Which costs move smoothly with demand and which change at capacity thresholds?
- Can the bidder state assumptions, bands, minimum charges or volume discounts?
- Who measures usage, from which system and with what dispute process?
- At which demand levels does margin, staffing or infrastructure become unacceptable?
- Which residual exposure requires executive or contractual approval?

## Risks

- An evaluation quantity may be misread as a guaranteed order volume.
- A unit price may fail to recover fixed mobilization and governance cost.
- Averages may hide step changes in staffing, infrastructure or licensing.
- Different schedules may use inconsistent units, periods or volume assumptions.
- A bidder-created scenario may violate the required comparison method.
- Unclear measurement rules may create billing disputes after award.
- Volume discounts may make a lower band more expensive in total than a higher band.
- A broad risk premium may price uncertainty twice or make the offer uncompetitive.

## Metrics

- cost lines mapped to a named demand driver
- price cells traced to buyer instructions and source assumptions
- scenarios tested across the permitted volume range
- capacity and margin breakpoints with approved treatment
- unit definitions with measurement owner and source system
- material assumptions disclosed in every affected response component
- commercial inconsistencies found before submission

## Frequently asked questions

### Should we invent a volume so that we can submit a total price?

Use a bidder assumption only if the tender permits it, label it clearly and obtain approval. First check whether the buyer supplied an evaluation quantity elsewhere or whether a clarification is required. Never present an internal scenario as buyer demand.

### Does an estimated tender quantity guarantee that volume?

Not necessarily. An estimate may exist only for comparison or planning. Read the pricing instructions and contract to determine whether any minimum, maximum or commitment exists, and obtain legal review where the consequence is material.

### Is a single unit rate the safest answer?

Only if it follows the required format and remains viable across the contractual demand range. Model fixed, variable and step costs first. A simple submitted rate can sit above a detailed internal cost curve, but it should not replace that analysis.

### What scenarios should a pricing team test?

Test a low-volume case, the exact buyer evaluation case, a separately identified operational planning case, a credible high case and the values around each band or capacity threshold. Vary the cost drivers that materially affect the result.


## Primary sources

- [Cost Estimating Guidance](https://www.gov.uk/government/publications/cost-estimating-guidance/cost-estimating-guidance), UK Infrastructure and Projects Authority
- [Service Costing in Government](https://www.gov.uk/government/publications/service-costing-in-government/service-costing-in-government), UK Government Finance Function
- [FAR Part 16, Types of Contracts](https://www.acquisition.gov/far/part-16), Acquisition.gov
- [Evaluation quantities for an indefinite-quantity contract](https://www.acquisition.gov/car/1352.215-73-evaluation-quantities-indefinite-quantity-contract.), Acquisition.gov


## Related articles

- [Test inflation and indexation in a long-term tender](https://zephior.com/insights/respond-to-tender-price-indexation)
- [Price a tender without hiding exchange-rate risk](https://zephior.com/insights/price-a-multicurrency-tender)
- [How to clarify an ambiguous tender pricing template](https://zephior.com/insights/clarify-an-ambiguous-pricing-template)
- [Check a tender discount before committing the lower price](https://zephior.com/insights/apply-discounts-in-a-tender)