Acumen Solutions has no product licence

People search for an Acumen Solutions licence because most names on an acquisition list belong to products. This one does not. Acumen was a consulting firm that implemented Salesforce for public sector, manufacturing and financial services customers, and Salesforce bought it to add delivery capacity. The licence question therefore has a different shape. It is not "what does Acumen cost per user" but "what do I pay Salesforce for software, what do I pay for support and guidance, and what do I pay for people to do the work".

Salesforce's announcement, first posted on 1 December 2020 and updated at close, called Acumen "a leading professional services firm with deep Salesforce knowledge and extensive industry expertise". The close record says: "Acumen Solutions will become part of Salesforce Professional Services, which along with Salesforce partners, helps customers accelerate their time to value." The close was dated 1 February 2021. Everything after that sentence is about how Salesforce sells services, not about a product that was acquired.

#Why there is no Acumen licence

A licence is a right to use software, usually per user per month. Acumen had no software of that kind in this deal. Salesforce's own words place the firm inside Salesforce Professional Services "along with Salesforce partners". So the order form you receive will never have an Acumen product line. If a procurement template insists on one, the template is wrong. The line that exists is a services engagement, scoped by Salesforce or a partner, and it sits beside a licence order rather than inside it.

If someone quotes you an "Acumen licence", ask what they mean. It will turn out to be one of three things: a Salesforce product licence that the Acumen team will configure, a Success Plan, or a services quote. All three are real, and all three have their own pricing logic.

#What you actually license

The projects Acumen used to deliver ran on Salesforce clouds, and those clouds carry published per-user prices. Salesforce's Sales pricing page says that "Sales Cloud pricing follows a per-user, per-month subscription model." It lists five suites, in US dollars per user per month with the Australian dollar view alongside.

Source: Salesforce Sales pricing, read 13 October 2026. The page says it is for information only and subject to change, and that AI can be added to Core and above.

That is one cloud. Service, Marketing, Commerce, Revenue and the industry clouds each have their own page and their own list. A real project often licenses several, and the number to budget is the sum across the roles that will use each one, not the headline price of one edition. The common mistake is to price the cloud for the whole company when only a subset of people will hold a seat.

#Success Plans

The Sales pricing page also lists three levels of support and guidance, and they are where many buyers expect to find an "Acumen" cost, because they are the part of Salesforce that sells expertise by subscription rather than by project.

The Standard Success Plan is "Included in all licenses" and gives self-guided resources. The Premier Success Plan is described as expert guidance, product education, health checks and recommendations, plus access to 24/7 support for business-stopping issues. The page lists its price as three-tenths of net licence fees, and notes it is "Bundled with Unlimited Edition". The Signature Success Plan, with a designated Customer Success Manager, proactive monitoring and the fastest response times, is shown as contact your account executive.

Because Premier is a share of net licence fees, it behaves like a tax on your licence spend. On net fees of $100,000, three-tenths is $30,000. On $400,000, it is $120,000. That is arithmetic on the published rate and says nothing about what discount you will negotiate on the licences themselves, which also lowers the base. It does mean that adding a large cloud mid-term raises the Premier bill, and that cutting seats at renewal lowers it. Ask whether the plan is calculated on list or net, annual or term, and whether it recalculates when you add products.

Notably, the Core suite card on the same page says "Everything in Professional Edition plus Momentum and Premier Success", while the feature grid marks Premier as available for purchase on some suites. Whether your edition includes Premier or sells it separately is a contract question. Do not assume the card is your entitlement.

#Services are scoped and quoted

The Sales pricing page points to two ways to get delivery help: Salesforce Professional Services, described as helping you "realize value quickly and become self-sufficient", and Salesforce Certified Partners, who offer agents, apps and experts. The page sends you to learn-more links for each. Neither is sold from a rate card on that page, and we will not invent a range. An engagement is scoped against the work and quoted.

What goes into a services quote is more useful to know than a guess at its size. Discovery and design come first, then configuration, data migration and cleansing, integrations, testing, training and a post-go-live period. The size of each is driven by how many processes you are changing, how many objects and records you are moving, how many systems you connect and how many users must be trained. The Acumen Solutions and Salesforce services page covers how that work is scoped.

#Contract and renewal mechanics

Salesforce states that "Most Salesforce products use annual contracts, but Salesforce subscription terms vary." On the same page it says you can add products or upgrade at any time, but some products may need to scale together. Three consequences follow for a project budget.

First, licences are usually an annual commitment, so you pay for seats you hold, not seats you grow into. A phased go-live can mean paying for licences before the people have a working system. Ask whether start dates can be staggered or whether a ramp is available. Second, services are not recurring by default. A project fee is a one-off unless you agree a retainer, which is a different instrument. Third, the Success Plan renews with the licences, so a project that doubles your seat count also changes your support bill.

#Right-sizing the licence side of a project

Count roles, not employees. List each persona that will use the system, what they do in it and which licence type that needs. Ask Salesforce whether occasional users can hold a cheaper licence type, since the options differ by cloud and edition. Separate integration users, which are often forgotten, from human users. And decide how many environments you need, since testing and training sandboxes may carry their own charges depending on edition.

Phase the purchase to match the delivery plan. Buying the whole cloud for a pilot of twenty people is a common and avoidable overspend.

#Comparing offers

When you compare quotes, keep three columns. Licences from Salesforce, with the edition, seat count, term and any add-ons. A Success Plan, with the level and the base it is calculated on. And services, from Salesforce Professional Services or a partner, with the scope, assumptions, milestones and what is excluded. A single blended number across the three hides the thing you most need to see: how much is recurring and how much is one-off.

Be wary of a services proposal that buries licence assumptions inside the estimate, or a licence quote that assumes a partner you have not chosen. Each should stand on its own.

#Who is likely reading this page

Three kinds of reader land here. The first is a former Acumen customer who wants to know whether an Acumen contract is still honoured and what it was priced on. The answer sits in that contract, and the acquisition did not turn a services agreement into a licence. Check who the contracting party is now and whether the statement of work is unchanged.

The second is a buyer comparing Salesforce Professional Services with an independent partner for a new project. The decision is not primarily about licence cost, since the licences cost the same whoever delivers. It is about who carries delivery risk, who knows your industry and how the commercial terms are structured. Ask each to describe a comparable engagement and what went wrong in it.

The third is an analyst building a budget who has seen the Acumen name on a list of acquisitions. For that reader the skeleton below is the useful part.

#A budget skeleton for a Salesforce project

Line one is the annual licence total, built from personas and seat counts at the edition you choose. Line two is the Success Plan, calculated from the licence total for Premier or quoted for Signature. Line three is the services quote, built from discovery, configuration, data migration, integration, testing, training and hypercare. Line four is the cost of your own people: the product owner, subject experts, testers and trainers who will spend real time on the project. That fourth line is the one most often left out, and it is often the one that decides whether a project lands on time.

Add a fifth line for run costs after go-live, because the system needs an owner, an admin or managed service, and a release cadence. Keep every line labelled recurring or one-off.

#Questions to ask whoever delivers

Which edition and how many seats of each licence type do you assume? Where are the assumptions about data volumes, integrations and number of processes written down? What is excluded? How are change requests priced, and who approves them? Who owns the configuration if we part ways? Are there named people on the proposal or is the team to be confirmed?

None of those depends on who bought whom. They are the questions that protect a budget whether the delivery team sits in Salesforce Professional Services or a partner.

#Timing the licence and the work

Licences are an annual commitment while a project runs for months, so the order of purchase matters. Buying everything on day one is simple for procurement and expensive for the business. A better pattern is to commit to the discovery and design work first, confirm the edition and seat counts from that design, and then place the licence order shortly before build begins. Salesforce says you can add products or upgrade at any time, so there is little reason to buy ahead of need. Ask your account executive for a written confirmation that the list price you were shown will hold if the licence order follows the design phase by a quarter.

#Where this page stops

This is the licence page, and it exists mainly to redirect a search that does not match a product. For the deal see what happened to Acumen Solutions. For connection questions see integrating Acumen Solutions with Salesforce. For moving off anything Acumen delivered see should you migrate from Acumen Solutions. Delivery scope sits on Acumen Solutions and Salesforce services.

#The short version for procurement

Acumen Solutions was a services firm that joined Salesforce Professional Services on 1 February 2021, so there is no product licence. Budget three lines: Salesforce licences at their published per-user prices, a Success Plan (Premier is three-tenths of net licence fees) and a scoped services quote. Confirm in writing which of those your edition already includes.