The final software business model we look at is in complete contrast to the previous models where the business is about the output of the software, whether this is creation of the software itself or the outcomes it generates. The software supporting a service model intentionally relegates the software system to a supporting role that forms no part of the description of the service being sold. This is not to say that the software becomes irrelevant in this model; it's about the software being a mechanism to allow the delivery of service features.
This model is more often used for departments within larger organizations, especially where there's a reliance on in-house developed resources for supporting its operations. A successful mainstream example of this model in use is Uber; an Internet based taxi service whose operation is dependent on the use of their phone app to provide customers with software features to request rides. These software features are used to facilitate everything from capturing journey details and assignment of the most suitable driver, through to payment for the journey and facilitation of other information.
The software supporting a service model is unique in the way that it allows you to make money as the software is being developed. This provides several advantages when it comes to startup costs and risk reduction:
Although software supporting a business has advantages in getting started and the types of flexibility it offers to reduce risks associated with other models, it also has several unique disadvantages such as:
The software supporting a service model is possibly the easiest model to execute that doesn't require upfront investment and minimizes the risk of developing unused software features that erode profitability. With options to develop the software as the services are being delivered, it is possible to learn about the software requirements as you deliver your service, meaning that you are able to fund the research and development of your software system from selling your services before starting software development.
Success with this model requires you to fully understand the role of the software in supporting the services being sold. With the software itself not directly responsible for making money, the software features need to be strategically designed to support the business activities that generate money, which could be to produce more sales, retain customers or increase efficiency for improved profit margins. Understanding how to identify the purpose of the software in this model is the difference between your software being a critical component of a successful business or failing to provide any meaningful support that justifies the expense of the software development.
There is an importance to allocate the right amount of time between money making activities that the software supports and the development of the software. Even though the software development is an initial cost to the wider business, it is the software component that you are developing that can be used to open or take advantage of opportunities that increase your earning potential. Neglecting your software development in favor of focusing on short term money making activities can damage long term capabilities. This is of concern when opportunities only exist for a limited time, where delaying your software development leads to missing opportunities and resulting in your software having no purpose by the time it is completed.
"When opportunities occur through events but you are unable to respond, you are not smart." | ||
--Sun Tzu, The Art of War |
With this in mind, there is a need to incorporate risk assessment into your project planning, allowing you to weigh up whether the goals of the software you develop are achievable before you invest your time into developing the software.
18.224.44.108