Who to hire for Acumen Solutions

People type "Acumen Solutions" into a search box for a few reasons. Some worked with the firm and want the people back. Some saw the name in an acquisitions list and assumed a product sat behind it. Some have a legacy document that mentions Acumen and want to know what to do about it. The honest answer is the same in all three cases and it is short: Acumen Solutions was a professional services firm, and there is no Acumen system to implement, integrate, migrate from or license. This page does not ask you to take that on faith. The close announcement says it in its own words: "Acumen Solutions will become part of Salesforce Professional Services, which along with Salesforce partners, helps customers accelerate their time to value." The announcement was dated 1 February 2021, and an earlier version had been posted on 1 December 2020 when the agreement was signed.

What the announcement does give you is a description of the firm's value, and that description is the real subject of this page. Acumen was "a leading professional services firm with deep Salesforce knowledge and extensive industry expertise across public sector, manufacturing, financial services and more". Anyone searching for Acumen today is, more often than not, looking for exactly that: a firm that understands how Salesforce works in a regulated or complicated industry. That is a legitimate thing to hire for, and the rest of this page shows how to do it without a brand name to lean on.

We have not tried to say what any former Acumen staff member now does, or where they work, because we cannot verify it and would not publish it if we could. Hire against capability and evidence, not a hunch about who moved where.

#Two routes, and no ranking between them

The announcement says Acumen "will become part of Salesforce Professional Services, which along with Salesforce partners, helps customers accelerate their time to value". That sentence names two routes without ranking them, and so will this page. Salesforce's own page for the first route reads: "Implement, innovate, and transform your enterprise with help from Salesforce experts." The other route is the wider partner ecosystem, which ranges from large global integrators to small specialists.

Some buyers use both: Salesforce Professional Services for a first release on a new product, and a partner for run and enhancement. We will not tell you that one is better. The right choice depends on what you are building, which team you are dealing with and what each will commit to in writing. Treat the table as a list of things to ask, not a verdict.

#Match the industry credential to the scope

If the search was really for public sector, manufacturing or financial services delivery, Salesforce publishes industry-specific Accredited Professional credentials, and you can ask for them by name. Trailhead's list includes Salesforce Accredited Agentforce 360 for Public Sector Professional, Salesforce Accredited Agentforce Manufacturing Professional and Salesforce Accredited Agentforce Financial Services Professional. The page describes the financial services one this way: "Accredited Financial Services Cloud Professionals have demonstrated the skills and knowledge to implement the Salesforce Financial Services Cloud." Names have changed over time, so older CVs may use earlier titles such as Public Sector Solutions or Manufacturing Cloud. Ask the individual to show the credential on their Trailhead profile.

Add the architecture credentials when the project is complicated. Trailhead lists Salesforce Certified Application Architect, System Architect and Technical Architect. For work that uses Omnistudio, which many industry implementations do, look for Salesforce Certified Omnistudio Consultant. None of these proves the person has worked in your industry, so the credential is where the conversation starts.

The most useful check of all is dull: ask for the name, the role and the tenure of the person who will lead the work, and ask to speak to a customer in your industry about that same person.

#What changes by sector

The three industries named in the announcement make different demands, and a partner's answers should show it.

In government and the wider public sector, the constraints usually arrive from outside the project: procurement panels, security classifications, accessibility obligations and records laws that decide how long case notes must be kept. A partner who has not worked in that setting tends to underestimate the time that approvals take, so ask them to put the approval steps in the plan, with your staff named against each.

In manufacturing, the difficulty is typically the connection between sales and operations: forecasts, orders, dealer or distributor relationships, warranty and service. Ask how the partner links Salesforce to the enterprise resource planning system, who owns the product and price master, and what happens when a forecast changes mid-quarter.

In financial services, the weight falls on client data, suitability and audit trails. Ask who in the partner's team has handled a regulator's review of a Salesforce implementation, and what evidence they were asked to produce. The answer reveals more than any list of accreditations.

Whatever the sector, ask the same underlying question: what in this industry can stop the project that has nothing to do with software? A partner who answers at once, with examples, has been there before, and one who changes the subject to features has probably not.

#A realistic first engagement for an industry project

Industry implementations go wrong most often when the first phase is too broad. A sensible opening engagement is a paid discovery that produces a scoped plan, not a build. Over a few weeks the partner should:

1. Map your processes in the industry's own vocabulary, such as case types and statutory deadlines in government, or dealer, order and warranty flows in manufacturing.
2. Identify which Salesforce products fit each process, and which parts need configuration versus custom work.
3. Surface the regulatory constraints: data residency, retention, accessibility and procurement rules, which are often decisive in public sector work.
4. Propose a thin first release with a measurable outcome and a list of what is deliberately left out.
5. Produce a plan with named roles, dependencies on your staff, and assumptions that a finance or procurement reader can challenge.

The deliverable is a document you could hand to any firm. If a discovery produces something only the author can deliver, you have been sold a dependency.

#Red flags when someone sells Acumen heritage

• A proposal that treats Acumen as a product, with phases such as "Acumen implementation" or "Acumen data migration". There is no such thing, and the phases will be generic.
• A claim to be "the former Acumen team" or an heir to its practice, with no names, no credentials and no references you can check.
• Senior people in the pitch and no commitment about who will do the work.
• Industry expertise asserted from the website with no named industry credentials among the staff.
• A licence line on an order form that mentions Acumen. There is no such licence.
• A reference list with large brands and no named contact in your industry.
• A fixed price for a phase that has not yet been scoped.

#Ten questions for the interview or RFP

1. Who will lead the work, how long have they worked in our industry, and may we speak to a customer about them?
2. Which industry credentials do the delivery staff hold, and can we see them on Trailhead profiles?
3. Describe the most recent project like ours: the size, the Salesforce products used, the problems you hit and how they were resolved.
4. How do you handle regulatory constraints we face, such as data residency, retention and accessibility? Give an example from our sector.
5. Which parts of this project would you expect to configure, and which to build with code? What drives that split?
6. What will you do about the people and process changes, not just the system? Who from our side must be involved and for how many days?
7. Do you recommend Salesforce Professional Services for any part of this, and why or why not?
8. Which of the team named in your proposal will still be on the project at go-live? How do you handle staff changes?
9. What do you expect to go wrong, and what is the plan when it does?
10. What do we own at the end: documentation, configuration, code, and the knowledge to maintain it?

#References and evidence

Because there is no Acumen case study that proves anything about your hire, ignore any that appear and ask for current evidence. A strong reference is from your industry, at a similar size, within the last two years, and is willing to discuss what went wrong. Ask the reference whether the team they met in the pitch did the work, whether the plan survived contact with their regulator or auditor, and whether their own staff could maintain it afterwards.

Ask the partner for a sanitised project plan and a sanitised set of lessons learned from a similar engagement. Firms that run projects well keep both, and firms that do not tend to find reasons to delay.

#Commercial models and the statement of work

For industry work, a paid discovery followed by a priced build is the least risky structure, because the build price can then rest on a scope you have both seen. For a later release, a fixed price for a well-defined increment suits stable requirements, and a capped time-and-materials arrangement suits uncertainty. Whichever you use, tie payments to deliverables you can inspect, not to calendar dates.

The statement of work should name the Salesforce products and the processes in scope, the roles and the named individuals for lead and architect, the credentials required of them, the regulatory constraints in scope, the acceptance criteria for each release, your own staff's commitments, the knowledge-transfer deliverables, and the process for substituting a named person. We have not put a price on any of this. We found no citable source giving a services cost for industry work, and a made-up range would only mislead you.

#When you can skip a partner

If the need is a small, well-understood configuration, such as adding a field and a report to an existing org, your own administrator can usually do it. A partner earns their fee when the process is industry-specific, regulation shapes the design, or the project is large enough that a mistake would be expensive. And if what you really want is to reconnect with someone you once worked with, a direct conversation, not a search for a firm that no longer exists as a brand, is the faster route.

For the history and the services facts, see Acumen Solutions joined Salesforce services and What happened to Acumen Solutions. For the missing diagram, move, licence and quote, see Integrating Acumen Solutions with Salesforce, Should I migrate from Acumen Solutions, Acumen Solutions Salesforce licence cost and Acumen Solutions Salesforce implementation cost.