diff --git a/devdocs/pricing.md b/devdocs/pricing.md index 2bf3dbbd..be5f6882 100644 --- a/devdocs/pricing.md +++ b/devdocs/pricing.md @@ -13,28 +13,27 @@ The method by which a user starts using your product is called the activation mo This is the method we use and will continue to use but needs tweaking. ### Lead quality -We must require something to improve lead quality, if it's too easy people will just fuck around for the fun of it and waste our time. Some require a credit card but that's a *very* high barrier I think for just kicking the tires and right now how would we even use that with our payment processor since it's a zero dollar thing up front? + +We must require something to improve lead quality, if it's too easy people will just fuck around for the fun of it and waste our time. Some require a credit card but that's a _very_ high barrier I think for just kicking the tires and right now how would we even use that with our payment processor since it's a zero dollar thing up front? At the very least we should continue to require a valid email address to get started. Not sure of any better commitment that is simple and works for us so no change there I guess but they cannot download and try without an email address unlike v7 which just works from download automatically. ### trial period Right now we have 45 day trial, that's way too long, it ties up resources and prevents any sense of urgency on the part of the customer. -It needs to be as short as possible but still allow them to try it all out. In fact, there are two different types of trial periods now, the perpetual and the saas subscription. +It needs to be as short as possible but still allow them to try it all out. In fact, there are two different types of trial periods now, the perpetual and the saas subscription. For perpetual it takes much more time to install and set up to even get running and that's part of the testing process, however they can repeatedly request a trial license no problem but have to erase the data each time so I guess at the end of the day it's not necessary to have different length trial periods. -I think a three day trial period is sufficient. It creates hella urgency, it is really enough time to kick the tires and try everything out for real, if they are super serious but uncommitted yet they can move to renting for a month and really get into it. +I think a three day trial period is sufficient. It creates hella urgency, it is really enough time to kick the tires and try everything out for real, if they are super serious but uncommitted yet they can move to renting for a month and really get into it. "3 Day trial, if you need more time we suggest sign up for a month" ### Existing v7 users going SAAS - We offer the import of data ourselves so that they don't need to fuck around with that as part of the SAAS service? Hmm... a lot of it requires specific to them choices, maybe not. - ## PRICING (Joyce made two docs one for pricing as well as historical and projected license sales and a doc about payment processing providers both saved in raven project folder devdocs) @@ -50,11 +49,64 @@ Subscription hosted (We host they pay a flat fee per month / year to get access Eventually I'm going to want to cash out and sell the business and recurring revenue model is far easier to sell than a perpetual model. +### Positioning + +Our price position is in the middle: the best value for dollar, not the lowest cost and not the most expensive fanciest one but best value. + ### Value to Price ratio factors Value to price ration of 10:1 is ideal, means customers feel like they are getting 10 times more than what they pay I've never heard anyone say AyaNova is too expensive +### Comparatives + +(as of 2022-08-11) + +#### Jobber + +Jobber has good set of options comparable in many ways and has some more features for payment processing integrated etc, is an app based system but fewer strictly service management options no qb desktop integration but does qb online. I'd say it's better than AyaNova in terms of listed features but no idea for usability + + +1 user = 49/mo or 39/mo yearly +up to 7 users = 149/mo or 119/mo yearly +up to 30 users = 299/mo or 239/mo yearly prepaid This is where the majority of our customers would fall + +They have a good license agreement terms that is very restrictive with wide open terminology giving user little to no rights and good terms for cancellations like NO REFUNDS etc saved a copy in xfer research folder +good text around bandwidth "substantially higher htan average jobber users" throttle terminate etc + +Yearly payment discount 20% + +Bottom line Average per user price is $13.00/mo but not really broken out that way. Majority of our current users would fall into the $10/mo price range with them per user (up to 30) + +#### AI Field management + +This one is hella complex website and pricing, very confusing, my eyes glazed over a bit +Essentially there are 4 tiers with a separate price per user per tier. It's very hard to compare as some of our features are only in their most expensive tier but many of their featuers we don't have and are esoteric like translation by ai of something, ai routing of service calls I think, integration with some things like qb desktop which we can add, what's app, several things we could likely add ourselves. +At the very least I'd say the comparable is their "business" level which is 21.99 per user per month no apparent discounts for volume or payment over a year vs a month. The chepest is 9.99 and the most expensive ultimate level is 49.99 per user per month. so average would be 30. The level they push is the "advanced" at 38.49/mo + +No yearly payment discount listed + +bottom line $39 / monthly per user (at a guesstimate) + + +#### Housecall pro HVAC field service software + +https://www.housecallpro.com/pricing/ + +Clean website pretty clear. Features are hella confusing though, the first listed feature is a credit card with low %, also a phone number, I can't figure out if this is service management or something else, weirdness + +They take payments, a lot of these packages do, need to look into that it's common. +They have a "local phone number" whatever the fuck that is weird things these companies offer, not strictly service +Three tiers but only two have listed pricing. + +quoting is an addon for 40 a month, recurring service 40 a month +The one user is fucking wierd it says chat between users but only has one user so wtf? + +I think the other tier is more comparable at 169/mo or 129/mo yearly 1 to 5 users qb integration, no quote +$40 or pm's + $40 each 40/mo so to compare to ayanova would be at least 249monthly, I don't know about the weird oddball features so I'll ignore them as they are missing a lot of what we do offer, I'm seeing a lot of qb integration included so I'm starting to think that's not an upsell but something to just include with SAAS + +Bottom line $50.00/monthly per user + + ### License types and programs we will offer TWO types makes the most sense after considering options: @@ -89,10 +141,11 @@ We need a formal declaration of how to switch from one to the other models. ##### Subscription to perpetual - We post a guide on how to backup and restore to local + They must purchase a perpetual license as the SAAS license wont' work with perpetual but they can restore their database from the subscription. ### Pricing for v8 +#### PERPETUAL IDEA: figure out average license cost over all sizes of existing license sales, factor _that_ with the 19.4% inflation figure Joyce determined before and make that the average license price?? For active subscribers the average price paid for licenses was 121.25 so with inflation of 19.4 that would be 144.78. Tech counts by level is single=30 $4,770.00 total sales, 5=85 $11,815.00 total sales, 10=110 $13,090.00 total sales, 15=15 $1650.00 total sales, 20=100 $9,900.00 total sales @@ -126,6 +179,13 @@ Meaning if use 19.4% inflation figure v8 would be $110.00 for the license and $5 ACTUAL INFLATION just looked it up is 24% between now and 2016 including the prior months of huge increases, let's just round that up to 25% because inflation is still on the up trend so: Taking the average v7 license plus 90 days v7 average sub cost is $92.20 + 25% = $115.25 1 tech + 90 days support in 2022 prices and yearly afterwards is $54.60 average per tech subscription (not factored tiers in yet) +#### SUBSCRIPTION / SAAS + +So it's clear looking over things that there's a cost for a droplet and adding x more users doesn't really add to that for us so if a $5 droplet works for a single user up to let's say at least 10 users, just speculation, we make way more money off the 10 user. The price for a single user must be increased to accomodate that or...we host more than one site on a single droplet to offset the cost, but charge enough to move them up to a higher level without needing to increase the charges to compensate. + +so pricing should be the highest normal droplet we can use + + #### New idea perpetual vs subscription There is something to be said for a subscription model even if we don't host it. In this system a "perpetual license" is a one time purchase and comes with no support or maybe a very short window they get to use it forever afterwards. The subscription is a rental service only aka a "term license", if they stop paying it stops working. Separate from hosted AyaNova. @@ -162,6 +222,7 @@ OUR FACTORS: | | | Links to read with good ideas: +This one lets you search actual product pricing for SAAS and has comments about pricing value etc https://www.getapp.com/it-management-software/a/service-now-com/pricing/ https://baremetrics.com/blog/perpetual-license-vs-annual-license-vs-subscriptions https://baremetrics.com/blog/saas-pricing-models https://www.getapp.com/resources/software-pricing-models/ diff --git a/devdocs/todo.txt b/devdocs/todo.txt index 64cd5105..8d6ceb08 100644 --- a/devdocs/todo.txt +++ b/devdocs/todo.txt @@ -6,6 +6,7 @@ todo: License agreement changes for SAAS customers, this is huge and I hadn't thought of it before, wording is very different in this case, fuck, need to wing it I guess https://flgpartners.com/saas-pivots-transitions-perpetual-to-subscription-saas-models/ needs to be available separately in docs + Needs a disclaimer about the right to refuse service if becomes too high usage i.e. subject to usage limitations to cover our ass and check with D.O. how to clamp that from going into expensive territory for us? todo: ROCKFISH different license key signature if it's a SAAS license @@ -23,8 +24,15 @@ todo: if SAAS needs to do some things differently: CLIENT - alt license agreement when SAAS CLIENT - hits OUR copy of documentation if SAAS?? (not sure if this is necessary or desireable but something to consider) DOCS - alternative txt when SAAS about how licensing works - - + DOCS - doesn't need a version selector ultimately as always latest version + BACKUPS - do we backup, do they who is ultimately responsible for the preservation of the data? + what does D.O. say about this? + Can it just be an on top of charge or should we just bundle it into the charge and accept it's necessary? + SERVER - much smaller attachments max size, right now it's set to huge as possible but we need to cap that shit hardcore + SERVER - Ability to set a maximum attachment size + SERVER - hide any info about the droplet technical stuff like ram and ops stuff, we don't want them to have an idea how much memory they can have, or do we? + maybe it's a plust because we can say you get a maximum storage for attachments of XXGb based on droplet size and it's an add-on to go with a bigger server?? + Because some people need it and will pay for it if it's offered.