Solve This Problem
So, a lot of the problem users have with SaaS products is worrying about their data.
Why don’t one of you super evil Uber-genius types solve this problem with an intermediary?
In the music world, specifically plugins, there are numerous solutions to run your plugins on a separate platform from your DAW, to increase speed and free up processing power.
Why not build an intermediary for something like Notion, for example, so people can feel comfortable with where their data is stored and for having more control over it?
Just a thought for you coders that dig a challenge. How can an intermediary possibly help? Notion has to have access to your data to work their app. Add an intermediary and now you have somebody else who has access to your data. You're not thinking about this the right way. Check it out: Most users don't have a problem with a SaaS accessing their data - it's 'what happens when they get bought out or close up shop', etc. The problem is the user having limited access over their own data. I mentioned VST/AU audio plugins and the ability to do just this. Here's an example of what I'm talking about: https://www.sweetwater.com/store/detail/UAD2SatTB38--univers... So, let a SaaS like Notion have access to your data, but you store it...or it's colocated. If they close up shop or get bought out, your data doesn't disappear because you already have it. Two possibilities: (1) They host but you can get an export of your data; in some cases there is a local copy and a hosted version of the same app, for instance: (2) You could provide a database like Firebase or DynamoDB that Notion connects to and runs the service out of. If you were running in the same cloud availability center it could be snappy. Now you’re cooking! Conifer looks interesting and the user-provided DB is as well. Both seem like valid ways to potentially provide a greater piece of mind to the SaaS user. Do you think that most SaaS co.’s wall in the ecosystem from a business standpoint (i.e., price increases) or is it merely a consideration of efficiency? The 2nd option is dramatically more hassle for "Notion" and the customer. If something goes wrong with the database provided by the customer the service will go down. Or just be slow, which is bad enough. Requests you make to "Notion" still suck resources when they are waiting for the customer database. So far as pricing I think many SaaS stumble through life, one day you take the plunge and make a 3-column pricing chart (it works for the phone company) or 4-column (from $199 a month it jumps to "starting at" $4999 for the 'Enterprise') I would rather pay an 'everyday low price' (Southwest Airlines) than 'pick the plan that is right for me' from a list of options that doesn't make a lot of sense to me. SaaSers go with the $C (constant) a month plan instead of the $V (variable based on what you use) plan because it is harder to get credit cards to let you bill $X (variable) recurrently. The two schools on pricing are cost-based and value-based; they are both wrong. Profits come when cost is greater than value; you don't need value greater than price to make a sale but it sure helps. (e.g. markets may be irrational but it doesn't mean the marketer should be) Good explanation. Thank you. You might enjoy this: https://blog.chartmogul.com/saas-pricing-report/ It doesn’t get really interesting until The SaaS Pricing Report.