devdocs/pricing.md

@@ -12,7 +12,28 @@ 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?  
+
+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.
+
+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.
+
+"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
 

devdocs/todo.txt

@@ -2,14 +2,36 @@
 
 
 
-todo: update post on forum on Thursday, not before trip to vic.
-todo: Licensing 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/
 
-todo: 45 day trial is way too long it means a long sales cycle and if we are hosting then it means tying up resources for far too long
-	if they are testing us out they can simply buy a month anyway once the free trial has expired
-	It needs to be the shortest possible time it takes to evaluate AyaNova and get an idea if it will work or not so there is urgency and less resources tied up
-	10 days maybe?
+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
+
+
+todo: ROCKFISH different license key signature if it's a SAAS license
+	this solves a lot of problems, effectively it's unlicensed if they move their data to their own hardware without a key
+	requires that AyaNova have different internal key to check, maybe it's actually a build switch for that since only we will be running our SAAS version.
+
+todo: if SAAS needs to do some things differently:
+	if it helps, consider a different build flag since SAAS is like an internal build for us
+	SERVER - count total active users towards license not techs only
+	SERVER - different signature for license keys
+	ROCKFISH - different signature when SAAS key
+	SERVER - some routes not enabled around licensing, operations etc
+	CLIENT - some info not displayed or routes not available if SAAS key
+	SERVER - alternatives for initial license agreement before first use?
+	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
+	
+
+
+
+
+todo: Change 45 day trial to 3 day trial but offer that they can email if they are going perpetual and need a special requested more period of time.
+	If they need more time they can sign up for a month's use of the SAAS model
+	is this in rockfish??
+	also if I can override in the UI that would be great (I think I can but check)
 
 todo: CLIENT UI license changes for subscribers around the LICENSE pages and route??