Siebel SPE vs SEE Licensing Cost Comparison
This article compares the licensing costs of Siebel Professional Edition (SPE) versus Siebel Enterprise Edition (SEE). We explain how each edition is licensed (per user, processor, or enterprise metrics), typical pricing structures for licenses and modules, and the ongoing support fees.
Real-world examples illustrate the cost difference for a small business using SPE and a large enterprise using SEE.
By understanding these details, IT executives can budget effectively and choose their organization’s most cost-efficient licensing model.
Understanding SPE vs SEE Licensing Models
Oracle Siebel CRM offers multiple licensing models, and the edition you choose influences how you pay for licenses:
- Siebel Professional Edition (SPE): Typically licensed on a per-user basis (Named User or Application User licenses). SPE is sold as a streamlined package for small to mid-sized businesses, often including core CRM functionality at a bundled rate. It’s designed for simplicity and cost-effectiveness, meaning fewer components to license separately. Users are the main metric – each individual accessing the system needs a license.
- Siebel Enterprise Edition (SEE): Also often uses per-user licensing for each module needed, but enterprises have more flexibility in metrics. Large deployments might consider alternative metrics like processor licenses (licensing server CPUs for unlimited users) or enterprise licenses (fixed fees for unrestricted use across the company). SEE is modular – an enterprise can license additional modules (analytics, loyalty, etc.) on top of the base CRM, which increases costs accordingly. This edition’s licensing is more complex because it covers a broader feature set and higher user counts, sometimes requiring mixed metrics (e.g., user licenses for internal staff and processor licenses for external or high-volume access).
Named User vs Application User: Oracle uses terms like Application User or Named User Plus (NUP) in Siebel licensing. Both essentially count individual people (or devices) authorized to use the software. Application User is the standard Siebel user metric (each human user counts as one license).
Named User Plus is a similar metric that counts non-human accesses (like integrations) and often comes with minimum purchase requirements (for example, Oracle may require a minimum of 25 named users per processor core if you choose a NUP metric in a large environment).
Application user licensing is common for most SPE or SEE deployments, but large SEE environments might switch to processor-based licensing when it is more cost-effective.
Read Upgrading from Siebel Professional Edition to Enterprise Edition: Licensing Challenges and Best Practices.
License Fee Components and Pricing Structure
Base License vs Modules: Every Siebel deployment requires at least a Base CRM license. Oracle’s list price for the Siebel CRM Base Application is roughly $3,750 per user (perpetual) license.
This base license grants core CRM features (sales, service, marketing automation, etc.). For Siebel Professional Edition, this base license often covers the needs of an SMB without many add-ons. In Enterprise Edition, a large company usually needs additional module licenses for advanced functionality:
- Industry Modules, such as Siebel Financial Services, Communications, Manufacturing, etc., might cost around $400 per user for the added specialized features. Enterprises often license one or more of these based on their industry.
- Advanced Modules: e.g., Siebel Analytics or Siebel Loyalty, which could have their pricing (often similar add-on user costs, or in some cases, different metrics like a server license).
- Developer and Testing Tools: Large enterprises may need options like Siebel Tools (~$20,000 per user license for development capabilities) or Test Automation ($5,800 per user license), but smaller SPE customers usually avoid them due to their cost.
Initial License Cost Example:
- Small Business using SPE: 50 users all on the base CRM (no extra modules). License cost = 50 × $3,750 = $187,500 up front for perpetual licenses.
- Large Enterprise using SEE: 500 users with base CRM plus two industry modules (e.g., Communications and Financial Services modules at $400 each per user). Base cost = 500 × $3,750 = $1,875,000. Module costs = 500 × $400 × 2 modules = $400,000. Total initial license = $2.275 million for licenses. This enterprise might also consider processor licensing if 500 users grow into thousands (e.g., licensing servers instead of each user).
Named User vs Processor Cost Trade-off: In SEE deployments, if user counts are very high or hard to track (for instance, thousands of employees or a customer-facing portal), Oracle offers processor licenses.
A processor license lets unlimited users access a module on a given server, priced per CPU core (Oracle’s core pricing for Siebel modules isn’t public, but as a reference, many Oracle enterprise apps have processor prices that are roughly equal to a certain number of user licenses—often 50 or more users’ worth per processor).
For example, if a Siebel module costs $1,000 per user, a processor license might be around $50,000 per CPU for unlimited use. Large enterprises evaluate this when user counts per server are high; buying four processor licenses for a server can be cheaper than 1,000 individual user licenses.
SPE environments rarely use processor licensing (since user counts are small). In contrast, SEE environments may mix metrics (with careful contract terms to avoid compliance issues when mixing user and processor metrics).
Annual Support and Maintenance Fees (22% Cost Add-on)
When budgeting for Oracle software, the Software Update License & Support (SULS) fee is a significant ongoing cost. Oracle charges a standard 22% of the license fee per year for support on Siebel licenses:
- This fee entitles you to software updates, patches, and technical support.
- It is mandatory to maintain support if you want Oracle’s assistance and access to new versions. For example, on a $3,750 user license, support is about $825 per user, per year (22% of 3750).
- Support costs accumulate as you add more licenses or modules. In our examples above, the 50-user SPE deployment ($187,500 license cost) would incur roughly $41,250 per year in support, and the 500-user SEE deployment ($2.275M license cost) would incur about $500,500 per year in support.
CIOS must factor in these recurring costs. Over a typical 5-year period, support fees will roughly equal the initial license cost itself (5 × 22% = 110% of license cost over five years). Unlike a subscription, you’re not obligated to pay support annually, but dropping support can be risky – you lose upgrades, and Oracle will charge back-support fees plus penalties if you later need support reinstated.
Cost-saving tip: If your organization is not heavily using Oracle’s support (e.g., you have a stable, older Siebel deployment), some enterprises consider third-party support providers at a lower rate or negotiate with Oracle for a reduced support uplift. However, be cautious: without official support, you cannot upgrade the software or get patches, which can be a critical limitation.
Cost Comparison: SPE vs SEE in a Scenario
To illustrate the cost differences, consider a scenario of a growing business:
Scenario: A company starts with 100 users on Siebel Professional Edition (SPE) and later grows to 1000, moving to Siebel Enterprise Edition (SEE) with additional modules.
- Initial SPE Deployment (100 users): They license 100 Base CRM application User licenses. No extra modules needed initially.
- License Spend: 100 × $3,750 = $375,000.
- Annual Support: 22% of $375k = $82,500 per year.
- This covers core CRM functionality for 100 users.
- Upgraded SEE Deployment (1000 users + modules): As the business expands, more users and advanced modules (say, Analytics and an Industry module) are required.
- Base License: 1000 × $3,750 = $3.75 million.
- Modules: 1000 × $400 (Analytics) + 1000 × $400 (Industry) = $800,000 (for two modules across all users).
- License Spend: approximately $4.55 million for the expanded user count and functionality.
- Annual Support: ~22% of 4.55M = $1 million per year (approximately).
- Alternative: Instead of 1000 Named User licenses, the company might license some servers by processor. For instance, if the Siebel Analytics server has eight cores and Oracle’s policy allows processor licensing, they might buy eight processor licenses for that module instead of 1000 user licenses—this could be more economical if the cost per processor is favorable. This approach is evaluated during the move to Enterprise Edition to control costs.
This comparison highlights that scaling up Siebel usage can exponentially increase costs. SPE lowers costs by limiting scope (fewer modules, moderate user counts), whereas SEE enables breadth and scale at a high price.
Also, support fees grow correspondingly – in the SPE scenario, support is tens of thousands per year, whereas in the SEE scenario it’s around a million per year.
Over time, support can become a major portion of TCO (Total Cost of Ownership). CIOs should project these multi-year support costs when planning a Siebel investment.
Budget Considerations and Hidden Costs
When evaluating SPE vs SEE, consider the following financial factors:
- Minimum License Quantities: Oracle sometimes imposes minimum license purchases for certain metrics or modules. For example, opt for Named User Plus licensing on an enterprise module. There might be a minimum (e.g., “at least 200 Named User Plus licenses” for a given component, even if you have fewer users). SPE customers usually meet minimums easily (since user counts are smaller, you’re licensing actual people), but SEE customers need to be mindful of such clauses to avoid surprise costs. Always check your Oracle order documents for any per-processor or per-module minimums.
- Multi-module Overlap: In an Enterprise Edition deployment, you might license the same user for multiple modules (e.g., a sales representative might need Sales module and Service module licenses). This “stacking” of licenses per user increases the cost per user. In Professional Edition, Oracle might offer a bundle that covers the essentials at one price. Be sure to clarify if the SPE package includes multiple functionalities under one license – it often does for core CRM. In SEE, assume each module is licensed separately unless a bundled suite is negotiated.
- Discounts and Negotiations: Oracle’s list prices are high, but large enterprises can negotiate discounts. It’s not uncommon to get a 20-30% discount on license fees for a big purchase. Support is usually calculated at the discounted price (so the 22% annual fee would be applied to the reduced license cost). SPE deals for SMBs might have smaller discounts (or standardized pricing), whereas SEE deals (larger) have more room for negotiation. Engaging Oracle contract specialists or using a volume purchase (like an Unlimited License Agreement or a global deal) can significantly alter the cost dynamics. CIOs should approach SEE licensing as a negotiable investment, not a fixed price tag.
- Growth Path Costs: If you plan to start with SPE and later possibly move to SEE, ask Oracle about trade-up credits or flexible licensing. In some cases, Oracle may credit a portion of your SPE investment if you upgrade to SEE (essentially allowing you to apply the money spent on SPE licenses toward the Enterprise Edition licenses). This isn’t guaranteed, but if negotiated upfront, it can save money when scaling up. Without such an arrangement, you might end up paying for SPE licenses and then paying all over again for SEE licenses separately. It’s better to structure contracts with growth, especially for rapidly scaling companies.
By fully understanding these licensing cost components and differences, enterprise leaders can make an informed decision that balances CRM capabilities with budget realities.
Recommendations
- Match Edition to Business Size: Use SPE for as long as it meets your needs. Its lower cost structure is ideal for SMB budgets. Only consider SEE when your user count or required functionality justifies the higher cost.
- Budget for Support: Include the 22% annual support in all cost projections. Over 5 years, expect to pay more in support than the upfront license cost – ensure this fits your IT budget.
- Explore Processor Licensing: If deploying SEE with thousands of users, ask Oracle if processor-based licensing is available for certain modules. It can cap costs by allowing unlimited users on a server for a fixed price, potentially cheaper than thousands of named users.
- Negotiate Enterprise Terms: When committing to Siebel Enterprise Edition, negotiate volume discounts or an enterprise agreement. Large deals often get discounted pricing; push for better rates or bundled module packages.
- Check Minimums: Always review Oracle’s licensing policies for minimum required licenses (e.g., Named User Plus minimums per core or module). Plan your license counts to meet these, so you’re not caught off guard having to buy more than you need.
- Use Phased Module Adoption: With SEE, you don’t have to enable every module simultaneously. License additional modules in phases to spread out costs, rather than purchasing all upfront.
- Monitor User Counts: Keep track of active Siebel users. If you are near a higher pricing tier (e.g., jumping from 50 to 100 users or 500 to 1000), consult Oracle on the cost implications. Sometimes, a slight user increase can lead to needing more module licenses or a different metric.
- Plan for Upgrade Costs: If you foresee outgrowing SPE, plan a license transition budget. Save a portion of the IT budget in advance for the eventual increase in license and support fees when moving to SEE.
- Consider Third-Party Support (Carefully): Third-party support vendors might offer lower annual fees for older Siebel deployments. This can save money, but weigh it against losing official Oracle updates. It might be an interim cost-saving measure if upgrades are not immediately needed.
- Engage Licensing Experts: Consider consulting Oracle licensing specialists to validate your cost model. An expert can identify hidden costs or savings opportunities (such as unused licenses or better metrics) for your specific Siebel deployment.
FAQ
Q1: How is Siebel Professional Edition typically priced compared to Enterprise Edition?
A: Siebel Professional Edition is generally cheaper upfront – it often involves purchasing just the base user licenses for core CRM functions. Enterprise Edition is more expensive because you usually need to license additional modules and possibly more users. Essentially, SPE might be a single bundled cost for basic CRM per user, while SEE is a sum of costs for each module/user combination needed.
Q2: Do SPE and SEE have different license types or metrics?
A: Not different (both can use user-based licenses), but SPE is almost always licensed per named user (Application User metric). On the other hand, SEE might involve a mix of metrics – still predominantly per user per module, but large enterprises can choose processor or enterprise licensing if it’s more efficient. Oracle might not offer an “unlimited” license specifically for Siebel except as part of a broader agreement, but the Enterprise Edition environment allows more flexibility in how you license it.
Q3: What is the cost of a Siebel CRM user license?
A: Oracle’s list price for a Siebel Base CRM (Application User) license is about $3,750. Industry module add-ons are about $400 per user each. These are list prices as of recent data; actual prices can vary with negotiations. So if a user needs access to one industry module besides base CRM, the list price would be $4,150 for that user license (plus that user’s share of annual support).
Q4: How much is Oracle’s support fee for Siebel?
A: Oracle charges 22% of the annual license fees for support. For example, if you spend $100,000 on licenses, support will cost $22,000 annually. This applies to both SPE and SEE licenses. It’s a standard rate – nearly a quarter of the yearly license cost to get updates and support.
Q5: Can we start with SPE and later upgrade to SEE without paying for everything again?
A: Upgrading will increase your costs significantly because you’ll need to purchase additional licenses (for more users or modules). Oracle doesn’t have an automatic free upgrade from SPE to SEE; however, you can negotiate terms. Sometimes Oracle might give credit for the original SPE licenses toward the Enterprise Edition licensing, but this must be agreed to in a contract. Otherwise, you essentially buy the new licenses needed for SEE. It’s wise to involve Oracle early when you foresee needing an upgrade – they may offer a deal or package to facilitate the transition.
Q6: Is there a user limit or cap in Siebel Professional Edition that would force us to switch to Enterprise?
A: There isn’t a hard-coded user cap in the software, but contractually or practically, SPE is meant for smaller deployments. In some cases, Oracle sales might enforce that you should move to Enterprise Edition licensing beyond a certain number of users (or if you need certain advanced modules). Also, the SPE package might exclude certain modules entirely – if you find you need those, that effectively forces an upgrade. Think of it like outgrowing a smaller software edition; at some point, the features you need are only available in the enterprise package.
Q7: Can large enterprises stick with the Professional Edition to save money?
A: Not usually. Professional Edition is feature-limited. A large enterprise may find that SPE doesn’t include critical functionality (for example, extensive customization, advanced analytics, multi-currency support, etc., might only be in SEE). Even if a big company tried to use SPE, they might violate licensing terms if they extend it beyond its intended use. Oracle could audit and determine that the usage aligns with Enterprise Edition features and require an upgrade. So while it’s technically possible for a smaller enterprise to run on SPE if they have basic needs, most larger organizations will require SEE to cover their usage and needs legally.
Q8: Are there any maintenance or support cost differences between SPE and SEE?
A: The support percentage (22%) is the same, but since SEE involves more licenses (and more expensive ones), the absolute support dollars are higher. Oracle doesn’t charge a different support rate for SPE vs SEE – it’s always tied to your license. However, an SPE customer paying $100k in licenses pays $22k/yr support, whereas an SEE customer who spent $1M on licenses pays $220k/yr. Both editions get you Oracle Premier Support; Enterprise Edition users may utilize support more due to the complexity of their deployment.
Q9: What’s an “Enterprise license” in the context of Siebel?
A: This can refer to a licensing metric where an organization licenses the software for enterprise-wide use instead of counting users or processors. Oracle sometimes offers this for large customers: you pay a large flat fee to cover unlimited usage (often time-bound or with conditions). It’s not specific to “Enterprise Edition”, the product; it’s a license deal. In Siebel’s case, a massive company might negotiate an enterprise license covering all employees, which would be part of a broader Oracle agreement (like an Unlimited License Agreement, ULA). It’s usually only cost-effective if tracking individual licenses becomes too cumbersome and the organization is large.
Q10: How do discounts work for Oracle Siebel licenses?
A: Oracle’s prices are negotiable. They publish list prices, but most enterprise customers get a discount off list – the percentage depends on the deal size and Oracle’s pricing policies. You might pay close to list price for a small SPE purchase if it’s straightforward. For a significant SEE purchase (millions of dollars list), Oracle might give a discount (e.g., 20% off), especially if it’s part of a bigger Oracle purchase or end-of-quarter deal. Always negotiate – Oracle sales reps expect it, and you can often reduce the price or get extra modules bundled if you ask for them as part of the agreement.
Read more about our Oracle License Management Service.
Do you want to know more about our Oracle License Management Services?
.
