Provide Data and Evidence Use Metrics: Whenever possible, support your solution with hard data, metrics, and benchmarks. Showing tangible benefits (like ROI, performance improvements, etc.) will help the client see the real-world value. Prototypes or Demos: Offer a live demonstration, prototype, or pilot project that allows the client to see the solution in action. This lowers perceived risk and gives them a clear sense of how the technology will function.

First thing --> try to understand why he is skeptical. This is the only way to argument and explain the right things. You need to know the deep why... in order to go deeper, ask various questions and try to find incoherences and find the right objections. Once you have understand why your client is skeptical you can argument, and build reinsurance

Earning a skeptical client's trust requires empathy, expertise, and proof. First, I actively listen to their concerns to ensure they feel heard. Next, I show how the solution addresses their specific pain points, emphasizing it's tailored to their needs. To build confidence, I present clear evidence like case studies and data. Transparency is key, so I provide clarity on costs, risks, and timelines. If needed, I propose a small pilot project to prove value without heavy commitment. Building trust is about creating partnerships, aligning goals, and delivering results that speak for themselves.

Skeptical about what? The solution, you, your company, or the probability it can be funded, deployed, and adopted. Maybe it is skepticism about 'it' getting past the due diligence of the cast of characters that must buy-in. What do we know about the skeptic? What is their decision process? There are many sources of skepticism. On a positive note, an expression of skepticism is an expression of interest. So many missing elements...

First, understanding their concerns: have a good conversation, ask relevant questions to confirm the pain points and make sure you listen actively and take notes as you might not have all answers with you at that point. Second, addressing their concerns with relevant arguments, preferably using best practises cases from other project/customers who when through that process before and are relevant to the case. A good demo, going through the customer painpoints so the customer can see how their concerns are addressed will always help. A pre-production pilot trial where possible, even at a cost, before final implementation, adds an additional control point for the customer team in charge and can make team feel really good.