What we do in Salesforce
Salesforce is a powerful, flexible platform, but its strength only shows with the right configuration for your processes. We set up objects, fields, deal stages, access rights, Flows, and reports - and where standard functionality isn't enough, we develop in Apex and build Lightning components.
What we work on
- Process configuration - objects, fields, pipelines, access rights, reports, and dashboards.
- Automations - Flows, task assignment, follow-up, and notifications.
- Custom development - Apex classes and triggers, Lightning components, API integrations. See integrations and development.
- Data migration - objects, associations, and history between systems with the data model preserved.
What to know about cost of ownership
Salesforce almost never costs what the plan says. On top of the licence come add-ons, AppExchange apps and administrator time: the platform is rarely configured in-house, and that is normal - it is built for continuous administration.
Messaging is the clearest example. It is not a CRM feature but a paid add-on: without Digital Engagement (75 usd per user per month) you cannot connect WhatsApp. On top of that, the numbers Salesforce provides with the add-on are SMS-only - for WhatsApp you bring your own. If your customers talk to you in messengers, that budget line appears immediately.
Migration and the data model
The hard part of moving in or out of Salesforce is not the volume of data but the model. Salesforce uses Account, Contact and Opportunity, while most simpler CRMs use lead, contact, deal. Fields do not map one to one and some records have to be rebuilt. So we agree the field mapping before the migration rather than during it. A worked example: Salesforce to Kommo.
When Salesforce is overkill
We say so when the platform is not needed. Salesforce is justified with complex processes, many roles and permissions, in-house development and someone to run the system. If the job is to collect enquiries from messengers and keep a clear pipeline, Kommo is cheaper and faster. For marketing and reporting, HubSpot. For a simple sales pipeline, Pipedrive. See the CRM comparison.
Other systems
Besides Salesforce we implement Kommo, HubSpot, and Pipedrive. Still choosing a system? See the CRM comparison.
FAQ
What does Salesforce implementation include?
Configuration for your processes: objects and fields, deal stages, access rights, Flows and automations, reports and dashboards. When standard functionality is not enough - we develop in Apex and build Lightning components.
Do you do custom Apex development?
Yes. We write Apex classes and triggers, build Flows, develop Lightning components and API integrations for tasks that standard configuration can't cover.
Can we move off Salesforce to another CRM?
Yes. We map the Salesforce data model and transfer objects, associations, and history into the target system. See the article on Salesforce data-model migration for detail.