Hacker News new | ask | show | jobs
by dalke 3654 days ago
> "much larger audience"

Yes, that is the problem.

The biggest conference in my field has ~200 people. There might be 10,000 people around the world who might ever use my software in one way or another.

They tend to work in one of the one to two hundred or so companies doing drug discovery cheminformatics.

A "small percentage" of 200 is only a handful of companies. That's not enough to make a living. Rather, in that case it's more profitable to do custom software development in that case than off-the-shelf software. Because (oddly) people are willing to pay more for special one-off solutions than general solutions.

While if 10% of the field was willing to pay me once, and the handful of companies willing to pay support, then that's good money.

> "Another benefit is customers fix bugs and feed those back to you, so you've got a stronger product."

I've heard that a lot. I've also been doing free software in this field for 20 years. I've only ever received a handful of minor bug fixes.

My users are computational chemists and their IT support staff. They are not professional programmers. It's easier for them to pay me money to fix bugs than for them to do it.

Also, at some pharmas, code needs to be reviewed by the lawyers before being sent out.

I know one company that distributed source under the GPL, then found that their customers weren't willing to upgrade. Because they had made local changes, and found it too difficult to go through the lawyer review in order to send the changes upstream. It was easier for them to ask for new features instead.

> "advertising delivery platform"

Sure, and in-app sales. Except my software works on proprietary chemical compounds. I don't have access to the machines or the data, and no pharma in their right mind will allow me that sort of control of their in-house informatics platform.

> be prepared to invest a lot in marketing.

I wish to clarify that I am not looking to make my software proprietary. My argument is that I'm sure I could make more money with proprietary software than with free software.

Even if I make it proprietary, customers will get full source, no DRM, and the right to redistribute after (say), 10 years.

As for marketing, and as I found out, most people know of my software, and already use it. The problem is one of conversion less than marketing. Which is still a form of marketing, but less expensive.

> trusting customers works

So, one potential lead said they might buy my software. I gave them my list price. They said they didn't have the money to pay full price so could they get it for only $10K? This London-based organization has a full-time cheminformatics staff member, and over $100M in funding. I don't know if I should trust them, but I suspect it's a negotiating tactic.

Again, my point isn't to say that open source is a bad approach. I agree that there are business models where it does work. But it's not a panacea.

1 comments

I would not argue that it works in all cases, my only point was that open source is very compatible with capitalism and lots of companies find it very profitable to go open and free source.

> I suspect it's a negotiating tactic.

Of course it is!

Certainly. So, what does "trust" mean?

Do I trust them to undercut the price I think is reasonable? Do I trust them to tell me what the software is really worth to them? Do I trust that they will value my time appropriately?

That's why I have a problem with the word "trust" in this context.

Trust means if you make a deal with them, they'll abide by the terms.

Trust does not mean they won't negotiate hard to get the best deal they can. Trust does not mean they are obliged to show you their cards. Trust does not mean they value your time as you would.

I suspect you'll be very disappointed if you consider the latter to be trust issues.

I understand what you are saying. I want "trust" to mean something more than "will follow the terms of a deal."

Instead, trust is a highly multi-dimensional, culturally context-dependent concept. As such, I get little guidance from the phrase "trusting customers works", when I know that each aspect of trust has its own set of parameters, including some where I have no experience to guide me.