Turn Conflicting Buyer Requests Into One Quotable Brief
Prepared with AI assistance by Alactic Editorial. Examples identified as hypothetical are illustrative, not customer results.
Operations wants an onsite launch. Procurement asks you to remove travel. The project sponsor wants the original deadline, while the delivery team adds another review stage. Each request sounds reasonable alone; together, they describe work you cannot confidently price.
To resolve conflicting customer requirements before quoting, create one consolidated brief that records the competing requests, explains their pricing consequences, names the buyer’s decision owner, and captures an explicit resolution. Price the confirmed scope, not your guess about whose message matters most. Where a decision remains open, separate that work from the firm quote rather than hiding uncertainty inside a contingency.
The brief should preserve disagreement without turning it into a dispute about people. Its job is to make the buyer’s choices visible enough to confirm.
1. Separate a genuine conflict from an incomplete requirement
Not every difference between stakeholder messages needs escalation. First distinguish between requests that can coexist, missing details, and instructions that cannot both govern the same deliverable.
- Compatible requests: One stakeholder asks for a facilitator guide; another asks for participant exercises. Both may fit, subject to scope and price.
- Incomplete requests: A stakeholder requests training but does not specify audience size. Ask for the missing input.
- Conflicting requests: One stakeholder requires an onsite session, while another requires a remote-only delivery price. A choice or an explicitly priced alternative is needed.
Look beyond direct contradictions. A new approval step can conflict with a fixed completion date. An expanded audience can conflict with a single-session format. A request to include editable working files can conflict with an earlier scope limited to finished outputs.
For each suspected conflict, write one neutral sentence: both requests cannot be included in the same baseline because they change the delivery method, quantity, timing, or acceptance condition. If you cannot identify that consequence, you may need clarification rather than a decision.
2. Build a brief that keeps the original requests visible
Do not replace the incoming messages with a polished scope document too early. That removes the evidence of what changed and makes your interpretation look like an instruction from the buyer.
Start with a short brief header: proposal name, version, intended delivery outcome, buyer decision owner, and current status. Below it, maintain a reconciliation table. Each row should contain:
- Requests and sources: Who requested what, through which message or meeting, and when.
- Conflict: The specific reason those instructions cannot jointly define the baseline.
- Pricing consequence: What changes in effort, expenses, quantity, sequencing, or uncertainty.
- Decision owner: The buyer role or named person authorised to settle that issue.
- Resolution and confirmation: The selected scope, excluded work, and evidence of confirmation.
Paraphrase requests accurately and retain a reference to the original correspondence in your working records. Keep the distinction between a stakeholder’s request and the buyer’s confirmed decision. A recommendation from the seller belongs in a separate note until the buyer accepts it.
Use explicit statuses such as awaiting clarification, awaiting buyer decision, confirmed for pricing, and reopened. Avoid a vague status such as reviewed: it does not tell the estimator whether the row is settled.
3. Name the buyer’s decision owner before asking for a compromise
The person who sends the most messages is not necessarily the person authorised to resolve scope. Nor does involvement in purchasing automatically establish authority over delivery requirements.
Ask the buyer to identify who can confirm the proposal baseline and whether any decisions require another person’s agreement. Keep the question narrow: you are establishing authority for this proposal, not redesigning the buyer’s organisation.
Who should confirm the final scope for this proposal? Please also flag any decisions that require another stakeholder’s agreement, such as delivery format, expenditure, or acceptance criteria.
A single coordinating owner is useful, but do not pretend that person can overrule every specialist. If the buyer says a particular issue needs joint agreement, record both approvers and leave the issue open until that agreement is clear.
If nobody will take ownership, explain the practical limit: you can provide clearly labelled alternatives or an indicative estimate, but you cannot treat disputed work as an agreed fixed-price baseline. That is more useful than repeatedly asking everyone to align without stating what decision is missing.
4. Worked example: a filled requirements reconciliation table
Fictional worked example: A seller is preparing a proposal for a customer-service training project. All people, requests, quantities, timings, and confirmations below are hypothetical. They are not customer results or product capabilities.
The buyer names Maya, the project sponsor, as the coordinating decision owner. Procurement must also agree to expense treatment. The seller prepares the following plain-text table; each numbered record is one row, with the same six fields repeated for readability.
REQUIREMENTS RECONCILIATION TABLE
Proposal: Service-team training | Brief version: B
Status: Confirmed for pricing after the hypothetical review
ROW 1 — DELIVERY FORMAT
Request: Onsite workshop; remote-only delivery without travel.
Source: Lena, Operations, kickoff notes; Arun, Procurement,
follow-up email.
Conflict: The same workshop cannot be both onsite and remote-only.
Pricing consequence: Onsite delivery changes travel expenses and
facilitator time; remote delivery removes travel.
Decision owner: Maya, with Arun confirming expense treatment.
Confirmed resolution: One remote workshop is the baseline.
Onsite delivery is excluded, not an allowance.
Maya confirmed in the version-B email reply;
Arun confirmed no travel provision is needed.
ROW 2 — AUDIENCE AND SESSION COUNT
Request: Train all 60 participants; keep one workshop designed
for a maximum of 20 participants.
Source: Lena, Operations, audience list; initial project scope
agreed with Maya at kickoff.
Conflict: All 60 cannot attend within the proposed 20-person format
in a single workshop.
Pricing consequence: Three deliveries require more facilitator time
than the original single-session scope.
Decision owner: Maya, after checking the audience with Lena.
Confirmed resolution: Three remote workshops, up to 20 participants
each, using the same core materials.
Additional sessions excluded.
Maya confirmed in the version-B email reply.
ROW 3 — REVIEW ROUNDS AND COMPLETION
Request: Complete within four weeks of kickoff; add three sequential
content-review rounds before scheduling delivery.
Source: Maya, kickoff notes; Elena, Quality, review-plan email.
Conflict: The proposed sequence no longer supports the original
four-week delivery plan.
Pricing consequence: Extra review work and a longer schedule would
require a revised estimate.
Decision owner: Maya, with Elena agreeing to the review arrangement.
Confirmed resolution: One consolidated content-review round.
Buyer feedback due within two working days
of receiving the draft. Four-week target assumes
that response time; late feedback triggers a
schedule review, not automatic acceleration.
Maya and Elena confirmed in the review thread.
ROW 4 — FINAL MATERIALS
Request: Participant PDF only; also provide editable facilitator
materials and an internal handover session.
Source: Original scope summary; Lena, Operations, follow-up email.
Conflict: The second request adds deliverables absent from the
original scope, rather than merely changing file format.
Pricing consequence: Editable-file preparation and handover time
add separately estimable work.
Decision owner: Maya.
Confirmed resolution: Participant PDF remains in the baseline.
Editable facilitator materials and one remote
handover session appear as a separate option.
The option is not included in the base total.
Maya confirmed in the version-B email reply.Notice what the table does not do. It does not label procurement as obstructive or operations as demanding. It also does not bury the expanded audience inside a general phrase such as training support. The quantity, delivery format, review limit, and optional work are visible enough for an estimator to use.
The resolutions also preserve consequences. Remote delivery removes onsite work; it does not silently promise a later visit. A faster review arrangement supports the target schedule only while its stated dependency holds.
5. Translate each resolution into a pricing treatment
Once the buyer decides, assign each item a pricing treatment. This prevents an otherwise clear brief from turning ambiguous again in the proposal.
- Included baseline: Confirmed work priced in the main total, with quantities and boundaries stated.
- Separate option: Defined additional work with its own price and a clear statement that it is outside the baseline.
- Excluded: Work the buyer has chosen not to include. Name important exclusions where an earlier request could otherwise create an expectation.
- Unresolved: Work that is not yet ready for a firm price. State the decision needed before it can be quoted.
For the hypothetical training proposal, the baseline includes three remote workshops and one consolidated review round. The editable materials and handover form an option. Onsite delivery is excluded. These treatments should match across the brief, price schedule, and delivery description.
Do not use an option to conceal a dependency. If the main deliverable cannot work without an item, explain that relationship rather than presenting it as freely removable. Likewise, a contingency may cover ordinary estimation uncertainty, but it should not substitute for a buyer decision between materially different scopes.
6. Send a confirmation request that can receive a meaningful answer
Ask for confirmation of a specific version, not general approval of the discussion. Include the resolved baseline, meaningful exclusions, remaining options, and the next action. Keep the detailed table attached or in the same thread so the summary has a traceable basis.
Hypothetical buyer confirmation message:
Subject: Please confirm training brief B before we price
Maya,
We have consolidated the requests from Operations, Procurement, and Quality into brief B. Before we prepare the price, please confirm that it is the basis we should use.
The baseline is three remote workshops for up to 20 participants each, using the same core materials, with participant PDFs and one consolidated content-review round.
The four-week completion target assumes buyer feedback within two working days of receiving the draft. If feedback is later, we will review the schedule rather than assume accelerated delivery.
Onsite delivery and travel are excluded. Editable facilitator materials and one remote handover session will be priced as a separate option, outside the base total.
The reconciliation table records the original requests and their resolutions. Please reply confirming brief B for pricing, or identify the row that needs changing and the required replacement. Please also confirm that you are the coordinating decision owner and that the Procurement and Quality confirmations recorded there remain valid.
We will price the confirmed baseline after your reply. If a row remains disputed, we can proceed with unaffected work only where it can be scoped independently.
A response such as proceed may be insufficient if the thread contains several versions. Ask a short follow-up linking that response to the exact brief. Silence should remain an unanswered confirmation request, not become an invented acceptance.
7. Recover when agreement breaks down
A stakeholder reopens a confirmed decision. Add the new request to the existing row, mark it reopened, and describe what it would change. Ask the decision owner whether the prior resolution still governs. Do not let the newest message silently overwrite the brief.
The buyer wants a price before deciding. Offer alternatives with visibly different scope, or a clearly labelled indicative estimate with stated assumptions. Explain which unresolved choice prevents a firm price. Avoid producing several supposedly interchangeable totals when the delivery outcomes differ.
Only part of the scope is disputed. Check dependencies before splitting the quote. You may be able to price standalone work while holding another section. If the disputed choice changes shared preparation, scheduling, or the whole delivery model, partial pricing may create more confusion than it removes.
The deadline arrives without confirmation. State what is still open and what you can responsibly provide. A quote deadline does not settle conflicting instructions. If you issue an assumption-based estimate, make its status conspicuous rather than describing it as an agreed proposal.
The buyer confirms a summary but contradicts a row. Treat the contradiction as unresolved. A broad approval and a specific correction cannot both govern the same item without clarification.
8. Use a quote-readiness check before estimating
For the next proposal with conflicting inputs, create one reconciliation brief before another estimate revision. Count the disputed rows, assign a buyer decision owner to each, and send a version-specific confirmation request.
Before pricing, check these observable conditions:
- Every known conflict has a recorded resolution or an explicit unresolved status.
- Every resolution affecting price has confirmation from the appropriate buyer decision owner.
- Every priced item matches the confirmed quantity, delivery method, review limit, and dependency.
- Every requested item outside the baseline is clearly optional, excluded, or awaiting a decision.
- The proposal references the same brief version the buyer confirmed.
Track the number of unresolved price-affecting rows, not just whether the brief was sent. The useful outcome is a scope the estimator can price without choosing between stakeholders on the buyer’s behalf.
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