| Sr No | Description | Opportune HRMS SaaS | Traditional License |
| HRMS Audience | |||
| 1 | Fits any type of organization small to big. 25 employees to 25000 employees |
Yes
|
No
|
| HRMS services Economics | |||
| 1 | Capital investment [Capex] |
No
|
Yes
|
| 2 | Opex cost |
Yes (as per use) |
Yes (Fix) |
| 3 | Payment link to deliverable |
Yes
|
No
|
| 4 | Expensive Back up & storage device requirement |
No
|
Yes
|
| 5 | Maintenance cost for server by the client |
No
|
Yes
|
| 6 | Annual Maintenance for the software updates |
No
|
Yes
|
| 7 | Pay only for what you use |
Yes
|
No
|
| HRMS Set Up | |||
| 1 | HRMS Go live with required payroll modules & functionality |
12-15 days
|
30-45 days (server set up will take more then 15 days) |
| Features & Value adds HRMS solution | |||
| 1 | Auto update of HRMS software |
Yes
|
No
|
| 2 | Flexibility for features |
Yes
|
Yes
|
| 3 | Business continuity 4 hours guarantee |
Yes
|
Yes (at a very high cost) |
| 4 | HRMS Vendor otivation model for quality service delivery |
Yes
|
No
|
| 5 | Scalability of the product with business dynamics of the Company & market [Future proof] |
Yes
|
Yes (Expensive & complex) |
| Whether you’re a founder thinking about using third party software for your start-up, or thinking about how best to structure licenses to your software, it’s important to consider how “Software as a Service” or “SaaS” licenses differ from traditional software licenses and understand the legal issues related to using them. |
| This report will help you understand the salient features of both the models. |
Traditional software Licenses
| In this model the vendor permits the organisation to use a copy of their software on your servers and systems. |
| This means the the client or the organisation must have a large initial capital outlay to “purchase” the license. |
| • The software has to be tested and certified to operate on various platforms. |
| • Updates and maintenance require a planned, structured and multiple stakeholders to be involved. Massive backup and precautions are a must. Plus upgrade cost is on the client |
On Cloud
| Everyone is talking about cloud now days |
| It enables browser-based delivery, developers realized that providing applications as a “hosted” software service (known as “Software as a Service” or “SaaS”) is a more efficient approach because : |
| • Customer doesn’t need to do capital investment for purchase of license and server. They essentially subscribe for the service. |
| • The client only pays for the number of employees on the roll. So no wastage of unused capacity. |
| • The developers can provide bug fixes and updates to all the licensees at once. |
| • You can work on your regular platforms. No need to install new systems and platforms. Which mean no extra installation costs? No learning curve. |
| • Auto updates & upgrades |
| • NO Annual Maintenance cost |
| • Green Environment |
| • Guarantee of quality of service, as it is linked to payments to the SaaS provider. |
| • Why own an item, which has no appreciation value |
