Ayende @ Rahien

Hi!
My name is Oren Eini
Founder of Hibernating Rhinos LTD and RavenDB.
You can reach me by phone or email:

ayende@ayende.com

+972 52-548-6969

, @ Q c

Posts: 18 | Comments: 71

filter by tags archive

The strange world of products psychology

time to read 2 min | 343 words

Originally posted at 12/13/2010

A while ago my company started to offer Commercial Support for NHibernate. It seems like a complementary product to what we are already doing, but it actually had a few other reasons to want to do so.

Put simply, my pool of potential clients for the NHibernate Profiler are… NHibernate users. Anything that increases the pool of NHibernate’s users also increase the pool of potential clients for NH Prof.

The reason that we offer commercial support for NHibernate in the first place was to increase the trust people have with NHibernate. It reduce a barrier to entry, since if a company asks about the support options, they know that there are commercial support options out there.

With that in mind, I set out to design the pricing structure for the commercial support very carefully. One of the most important aspects of offering commercial support is that you want to have it behave just like insurance. For the most part, people need the support contract very rarely, and even if you end up spending three days working on a customer problem, that cost is amortized with other customers who did not call.

Knowing that, I explicitly added an Ad Hoc option for the commercial support offering for NHibernate. Ad Hoc support doesn’t really make a lot of sense, to tell you the truth. Not as a product, at least. It basically means that someone can call you, pay a fixed amount and then require potentially unlimited amount of time / effort. The reason that I did that is that having an Ad Hoc support option is a very compelling feature from the customer point of view. For precisely the same reason.

I was looking to make NHibernate itself more attractive with that offer, not to actually have a viable product.

Now, however, I feel that NHibernate no longer need the prop of the Ad Hoc support option, and thus it is no longer an option for our commercial support offering for NHibernate.


Comments

Tonio Guzzi

Ad Hoc support option is a great idea! ..and i think you should not leave ...maybe tomorrow i need that :)

Ayende Rahien

Tonio,

As I said, it IS a great deal to you, not so much for me, who have to supply that.

Francois Ward

Wouldn't ad-hoc support paid per hour instead of per call make sense though? Or do you already do that via consulting?

Ayende Rahien

Francois,

That could be handled via consulting, yes.

sprong

why do you fell that nh doesn't need it any longer ?

Ayende Rahien

Sprong,

Because it is already established enough.

Comment preview

Comments have been closed on this topic.

FUTURE POSTS

  1. RavenDB 3.0 New Stable Release - one day from now
  2. Production postmortem: The industry at large - about one day from now
  3. The insidious cost of allocations - 3 days from now
  4. Buffer allocation strategies: A possible solution - 6 days from now
  5. Buffer allocation strategies: Explaining the solution - 7 days from now

And 3 more posts are pending...

There are posts all the way to Sep 11, 2015

RECENT SERIES

  1. Find the bug (5):
    20 Apr 2011 - Why do I get a Null Reference Exception?
  2. Production postmortem (10):
    01 Sep 2015 - The case of the lying configuration file
  3. What is new in RavenDB 3.5 (7):
    12 Aug 2015 - Monitoring support
  4. Career planning (6):
    24 Jul 2015 - The immortal choices aren't
View all series

RECENT COMMENTS

Syndication

Main feed Feed Stats
Comments feed   Comments Feed Stats