The systems that run sales, service, claims and finance, kept current and connected.
We implement, upgrade and run Salesforce, Microsoft Dynamics 365, TriZetto Facets and ERP platforms. We also wire them to your identity provider and your data platform, because that is where most enterprise projects quietly break.
Enterprise platforms are the packaged systems a company runs on.
Think CRM, ERP and, for a health plan, payer administration. Cohash implements and upgrades Salesforce, Dynamics 365, TriZetto Facets and ERP systems and builds the integrations between them. We also connect each one to your identity provider and your data warehouse. When a vendor ships a release, we read the notes and tell you what changes in your org.
From the first call to a setup your own team can run.
Here's what usually prompts a call about your Enterprise Platforms, what we do about it and in which order, and where you end up.
01 · where it hurts02 · what we change03 · where you end up
incident board · enterprise platforms3 open
openOne customer, three addresses. Salesforce, Dynamics 365 and the ERP each hold a different one.
recurringEach seasonal release ends in a scramble to work out what just broke in production.
blockedAccess to CRM and ERP is still granted by an admin working from a spreadsheet.
exposure
CRM implementation and rescueRelease readinessHealthcare payer administrationERP and finance systemsIdentity at the platform edgePlatform data into the warehouse
ready to hand over
Every address field now has one owning system, and the others copy from it.
Each release arrives with a known test list and a named owner for each risk.
chapter 01 · where it hurts
Why teams reach out
One customer, three addresses. Salesforce, Dynamics 365 and the ERP each hold a different one.
Each seasonal release ends in a scramble to work out what just broke in production.
Access to CRM and ERP is still granted by an admin working from a spreadsheet.
chapter 02 · what we change
How we solve it
CRM implementation and rescue
Release readiness
Healthcare payer administration
ERP and finance systems
Identity at the platform edge
Platform data into the warehouse
chapter 03 · where you end up
What changes
Every address field now has one owning system, and the others copy from it.
Each release arrives with a known test list and a named owner for each risk.
what we do
Where we spend the hours
7 areas of work, each one done by an engineer who has run it in production.
Salesforce and Dynamics 365 builds, plus clean-up of orgs that grew through years of unmanaged customization.
Check each Salesforce seasonal release and each Microsoft service update against your configuration. Out of that comes a short list. What to test. What to switch off.
Configuration and integration on TriZetto Facets, plus the data work. That covers the FHIR APIs that CMS interoperability rules require.
Dynamics 365 Finance, Business Central and SAP integration work, with data migration planned around your close calendar.
We set up single sign-on and SCIM provisioning and design the permissions, so CRM and ERP access comes from your identity provider. Nobody grants it off a spreadsheet.
CRM, ERP and claims data landed in Snowflake, Databricks or Microsoft Fabric with models the business can query.
Power Automate, Salesforce Flow and Copilot Studio agent flows built for processes that cross more than one system.
capability 01 / 07in production
CRM implementation and rescue
Salesforce and Dynamics 365 builds, plus clean-up of orgs that grew through years of unmanaged customization.
Check each Salesforce seasonal release and each Microsoft service update against your configuration. Out of that comes a short list. What to test. What to switch off.
We set up single sign-on and SCIM provisioning and design the permissions, so CRM and ERP access comes from your identity provider. Nobody grants it off a spreadsheet.
We pieced these together from Enterprise Platforms situations that come up a lot. They're patterns. You won't find a specific client in them.
case file 01
Three billing addresses for one customer across CRM, ERP and warehouse
composite · not a client story
Beforethe situation
Sales runs on Salesforce, finance on Dynamics 365 Finance, and the warehouse loads both overnight. One customer can carry three billing addresses, and invoices go to the wrong one after every account change.
What we dothe work
Agree field-level ownership first: finance owns billing address, sales owns contacts. Build the sync with one integration user per direction and idempotent upserts, point the warehouse at the owning system for each field, and clean existing mismatches in reviewed batches.
Afterwhere you end up
Every address field now has one owning system, and the others copy from it. The billing address in the warehouse is the one finance actually invoices.
case file 02
Winter '27 and a retired Dynamics release wave model in the same quarter
composite · not a client story
Beforethe situation
Salesforce Winter '27 became generally available on 12 October 2026, and Microsoft has retired Dynamics 365 release waves in favor of a continuous roadmap. One admin team runs both platforms and has no regression test list for either.
What we dothe work
Write a regression list per platform from the processes that bring in revenue or carry audit risk. Read Salesforce release notes and the AI at Work roadmap against your configuration, run the list in a preview sandbox, and send each process owner a short note on what changes for them.
Afterwhere you end up
Each release arrives with a known test list and a named owner for each risk. Changes get found in a sandbox before users find them in production.
How CRM, ERP and payer platforms connect to identity and data
Your identity provider controls who can sign in to each enterprise platform, and integrations keep customer, order and claims records in step between them. Each platform then lands its data in the warehouse for cross-system reporting.
01 · Identity
Identity providerOkta · Entra ID → Salesforce · SSO and SCIM→ Dynamics 365 · SSO and groups
02 · Enterprise platforms
SalesforceSales Cloud · Service Cloud → APIs and middleware · orders and accounts
Dynamics 365Sales · Finance · Business Central → APIs and middleware · invoices
TriZetto Facetsenrollment · claims · billing → APIs and middleware · members and claims→ Warehouse · claims extracts
03 · Integration
APIs and middlewareREST · events · batch → Warehouse · CDC and extracts
Put these to anyone bidding on your Enterprise Platforms work. The ones who've done it answer differently from the ones who've read about it.
Q1
How will you decide which system owns each customer field?
CRM, ERP and claims systems each assume they own the customer. A field-level ownership table agreed before integration work prevents sync loops and silent overwrites.
Q2
Do you have a release impact note from a past Salesforce or Microsoft release that we could read?
With three Salesforce releases a year and Dynamics 365 plans published continuously, release review is easy to promise and easy to skip. A real past note and the test list behind it tell you which kind of partner you've got.
Q3
What permissions will your integration users hold in each platform?
An integration user with System Administrator, or a broad Dataverse role, is one of the most powerful accounts you have. Scope each one down to the objects it actually reads and writes.
Q4
How will access to CRM and ERP follow our identity provider?
When admins grant access from a spreadsheet, it drifts away from what HR has on file. With SSO and SCIM, or roles mapped from directory groups, disabling a leaver's directory account also cuts their CRM and ERP access.
Q5
If we change partners later, what configuration knowledge stays with us?
Undocumented customizations tie you to whoever built them. Source-controlled metadata and admin runbooks should be listed deliverables, not favors.
01Do you work on Salesforce and Dynamics 365, or do we have to pick one?
Both. We have no reason to steer you toward either. If you're choosing, we compare licensing, the apps you already run on Microsoft 365 or Salesforce, and the skills your team has, then give you a recommendation.
02Can you take over a platform another partner built?
Yes. We start with a health check of configuration, custom code, integrations and permissions, then agree with you what to keep, fix and rebuild.
03How do you handle vendor releases?
We read the release notes ahead of each Salesforce release and each Microsoft service update, check them against your org, and send a short note covering changes, risks and tests.
04What drives the cost of a platform project?
Mostly the number of integrations, how much data has to move, and how far the design departs from what the product does out of the box. A short discovery measures all three before we estimate.
05Do you support platforms after go-live?
Yes. Some clients keep us for release reviews and a change backlog. Others take over with runbooks and bring us back for upgrades. We agree the scope and response times in writing before the work starts.
related
Often paired with
Projects on Enterprise Platforms usually end up touching one of these, so they're worth a look.
