A former community discussing the business of software, from the smallest shareware operation to Microsoft. A part of Joel on Software.
We're closed, folks!
Doug Nebeker ("Doug")
I'm developing a full on flexible SAAS implementation kit (ASP.Net MVC SAAS Kit), for my own use, as well as possibly thinking of polishing it and releasing as a complete commercial product so other developers can use it to jump start their SAAS products without having to think about the identity membership, billing, sub users, user profiles, account upgrades, packages, etc.. The basics that every single online web app or service (SAAS) needs.
You would just worry about building the actual software business logic and get to the market quicker.
Let me know if you are interested in such a framework to use as a starting point for your SAAS projects.
I'm thinking of it being commercial, however, you would purchase the source code, and can see all the code and use as a base to start your saas project. So you only worry about building the actual code functionality of your app instead of worrying about the stuff that any and every webapp / saas should include.
How many hours of work did you spend on the extra saas implementation that's not related to the core functionality of your saas offering. (e.g. billing, user management, profiles, etc..)
How much time/money was spent on the SAAS framework as opposed to the "app"?
I'd say 50% of the initial costs ( which were 3 months of my time + $15k of "hired in help" ).
However selling a "Framework" is a big task. You are asking me to base my whole application from on your work.
Will you be still in business in 3 years time? How much effort will I have to invest in learning your framework? Will you keep it up to date? Will it be flexible enough or just get in the way?
A framework is a hard sell. That's why it's only the Microsofts, Googles of this world who are generally the only people successful with them.
And the trend is very much for "IT Software Infrastructure" to be free and open ... for these very reasons.
Another approach you could consider is selling plug-in modules that do certain SAAS functions ( billing, tenant subscription, etc etc ).
So that instead of having to go "All-in" with a framework your customers would have the option just to buy and use what they want or needed.
The advantage of this is that a) you get to write smaller bits of code .. and therefore get to market quicker.
b) your customer doesn't have to overcome the high barrier that adopting a 3rd party framework is.
Just my thoughts.
I agree with all, even if it is free and not open-source, I would not use it. If it open-source, I'd only take a look and take some parts of it.
>identity membership, billing, sub users, user profiles, account upgrades, packages, etc..
these things are not hard to do. very easy. it can take about one day for me to get an initial working version
Tuesday, December 30, 2014
This topic is archived. No further replies will be accepted.Other recent topics
Powered by FogBugz