There are two main sources of income for a SaaS business and one should obviously optimise for both:
- Recurring income/profit.
- Value of the business for eventual sale. This can range from zero to multiples of annual profit and amount to a substantial lump sum.
In this excellent guide for budding SaaS entrepreneurs there are some interesting points regarding optimising for each:
https://startingandsustaining.com/chapters/valuation/
A factor for #1 includes costs of the individual required to do support and basic maintenance.
Possible AwareIM advantages: Easier support & maintenance?
Possible AwareIM disadvantages: A very small pool of expertise than a mainstream tool? Much costlier?
A factor for #2 includes code quality:
"Code quality is a more subtle but still key factor that affects your multiple. High quality code, good test coverage, static analysis tools, and well-defined processes signal that the codebase is healthy. A healthy codebase hides fewer secrets and means fewer risks. It also means a quicker transition and less dependence on you or your team. Take care of your code. Document it. Test it. And remember, it’s much easier to do this as you go than try to circle back after the fact and try to clean things up before you sell."
Possible AwareIM advantages: There is minimal "code" so the codebase is by definition "healthier"?
Possible AwareIM disadvantages: Difficult to implement test coverage and prove "health"?
Would anyone care to comment on these aspects of AwareIM and on optimising for #2?
I'd be grateful for other user's experiences, observations and tips.
Thanks,
Michael