This applies to customers, potential employers, and basically everything in life. There is ALWAYS a price. So take the gamble. Let them decide if it's worth it from their own perspective... maybe you'll get lucky!
This applies to customers, potential employers, and basically everything in life. There is ALWAYS a price. So take the gamble. Let them decide if it's worth it from their own perspective... maybe you'll get lucky!
I think both perspectives are worth considering.
The release of git and hg was a direct response to McVoy yanking BitKeeper away (withdrawing the free-beer licensing terms that had previously allowed gratis use for free/open source projects); both were initially announced on the Linux-kernel mailing list as responses to McVoy's move, and each had had only a few weeks' worth of work at that point.
Before that, there had been a good deal of grumbling about the ever-shifting terms of the "don't piss off Larry license", whose increasingly draconian terms were designed to prevent the development of competitive software. (The last available version purported to bind all users to a non-compete preventing them from contributing to another SCM; I'm not sure California law would have allowed McVoy to enforce a non-compete on his own employees!) However, so long as these difficulties remained theoretical, there was not, in fact, much serious work going on to develop such competition. But when Larry revoked the license, effectively forcing the kernel developers to come up with an alternative damn quick, they did --- and damn quick.
So, the clones aren't something that the customers did when they got dissatisfied with BitMover; they're something that happened after BitMover chose, on their own, to end the relationship. Which makes them, as I said, a self-inflicted wound, that BitMover could have avoided through better customer relations management.
http://web.mit.edu/ghudson/thoughts/bitkeeper.whynot
"From the beginning, Bitkeeper has been aimed at making it easier to do development the way Linux kernel development is done. As Larry McVoy put it: 'BK makes it really easy to do what Linus is doing.'"
If you follow the links in that article, Larry McVoy doesn't really say what he's quoted as saying there, though he does make similar assertions.
BitKeeper certainly made no money on supporting Linux but I think the idea, on some level, must have been to get the software out there being used by serious programmers who would then love it, buy it, and evangelize it. In the driest sense, it was not a success. But in a wider sense in backfired so thoroughly that the idea of starting a commercial VCS project at this point is laughably absurd. Several things McVoy said turned out to be wrong, even though they must have sounded plausible at the time. I'm particularly pointing to this one:
"All you people trying to copy BK are just shooting yourself in the foot unless you can come up with a solution that Linus will use in the short term. And nobody but an idiot believes that is possible."
http://lkml.indiana.edu/hypermail/linux/kernel/0303.1/0315.h...
So, it probably isn't the best analogy, but on the other hand it was the first one that came to mind. :) I'd be curious to know what you think about this, and more importantly what your opinion of BK is today and how it compares after having a decade to mature.
http://www.inc.com/magazine/201206/jason-fried/huge-accounts...
My view is that it's healthy to say "no thanks," politely and frequently.
There are people who are just unbelievably unreasonable, mistrusting, and impossible to satisfy. These types can take you off course, reduce morale, harm your reputation, and generally almost "break" your company. As a small boot-strapped, but profitable company, I would rather expend our efforts on finding and supporting good lower-paying customers who are happy with our service and with whom there is a mutually beneficial relationship.
As they say, "money isn't everything", but even to the extent that one focuses solely on money, it's not always more profitable longer-term, even with a customer who's willing to pay an outsized price.
In OP's case, if he had offered the spreadsheet guy some insane amount he probably never would have gotten any business. The more reasonable colleague would have seen the amount and scoffed, forming a poor opinion of OP's business.
Unfortunately it's not always easy to arbitrarily raise your prices for the difficult customers because they complain even more and ask "where does it say that there will be a charge or fee for this on your website?"
I always thought it would be nice to have an extra line on my pricing page that stated "Difficult Customer Fee: $TBD" :)
However even my best (and nicest) customers do some of the things here...sometimes they give me a big long list of questions at their first contact, or persistently call if they have what they think is an urgent problem or question. Usually as long as they're not rude I don't have a problem with it, and they're normally pretty happy if I send an email saying I'll reply after the weekend or whatever.
We try to detect/filter them in the sales process. Unfortunately saying "I don't thing our product is a good fit for you" invariably seems to make them want it even more.