Package pricing
# package-development
t
Welcome, I developed an Umbraco package and I have the question below before making decision: What is pricing model recommended by Umbraco package developer?
n
Hi Tarik, That's exciting to hear you've created a package for Umbraco. That's a bit of a loaded question to be honest. The vast majority of packages for Umbraco have been created and released for free. There are some that have one off payments, and some that do subscription. How successful these packages are, I suspect, has very little do with their cost but more around their quality and their functionality. Based on that, I suspect there isn't really a recommended pricing model it's more down to what you feel is suitable for your package.
c
I heard Matt and Kevin talking about charging for packages. If it’s something that would take a developer more than a month to recreate then it’s worth putting a price on it but anything less than that and people won’t pay for it they will make it themselves.
t
Thank you, @Nik and @CodeSharePaul The current plan for package pricing model has two options: 1. Free for community. (limited features) 2. Premium with a one time fee. > I suspect there isn't really a recommended pricing model it's more down to what you feel is suitable for your package. I think a major version pricing model is valuable. > If it’s something that would take a developer more than a month to recreate then it’s worth putting a price on it but anything less than that and people won’t pay for it they will make it themselves. Yes, something easy to do with current features why paying for it.
w
There are lots of things to consider as well. Licensing, Online Card Payments, Invoices, Charging VAT correctly etc..
But I agree with @CodeSharePaul it needs to be about a month's dev time/effort otherwise people will just recreate/build it themselves
t
I think my package will have a new model using a provider the first time in Umbraco package + the technology I'm using. (let it be an excellent news when launching it)
w
OK well look forward to it then
c
Looking forward to seeing it mate.
n
Something to consider when commercialising a package - even if you're explicit about NOT providing support, you will still be dealing with support requests from customers. Trust me, I've been there.
j
You’re probably going to get that with unpaid packages too though (see me, in Nathan’s DMs asking him about Tabulate )
t
Thank you, Nathan. Yes, I plan to support them in Github.
n
@Janae if I didn't like you I'd tell you to bugger off
t
I didn't find a lot of issues on Github just 9 in total! Anyway, it depends on the popularity of the package in case it is accepted and very useful for Umbracians ...
j
I hope it goes really well!
c
Agreed, that's one of the primary things to consider when it comes to pricing IMO; How much would it cost for someone to have to create something similar themselves, and/or how much time does it save when purchasing? But it can also very much depend on what type of package it is; Does it provide developer convenience, end-user convenience, or does it e.g. allow for more revenue generation of a website that could make it worth purchasing?
t
2 Views