Platform
Salesforce integration and automation
Salesforce can model almost any customer process, which is its strength and its risk. We connect Salesforce to the systems around it, automate what people repeat, and help organizations keep their set-up understandable.
- 1,200+ clients helped
- Building since 2010
- 15 services, one team
- 50+ technologies
At a glance
What it is
Salesforce is a customer platform used by larger and more complex organizations, with deep customization for sales, service, and custom business processes.
Problems it solves
Salesforce implementations drift into complexity: custom fields nobody uses, overlapping automations, and integrations that break when either side changes.
Who it suits
Organizations that run Salesforce and need it connected to other systems, and teams whose set-up has become hard to change.
How to choose
Keep Salesforce simple, document every customization, and connect it to other systems through a small number of well-owned integrations.
What it means
A platform you shape to your process
Salesforce is a CRM (customer relationship management) platform, a shared record of customers and deals, that can be extended with custom objects, automation, and applications. Organizations use it for sales, service, and increasingly for processes that go beyond customer management.
Its breadth suits complex organizations: many teams, regions, products, and approval steps. It is also why a Salesforce set-up needs governance. Anyone with access can add a field or a rule, and over the years those pile up.
Most of the problems we see are not about Salesforce itself. They are about customization nobody documented and integrations nobody owns.
What DECHY can do
Working with Salesforce
Connect
- Links to finance, billing, products, and marketing tools.
- Use of the Salesforce API (the way other programs read and change its records) and standard connectors.
Automate
- Flows for approvals, hand-offs, and reminders.
- Clean-up of overlapping automations.
Review
- Audits of fields, rules, and permissions.
- A plain list of what to remove, merge, or document.
Migrate
- Moves from spreadsheets or other CRMs.
- Data cleaning and mapping before cut-over.
Options
Salesforce compared with other CRMs
Suits
Complex organizations with many teams, custom processes, and a budget for administration.
- Trade-off
- Cost and complexity, and a need for skilled administration.
Suits
Small and mid-sized teams who want to adopt quickly.
- Trade-off
- Less deep customization for unusual processes.
Zoho
Suits
Cost-conscious teams wanting a broad suite.
- Trade-off
- Smaller partner and talent ecosystem.
Suits
Very unusual processes that no product fits.
- Trade-off
- Highest cost, and you maintain everything.
How we work
Connecting Salesforce to your other systems
Map the data
We list which system owns each piece of data, such as customer details, prices, and payment status, and where each must appear.
What it produces
- Data ownership map
Choose the connection
We choose between built-in connectors, an automation platform, and a custom integration, based on volume and risk.
What it produces
- Integration design
Build with failure in mind
We handle duplicates, retries, and limits, and decide what happens when one side is unavailable.
What it produces
- Working integration
- Error handling
Test and monitor
We test with realistic data, and set up alerts so a broken sync is noticed within hours.
What it produces
- Test results
- Alerts
Document and hand over
We document the integration and its owner, so it survives staff changes.
What it produces
- Integration guide
Choosing the right approach
Customization has a carrying cost
Every custom field, rule, and integration is something to maintain, test at each platform release, and explain to new staff. The cheapest customization is the one you decide not to build.
We use standard features first, and add custom code only where the standard options would force a worse process.
Technical depth
How we build with Salesforce
What we settle early on Salesforce work: integration patterns, reliability, and security, so nothing surprises your team later.
We choose between request-and-response calls, event messages, and scheduled batch syncs depending on volume and how fresh the data must be, and respect API limits and bulk interfaces.
- External identifiers on records, so repeated messages update instead of duplicating.
- Queues and retries for outages on either side.
- A sandbox for testing, with a repeatable deployment process.
- Every custom field and automation documented, so the next administrator knows why it exists.
- Integration users with the minimum permissions they need.
- Credentials held in a secrets store, and rotated.
Common questions
Questions about Salesforce
Can you work with our Salesforce administrator?
Yes, and we prefer to. We work alongside administrators, and leave documentation so the knowledge stays in your team.
Can you connect Salesforce to our own software?
Yes. We build integrations through the platform's standard interfaces, with clear ownership of each piece of data, tests with realistic data, and alerts when a connection fails.
Should we change CRM?
Only if the cost or complexity of the current set-up outweighs the cost of moving. We assess this honestly, and often recommend simplifying what you have.
Do you resell Salesforce or hold certifications?
We do not claim partner status or certification with Salesforce. We work with the platform as a technology, and recommend it only where it fits.
Have a different question?
Tell us what you are weighing up and we will answer it plainly.
Ask a questionAlready a client? Email support@dechytech.com
Tell us which systems must share data
Describe your Salesforce set-up, the systems around it, and where the pain is. We will review it and recommend the smallest useful fix.