Live data from Hacker News

Building relationships with customers through support didn't turn out as hoped

uncommonapps.nyc

81–90 of 205 posts

Re: Building relationships with customers through support didn't turn out as hoped

#81
post #15

I know this isn’t a very interesting comment, but just to provide some balance to the mostly negative comments I’m seeing: It’s interesting that you did the experiment, and I appreciate you sharing your results. It all seems reasonable, even if a bit depressing.

Everybody on HN knows better than OP how to run their own business and could absolutely please 100% of customers or potential customers 100% of the time. Apparently.

Idealism doesn't survive contact with reality.

Re: Building relationships with customers through support didn't turn out as hoped

#82
post #71
post #68

Earlier quoted context omitted.

Depends though what you pay for the one-time price. You can pay an offline version of the application (no extra costs afterwards), or a limited period of SaaS application updates (let's say 3 years). I agree that paying a one time price and expecting continuos updates and new features is not reasonable.

For the majority of software I use, I don't really care about continuous upgrades and new features, as long as it works with the feature set I signed up for. A great example for me is the Xodo app on Android. It's by far the best PDF editor that I've found on Android, particularly for annotating with a digital pen. Some features are locked. If I want to unlock them, it's $5 a month. I get nothing out of that which is…

The biggest tension between software and one-off purchases is related to bugfixing, and especially security. It makes sense that you don't expect new features for a product that you paid for once. But, what is the case with bugs? If the product mostly does what it promised to do, but sometimes crashes, do you expect those crashes to be fixed for your version, or not? What it you're using a 10-year old version and a new critical (say, unauthenticated remote execution) vulnerability is found in it? Do you expect to get it resolved as part of the price you originally paid, or would you be ok with being told you have to buy a new version if you want this ?

Re: Building relationships with customers through support didn't turn out as hoped

#83
post #55

Earlier quoted context omitted.

> You have to accept that your pricing model sucks to a group of people (who are likely experiencing subscription fatigue) and decide if it’s worth losing or never getting their money. And for some subscription situations, you can probably offer them a price that works for both of you. There's a 'PhotoSync' app that offers a premium option for either $1/month or $24 for life. Presumably because they looked at the ave…

> you can probably offer them a price that works for both of you There is no such price, because there is no way to sustainably develop a product without subscriptions. You can't go to a local bakery and pay $24 for life to get fresh rolls every day. Every one-time price is a gamble, where somebody is betting on something. It's a way to close your eyes and pretend ongoing costs do not exist.

> Every one-time price is a gamble, where somebody is betting on something. It's a way to close your eyes and pretend ongoing costs do not exist.

The gambling goes both ways. Your $1 subscription price is betting that you can convince each user to keep on paying that subscription forever, their $24 lifetime price is betting that customers are going to churn after a year on average.

Your gamble is perhaps slightly safer, in the sense that if subscriptions fall so too do the ongoing costs. But there is a floor to costs (i.e. you need to keep paying your team), so both approaches are pretty dependent on the sales funnel bringing in new subscribers

Re: Building relationships with customers through support didn't turn out as hoped

#84
post #71

Earlier quoted context omitted.

For the majority of software I use, I don't really care about continuous upgrades and new features, as long as it works with the feature set I signed up for. A great example for me is the Xodo app on Android. It's by far the best PDF editor that I've found on Android, particularly for annotating with a digital pen. Some features are locked. If I want to unlock them, it's $5 a month. I get nothing out of that which is…

The biggest tension between software and one-off purchases is related to bugfixing, and especially security. It makes sense that you don't expect new features for a product that you paid for once. But, what is the case with bugs? If the product mostly does what it promised to do, but sometimes crashes, do you expect those crashes to be fixed for your version, or not? What it you're using a 10-year old version and a n…

A good chunk of the software on my device doesn't need to access the internet, another big chunk does so using standard mechanisms (i.e. libcurl) that could be security patched out of band by the OS.

The only reason I routinely need to update most software, is that Apple/Google keep changing device screen resolutions/cutouts and they keep killing off old APIs

Re: Building relationships with customers through support didn't turn out as hoped

#86
post #76
post #72

Earlier quoted context omitted.

A lot of people in the comments are saying he did it for "likes" - that's a pretty harsh reading of the article. What I think a lot of people are missing is that the difference between supporting corporates who spend up to millions per year on your product and supporting end-users who are literlly counting every cent they spend is a huge gulf in terms of expectations, technical ability, professionalism.... the list g…

Thanks. I'm not really understanding the likes comment. What are likes in this context? I was very explicit in the post I thought providing better support would build customer relationships and improve retention, and I learned that really isn't true. Also I wrote this a couple days ago so the blog would have content and only submitted on a whim, had I known I'd get 10K views and 100 comments I would've written it mor…

Thanks for posting this. I have experienced similar. I have found that nasty bug reports are most effective. Good data, and the people are too cheesed off/embarrassed, to follow up, after you address it. Occasionally, it can actually be turned around, and they can become evangelists.

I have integrated a simple feedback form into the app, with the option to send anonymously. That seems to help.

> had I known I'd get 10K views and 100 comments

Is that still the case, after being frontpaged on HN (but most comments are probably here)?

Re: Building relationships with customers through support didn't turn out as hoped

#87
post #71

Earlier quoted context omitted.

For the majority of software I use, I don't really care about continuous upgrades and new features, as long as it works with the feature set I signed up for. A great example for me is the Xodo app on Android. It's by far the best PDF editor that I've found on Android, particularly for annotating with a digital pen. Some features are locked. If I want to unlock them, it's $5 a month. I get nothing out of that which is…

The biggest tension between software and one-off purchases is related to bugfixing, and especially security. It makes sense that you don't expect new features for a product that you paid for once. But, what is the case with bugs? If the product mostly does what it promised to do, but sometimes crashes, do you expect those crashes to be fixed for your version, or not? What it you're using a 10-year old version and a n…

There's some merit to your arguments, but not enough to justify a subscription:

- Subscriptions are marketed as being a lot more than just bugfixes - new features being the big one. But there's usually no cheaper "bugfix-only" subscription, which means that someone who doesn't care about new features has to pay for them anyway.

- To be honest - yes, I do expect bugfixes for free if I've paid to buy the product. After all, a bug is a defect, and products are usually sold with the expectation that they will be fit for purpose. That's the principle which applies to physical consumer products, so why should it be any different for software? If I bought software that calculates my taxes for me, and it turns out a bug means that it applies the wrong tax rules, then I haven't got what I paid for. Why am I expected to pay every month just to make my software do what it was supposed to do in the first place?

- The developer is still incentivised to fix bugs in order to attract new purchasers.

- Subscriptions aren't a magic solution financially anyway, because there's an average limit to how long a customer stays subscribed for.

Re: Building relationships with customers through support didn't turn out as hoped

#88
post #71
post #68

Earlier quoted context omitted.

Depends though what you pay for the one-time price. You can pay an offline version of the application (no extra costs afterwards), or a limited period of SaaS application updates (let's say 3 years). I agree that paying a one time price and expecting continuos updates and new features is not reasonable.

For the majority of software I use, I don't really care about continuous upgrades and new features, as long as it works with the feature set I signed up for. A great example for me is the Xodo app on Android. It's by far the best PDF editor that I've found on Android, particularly for annotating with a digital pen. Some features are locked. If I want to unlock them, it's $5 a month. I get nothing out of that which is…

> as long as it works with the feature set I signed up for.

Yes. On the exact major OS version you signed up on.

Re: Building relationships with customers through support didn't turn out as hoped

#89
post #79
post #64

Earlier quoted context omitted.

I think this is an uncharitable reading of GDPR that is probably not backed by actual decisions?

Who said anything about GDPR? If someone reveals to you that they are in some kind of protected class, then there’s a risk that anything you do they don’t like could see you tagged for discrimination even if it’s how you’d treat any customer in the same situation.

If you have evidence it's the usual approach (e.g. written policy documents, aggregate statistics), then it should be fine. If it's a situation that only comes up for certain demographics, and you handle it poorly such that members of those demographics consistently have a worse time than everyone else, then that might be a legitimate discrimination issue even if there's no malice intended.

Re: Building relationships with customers through support didn't turn out as hoped

#90
post #76

Earlier quoted context omitted.

Thanks. I'm not really understanding the likes comment. What are likes in this context? I was very explicit in the post I thought providing better support would build customer relationships and improve retention, and I learned that really isn't true. Also I wrote this a couple days ago so the blog would have content and only submitted on a whim, had I known I'd get 10K views and 100 comments I would've written it mor…

Thanks for posting this. I have experienced similar. I have found that nasty bug reports are most effective. Good data, and the people are too cheesed off/embarrassed, to follow up, after you address it. Occasionally, it can actually be turned around, and they can become evangelists. I have integrated a simple feedback form into the app, with the option to send anonymously. That seems to help. > had I known I'd get 1…

All comments here yeah. Almost to 11K views and there were less than 50 before I posted, with a dozen new subscribers to the blog.
Post reply on HN