The technique when you’re selling software, and you don’t have the program even built, is usually you’ll go to somewhere like LinkedIn, and you’ll look for people who are very specifically targeted for the use case. Or Facebook, if it’s that kind of place, but often there’s a commercial application for it. And then you would contact people after sort of connecting with them and interacting with them a little bit first. You’d contact them and say, Hey, you look like you’re quite established in this field. I could see your achievements there. So using some sort of flattery.
And then you’d say, I would love to just ask you a couple of questions about some software program that I’m developing, because I would value your opinion. Clearly, your feedback would be extremely useful. So then they tell them what the thing is. And then they get the feedback. And then they say, by the way, is this something you’d be interested in? That’s kind of like the Inspector Clouseau add-on. And often the person will say yes or no.
And if they say, No, just, Tell me why that is. What would stop you from going ahead with this sort of software? And you’d get all the objections out. If it’s yes, then they might actually buy it or preorder it and then you go and develop it. So that’s the common sort of software outreach, pitch method, that validate software that then they go and develop.
See our products here
who is the persona? what is the customer journey inside the company? what’s the price and how many decision-makers? selling a product once to a person is not a statistically significant result, nor a result showing the viability of the product. especially if that’s an inexpensive product for a one-man show business
All of those things would be ideal to research and know.
I agree – one is not statistically valid. You would be wise to set a target of committed buyers much higher than one before committing to a draft version.