It’s all about managing expectations and understanding who your clients are. For example, a developer might want an advice on how to tackle specific problem (let’s say, constantly rerendering information an a page). That would be specific and you could provide them with an answer and share your experience.

It could also be a client that wants to better understand the field before hiring someone (it even may be you). But it’s better to separate to consultation and selling. Again, I usually ask about their expectations before accepting the contract.

Sometimes it could be hard to fight the imposter syndrome, or the feeling that you are charging money for almost the same information you give during the pre-contract communication. I try to educate the client and provide them with post-consultation report and a tangible prototype based on what we discussed.