Stop Informal Additions From Becoming Unpriced Proposal Commitments
Prepared with AI assistance by Alactic Editorial. Examples identified as hypothetical are illustrative, not customer results.
A buyer asks for one more report on a call, a second workshop in a message and a different export format while reviewing the proposal. Each request sounds manageable. By the next revision, the buyer may believe all three are included, while the seller is still pricing the original work.
To track extra customer requests during proposal negotiation, keep a separate additions ledger linked to the current priced proposal. Record each request, assess its effect alongside the others, and give it an explicit decision: include it, trade it for something already offered, price it separately or decline it. Keep unresolved requests visibly pending rather than silently carrying them into the next version.
The ledger is not a transcript archive. It is a decision record for changes to an offer that is still being negotiated. Its most important job is to separate we discussed this from we have authorised and included this.
1. Establish the baseline before recording the extras
An addition only makes sense relative to a defined offer. Start the ledger with the proposal version under discussion, its deliverables, assumptions, exclusions and commercial basis. If the baseline is vague, the ledger will become a dispute about what was already included.
For example, a request for an additional report is not necessarily extra if the proposal already promises an unspecified set of reports. Resolve that ambiguity first: identify which reports the price covers, then assess the requested change against that list.
For each negotiation, record:
- Baseline reference: the proposal version and issue date.
- Included scope: the deliverables and quantities relevant to likely changes.
- Effort basis: an internal estimate, if you use one, with its assumptions.
- Decision authority: who can absorb effort, approve a substitution or revise the price.
- Revision owner: who checks that ledger decisions appear correctly in the next offer.
Internal effort estimates need not become buyer-facing pricing formulas. They provide a consistent way to compare requests. A small addition can still affect a deadline, require specialist availability or create a dependency that hours alone do not explain.
2. Capture the requested outcome, not just the buyer’s phrase
A note that says “add dashboard” is too loose to estimate or approve. Record what the buyer wants to achieve, the proposed output and the boundaries that remain uncertain.
Use a short ledger entry with a request ID, source, request description, estimate, dependencies, cumulative impact, decision and buyer-facing wording. Add an owner and a decision date when the request needs investigation.
The source should identify where the request came from without copying an entire conversation. A call date and participant, or a message date and sender, is usually enough to locate the relevant exchange. Capture only the detail needed to understand and resolve the addition.
Do not treat every request as extra chargeable work. First classify it:
- Clarification: explains an existing deliverable without changing it.
- Correction: fixes an omission or inconsistency in the seller’s proposal.
- Proposed addition: changes a quantity, output, dependency or responsibility.
- Unclear: needs a specific answer before anyone can estimate it.
If an estimate depends on an unanswered question, mark it provisional. A precise-looking number can create false confidence when the real uncertainty is whether the buyer wants one output or several.
3. Filled hypothetical additions ledger
Fictional worked example: All requests, figures, roles and wording below are hypothetical. They illustrate a recommended operating method, not customer results or product functionality.
A supplier is negotiating a reporting project. Proposal V2 includes one dashboard, one monthly export format, one remote workshop and a presentation walkthrough. Its internal effort estimate is 80 hours. The commercial owner has set a hypothetical discretionary allowance of up to four additional hours, subject to review; this is not an entitlement offered to the buyer.
The following requests arrive before V3 is issued. Running totals show gross requested effort before substitutions or decisions, so rejected and pending ideas remain visible without being mistaken for approved work.
A01 — Add an explanatory notes page
- Request source: Buyer project lead, negotiation call on 6 May.
- Requested output: One page explaining the dashboard’s existing measures; no new calculations.
- Estimated effort: 2 hours.
- Cumulative impact: 2 gross additional hours requested; no new external dependency identified.
- Decision: Include at the existing price. Commercial owner approves absorbing 2 hours.
- Buyer-facing wording: “V3 will include one explanatory notes page for the measures already listed, at the existing price. This does not add new measures.”
A02 — Add a second remote workshop
- Request source: Buyer operations manager, email on 7 May.
- Requested output: A second workshop, including preparation and follow-up.
- Estimated effort: 6 hours.
- Cumulative impact: 8 gross additional hours requested. If simply added, this would exceed the discretionary allowance.
- Decision: Trade. Replace the originally included presentation walkthrough, also estimated at 6 hours. Buyer confirms the substitution before V3 is issued.
- Buyer-facing wording: “V3 replaces the presentation walkthrough with a second remote workshop. The price is unchanged; both activities are not included.”
A03 — Add a second export format
- Request source: Buyer analyst, message on 8 May.
- Requested output: One additional export layout using the same agreed fields.
- Estimated effort: 4 hours, assuming no additional fields or destination system work.
- Cumulative impact: 12 gross additional hours requested. Together with A01, retained net additions would be 6 hours after the A02 substitution.
- Decision: Price separately. Include as an unselected option in V3, not in the base scope or base total.
- Buyer-facing wording: “V3 lists the second export layout as a separately priced option. It is excluded from the base offer unless selected and confirmed through the agreed acceptance process.”
A04 — Add a recorded walkthrough
- Request source: Buyer sponsor, review call on 9 May.
- Requested output: A short recorded walkthrough of the agreed dashboard.
- Estimated effort: 3 hours for preparation, recording and one correction pass.
- Cumulative impact: 15 gross additional hours requested; would add another review activity.
- Decision: Decline for this offer and defer consideration. No later commitment is made.
- Buyer-facing wording: “The recorded walkthrough is not included in V3. We can assess a separate request later, but no future work or price is reserved by this discussion.”
A05 — Connect another data source
- Request source: Buyer department head, forwarded email on 9 May.
- Requested output: Bring data from a second source into the dashboard.
- Estimated effort: Provisional 8 hours; access and data quality are unverified.
- Cumulative impact: 23 gross additional hours requested, plus unresolved access and data-quality dependencies.
- Decision: Decline within the current offer. The estimate is not a priced option.
- Buyer-facing wording: “V3 covers only the original data source. The second source is excluded; the initial effort discussion was not a price or an agreement to connect it.”
A06 — Produce department-specific dashboard views
- Request source: Buyer project lead, message on 10 May.
- Requested output: Department-specific views; departments and differences remain unspecified.
- Estimated effort: Provisional 5 hours, pending a list of views and required differences.
- Cumulative impact: 28 gross additional hours requested. The total includes uncertain estimates and is not an approved workload.
- Decision: Pending clarification; excluded from V3 unless resolved before issue. Proposal owner requests the missing detail.
- Buyer-facing wording: “We have recorded the request for department-specific views. It remains under assessment and is not included in V3. Please identify the departments and differences so we can propose a decision.”
4. Read the cumulative position, not just each row
In the hypothetical ledger, gross requested effort reaches 28 hours. That figure is useful as a warning about negotiation drift, but adding it to the original estimate would misrepresent the offer. Some work replaces existing work; some is excluded; some remains uncertain.
The decision summary is more useful:
- Base V3 internal effort: 82 hours: the original 80 plus 2 absorbed hours for A01.
- Substitution: A02 adds 6 hours and removes 6 hours, leaving no estimated net effort increase.
- Separately priced option: A03 adds 4 hours only if selected, taking estimated effort to 86 hours.
- Excluded or deferred: A04 and A05 do not enter the offered workload.
- Pending and excluded: A06 remains outside the offer until clarified and decided.
The base offer uses two of the four discretionary hours. That does not mean another two hours should automatically be given away. Check the combined review burden, specialist requirements and schedule before using the remaining allowance.
Also check interactions. Two additions may both require the same preparation, reducing combined effort. Alternatively, a new output may need another review cycle that neither individual estimate captured. Record the reason for any adjustment rather than quietly changing the total.
5. Give each decision a boundary the buyer can understand
“Include” should specify what is included and whether the price changes. “Trade” should name both the added item and the removed item. “Price” should distinguish a selectable option from the base offer. “Decline” should say what is excluded without implying that it has been promised for later.
A pending status is a temporary control, not a fifth commercial outcome. Give it an owner and a condition for resolution. If the proposal must go out before that condition is met, explicitly exclude the unresolved request from that version.
A useful acknowledgement before a decision is:
“I have recorded the additional request. We will assess it against the current scope, price and timing before revising the offer. It is not included in the current proposal.”
This is clearer than an enthusiastic “no problem” followed by an internal note saying “needs pricing.” Buyer-facing wording and the internal decision record should not tell different stories.
Keep seller approval separate from buyer agreement. A commercial owner may authorise a substitution, but the buyer still needs to understand that something is being removed. Likewise, permission to quote an option does not mean the buyer has selected it.
6. Reconcile the ledger before issuing the next version
The ledger is useful only if the proposal reflects its decisions. Before issue, the revision owner should complete a short reconciliation:
- Match every included addition to a specific scope statement.
- Remove deliverables replaced through agreed trades, including mentions elsewhere in the offer.
- Keep optional items separate from the base scope and total.
- State relevant exclusions where earlier discussions could have created a different expectation.
- Recheck assumptions, timing and price together, not as independent edits.
- Confirm that pending requests have not slipped into descriptive text or summaries.
Send a concise revision summary with the offer. For the hypothetical example, it would identify the added notes page, the workshop substitution, the optional export layout and the requests not included. The buyer should not have to reconstruct these changes from scattered messages.
Any later request starts a new ledger entry against the latest issued baseline. Preserve earlier decisions rather than overwriting them; otherwise a previously declined idea can reappear as though it were never assessed.
7. Recover when an informal promise has already been made
If someone has already said an addition is included, do not quietly relabel it as pending. Record the wording, identify who said it and raise the mismatch with the person responsible for the offer.
Then explain the correction to the buyer before issuing another version. A useful recovery acknowledges the ambiguity and presents choices:
“Our earlier response suggested the additional workshop would be included alongside the walkthrough. We had not assessed the combined scope. We can offer the workshop as a replacement at the current price, or price both activities together. Please confirm which version you want us to prepare.”
The commercial owner may instead decide to honour the earlier statement and absorb the work. If so, record that as an explicit exception with its effort and scope boundaries. Do not hide it by reducing the estimate to make the original price appear adequate.
If the buyer says a request was already covered, return to the baseline wording. The right response may be to clarify the original offer, not to charge for an addition. A ledger should expose uncertainty, not automatically resolve every disagreement in the seller’s favour.
8. Run one negotiation through the ledger tomorrow
Choose one live proposal and review the requests made since its latest issued version. Create one entry per distinct change, identify the source and mark each as clarification, correction, addition or unclear. Then assign every addition a decision owner.
Before the next revision, measure three things: how many proposed additions have a decision, how much estimated effort is being absorbed or separately priced, and how many unresolved items remain excluded. Check that every approved trade names the deliverable being removed.
The immediate target is observable: every known request is either reflected accurately in the revised offer or explicitly kept outside it. That is a stronger negotiating position than relying on everyone to remember which friendly conversation became a commitment.
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