You're not buying software. Here's what you're actually buying.
Most organisations come to Salesforce trying to solve a specific problem. The sales team needs a better way to manage pipeline. The service team is drowning in email and needs a case management system. A business unit has a workflow problem and someone has identified Salesforce as the solution. That's a perfectly reasonable way to start, and there's nothing wrong with it.
The problem doesn't emerge with the first purchase. It emerges with the second and third.
This article is for the buyer who wants to understand what they're actually purchasing before they sign — not in technical terms, but in commercial ones.
The platform problem nobody warns you about
The first Salesforce purchase in most ANZ organisations is a business unit decision, made to solve a business unit problem. Procurement may be involved to negotiate price. Architecture may or may not be consulted. But the framing is almost always tactical: we have a problem, Salesforce solves it, let's buy it.
That's fine. The issue is that the second and third purchases happen the same way — by a different business unit, through the same tactical procurement lens, often without any visibility into what the organisation already has. Enterprise functions like procurement and architecture are frequently unaware of the first or second purchase, or aware but not engaged. Each decision is reasonable in isolation. Nobody is making a bad call at the time they make it.
What nobody flags is that by the time you're on your second or third Salesforce purchase, you are no longer in a software conversation. You are in a platform conversation — whether you realise it or not. You have multiple contracts, multiple instances, multiple sets of data that don't talk to each other, and multiple renewal cycles that are now out of sync.
The moment of reckoning is always painful. It's usually driven by finance or procurement — sometimes in partnership with architecture — when someone finally looks across the organisation and realises they're paying for three separate Salesforce contracts out of three separate cost centres. Bringing those contracts together commercially is difficult. Migrating the separate instances technically is costly and disruptive. And once you've started asking whether to consolidate, you've walked straight into one of the most complex debates in Salesforce governance: single org versus multi-org, and whether the pain of consolidation is worth it.
Most organisations that reach this point experience paralysis. The right answer is usually clear in principle and almost impossible to execute cleanly in practice.
The way to avoid it is not to second-guess the first purchase — that was the right call. It's to recognise, at the point of the second purchase, that the conversation has changed. That's when platform thinking needs to enter the room.
What a Cloud actually is
Salesforce organises its products into Clouds — Sales Cloud, Service Cloud, Marketing Cloud, and others. The plain-English version: each Cloud is a packaged application built for a specific business job. Sales Cloud is built for pipeline management, forecasting, and opportunity tracking. Service Cloud is built for case management, knowledge bases, and customer support workflows. They are different products, not different features of the same product.
This matters commercially because you buy capability, not just access. Sales Cloud Enterprise and Service Cloud Enterprise are different licences at different price points, and what you can do in one is not what you can do in the other. Organisations that assume they can handle service workflows inside Sales Cloud — or vice versa — typically discover the limitation when they're already committed to a contract.
The newer consumption-based products — Data Cloud and Agentforce — sit alongside Clouds rather than within them. They add a usage-based billing layer on top of whatever Cloud licences you hold, which introduces a different commercial dynamic that we'll come back to.
Editions: engine size, not just feature lists
Within each Cloud, Salesforce offers multiple editions — typically Starter, Pro, Enterprise, and Unlimited. The useful way to think about editions is as engine sizes: they determine not just what features you have access to, but how much operational capacity you're buying. Sandboxes for development and testing, data storage, API call limits — these all vary by edition and they matter more than most first-time buyers realise.
Enterprise is the most common choice for ANZ mid-market organisations. It gives development teams what they need — full customisation capability, a reasonable sandbox allocation, meaningful data storage — without the premium of Unlimited.
Here is something that doesn't get said clearly enough: you can upgrade editions and it is relatively straightforward to do so. But you cannot downgrade. The only way to move from a higher edition to a lower one is to replatform entirely — migrate your data, your configuration, your integrations — which is a significant and costly exercise. In practice, it doesn't happen.
This asymmetry matters because there is a commercial incentive for account executives to sell the higher edition from the start. The upgrade path is easy, which makes a higher edition sound like a reasonable hedge against future growth. But if your actual requirements would be well served by Enterprise, buying Unlimited from day one locks you into the higher cost permanently, with no practical exit.
The right approach is to buy for your actual current and near-term requirements. If you outgrow the edition, upgrading is genuinely low-friction. Starting higher than you need has no equivalent correction.
The licensing layer that confuses almost everyone
The base Cloud licence is the starting point, not the complete picture. What a user can actually do in Salesforce is determined by a stack of decisions: the user licence type, any feature licences added on top, and permission sets that control access within those licences.
Most first-time buyers encounter this when they look at a quote and see line items they don't recognise. A Sales Cloud Enterprise user licence is one thing. Additional feature licences for specific capabilities are another. Permission set licences for products like Einstein are another again. The total is often more than the base licence cost implied.
The honest observation is that most first-time buyers sign without fully understanding what each line item does. They're often guided through the quote by a Salesforce partner or consultant — whose commercial interests may or may not be fully aligned with the buyer's — or by their own technical team doing their best with limited context. Understanding comes later, usually when something doesn't work the way they expected and they find out why.
The practical advice is simple: before you sign, ask for a plain-English explanation of every line item on the quote. What does this licence allow? What does it prevent? What would I need to add if I wanted to do X? Those questions are not unreasonable, and a good account executive or partner should be able to answer them without hesitation.
Contracts: the one thing almost nobody reads
Salesforce order forms are straightforward documents — typically one or two pages. The commercial terms are basic enough that most organisations sign without deep scrutiny. Legal may review the underlying terms and conditions; most business stakeholders don't.
The thing that almost nobody notices at signing is the renewal uplift clause. Buried in the terms is a provision that allows Salesforce to increase pricing at renewal by a defined percentage — typically in the range of 3–7%, though this is negotiable (verify current terms with Salesforce directly). At signing, that clause feels abstract. The renewal is two or three years away, and there's enough to focus on getting the initial implementation right.
The problem is that the uplift is negotiable at signing and not negotiable at renewal. By the time you're sitting in a renewal conversation, the clause is the clause. Customers who understood this at the beginning and pushed back on the uplift rate — or negotiated a cap — are in a fundamentally better commercial position three years later than customers who didn't.
Read the renewal uplift clause. Negotiate it before you sign. When that renewal conversation eventually arrives, Salesforce Renewal: Where to Start covers the preparation principles that apply to every contract type.
The commercial mistake that costs the most
The single most expensive mistake a first-time Salesforce buyer makes is one that happens before implementation even begins: buying at full production capacity from day one.
Account executives are incentivised to maximise the initial contract value. The natural pitch is to size the licence for where the organisation will be at full deployment — full user count, full feature utilisation, production-ready capacity. That sounds like prudent planning. In practice, most ANZ mid-market organisations spend twelve to eighteen months in development and configuration before they go live in production. During that period, they're paying for production-scale licences they cannot yet use.
There are better ways to structure the contract. A ramp deal, for example, lets you commit to a three-year term but start at development-scale numbers and step up to production numbers at an agreed point — typically month twelve or eighteen. The per-unit cost may be slightly higher than a flat deal at production volumes, but the total cost of ownership over the term is lower because you're not paying for capacity you can't use in the early phase.
This is not a complicated negotiation. Salesforce does ramp deals regularly. But it requires the buyer to understand the option exists and to ask for it before the contract is signed. Nobody will volunteer it unprompted.
What a CFO actually needs to understand
Commercial leaders don't need to understand Salesforce technically. What they need to understand is where the value is and where the exposure is.
The value case is straightforward: Salesforce is a platform investment, and platform investments compound. Getting the right foundation — right edition, right Cloud, right contract structure — makes everything that follows cheaper and more effective.
The exposure sits in three places. First, overbuy at the start — too high an edition, too many licences at production volume before you're in production. Second, the renewal uplift that was never negotiated. Third, the consumption layer — Data Cloud, Agentforce — which introduces variable costs alongside the fixed seat costs, and requires active monitoring to avoid budget surprises.
The organisations that get the most commercial value from Salesforce are the ones that treated the initial purchase as a deliberate platform decision, not a tactical software buy. They bought for their actual requirements, structured the contract for how they'd actually use the system in the first two years, and read the renewal clause before they signed.
That is genuinely all it takes to avoid most of what goes wrong.
Mike Roberts spent over eight years at Salesforce, including time as a Strategic Account Director, before founding Aequus Consulting. He works with New Zealand organisations on Salesforce licence optimisation and renewal preparation, with no vendor affiliations.