How much of a SaaS companies’ revenue should come from services?
There is a fundamental issue in the SaaS market; If a SaaS company makes more money from services that from their software, then they are not motivated to make their software better, because it would actually reduce their revenue.
Why would anyone invest in making a product that will make them less money?
This has been an economic conundrum for a very long time.
People who made horse drawn buggies and technologies associated with horses, made a case against the car.
Companies who made vinyl records made the case against compact cassettes, and then against Compact discs, and then against streaming music services.
And in all cases the case they were making was in support of their existing business model, not in support of the user requirement.
When the SaaS business model was first launched, it was to be able to sell solutions directly to business departments (such as sales) as opposed to having to have an internal IT department build or configure the solution. When companies such as salesforce.com first entered the market, they were offering a solution that was at least 50% of what the business needed. This was in a time when the business was only able to get maybe 30% of what they needed from their internal services teams, and the time to market and the cost was far higher (with internal teams) than they could justify. The result was using SaaS was seen as a low risk purchase, but over time required a significant additional investment in services to add the additional functions and configurations that were not in place “out of the box”.
Over time these services actually exceeded the budget for the SaaS product itself, and this created pressure within the SaaS companies (and their partner ecosystems) to maintain and grow this revenue stream. This pressure made it hard for the SaaS platform to solve these problems in software, as doing so would reduce service revenue and increase development costs. This is why SaaS products which seem to offer so much promise at their inception seem to slow down their innovation as their sales skyrocket.
SaaS has become the ultimate “bait and switch”, with the initial sale often being predicated on a free trial (or a very low starting price), that quickly becomes the standard within a business, and as they scale the use of the platform, complexity and additional requirements require large investments in services and additional licenses.
The ultimate SaaS company shouldn’t make any money from services, so what is an acceptable level of services that a SaaS company can make without corrupting their business model?
Quite simply a SaaS business must make more from their SaaS software than from services to ensure that they are motivated to continue to innovate in the platform at the expense of services. They should see services as an embarrassment, and they should be motivated to do whatever it takes to eliminate the need for services from their implementations.
Look for SaaS companies who make significantly more from their software than they do from their services (and in this include the services offered by their partners), only then do you know that the vendor has the same interests as you.
Nastel Technologies is the global leader in Integration Infrastructure Management (i2M). It helps companies achieve flawless delivery of digital services powered by integration infrastructure by delivering Middleware Management, Monitoring, Tracking, and Analytics to detect anomalies, accelerate decisions, and enable customers to constantly innovate, to answer business-centric questions, and provide actionable guidance for decision-makers. It is particularly focused on IBM MQ, Apache Kafka, Solace, TIBCO EMS, ACE/IIB and also supports RabbitMQ, ActiveMQ, Blockchain, IOT, DataPower, MFT and many more.
The Nastel i2M Platform provides:
- Secure self-service configuration management with auditing for governance & compliance
- Message management for Application Development, Test, & Support
- Real-time performance monitoring, alerting, and remediation
- Business transaction tracking and IT message tracing
- AIOps and APM
- Automation for CI/CD DevOps
- Analytics for root cause analysis & Management Information (MI)
- Integration with ITSM/SIEM solutions including ServiceNow, Splunk, & AppDynamics