You don't. Don't ever convince anyone of how well your solution fits anything. First... always understand what are their business needs, quantify that need, determine if that need is worth solving, if the need is worth solving today, if the need is a top 3 priority to customer, and jointly with the customers work out the positive business outcomes they require, and then prove how you can meet those positive business outcomes.

First try and understand the customer situation as elaborately as one can. Listen more. Co-relate the technical solution to customer scenarios Offer demos Make customer practice themselves Sale is certain

Embrace the skepticism. Feed it. Agree with them. Ask them what else they’re skeptical about. Build the worst possible outcome with them. Find out what fuels their skepticism: Have they been burned before? How have they tried to solve their problems before? What went wrong? What happened because of that? Then invite them to imagine the best case scenario: what would be true, how would it be measured, what would the impact of a best case scenario look like. Then find a way to bridge the gap between how it has been and how it could be. Unless they’re right, and your solution isn’t a good fit. If that’s the case, get feedback on why, and if possible, recommend an alternative solution.

It'll be a logical practice to focus on pitching "F.A.B" methodology to convince clients. "F"eatures: - The technical specifications your solution is going to bring onboard to a particular pain area of a client. "A"dvantages: - The USPs of your proposed solution which addresses the pain areas of the client. "B"enefits: - The value which the client derives from your proposed solution. It's a meticulous approach which transforms a sales pitch to a solution centric consultative pitch.