FAQ

Frequently asked questions

Answers to the questions CRM Unity hears most before a Salesforce engagement starts. For a question about a specific cloud or service, see that service's page — each has its own FAQ.

Cost & engagement model

How much does a Salesforce implementation cost?

Salesforce implementation cost depends on scope: how many clouds are involved, how much custom development and integration work is required, and how much data needs to migrate. CRM Unity doesn't publish a flat rate, and doesn't price by the hour either — every project is scoped and quoted as a fixed price for a fixed outcome. That's deliberate: hourly billing creates an incentive to run up hours, while a scope-based price ties what you pay to the business outcome delivered, not the time it took to get there.

How much does a Salesforce consultant cost per hour?

CRM Unity doesn't price by the hour. Every engagement, project or retainer, is scoped and quoted before work starts, after CRM Unity has actually looked at your org. That avoids the incentive an hourly rate creates to bill for time instead of outcomes.

What's the difference between project-based and retainer Salesforce consulting?

Project work is a fixed scope, timeline and price for a defined outcome, like an implementation or an integration. Retainer work is dedicated monthly capacity for ongoing enhancements, admin support and quarterly strategy once you're live. Most clients start with a project and move to a retainer once the org is stable.

How long does a Salesforce implementation take?

Timeline depends on the same factors as cost: scope, number of clouds, integration complexity, and data volume. A narrowly scoped project can move in weeks; a multi-cloud implementation with several integrations takes longer. CRM Unity sets a fixed timeline as part of every project quote, once the scope is defined.

Do I need this?

Do I need a Salesforce consultant or can my admin handle it?

A capable in-house admin can usually handle day-to-day configuration, but architecture decisions, complex integrations and multi-cloud implementations benefit from someone who has built them before. A common pattern is bringing in an architect for a scoped project or an org audit, then handing a documented system back to your admin to run.

When should a company hire a Salesforce architect?

The clearest signals are a Salesforce org that's grown past what ad hoc configuration can safely support, a project involving more than one cloud or a non-trivial integration, or a plan to build custom automation that will be hard to unwind later if it's built wrong the first time. An architect is most valuable before those decisions are made, not after.

Selection criteria

How do I choose a Salesforce consulting partner?

Look at who will actually do the work, not just who sells it. Ask whether the person scoping the engagement is the person building it, how they price (by the hour vs. by scope), and whether they'll hand you documentation you could use with a different consultant later. A partner confident in their work won't need to lock you in.

What should I ask a Salesforce consultant before hiring them?

Ask who specifically will do the work and what their background is, how they price and what happens if the scope changes mid-project, whether they document their work, and what a typical engagement looks like end to end. Vague answers to any of those are worth noticing.

Is a small Salesforce consulting firm better than a large systems integrator?

It depends on what you need, but for most mid-size orgs a small firm removes a layer most large systems integrators keep: the account manager or junior delivery team between you and the person actually doing the work. At CRM Unity, the two people who scope an engagement are the same two people who build and run it.

What certifications should a Salesforce consultant have?

At minimum, certifications relevant to the clouds involved in your project, Sales Cloud, Service Cloud, Experience Cloud, Field Service, or Financial Services Cloud consultant credentials, plus Platform Developer credentials for custom-code-heavy work. Certifications confirm baseline platform knowledge; ask for real project examples to confirm applied experience.

Have a technical question instead? See Agentforce, org audits, Experience Cloud, integrations, and Process Builder to Flow migration for FAQs specific to each.

Still have a question? Talk to us →