Choose Between a Fixed Quote, a Range, and Paid Scoping
Prepared with AI assistance by Alactic Editorial. Examples identified as hypothetical are illustrative, not customer results.
A buyer asks what the work will cost. You understand the outcome they want, but not yet the condition of their inputs or the exceptions you will encounter. A precise price could rest on guesses. Refusing to discuss price until everything is known could stall a sensible buying decision.
Choose a fixed quote when the work and its boundaries are sufficiently understood. Choose a bounded estimate when credible lower and upper scenarios describe the remaining variation. Propose paid scoping when resolving important unknowns requires substantial investigation that produces useful work for the buyer. If one ordinary clarification would settle the issue, ask for it.
This is an operating method for deciding quotation readiness, not a guide to legal distinctions between documents. The key question is whether the evidence supports the commercial response.
1. Separate three reasons a price is not ready
Uncertainty, variability, and investigation effort often get bundled together as unclear scope. Separate them because they lead to different next steps.
- Uncertainty: something consequential is unknown. You have not inspected the files, for example.
- Variability: the work can take different known forms or volumes, such as different quantities of corrections.
- Investigation effort: the work required to establish usable facts. Reading an existing specification is different from interviewing teams and reconstructing an undocumented process.
An unknown does not automatically justify paid discovery. The buyer may already have the answer in a document. Equally, familiarity with a service does not make unfamiliar inputs predictable.
Ask whether a missing answer could change the delivery method, rather than merely the amount of work. If it could, two price endpoints may be premature: you do not yet know which job you are estimating.
2. Apply a readiness gate before choosing the format
Write a short internal scope note covering the requested outcome, deliverables, exclusions, quantities, input conditions, buyer responsibilities, supporting evidence, and reasons to reconsider the scope. Keep it proportionate to the work.
Use the note to choose the next response:
- Clarify first if readily available information could make the enquiry quote-ready.
- Quote a fixed price if deliverables, inputs, dependencies, and change triggers are sufficiently clear.
- Offer a bounded estimate if both endpoints have credible scenarios and explicit conditions.
- Propose paid scoping if meaningful investigation is required before a delivery approach or price boundary can be justified.
Do not average these judgments into a score that conceals a decisive gap. Several well-understood tasks cannot compensate for one unresolved dependency that could change the whole approach.
Also separate the decision to discuss a price from the decision to start work. Receiving files, answering questions, or accepting a planning range does not by itself authorise chargeable delivery.
3. Compare three enquiries side by side
Fictional worked examples: All enquiries, amounts, quantities, limits, and effort allowances below are hypothetical. Prices illustrate decisions, not market rates. This filled table can be reused as the structure for an enquiry review.
| Enquiry | Uncertainty drivers | Evidence or investigation effort | Pricing response | Caveats | Buyer-facing explanation |
|---|---|---|---|---|---|
| A: Refresh a sales document | Whether copy is final and brand assets are usable. | Seller has inspected approved copy and assets for a 12-page document. One buyer approver is named. Remaining checks are ordinary quotation preparation. | Fixed quote: £2,400 for print-ready and editable files, with two consolidated review rounds. | Excludes new copywriting, extra pages, and a replacement visual identity. Changes require a separate decision before changed work begins. | The supplied materials support a fixed price for these deliverables. Additional pages or new copy would be priced before proceeding. |
| B: Transfer a contact dataset | Correction volume within an otherwise known transfer method. | Complete frozen export inspected: 8,000 rows, one source file, 12 fields. Profiling finds 240 duplicate groups and 360 values needing an agreed standardisation rule. | Bounded planning estimate: £3,500–£5,500, supported by the effort scenarios below. | At most 10,000 rows, 300 duplicate groups, 500 standardisation values, and 16 correction hours. Only agreed deterministic rules; no individual research. Full conditions must still hold before authorisation. | The inspected export supports this range. Correction effort moves the price within it. If the input or correction conditions fail, we will withdraw or revise the estimate before asking you to authorise delivery. |
| C: Redesign enquiry handling | Undocumented routing, disputed ownership, and no agreed acceptance criteria. Findings could change the delivery method. | Requires stakeholder sessions, sample enquiry review, and a documented process design; a sales clarification cannot resolve it. | Separately scoped discovery: fixed £1,800. | Three stakeholder sessions, current-state map, exception register, and scope options. Excludes implementation and any promised implementation price. | Discovery produces a process map and scope options you can use to decide what to commission. Implementation needs a separate proposal and approval. |
The distinction is not project size. A has evidence-supported boundaries. B has an established method and measurable remaining variation. C needs investigation to determine what the work should be.
4. Work through the bounded estimate, not just its endpoints
Enquiry B deserves closer attention because a sample alone would not justify its upper scenario. In this hypothetical example, obtaining and inspecting the complete export is a prerequisite to issuing the range. Before that inspection, the seller requests the file rather than presenting £3,500–£5,500 as a defensible estimate.
The inspection counts every row, checks all 12 fields against the agreed rules, and inventories duplicate groups and inconsistent values. A small rehearsal on representative exceptions helps assess correction effort, but does not establish dataset-wide volume. The full-file inventory does that.
The hypothetical internal model uses a £125 hourly planning basis. It is a costing illustration, not a recommended rate:
- Lower scenario: 24 hours for agreed mapping, transfer preparation, reconciliation, and exception reporting, plus four correction hours. Total: 28 hours, or £3,500.
- Upper scenario: the same 24 core hours, plus 16 correction hours and four additional verification hours. Total: 44 hours, or £5,500.
The observed exception counts fit inside the stated volume limits. The rehearsal indicates that the agreed correction rules can fit inside the upper effort allowance. Both pieces of evidence are necessary: a row count alone says little about correction difficulty.
The buyer must confirm the correction rules, including which record wins when a duplicate is resolved. Unresolved cases are listed in the exception report, not researched individually. That exclusion prevents an apparently simple transfer from becoming an open-ended data investigation.
Findings that invalidate the range include another source file, changed destination fields, more than the stated volume limits, ambiguous rules requiring record-by-record judgment, or evidence that corrections cannot fit within 16 hours. Any such finding requires a revised scope and estimate before delivery authorisation. The seller cannot keep the same assumptions and casually treat £5,500 as exceedable.
5. State what each pricing format actually buys
A fixed quote needs boundaries as well as a number. Include deliverables, quantities, input requirements, review arrangements, dependencies, and exclusions. Use assumptions for visible, reasonable conditions—not as a substitute for inspecting a decisive input.
Distinguish a buyer-requested scope change from a seller estimation error. If the work remains unchanged but you underestimated your effort, do not describe that as a new requirement. Review the cause internally and manage the commercial response deliberately.
A bounded estimate needs a different explanation. Its upper scenario applies only within the stated scope and input conditions. It is not an open-ended estimate with a reassuring second number attached.
- State its purpose: budgeting, selecting an approach, or deciding whether to investigate further.
- Explain movement: identify the work that separates the lower and upper scenarios.
- Define invalidation: list findings that would make neither endpoint reliable.
- Name the approval step: specify how the buyer will authorise delivery and any spending limit.
A conditional planning range is not automatically a spending authorisation. If conditions fail, withdraw or revise it before seeking authorisation. If conditions remain unchanged, effort above the upper scenario is not simply normal range movement; it calls for an explanation of the estimation problem, not an automatic extra charge.
When the buyer needs certainty, consider narrowing the work to a bounded phase. Do not relabel an uncertain total as fixed merely to fit a purchasing process.
6. Make paid scoping useful on its own
Paid scoping should produce something the buyer can use, not charge for access to a sales conversation. Its proposal needs the same discipline as delivery work: questions, evidence, participants, outputs, exclusions, and completion criteria.
For hypothetical Enquiry C, the three sessions address intake, routing, and exception ownership. The process map records handoffs; the exception register identifies unresolved decisions; the scope options distinguish essential changes from optional improvements. Those outputs help the buyer decide even if implementation is postponed.
State what happens if participants or evidence are unavailable. A blocked workshop should not silently become a completed investigation. Record which conclusions remain unsupported and what input would unblock them.
Discovery need not remove every unknown. It should identify remaining uncertainty and show whether a bounded phase, an estimate, or further investigation is appropriate. Do not promise that discovery must yield a fixed implementation quote. Clarify whether its fee is credited against later work rather than leaving the buyer to assume it is.
7. Keep a filled decision record beside the proposal
The comparison table helps select a format. A short decision record preserves why you selected it. This filled hypothetical record for Enquiry B is reusable: replace each value with evidence from the next enquiry.
- Requested outcome
- Transfer the inspected contact export into the agreed destination structure and supply reconciliation and exception reports.
- Evidence version
- Complete frozen export B-01: 8,000 rows and 12 fields; full-file exception inventory recorded.
- Remaining variable
- Correction effort under buyer-approved deterministic rules, within the stated volume limits and 16-hour allowance.
- Selected response
- £3,500–£5,500 conditional planning estimate; not permission to start delivery.
- Buyer input owner
- Operations lead: confirm duplicate precedence and standardisation rules before proposal approval.
- Seller check owner
- Delivery lead: confirm the authorised input matches B-01 and the conditions remain valid.
- Invalidation triggers
- Additional sources, changed structure, exceeded volume limits, individual research, or unsupported correction effort.
- Next approval
- Buyer reviews the confirmed scope and commercial authorisation; changed conditions require a revised proposal first.
The record makes missing evidence visible and assigns someone to obtain it. It also prevents a provisional conversation from becoming an unexplained commitment.
8. Recover when the first response proves wrong
If a fixed quote exposes a major unknown, compare the finding with the stated scope. Separate changed requirements from estimation mistakes before proposing a remedy. Do not expand the work informally while deciding who should pay.
If a range cannot be narrowed, identify the missing evidence. Request a specific input if that will resolve it. If meaningful investigation is now necessary, explain why the old estimate is no longer reliable and propose a bounded scoping engagement.
If discovery produces no decision-ready output, review the agreed deliverables before proposing more discovery. Explain blocked inputs, unanswered questions, and what can still be concluded.
After the next few enquiries, review whether assumptions were recorded, ranges narrowed when evidence arrived, and work waited for approval. These observable outcomes are more useful than trying to make every enquiry fit the same pricing format.
Put the next conversation to work.
Explore Alactic Communications for WhatsApp conversations, campaigns and AI-assisted workflows. Choose the product and plan that fit your team.
Explore Communications