If I'm in someone's business (even as a retail customer), I often ask to watch as they enter data into their customer facing system. This invariably leads to some discussion and who knows what else. I attend events and network regularly, even if it's just staying in touch with acquaintances and asking what others are up to. Email works really well for this.
I don't have a solution in mind because I want to listen to the other's problems first. If something I have written (generally small business or e-commerce) sounds close to what can help them, I may go down that path. Anything else, I pass, but gladly provide a referral to someone who can help, if I know of any.
I don't cold call in the pure sense. That's just not my nature. If I ever got good at that, then I wouldn't need to be a programmer, I'd just sell someone else's product.
I found an old semi-related post of mine that may also be helpful:
When you're writing tools for less technical groups, and taking the effort to make them highly usable by those who are less technically savvy the odds of running into similar problems are lower.
1. "Scratch an itch."
2. "Find a customer."
#1 comes naturally to a hacker. I'm always building things for myself. Then I think, "If I need it, someone else probably does, too."
#2 does not come naturally at all. I have to work at it. Frankly, I'd rather build stuff than talk to people (although that has changed quite a bit over the years).
FWIW, I have found very little success with #1 (one big exception: a program generator I wrote for myself was very well received by others).
#2 has worked beautifully. Every time I have ever found and satisfied a first customer, the second, third, fourth, etc. were much easier to find and satisfy because they needed the same thing. What great advice. I wish I had listened much earlier.