Negotiation Strategy and Tactics Questions

Direct answer

The best low-cost, high-perceived-value concessions are things that cost me little to deliver but that the other side genuinely values: flexibility on timing, extra visibility, small amounts of expert time, access, and recognition. I make sure each is traded by attaching it to an explicit condition ("if you can sign by the 30th, I can include...") and by never offering it unprompted. A concession given without a get teaches the other side that asking works.

The ranking logic: value per unit of cost

A concession is anything I give up or add. Perceived value is what the buyer thinks it is worth, which may differ from my cost. I want a high ratio of their perceived value to my real cost (for example, a give that costs me $300 and is worth $3,000 to them is a 10x ratio, while a 5% discount on a $100,000 deal costs me $5,000 and is worth $5,000 to them, a 1x ratio), and I also want to protect gross margin (revenue minus the direct cost of delivering, as a share of revenue). Discounts hit margin directly; the items below mostly do not.

Ranking worked example (assumed numbers): the architecture workshop costs me about 4 hours at $150 = $600 and the buyer would otherwise pay roughly $5,000 for outside consulting, so the ratio is about 8x. The executive call costs one hour at $300 = $300 and is worth about $3,000 to their internal case, 10x. Flexible billing on a $50,000 invoice delayed 60 days costs me about 50,000 x 8% x 60/365 = $660 of financing, and may be worth far more to a buyer stuck in a budget cycle. I rank the gives by that ratio, offer the highest first, and keep the discount, at 1x, for last.

How I keep each one traded

1. Know my list before I walk in. I write each give, its cost to me and the get I want, so I am never inventing a trade under pressure.
2. Say "if... then" every time. "If we can lock the end date this week, then I can include the architecture workshop." The sentence structure is the control.
3. Trade small for small, and step down. Large asks get large conditions; I never give the last concession for free.
4. Hold gives in reserve. I introduce them one at a time, so I always have something to move with.
5. Keep a ledger. After each call I note what was given and received, which stops quiet drift into free gives. A ledger row looks like: "12 Mar | gave: 2-week pilot extension (cost about 10 engineer hours) | got: written success criteria signed by their VP | open: reference call still owed."

Applying it: a price-sensitive partner on a 90-day plan

A common variation of this situation is a reseller or integration partner who pushes hard on price when my pricing is fixed. A partner here is another company that resells or builds on my product. In that case I cannot cut price, so I pitch a bundle of gives that cost me time, not margin. Example pitch: "I cannot move the price, but I can offer a joint onboarding plan with a named engineer for the first 90 days, a quarterly business review (QBR, a scheduled meeting where we review results and plans), and a co-branded case study (a customer story published under both our names), in return for a 12-month commitment." Resources I need: roughly one engineer-day per week for 90 days and a manager hour per month. Success in 90 days, measured: onboarding finished by day 30, partner live in production by day 60, and one referenceable outcome (a result they allow me to quote publicly) by day 90 (for instance a measured reduction in their ticket volume). All of it is conditional: if the 30-day milestone slips because of the partner, the later gives pause.

Trade-offs and pitfalls

• Low cost to me is not zero cost. If three customers each get an engineer, my capacity is gone. I cap each give (hours, duration) in the offer.
• A give with no deadline becomes an entitlement. I time-box every one.
• If the counterparty values something I mis-estimated, I check with a question ("which of these would matter most to your team?") rather than guessing.
• What would change the list: for a deal where the buyer is really negotiating on price, non-price gives will not satisfy them, and I need to talk about scope or terms instead.

Direct answer

I would not claim compliance I do not have, and I would not simply say "months". I would find the real risk behind the requirement, show what my architecture does cover, and negotiate a package that lets the customer go live safely sooner: a gap analysis (a side-by-side check of what I meet against what they require) mapped to their controls, compensating controls and independent evidence for the gap, a phased go-live that keeps the regulated workload (the part that handles data the rules cover) out of scope until the control exists, and a dated, contractually backed roadmap. The one thing I hold firm on is honesty about the gap; I will trade timing, scope and assurance, not the truth.

Step 1: understand the requirement, not just the label

I ask for the exact control text, the standard it comes from (for example a security certification or a data-protection regulation), and who in the customer organisation owns the risk. Often the buyer's procurement checklist is stricter than what their own risk team needs for this workload. I confirm what risk the requirement is meant to cover (data leaving a region, unauthorised access, vendor failure) so my alternatives can address that risk.

Step 2: map what is covered

I make a table of the requirement's sub-controls (the individual checks inside the requirement) against my architecture: fully met, partly met, not met, with evidence for each. The rows below are illustrative; in practice I take them from the numbered controls in the customer's own standard or questionnaire, which is why I ask for the exact text in step 1.

Step 3: offer alternatives that address the underlying risk

• Compensating controls: an interim control that reduces the same risk (for example excluding the affected data from the analytics workload, or tokenising it, which means replacing real values with meaningless stand-ins).
• Independent assurance: a third-party attestation (a signed independent statement that a control works) or penetration test (an authorised simulated attack), or a customer audit right, so they are not relying on my word.
• Contractual protection: a warranty on the stated controls, a remedy if the date is missed, and notification duties.
• Narrower alternatives for escrow or similar demands: security reviews often arrive with continuity demands attached to the compliance gate, and escrow is the common one. If the demand is escrow (a neutral third party holds code or data so the customer can continue if I fail), I examine the risk it covers. If the real concern is continuity, I can offer a narrower escrow of deployment artefacts, a financial-health attestation and a step-in plan (a pre-agreed way for the customer or a named third party to take over running the service if I fail) instead of full source escrow.
• Phased go-live: start with workloads that do not need the control; regulated data follows when it exists.

Worked example (illustrative figures)

Deal: 600,000 USD annual recurring revenue (ARR, the yearly subscription value). The unsupported control affects workloads representing 60 percent of the value, and delivering it takes 6 months (about 5 months of re-architecture, the figure I give the customer, plus about 1 month for the independent attestation before phase 2 can start). Proposal: phase 1 (the other 40 percent, 240,000 USD a year) starts in month 1; phase 2 (360,000 USD a year) starts when the control is delivered and independently attested, with a dated roadmap in the contract and a right for the customer to cancel phase 2 without penalty if the date slips more than 90 days. Year-one revenue: 240,000 + 360,000 x 6/12 = 420,000 USD, instead of zero if the customer walks, and the customer is protected by dates and a cancellation right. The result depends most on whether the customer really can split the workload; I test that early.

Holding the lines that matter

A security review rarely stops at one requirement, so other demands arrive in the same conversation, and I have three lines I hold. I will not remove a mandatory control to hit a price (the cost saving is smaller than the breach cost). I will not weaken a security-driven architecture to meet a date. And if the customer asks for data that privacy law restricts, for example every record about named individuals in response to a request, I separate what the law allows from what they would like. The same honesty applies to capacity: if the customer wants guaranteed capacity for a seasonal peak, I commit to what I can provision and show the scaling plan rather than promise capacity I cannot deliver. These are the non-negotiables; timing, scope, phasing and evidence are my currency.

Trade-offs and pitfalls

• Overpromising a date to close the deal: a missed compliance date is a breach, not a delay.
• Offering a workaround the customer's auditors will not accept: I check with their risk team before I rely on it.
• Treating the customer as the enemy: their security team is usually an ally if I help them document the risk acceptance (their formal, signed decision to live with a stated remaining risk).

What I say to the customer's security team

"I want to be straightforward: we meet the encryption and access controls today, we meet customer-controlled keys for storage but not yet for backups, and regional residency for analytics needs about five months of work. I will not tell you we are compliant when we are not. What I can offer is to put your regulated data in phase 2 behind that control, run the rest from month one, give you an independent attestation when it is built, and put the delivery date in the contract with your right to cancel phase 2 if it slips more than 90 days. If your risk team needs something else to accept the interim, tell me what and I will cost it."
If the customer will accept no gap at all and no phase, I walk away and say so respectfully.

Direct answer

I would not say yes or no to the concession as asked. I would separate the customer's underlying need from the specific ask, then offer something that meets the need through a rule that any similar customer could also qualify for, in exchange for something I can name. If the ask can only be met by a one-off the rest of the book would resent or copy, I decline that form politely and say what I can do instead. Precedent is the cost I am pricing, not just the dollars in this one deal.

Why precedent is the real cost

A concession has a direct cost (the discount, the free work) and an indirect cost: other customers learn about it (through shared partners, user groups, procurement networks, or a renewal comparison), and your sales team learns that pushing hard works. Terms of art used here: a concession is anything you give up to move a deal; a walk-away point is the worst deal you would still accept; anchoring is the first number on the table that frames the rest. The book is your whole set of customers. A reference customer agrees to speak to prospects or be named publicly. Strategic logo deals are discounted deals with prestigious names that help win others. A price-hold is a promise not to raise the price for a set period. A volume tier is a price band that drops as commitment grows.

Steps, with the words I would use

Before the call I fix my walk-away point (here, nothing below the 12% tier). The customer's 25% is an anchor, a first number meant to frame the talk, so I re-anchor on my tier prices rather than argue from 25%.

1. Ask what the concession is for. "Help me understand what the 25% gets you. Is it a budget ceiling, a comparison with a competitor quote, or an internal approval hurdle?" Many asks are really a budget-cycle problem, which can be solved with payment timing rather than price.
2. Test fairness against a written rule, not a feeling. Does the ask match an existing, published category (volume tier, multi-year commitment, reference customer, early adopter, meaning a customer who adopts a new product early and gives feedback)? If yes, grant it as that category, so it is repeatable and defensible. If no, it is a one-off.
3. Trade, never give. "I cannot move the unit price, because we hold one price per tier for every customer. What I can do is move you to the next tier if you commit to three years, which is a rule others can also earn." A concession with nothing asked in return teaches the counterparty that asking is free.
4. Offer something that is cheap for you and valuable for them, and is not price. Extended payment terms, a longer price-hold, a named support contact, or an additional training session. These rarely set a visible price precedent.
5. If they insist on the one-off, quantify it and escalate: "To do that I need approval from our pricing owner, and the question they will ask is whether we are willing to offer it to every customer in your situation. Are you comfortable with the commitment that would justify?"
6. Document the reason and the trade in the deal record (the entry in the CRM, the sales team's customer-tracking system) so the exception is traceable and can be reviewed rather than becoming folklore.

Worked example (illustrative numbers)

Illustrative tier table (list price $100,000):

A customer on a 2-year renewal at $100,000 per year (a renewal comparison: the customer is comparing the renewal price with what they think others pay) asks for 25% off because "another customer got that." Rather than refusing outright I would say: "I cannot discuss other customers, and I would not discuss yours either. Our list holds at tier prices. If you extend to a 3-year term and agree to be a reference, I can place you in our top tier, which is 12% lower." The cost of 12% is $12,000 per year, repeatable under a rule. A one-off 25% would cost $25,000 per year and, if three comparable customers learned of it and asked, would put up to $75,000 per year of price at risk (an exposure estimate, using the 3 as an assumption, not a measured count).

Internal version (Product Manager or Technical Product Manager mediating)

When sales wants the discount and product worries about precedent, I would not pick a side. I would ask sales for the deal facts (competitor, deal size, how likely the loss is without it) and ask product what exactly the precedent would break (a list price, a feature-gating rule, a packaging boundary). Then I would propose a time-boxed, criteria-based exception policy (for example, "strategic logo deals over a stated size, approved by a named pricing owner, the person accountable for price policy, reviewed quarterly") so the exception is a rule with an owner rather than a negotiated favour each time.

Trade-offs and pitfalls

• Refusing everything wins the principle and can lose the deal. Granting everything wins the deal and erodes the book. The skill is converting a one-off into a rule or a trade.
• Do not claim a "company policy" that does not exist. A bluff is discovered at the first renewal and costs trust.
• Do not disclose other customers' terms. Say you hold the same terms for every customer in the same position.
• What would change my call: a strategic account whose loss costs more than the precedent (for example, a flagship reference), with executive sign-off and a written reason.

Direct answer

I would run a structured review that separates what happened from my interpretation of it, using the counterparty's own words and actions as evidence, and then change specific habits in how I listen and question. In many cultures where direct disagreement is rare (often called high-context communication, where meaning is carried by context and relationship more than by explicit words), a polite phrase like "we will consider it" or "this may be difficult" can mean a firm no, and silence or a change of subject can mean disagreement. My failure, most likely, was reading politeness as agreement. I would also avoid replacing one stereotype with another, and treat culture as a hypothesis to test with the specific people involved.

How I would review it

1. Reconstruct the timeline from notes, emails and calendar entries: each of my claims and each of their responses, in order.
2. Mark every signal I treated as agreement ("yes", nodding, "we will study it", "interesting") and list the evidence for each reading. Ask: was there ever a specific commitment (a date, a named person, a number, a next step)? Where was there none?
3. Mark every signal I missed: delayed replies, a new person joining at a late stage, a change of topic when price came up, a request to "send more material" without a decision date, a decision-maker who never spoke.
4. Check the structure, not only the conversation: were decisions made by consensus in a group or by a senior person not in the meeting? Did the meeting format (large group, hierarchy, a translator) prevent open disagreement?
5. Get outside perspective: ask a colleague from that region, a local partner or an interpreter to read the transcript and tell me what they would have heard. Ask the counterparty, through a trusted intermediary, for feedback if the relationship allows.
6. Write down the root causes (for example, I assumed yes meant commitment; I asked only yes-or-no questions in a group setting; I pressed for a decision in the room).

What I would change in how I listen and question

Worked example (illustrative)

In a meeting I proposed a 90-day pilot and the regional director said "this is a very interesting proposal, we will study it carefully." I recorded this as positive. Two weeks later the response was a request for 12 more pages of material and no date. In the review I see that there was no owner, no date, and no budget conversation, and the person who spoke was not the one who signs. Next time I would ask afterwards: "Who else would need to see this, and what would they want to know first?" and then offer to meet that person with the director's introduction.

Pitfalls

Do not conclude "they are indirect" as a general rule: individuals vary, and company culture, seniority and age differ within one country. Do not blame the counterparty either. The disciplined conclusion is about my process: I relied on one reading of ambiguous evidence. I would share the lessons with the team, and add a rule to the deal plan that every pilot or next step needs an owner and a date on both sides.

Direct answer

I slow the clock down without refusing to engage. Hardball tactics (a sudden deadline, a "final offer", a demand to decide now) work because they push me to decide before I have checked anything. My response is calm, specific and process-based: acknowledge, test whether the deadline is real, buy time to consult, and keep the conversation on interests and options. I never concede under a clock that I cannot verify, and I stay willing to walk away, because a counterparty who knows I will not, controls the outcome.

What each tactic is, and the live response

A deadline tactic creates urgency. A staged final offer ("this is my final offer", then another one later) is a bluff to test your reaction. An immediate-decision demand removes your chance to consult. Key idea from Getting to Yes (Fisher and Ury): your BATNA (best alternative to a negotiated agreement) is what you do if no deal happens. Knowing mine before the meeting is what lets me stay calm. My walk-away point (also called the floor) is the worst deal I would still sign; it is set by my BATNA, because I should refuse anything worse than what I can get elsewhere. A term sheet is a short non-binding summary of the main deal terms, and a board slot is a place on the other side's board meeting agenda where they plan to approve the deal.

Buying responsible time, concretely

When a late-stage concession is demanded on the spot, I use a break rather than a refusal. Options: a five-minute pause ("let me step out and check with my finance lead"), a stated process ("anything touching price needs sign-off, which I can get by end of day"), or a conditional ("if you can confirm the term and volume, I can recommend it internally"). This is honest: I really do consult, so I am not bluffing.

Real-time sequence

1. Name it neutrally. "It sounds like timing is important to you."
2. Probe the reason. The reason reveals whether the deadline is real and what they actually need.
3. Offer a path that respects the need. For example: "If the need is a signed term sheet by Friday, I can deliver a draft Thursday that leaves price open."
4. Check my own position. What is my BATNA, and what is the cost of missing their date? If the cost is small, the deadline has little power.
5. If they escalate, restate and hold. "I would like this deal. I cannot decide on the terms as presented today. Here is when I can."
6. Decide whether to walk. Only if the final terms fall below my pre-set walk-away point (the worst deal I would still sign, decided before the meeting, not under pressure).

Worked example

Partner says: "Our final price is $240,000 per year, sign today or the board slot goes." I prepared my numbers beforehand (all assumed for illustration). Delivering the full scope costs me $200,000 per year, so my margin is price minus $200,000. My BATNA is another partner who would pay $250,000 per year for the full scope, a margin of $50,000. So my walk-away is a margin of $50,000 per year, and the target is $280,000 (a margin of $80,000).

Check the offer: $240,000 for the full scope is a margin of $40,000, below my $50,000 walk-away, so I cannot accept it as stated. Reduced scope (two integrations deferred) would cost me $185,000 to deliver. I say: "I would like to reach agreement. At $240,000 we cannot deliver the full scope. Can you show me what has to stay the same on the board timeline? We might fit a reduced scope at $240,000 or the full scope at $265,000, and I can send either by noon tomorrow."

Check both options on margin, the unit my walk-away uses: reduced scope is $240,000 - $185,000 = $55,000, and full scope is $265,000 - $200,000 = $65,000. Both are above my $50,000 walk-away, even though $240,000 is a lower price than $250,000, because the scope is smaller and costs less to deliver. This converts the deadline into a choice between two options that each beat my BATNA. If they refuse both and the deal stays at $240,000 for full scope, I stop, since $40,000 is worse than the $50,000 I can get elsewhere.

Trade-offs and pitfalls

• Matching their aggression raises the temperature and ends the collaboration.
• Calling every deadline a bluff is a mistake; some are real, and missing them loses the deal. I test, not assume.
• Giving a "little" to get the pressure off teaches them that pressure works.
• What would change my call: a real deadline with high cost to me and a good price. Then I accept the date, and negotiate hard on the structure inside it.