Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

"Obviously a stupid response, but really seems to be a response out of pure desperation more than anything."

Yes, that seems to be the simplest explanation. But from the original article this was the second communication as well. The first one, (which is linked), was pretty clear that the choices were 'give us a link or pay us money, your choice.' The author notes it had a useless subject line. And useless or not, if a vendor I'm using sends me an email I read it, and if it truly is useless I ask them to not send useless email.

So this was an escalation on the part of Gigya from "We've changed our pricing, we don't offer a free version any more so you have to choose a new option." To "You ignored our previous response, let's be perfectly clear about what your choices are."

Now you can argue that the sequence might be: nice, nice, threat. But if the company is looking at a shrinking runway they might cut out the middle 'nice' version of the communication.

And the author comments "This almost makes it a paid link that can help them rank up for ‘Social Media for Business’" No, this is exactly a paid link for helping Gigya rank higher on Google. Clearly they feel like the paid link is 'equivalent value' to the $6,000 which they want to charge.

The only economic question here is what economic value does SupportBee put on a paidlink on their site? If it were less than $6,000 then they win by giving the link to Gigya, if its more then they should just pay the $6,000/yr. (or use a different service).

I can't find a lot of fault on Gigya's part here. That it caught SupportBee by surprise seems to be because the author didn't read their mail.



  > So this was an escalation on the part of Gigya from "We've 
  > changed our pricing, we don't offer a free version any more 
  > so you have to choose a new option." To "You ignored our 
  > previous response, let's be perfectly clear about what your 
  > choices are."
Exactly right.

  > I can't find a lot of fault on Gigya's part here. That it 
  > caught SupportBee by surprise seems to be because the 
  > author didn't read their mail.
Again, no argument from me (or I think anyone else?) -- the hub-bub is just over the tact Gigya took.

As you pointed out above and I mentioned in my comment, there are innumerable better ways to state what they were trying to get across and they chose one of the poorer ones.

So no problem with what they did, just how they did it.

I also can't help but wonder why they didn't just disable the widget for that client after the 1st or 2nd notice, let the client come to them and then start a peaceful up-sell discussion where a well-informed decision could be made (exactly the way you stated w.r.t. to the worth of the widget/vs first-page linking for SupportBee).

Net-net, nothing to see here, just some people being more rude than expected.

Why so rude? My guess is financial pressure is causing them to act more aggressively to secure income; as you put it, a shrinking runway.


The only economic question here is what economic value does SupportBee put on a paidlink on their site? If it were less than $6,000 then they win by giving the link to Gigya, if its more then they should just pay the $6,000/yr. (or use a different service).

I think this is almost the right question. The real one would compare the cost of having a paid link on their homepage, the cost of the service ($6000) and the value of the service. If the service isn't worth the cost of the paid link or of outright purchase, then dropping the service is the right decision.


I seemed to have missed the part about why Gigya did not just suspend the non-compliant users' service, or indicate they would do so in a communication.

Threatening legal action to the very people you worked so hard to get to use your free platform is just asking for problems.

Most of the Gigya apologists I've read seem to say something along the lines of, well the chips were down and they were shooting from the hip. As every true gunslinger knew, this was the fastest way to get killed.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: