How do you find customers with problems to fix in software?
I'm a contract developer but I've long been keen to make the leap to starting a software product company, ideally B2B.
I can fund getting an initial release out, but it seems to me the best way to do so is by finding a customer with a problem and a budget who can put a price on what they'd pay for a solution. I've tried doing this without a customer and it's not gone well.
--
This seems straightforwards, but it's escaped me so far. The closest I managed was an NHS (I'm based in the UK) team my wife works in who liked a prototype, passed it up the chain to get budget approval and were told they could have the software if it was developed in-house. I approached some NHS innovation departments for help getting it to other teams, but they said they'd only work with software that other people were already using. Catch 22.
Any tips?
12 comments
[ 2.9 ms ] story [ 48.9 ms ] threadWorking as employee and cotractor for about 10 years now.
I have the feeling all business lectures focus on what to do AFTER you got this kind of thing sorted out, before you are pretty much on your own.
I will go to a trade fair next week, maybe I'll find something there...
Once you've done that, products that people will actually pay for become easier to see.
VCs like this because with enough funding and persistence, you get a sticky high margin product.
How about B2C ? What is your technical skill set ?
B2B, IMO, is far easier than B2C. A business will pay serious cash for something that solves a problem without blinking. Consumers want to nickel and dime you to death.
For technical skillset, anything required to specify through to support a system that's probably got a thick slice of Java in it. On Linux.
I used to work in the gaming industry. I have 2 problems which they consider "difficult" but i know are solvable.
Its the "getting shit done" which is harder for me. All the small implementation details pile up ;(
Are you into web dev, desktop or backend ?
The systems I build tend to be Java at the core (uncool but I like it and it works with the sector), but I do everything from requirements gathering through to operations including UI. Although a minimum of UI is preferable.