If you read nothing else
Oracle Siebel CRM licensing runs on the Application User metric — a named-user licence near $3,750 list for the Base product, plus roughly $400 per user for each industry module — with Processor licensing via the Core Factor Table for high-volume use and a 22% annual support charge on net licence value. Right-size the user count and module stack before any audit or migration and the bill falls without touching functionality.
Most Siebel estates are over-licensed, not under-licensed. They carry idle Application User accounts that were never deactivated, industry modules paid for but never switched on, and a 22% support line that compounds on the original list price year after year. Oracle has no incentive to point any of this out — it surfaces only when a licence review forces a reconciliation, and by then the framing favours Oracle. This guide hands the buyer the same map: how each metric counts, what stacks onto the price, and where the recoverable money sits.
Key takeaways
- Application User is the primary Siebel metric. Siebel CRM is licensed mainly per Application User — a named-user licence counting every individual authorised to use the licensed modules — with the Base product listing near $3,750 per user (Oracle price list, 2026).
- Support is 22% of net licence value, every year. Oracle technical support runs at 22% of the net Siebel licence fee annually — roughly $825 per Application User — and compounds against the original list, so the lifetime support cost dwarfs the one-time licence (Oracle support policy, 2026).
- Industry modules stack on top of Base. Each user needs a Base CRM Application User licence first; enabling an industry module such as Finance or Telecom adds roughly $400 per user on top, so the per-user cost is a stack, not a single line (Oracle Siebel licensing, 2026).
- Processor licensing is the high-volume alternative. For external-facing or high-population deployments, Siebel can be licensed by Processor via the Core Factor Table instead of per user, decoupling cost from headcount (Oracle Core Factor Table, 2026).
- Over-licensing is the norm, and it is recoverable. Across 600+ Oracle engagements, the typical Siebel estate carries 15–30% idle Application Users and unused modules still under 22% support — recoverable at renewal without touching functionality — Oracle Licensing Experts engagement benchmark, 2026.
01Recommendations by role
A Siebel licence position has owners. Here is where each role should push before a renewal, audit or migration locks the cost in.
CIO / IT Director
- Map every live Siebel module to a business process; flag any paid module not actually in production.
- Confirm the 2037 support floor so no internal "Siebel is dying" assumption drives a rushed, full-price migration.
- Own the metric decision — Application User vs Processor — before Oracle frames it for you.
Procurement / Vendor Management
- Benchmark the 22% support line and quantify the third-party-support alternative before any renewal.
- Negotiate module pricing and discount on the stack, not just the Base licence line.
- Refuse to let a licence review set the negotiation clock; the 2037 runway is your strongest lever.
SAM / License Manager
- Reconcile Application User and Processor entitlements against deployment, and deactivate idle named accounts.
- Document which industry modules and options are actually enabled so you stop paying support on shelf-ware.
- Keep the ordering documents and metric definitions; they govern cost on every path.
CFO / Finance
- Model the recurring 22% support stream over five years — it is the dominant Siebel cost, not the licence.
- Quantify the saving from removing idle users and modules as a recurring line, not a one-off.
- Budget independent buyer-side review before any renewal or migration; the fee is a fraction of the overpayment.
02How Oracle Siebel CRM licensing works
How is Oracle Siebel CRM licensed in 2026?
Siebel CRM is licensed primarily on the Application User metric — a named-user licence that counts every individual authorised to access the licensed Siebel modules, whether or not they log in on a given day. Each user needs a Base CRM Application User licence, listing near $3,750, before any industry module is added. The alternative is the Processor metric, which licenses Siebel by processing capacity through the Core Factor Table and suits high-volume or external-facing deployments where counting named users is impractical. The metric you signed in your ordering document governs your cost and your compliance exposure, so the first step in any Siebel review is confirming exactly which one applies to each module.
Pull the ordering documents before you do anything else. The metric, the module list and the user counts you actually own are written there — not in the system. Reconciling deployment against the contract, not against Oracle's measurement scripts, is what keeps a Siebel review on the buyer's terms.
What does a Siebel Application User actually cost?
An Application User is not a single price — it is a stack. The Base CRM Application User lists near $3,750; layering an industry-specific module such as Siebel Financial Services or Communications adds roughly $400 per user on top, and additional functional options stack further. On top of the licence, Oracle charges 22% annual technical support on the net licence value — about $825 per Base user every year — which compounds against the original list price and quickly becomes the dominant lifetime cost. A 500-user estate with two industry modules is therefore carrying a six-figure recurring support line before a single new licence is bought.
Across 600+ Oracle engagements, the typical Siebel estate carries 15–30% idle Application Users — accounts never deactivated when staff left — plus industry modules paid for but never enabled, all still under 22% support. That is recoverable at renewal without touching a single live workflow — Oracle Licensing Experts engagement benchmark, 2026.
When should I use the Processor metric instead of Application User?
Processor licensing makes sense when the user population is large, external, or impossible to enumerate — a customer-facing self-service portal, a high-volume contact centre, or any deployment where named-user counting would balloon. Under the Processor metric, Siebel is licensed by the number of cores running the software, multiplied by the Core Factor Table value for the chip, with unlimited users on that capacity. The break-even depends on user density per core: below it, Application User is cheaper; above it, Processor wins. The mistake is letting the metric drift — running a high-population module under named-user licensing and accumulating a back-licence claim that surfaces in an audit.
"For each Siebel module we run, which metric is on our ordering document, and what is the current Core Factor for our processors?" Get it in writing. Metric and core-factor assumptions are where Siebel compliance gaps hide, and Oracle's measurement will assume the most expensive reading unless you have the contract in hand.
How does the 22% support charge drive lifetime cost?
Oracle technical support for Siebel is 22% of net licence value annually, funding updates, fixes, tax and regulatory updates, and My Oracle Support access. Because it is charged on the original net licence price and rarely decreases, the support line is the part of a Siebel estate that quietly dominates the budget: five years of support on a mature estate typically exceeds the one-time licence cost. It also keeps charging on idle users and unused modules, because Oracle bills the entitlement, not the usage. That is why right-sizing the entitlement — not just the deployment — is the single highest-value Siebel cost move.
Support repricing is the lever Oracle least wants you to pull. On a stable, customised Siebel estate, independent third-party support delivers equivalent break-fix and tax-update coverage for roughly half the 22% fee — quantify it before any renewal so the alternative is on the table when you negotiate.
Will Siebel be discontinued, and does that change my licensing?
No. Oracle has committed Premier Support for Siebel CRM through at least 2037 and moved to a monthly continuous-release model in 2018, so there is no forced end-of-life and no version cliff forcing an upgrade. That matters for licensing because it removes the manufactured urgency Oracle uses to push Fusion Cloud subscriptions: your perpetual Siebel licences remain owned, supported and right-sizeable for another decade-plus. A migration is a business-case decision, not a compliance deadline — and a Fusion move re-licenses you per user without crediting the perpetual Siebel licences you already hold.
How do I keep a Siebel estate clean before an audit?
A defensible Siebel estate is one where Application User and Processor entitlements reconcile to deployment, idle named accounts are deactivated, unused industry modules are identified, and the metric on each module matches its real usage pattern. Oracle frequently runs a licence review ahead of a renewal or migration push, using any compliance gap — unreconciled users, options in use but not licensed, a high-population module on a named-user metric — as leverage. Close those gaps on your own schedule, with your own evidence, so you negotiate any renewal from a clean, right-sized position rather than under an audit finding Oracle controls.
03Application User or Processor: the choice that sets your cost
Recognise the pattern
"License every module per named user"
Running a high-population, external-facing module on the Application User metric inflates the count and builds a back-licence claim Oracle finds in an audit.
"Match the metric to the population"
Put internal, enumerable users on Application User and high-volume or external deployments on Processor via the Core Factor Table.
"Keep paying support on the whole estate"
Paying 22% on idle users and unused modules funds entitlement you do not use, year after year.
"Right-size entitlement, then reprice support"
Deactivate idle users, drop unused modules at renewal, and benchmark third-party support on what remains.
Every Siebel cost decision reduces to the same pattern: the metric must match the population, and the support line must match the entitlement you actually use. Get both right and the bill falls without removing a single live capability.
04Siebel licensing options: strengths & cautions
| Option | What it does for the buyer | Caution |
|---|---|---|
| Application User (Base) | Simple per-user cost for enumerable internal populations; lists near $3,750/user | Inflates fast on high-population or external modules; idle accounts still billed |
| Industry module add-on | Adds vertical functionality (Finance, Telecom) at roughly +$400/user | Often enabled then forgotten — paid and supported but unused |
| Processor (Core Factor) | Decouples cost from headcount for external-facing or high-volume use | Core-factor and hardware definitions must be verified and kept current |
| Stay + third-party support | Cuts the 22% support line by roughly half on a stable, owned estate | Loses access to new Oracle updates and My Oracle Support |
| Migrate to Fusion Cloud | Modernises if the business has genuinely outgrown Siebel | Re-licenses per user; existing perpetual licences are not credited |
05Acronyms & definitions
- Application User
- Application User is Siebel's primary named-user metric, licensing each individual authorised to access the licensed modules.
- Named User Plus (NUP)
- Named User Plus is a named-user metric variant that also counts non-human operated devices or accounts authorised to use the software.
- Processor metric
- The Processor metric licenses Siebel by processing capacity via the Core Factor Table, used for high-volume or external-facing deployments.
- Core Factor Table
- The Core Factor Table is Oracle's multiplier that converts physical cores into licensable processors for Processor-metric licensing.
- Base CRM
- Base CRM is the foundational Siebel Application User licence every user requires before any industry module is added.
- Industry module
- An industry module is a vertical Siebel pack (e.g. Financial Services, Communications) licensed per user on top of Base CRM.
- Technical support (22%)
- Oracle technical support is the annual fee, 22% of net licence value, funding updates, fixes and My Oracle Support access.
- Premier Support
- Premier Support is Oracle's full support tier — updates, fixes and tax updates — committed for Siebel CRM through at least 2037.
- Ordering document
- An ordering document is the contract schedule that records the exact Siebel metric, module list and quantities you own.
- Third-party support
- Third-party support is independent maintenance for Siebel from a non-Oracle provider, typically at roughly half Oracle's 22% fee.
06Frequently asked questions
How is Oracle Siebel CRM licensed?
Siebel CRM is licensed primarily on the Application User metric — a named-user licence counting every individual authorised to use the licensed modules — with Processor licensing via the Core Factor Table as the alternative for high-volume or external-facing deployments. Each user needs a Base CRM licence before any industry module is added, and Oracle charges 22% annual technical support on the net licence value.
How much does Siebel CRM cost per user?
The Siebel CRM Base Application User licence lists near $3,750 per user in 2026, with industry modules such as Financial Services or Communications adding roughly $400 per user on top. Oracle then charges 22% annual technical support on the net licence value — about $825 per Base user every year — which compounds against the original list price and becomes the dominant lifetime cost. List prices are a negotiation starting point, not the price you should pay.
What is the difference between Application User and Processor licensing in Siebel?
Application User licenses each named individual authorised to use Siebel and suits internal, enumerable populations. The Processor metric licenses Siebel by core capacity via the Core Factor Table, allows unlimited users on that capacity, and suits external-facing or high-volume deployments where counting users is impractical. The right choice turns on user density per core; the mistake is running a high-population module on the named-user metric and accruing a back-licence claim.
How much is Oracle support for Siebel?
Oracle technical support for Siebel is 22% of net licence value annually, funding updates, fixes, tax and regulatory updates and My Oracle Support access. Because it is charged on the original net price and rarely decreases, five years of support on a mature estate typically exceeds the one-time licence cost. It also keeps billing idle users and unused modules, because Oracle charges the entitlement, not the usage.
Can I reduce my Siebel licensing costs without migrating?
Yes. Deactivate idle Application Users, drop unused industry modules at renewal, match each module's metric to its real user population, and benchmark independent third-party support, which delivers equivalent coverage for roughly half the 22% fee on a stable estate. Across 600+ engagements the typical Siebel estate carries 15–30% recoverable entitlement — idle users and shelf-ware modules — without touching any live workflow.
Is Oracle Siebel being discontinued?
No. Oracle has committed Premier Support for Siebel CRM through at least 2037 and moved to a monthly continuous-release model in 2018, so there is no forced end-of-life and no version cliff. Your perpetual Siebel licences remain owned, supported and right-sizeable for another decade-plus, which means any migration is a business-case decision rather than a compliance deadline Oracle can use to compress your timeline.
Do my Siebel licences carry over if I move to Fusion Cloud?
Generally no. A Fusion Cloud migration does not credit your existing perpetual Siebel licences; it re-licenses you on a per-user subscription. Any migration business case must therefore be modelled net of the licences you already own and the support you already pay. Ask Oracle in writing exactly what credit, if any, applies before assuming a saving the contract does not provide.
07Methodology & sources
Benchmarks in this paper draw on Oracle Licensing Experts engagement data across 600+ Oracle licensing, audit and negotiation projects, 2026. Pricing figures are list-price reference points from the Oracle price list and are starting points for negotiation, not the price a buyer should accept; idle-entitlement ranges are anonymised aggregates from buyer-side advisory work. Support-roadmap dates and the release model are taken from Oracle's primary Siebel documentation. We do not publish client names or fabricated deal counts.
Primary sources: Oracle, Siebel CRM Support Extended Through at Least 2037 (2026); Oracle, Siebel CRM Innovation & Roadmap (2026).
Download this white paper as a PDF
Keep the Siebel metrics, the per-user price stack and the right-sizing framework on hand for your next renewal or audit conversation. Use your browser's print-to-PDF to save a clean copy.
Download / Print PDF →08Related white papers
Over-paying on Siebel? Right-size before you renew.
Most Siebel estates carry idle users and shelf-ware modules under full 22% support. Our independent advisors reconcile your Application User and Processor entitlements, match the metric to the population, and benchmark third-party support — buyer-side, before your next Oracle renewal.
The buyer-side Oracle briefing
Monthly, independent intelligence on Oracle licensing, cloud pricing, audits and contract negotiation — written for buyers, never for Oracle.
Prefer to talk? Request a free Oracle licensing briefing or see how we cut Oracle support cost.