Earlier quoted context omitted.
> I don’t get it - asking ‘can you reduce line item n by x’ is exactly the same thing as ‘can you reduce the bottom line by x’ "Can you reduce bottom line by x" is like saying, "the documentation is a bit vague, can you improve it please?" "Can you reduce line item n by x" is like saying, "there's no way the user could possibly intuit that the sampling period may be truncated to precisely hit the target value after t…
Just look at the total-cost-of-ownership. As long as I can afford the down payment and I can afford the monthly payment then I just want to reduce the total-cost-of-ownership for the car I want. In other words I want the dealer to optimise for that variable and as long as they meet my constraint for affording the down and monthly payments then I don't care how those vary as long as the optimisation goal is met. Line…
But you would have already told them, "As long as I can afford..." So they'll spend the entire exchange trying to optimize for the maximum amount they think you can afford. They can try to convince you they've optimized when they really haven't, and they can try to pick a vehicle of a lower quality and persuade you that the price drop is the optimization.
If your response to every trick is to respond, "No, please try again to optimize for TCO," they'll eventually interpret your behavior as the equivalent of an ad-blocker. Then they'll either persuade you to reveal more data or move on to a customer who negotiates on their terms.