Live data from Hacker News

Our Recurring Payment Pricing Was Rejected

jerviswhitley.com

11–20 of 81 posts

Re: Our Recurring Payment Pricing Was Rejected

#12
post #3

Same manager is probably leasing their $50k car and will just get another when the lease is up. People have a hard time putting value on what they cannot touch.

Not sure I understand this sentiment. This same manager would likely be buying a 15k used car outright if he's worried about paying for software over time. The problem that I have with SaaS is that most companies pursuing it's business model fail at the value option. Take Freshbooks for instance - I started using their service 3 years ago for 9$ per month. This got bumped to 14$ per month. I now have to pay 20$ per m…

Would you rather pay a percentage of the payment you receive or a monthly fee like Freshbooks charges?

Re: Our Recurring Payment Pricing Was Rejected

#13
There are many considerations. For example, buyer may capitalize the expense and amortize it sooner: on their schedule, not yours schedule of payments, and get it off tax base sooner. The budgets for R&D (your contracting rate) may be different than budget for software purchases. Depending ob legislation, they may get tax credits for R&D work (even though done by a contractor). They may have budget now, but are not sure about later, but still want software to work, no matter what

Re: Our Recurring Payment Pricing Was Rejected

#14
post #6

In the example situation the choice wasn't quite so clear, as IP was on the line too. Regardless: A customer wants to pay an exorbitant fee up front, and you're fretting? Why? Take their money.

A customer wants to pay an exorbitant fee up front, and you're fretting? Why? Take their money.

I agree. If you're bummed about the result, then I suspect that you priced at least one of the options incorrectly.

First pricing rule: price so that no matter what your customer selects, even if it's to not do business with you, you're indifferent.

Re: Our Recurring Payment Pricing Was Rejected

#15
We get IP ownership, but we don’t bill for our time at all. Instead they become our first customer to use the new tool for a lower yearly fee (including maintenance).

You're taking on market and execution risk here, for which you are not receiving compensation. (Presumably you set your consulting rates high enough such that engagements are a win for you. The SaaSification option is at a discount to your rate, which you only make up if you sell it to other people. "Selling it to other people" is often much, much more difficult than writing working software.)

Any consultants in the room who happen to have an engagement which would create usable IP could consider the following alternative: "You pay our normal rates, and you pay for hosting/maintenance, and we own all the IP." This is actually very common, because most customers of software do not want to get into the software business and hence they don't give a fig nutton about commercial exploitation of this system they want to buy from you. No purchasing manager at the US federal government is going to nail his promotion to GSWhatever if he preserves the government's call option on starting a SaaS starttup.

Re: Our Recurring Payment Pricing Was Rejected

#17
post #3

Same manager is probably leasing their $50k car and will just get another when the lease is up. People have a hard time putting value on what they cannot touch.

Not sure I understand this sentiment. This same manager would likely be buying a 15k used car outright if he's worried about paying for software over time. The problem that I have with SaaS is that most companies pursuing it's business model fail at the value option. Take Freshbooks for instance - I started using their service 3 years ago for 9$ per month. This got bumped to 14$ per month. I now have to pay 20$ per m…

You're making the mistake of assuming everyone has the same problem as you do.

Pre-SaaS most companies would have paid upfront for a piece of software (before knowing if it works for them) and then upgraded ever few years in any case. For multi-user software they would have needed to pay for servers, ops staff, etc. on an on-going basis in any case.

When companies are evaluating a SaaS solution versus a boxed solution price is not typically a major deciding factor.

Re: Our Recurring Payment Pricing Was Rejected

#18
i think the pitch here could be made more enticing. With SaaS you are not only paying for the current product but also for the implied updates and improvements that will follow. So a comparable model would be how much would a box software cost and what would its upgrades cost (as well as how often are they upgraded).

If the saas cost is being imagined for n years than they should also take into account the inevitable upgrades they would have to pay for with boxed software to keep the software productive.

for example we could take adobe creative suite and its upgrades together for a comparable saas offer.

Re: Our Recurring Payment Pricing Was Rejected

#19
post #15

We get IP ownership, but we don’t bill for our time at all. Instead they become our first customer to use the new tool for a lower yearly fee (including maintenance). You're taking on market and execution risk here, for which you are not receiving compensation. (Presumably you set your consulting rates high enough such that engagements are a win for you. The SaaSification option is at a discount to your rate, which y…

While this certainly happens, there are companies that do not want their codified knowledge to leak to competitors. So they lock down the IP not because they want to sell it, but just in case code happens to contain trade secrets.

Re: Our Recurring Payment Pricing Was Rejected

#20
Here's an easy fix... charge them a yearly or longer fixed duration license fee. Like say 1, 3, or 5 years. Make it expensive enough that monthly pricing makes some sense.

Also, charge for support separately on a deal like this as you are unable to calculate their support needs on a longer time horizon.

Post reply on HN