You can be correct, but on different axis.

You can be correct that your method makes code more DRY, and miss the point that the other person believes that things are going to diverge significantly over time and doesn’t value DRY.

You can be correct that your method is more resilient to failure, and miss that the other person believes that some level of failure is OK and wants an option that is less technically complex.

I’ve seen people get upset that they were correct and yet the room shifted against them. Most times, it seems like they are correct. But they are correct on a narrow axis, that misses the motivations of the other people in the room.

This is part of the reason high level account reps focus on the mix and viewpoints of people in the room over technical specs. Get the lay of the land first, and then you can tailor your pitch to be correct in the way that the audience will be receptive to.