Acumen Solutions implementation cost: buying Salesforce services today

People still search for Acumen Solutions implementation costs, usually because the name appears in an old proposal, an architecture diagram, or a former consultant's CV. The answer is simple, and then the useful part begins.

Acumen Solutions was not software. Salesforce described it as a professional services firm with deep Salesforce knowledge and industry expertise across the public sector, manufacturing, financial services and more. When Salesforce closed the acquisition in 2021, it set out where the firm would go: "Acumen Solutions will become part of Salesforce Professional Services, which along with Salesforce partners, helps customers accelerate their time to value."

So there is no Acumen product to license, configure or migrate. What a buyer actually needs to know is how Salesforce services are bought today: from Salesforce Professional Services, the group Acumen joined, or from a Salesforce partner. This page explains how those engagements are priced and how to compare quotes, without inventing rates that nobody publishes.

For the history of the firm, read what happened to Acumen Solutions. For the services Acumen used to offer and where that expertise sits now, see Acumen Solutions Salesforce services.

#What Salesforce publishes, and what it does not

Salesforce's Success Plans and Professional Services pricing page is the single public source. As at October 2026 it lists three Success Plans and one Professional Services offer.

Three points from that page are worth reading closely.

Premier is tied to what you spend on licences, not to how much help you use. The page states the share as a proportion of net licence fees, so a larger contract buys a larger Premier fee automatically. It also says Premier is bundled with Unlimited and Agentforce 1 editions. Before buying Premier separately, check whether your edition already includes it. Some newer editions do: Salesforce's Sales pricing lists Premier Success inside Sales Cloud Core.

Success Plans and Professional Services are different things. The page's own FAQ separates them: Success Plans give support, guidance and expertise; Professional Services are "comprehensive advisory and implementation services". It also says the two are commonly combined: "Many of our customers work with Professional Services on a project while they have a Success Plans in place." A support plan is not a substitute for a project team, and a project team does not replace support after go-live.

Professional Services has no published rate. The page invites you to contact sales and says the work is tailored. That is normal for consulting, and it is also how every partner prices. Nobody can give you a credible number for "a Salesforce implementation" without a scope.

#What the support tiers actually buy

Because Success Plans are the only published price in this area, they are worth understanding before anyone talks about project fees. The pricing page compares them on response times and developer help. Its technical support row runs from a two-day response for all customer support inquiries, through a one-hour response for business-stopping issues, to a 15-minute response for business-stopping issues at the top. Its developer support row lists custom code troubleshooting up to 200 lines, and up to 5,000 lines with deployment guidance at the higher level.

Those lines tell you what support is for: keeping a live org healthy and getting help when something breaks. They do not tell you who designs a new process, writes the migration scripts, or trains your sales managers. That is project work, and it is quoted separately whether it comes from Salesforce or a partner.

The decision that saves the most money is matching the support tier to how critical the org is. A small internal org that can tolerate a slow fix does not need the fastest response time. A contact centre running on Salesforce around the clock probably does. Make that choice deliberately, and write it down, rather than letting it follow the licence contract by default.

#How a services quote is built

Whether it comes from Salesforce Professional Services or a partner, a services quote is assembled from the same parts. Knowing them lets you read any proposal.

Scope. The list of capabilities to be delivered: which clouds, which processes, which integrations, which data, which users. Everything else in the quote is derived from this, so it should be written in your words, not the vendor's.

Work packages. Discovery, solution design, build, data migration, integration, testing, training, cut-over and hypercare. Each should be visible as its own line, even if the price is fixed overall.

Roles and effort. Who will do the work: an engagement lead, a solution architect, consultants, developers, a data specialist, a test lead, a change lead. A credible quote names the roles and estimates their effort per package. You do not need anyone's rate to see whether the effort profile makes sense.

Commercial model. How the price behaves when reality differs from the plan. Fixed price, time and materials, capped time and materials, and ongoing managed service each move risk in a different direction.

Assumptions and exclusions. The most important pages in any proposal. Assumptions say what the vendor expects from you: data ready by a certain date, decisions within a set number of days, test users available. Exclusions say what is not included: licences, environments, third-party tools, legal review, training beyond a set number of sessions.

Change control. How changes to scope are requested, estimated and approved. Without a written process, every disagreement becomes a commercial dispute.

#Commercial models compared

A common and sensible pattern is a short time and materials discovery that produces a written design, followed by a fixed or capped build quoted against that design. It costs a little more up front and usually saves money overall, because the build quote is based on decisions rather than guesses.

#Salesforce Professional Services or a partner?

Both are legitimate choices, and Salesforce itself presents them as working together. Its own page answers the question directly: both bring valuable expertise. Professional Services offers direct access to people close to the product teams, and positions itself for complex, high-impact work; certified partners, in Salesforce's words, "deliver flexible, scalable solutions across industries". The same answer adds that most customers use both.

In practice, the choice turns on a few questions. Is the work at the edge of what the product does today, where direct access to product knowledge matters? Then Professional Services may be worth it. Is the work well understood, in your industry, and better served by a team that knows your region and will still be around for small changes in two years? A partner may suit better. Do you want both, with Salesforce providing architecture assurance and a partner delivering? That combination is common on large programmes.

What matters for cost is that you compare like with like. A Professional Services proposal and a partner proposal can only be compared if both quote the same scope, the same assumptions and the same exclusions.

#How to get comparable quotes

Write a request that any firm could price without a meeting. It should include the business outcomes, the processes in scope, the number and type of users, the systems to integrate and how, the data to migrate with volumes, the environments you already have, the go-live window, and the decision-makers who will be available.

Ask every bidder the same questions. Which work packages are in your price, and which are excluded? What roles will work on the project, and how much effort does each package carry? What do you assume we provide, and by when? How many test cycles are included? How much training, for whom? What hypercare is included and for how long? How are changes estimated and approved? Who from your side will still be there after go-live?

Then lay the answers side by side. The cheapest bid is often the one with the longest exclusions list, and the most expensive is sometimes the only one that included data migration. Comparing total cost against the same scope is the only fair test.

#If you inherited an org built by Acumen

Many organisations that ask about Acumen Solutions are not starting a project at all. They are running an org that Acumen designed years ago, and the people who built it have moved on. The cost question there is different: what will it take to understand, stabilise and modernise what is already live?

The usual first step is a fixed-scope review. A reviewer reads the configuration, automation, custom code, integrations, security model and data quality, and produces a written report with a prioritised list of fixes. Because the scope is bounded, it can be quoted as a fixed price, and it gives you the evidence to ask for remediation quotes that are based on facts rather than assumptions.

Expect the review to find a few common patterns in older orgs: automation built in tools that Salesforce has since retired, integrations that rely on a single named user, and custom code written for a version of the platform that is now several releases old. None of these is a crisis, but each is easier and cheaper to fix on a plan than in the middle of an outage.

Ask for the review report to separate three kinds of finding: things that are risky now, things that will block your next project, and things that are merely untidy. Only the first two belong in the remediation budget this year. The third can wait for routine administration, and treating it that way keeps the follow-on quote honest and small.

#Costs that sit outside every services quote

Licences. Services firms rarely include licence costs, and they should not. Licences come from Salesforce on separate contracts with their own terms.

Success Plan uplift. If Premier is not bundled with your edition, it is an additional charge tied to net licence fees. Budget it alongside the licences.

Environments. Full Copy sandboxes, extra storage and additional testing environments are licence items, not services. Check what your contract includes before the project needs them.

Your own people. Product owners, subject matter experts, testers and trainers from your business will spend real time on the project. That cost never appears on a proposal and often decides whether the project lands.

Change management. Communications, training refreshers and support for managers through the first months. Many proposals include a small amount; most organisations need more.

After go-live. Administration, small enhancements and release management continue indefinitely. Decide early whether that is in-house, a managed service, or support from your Success Plan.

#Where to go next

If you are choosing a delivery firm, read hiring a Salesforce partner after Acumen Solutions. The licence cost page explains why there is no Acumen licence and what you would license instead. The integration page covers integration work that used to sit with services firms like Acumen, and should I migrate from Acumen Solutions helps if an old Acumen-built org is still running.

The short version: there is no Acumen bill to estimate. There is a Salesforce services engagement, built from scope, roles, a commercial model and a list of exclusions, and it can be priced fairly once those are written down.