Service Cloud · the licence bill, not the build
You cannot find the price,
and that is the most useful fact about it.
Salesforce publishes one entry figure and routes everything above it through a salesperson. Every specific number you will find for the higher editions comes from somebody else guessing. So rather than add another guess, this page sets out the six things that actually decide the bill, and the four that reduce it.
Checked against the Salesforce European pricing pages on 30 August 2026.
First, two bills
The licences and the build are different money, paid to different people.
The licence bill goes to Salesforce, recurs every year, and grows with headcount. The implementation bill goes to whoever builds the system, is paid once, and ends. Almost every confused conversation about what Service Cloud costs is these two being discussed as though they were one number.
They also move in opposite directions. Over a single year the build usually looks like the larger figure. Over three years the licences normally overtake it. That comparison is worth an hour before an edition is chosen, and it is almost never made, because the two numbers arrive from different people at different times.
What decides the licence bill
Six things, and the edition on the brochure is not the first of them.
No figures below, deliberately. On 30 August 2026 the European pricing pages returned no published number for the editions above the entry tier, so any specific amount printed here would be somebody else guess repeated with more confidence. What can be stated is what moves the number, and that is more useful anyway.
Seats committed, not seats used
The invoice is written against the number on the contract for the length of the term. Buying headroom for growth that did not arrive is the single most common way organisations overpay, and it is invisible because nothing on any screen compares licences bought against licences logged into. Run that comparison before every renewal, not after.
The term, and when the notice window closes
A multi year term buys a better rate and removes the ability to reduce seats when the team shrinks. Whichever is chosen, the date that matters is not the renewal date but the day the notice window closes before it, which is earlier and is in the agreement rather than in any reminder. Put that date in a calendar the day the contract is signed.
One feature that forces the edition
Editions are usually chosen for a single capability somebody needs, and the jump then applies to every seat including the ones that will never touch it. Before accepting that, establish whether the capability is available as an add-on, a permission set licence, or on fewer seats. Frequently it is, and the answer changes the bill for every user.
Add-ons priced per seat rather than per org
The things bolted on afterwards are where the number grows quietly, because each is small on its own and each multiplies by the seat count. The test before agreeing to any of them is whether every seat needs it or only some, and whether it can be bought for only some.
Agentforce, which is not a seat cost at all
Agent work is billed on consumption rather than per user. Salesforce publishes a Flex Credits rate card, dated 21 April 2026, in which each action an agent performs consumes credits according to complexity, and a voice action consumes more than a standard one. Three models currently coexist: per conversation, credits, and a per user licence. Which one is on your agreement matters more than the rate on any of them, because they behave differently as usage grows.
Sandboxes, storage and API limits
These are bought at the moment they become a problem, which is the worst moment to negotiate anything. A build that will need a full sandbox should establish that during planning rather than during the week it is needed, because it is a line on the order and not a switch.
What actually reduces it
Four levers, and three of them work before signing rather than after.
Discount negotiation is the one everybody reaches for and the weakest of the four, because it operates on a number that has already been decided by the choices above it.
Count distinct jobs, not people
Not everybody who touches a case needs a full Service Cloud seat. Somebody who only reads, somebody who only submits, and somebody who lives in the console all day are three different requirements, and the platform has more than one answer for them. Establishing that before the order is written is worth more than any discount negotiated afterwards.
Ask what happens to the price at renewal
The first term is the negotiable one and the renewal is where the number usually moves. Ask, before signing, what governs the increase and whether there is a cap. A cap agreed at the start costs nothing and is impossible to obtain later.
Do not let an implementation buy licences for you
Whoever builds the system has an interest in it being built on the edition that makes the build easier. That is not dishonest, it is simply a different objective from yours. Keep the licence decision separate, take it after the data model is written, and require the reason for each seat type in a sentence.
Measure usage before every renewal
Last login, cases touched in the last quarter, and console time per user. Three reports, an hour of work, and they are the only evidence that turns a renewal conversation from an opinion into an arithmetic problem.
Why this page has no price table
Every number circulating for the higher editions comes from somewhere other than Salesforce.
That is checkable rather than an opinion. The European product pricing pages were read on 30 August 2026 and returned figures for the entry tier only. The amounts that appear confidently in comparison articles are third party reconstructions, they are not dated, and a budget built on one of them is a budget built on a blog post.
The consumption side is different and better documented: Salesforce publishes a Flex Credits rate card and dates it, currently 21 April 2026, so agent work at least has a stated structure. That is the part of the bill most likely to surprise a finance team, because it does not behave like a seat.
Asked often enough to answer here
Questions
Why can I not find the Service Cloud price on the Salesforce site?
Because only the entry tier is published. Everything above it is routed through a conversation with a salesperson, which is a deliberate commercial choice rather than an oversight. Checked on 30 August 2026: the European pricing pages returned no figures for the higher editions. Every specific number circulating for those editions comes from third party blogs rather than from Salesforce, which is worth knowing before budgeting against one.
Is the licence or the implementation the bigger cost?
Over a single year the implementation usually looks larger. Over three years the licences normally overtake it, because one is paid once and the other recurs and grows with headcount. That is the arithmetic worth doing before choosing an edition, and it is almost never done because the two are quoted by different people at different times.
How is Agentforce billed?
On consumption rather than per seat, under a Flex Credits rate card that Salesforce publishes and dates, currently 21 April 2026. Each action consumes credits according to complexity and a voice action consumes more than a standard one. Three billing models coexist right now, and the one on your agreement decides how the bill behaves as usage grows, which matters more than the headline rate.
Can we reduce the seat count mid term?
Usually not. Seats can be added during a term and reducing them normally waits for renewal, which is why the number agreed at the start is the number that matters. Buying for the team you expect rather than the team you have is a decision to pay for the gap for the whole term.
What does the build cost, separately from the licences?
7,250 euro for 145 hours at the smallest scope on this site: the case model, email to case, queues, reports, up to fifteen agents, training and a sixty day handover. That is a one off number, published rather than quoted, and it is entirely separate from what Salesforce bills you every year.
The build on this site is €7,250 for 145 hours at the smallest scope, which is hours multiplied by fifty and published rather than quoted. What Salesforce charges for licences is between you and Salesforce, and nothing on this page is a commission arrangement with anybody.
Serhii Skrypnyk · Senior Salesforce Administrator and developer · 7 Salesforce certifications · on the platform since 2018. Reviewed 30 August 2026.