Salesforce® consulting services is not a single category. A company that needs its Sales Cloud org configured with custom objects and approval workflows is buying something entirely different from a company that needs Marketing Cloud Journey Builder automation or a Revenue Cloud CPQ implementation. Confusing them during vendor selection is how projects stall, go over budget, and get handed off in an unmaintainable state.
This guide maps the full taxonomy of Salesforce consulting services available in 2026: what each service line covers, what skills it requires, what it typically costs, and which engagement models work best.
The 7 service lines
1. Org setup and configuration
What it covers: initial Salesforce org setup — user management, permission sets, role hierarchy, custom objects and fields, page layouts, validation rules, approval processes, and automation using Flow. This is primarily declarative work, meaning no custom code.
What it requires: Salesforce Platform Administrator certification (a real signal here, not just a title), deep understanding of the sharing model and visibility rules, and experience with common implementation pitfalls: over-customization of the data model, permission set sprawl, and automation conflicts.
What it costs: $5,000-$40,000 for an initial org setup depending on object complexity, user count, and the number of custom processes required. Smaller additions (a new object, a new approval process) are typically scoped at $1,000-$5,000.
Red flags: no visible admin certification, inability to explain sharing rules vs permission sets, proposing Apex code for logic that Flow can handle natively.
2. Apex and Lightning Web Component development
What it covers: custom code development on the Salesforce platform — Apex triggers, Apex classes, batch jobs, LWC components, and custom UI built within the Salesforce ecosystem. This is for business logic or UI requirements that cannot be met declaratively.
What it requires: Salesforce Platform Developer certification, Apex proficiency (governor limits, bulkification patterns, test class coverage), LWC and JavaScript, and clear judgment about when to use code vs declarative automation.
What it costs: $15,000-$100,000+ for complex Apex development projects. Custom integrations via Apex, bulk data processing jobs, and complex UI in LWC are the most common examples.
Red flags: test class coverage below 85%, inability to explain bulkification, using Apex for logic that Flow handles natively, no mention of governor limits during the design conversation.
3. Marketing Cloud
What it covers: Salesforce Marketing Cloud implementation and configuration — Journey Builder for lifecycle automation, Email Studio, Mobile Studio, Advertising Studio, and Data Cloud integration. SFMC is a separate product from core Salesforce with its own data architecture, AMPscript templating language, and contact model.
What it requires: Marketing Cloud-specific certifications (Marketing Cloud Administrator, Marketing Cloud Developer), hands-on experience with SFMC's contact and data extension model, AMPscript or SSJS for dynamic content, and integration experience connecting SFMC to core Salesforce via Marketing Cloud Connect or API.
What it costs: $20,000-$150,000 for a meaningful SFMC implementation depending on channel count, Journey complexity, and integration depth.
Red flags: Sales Cloud experience presented as SFMC qualification, no AMPscript examples, inability to explain SFMC's contact model vs Salesforce's lead and contact model, no mention of sender authentication (SPF/DKIM/DMARC) in any deliverability discussion.
4. Revenue Cloud
What it covers: CPQ (Configure, Price, Quote) and billing implementation — product catalog setup, pricing rules, quote templates, approval workflows, contract management, and revenue recognition. Revenue Cloud consolidates what was previously sold as Salesforce CPQ under a unified billing and revenue model.
What it requires: Revenue Cloud certification, deep understanding of product hierarchy and pricing logic, experience with complex quote approval processes, and integration with ERP for order management and invoicing.
What it costs: $40,000-$200,000+ for a full Revenue Cloud implementation. CPQ complexity scales directly with product catalog size, pricing rule count, and approval workflow depth.
Red flags: no Revenue Cloud certification, proposals that undercount integration scope (Revenue Cloud almost always connects to ERP, adding significant complexity), no mention of data migration from existing quoting tools.
5. Commerce Cloud
What it covers: Salesforce B2C Commerce (formerly Demandware) for consumer retail and B2B Commerce for wholesale and business buyer portals. Each uses a separate technology stack. B2C Commerce uses SFRA (Storefront Reference Architecture) with custom cartridges; B2B Commerce is natively built on the Salesforce platform.
What it requires: B2C Commerce requires SFRA experience, JavaScript controller and template patterns, and cartridge development. B2B Commerce requires core Salesforce platform skills plus B2B Commerce configuration.
What it costs: $80,000-$400,000+ for a full Commerce Cloud implementation depending on catalog complexity, custom features, and integration depth.
Red flags: B2C and B2B Commerce treated as equivalent (they are fundamentally different products), no cartridge examples for B2C work, no integration plan for catalog, pricing, or order management systems.
6. Integration development
What it covers: connecting Salesforce to external systems — ERP (SAP, Oracle, NetSuite), marketing platforms, data warehouses, external databases, and custom systems. Integrations move data reliably, handle failures, and maintain data consistency across systems of record.
What it requires: Salesforce API knowledge (REST, SOAP, Bulk, Streaming APIs), understanding of the target system's API, middleware architecture (MuleSoft, Boomi, Informatica, or custom), and production experience with failure handling and monitoring.
What it costs: $10,000-$80,000 per integration depending on data volume, transformation logic, and reliability requirements.
Red flags: no mention of idempotency or failure handling, no API rate limit strategy, no monitoring plan, inability to explain the tradeoffs between REST vs Bulk API for large data volumes.
7. Managed services
What it covers: ongoing stewardship of a Salesforce org after go-live — user support, configuration changes, new feature implementation, platform update testing, security review, and performance monitoring. Managed services is not a project with an end date; it is a subscription.
What it requires: broad Salesforce platform knowledge across the service lines relevant to the client's implementation, proactive monitoring capability, and a defined SLA for issue response.
What it costs: $2,000-$20,000/month depending on org complexity, user count, and SLA requirements.
Red flags: managed services sold as a project with a defined end date, no proactive update monitoring, no defined escalation path for production issues.
Buyer journey: when do you need a consultant?
The trigger for engaging Salesforce consulting services is almost never "we want to implement Salesforce." It is usually one of:
- Initial implementation: moving off spreadsheets, a legacy CRM, or a disconnected stack to Salesforce for the first time
- Major expansion: adding a new cloud (Sales Cloud to Marketing Cloud, core CRM to Revenue Cloud CPQ)
- Technical debt cleanup: an existing org that has accumulated years of conflicting automation, unused custom objects, and permission set sprawl
- Integration project: a new system — ERP, e-commerce, data warehouse — that needs to connect to Salesforce
- Platform update response: a major Salesforce release that breaks existing customizations or enables new functionality worth adopting
Engagement models
Project-based: Fixed scope, defined timeline, clear handoff. Works when the requirement is well-defined and the in-house team can maintain the output after handoff. Risk: the handoff often fails because the internal team was not involved during the build.
Retainer and managed services: Monthly contracted hours or a defined SLA. Works for orgs with a continuous backlog — new features, bug fixes, user requests — and no in-house Salesforce developer. Best for companies that have already implemented and need ongoing stewardship.
Staff augmentation: A Salesforce consultant embedded directly in the client's team for a defined period. Works when the internal team has Salesforce knowledge but needs additional capacity for a specific project or expansion.
Typical timeline and cost by project type
| Project type | Timeline | Cost range |
|---|---|---|
| Initial Sales Cloud setup (50-100 users) | 6-12 weeks | $20,000-$60,000 |
| Marketing Cloud implementation (3-5 journeys) | 8-16 weeks | $30,000-$80,000 |
| Revenue Cloud CPQ (medium catalog) | 12-24 weeks | $60,000-$150,000 |
| ERP integration (NetSuite or SAP) | 8-20 weeks | $30,000-$100,000 |
| Org cleanup and technical debt | 4-8 weeks | $15,000-$40,000 |
| Managed services (ongoing) | Continuous | $3,000-$12,000/month |
The Sapota team covers Salesforce consulting services across org setup, Apex and LWC development, Marketing Cloud, and integration work. If you want to discuss your project or get a second technical opinion on a proposal, reach out to the team.
