From MVP to SaaS
A path from testing a product idea through operating and hosting software to delivering a subscription service and measuring recurring revenue.
5 terms
From MVP to SaaS follows a product beyond its first test. An MVP helps test an assumption; DevOps connects ongoing delivery with operating the software. Serverless introduces one way to host parts of that software. SaaS describes how customers use a service, and MRR provides a way to track its monthly subscription revenue.
This Line joins Startup Delivery, Cloud Foundations, and Subscription Metrics. Serverless is an optional hosting approach, not a requirement for SaaS, and MRR applies when the product uses recurring subscriptions.
Along this line
5 terms
1.MVPMinimum viable product: an early version of a product used to test important assumptions about customers with the least effort needed to learn.Business & Work2.DevOpsA way of developing and running software that combines shared responsibility, collaboration, and automation to improve delivery and reliability.Business & Work · Software & Data3.ServerlessA cloud application model in which the provider manages much of the underlying server infrastructure, scaling, and runtime operations for the developer.Cloud & Systems4.SaaSSoftware as a service: a cloud service model in which customers use software applications operated by a provider rather than managing the underlying infrastructure themselves.Business & Work5.MRRMonthly recurring revenue: the recurring subscription revenue a business expects from active customer contracts normalized to a one-month period.Business & Work