CRM implementation and a foundation your team actually uses.

Yes, for us those are one and the same engagement. A CRM that is technically set up but not used is wasted money, so adoption and training are fixed steps, not an optional extra billed afterwards. Carsten leads the setup and data architecture, Kim runs the adoption: hands-on sessions on your own pipeline, parallel support after go-live and an internal CRM owner who takes it over. Those who want to train more deeply can add CRM training. That way it runs from implementation to daily use without a gap.

When marketing, sales and service need to sit in one platform with a shared data model. The UI is light enough for commercial teams to use without days of training, and the reporting layer is mature enough for a board pack. We have been Platinum Partner since 2020, so 5+ years in the same stack.

We encounter three situations. One, if a signed deal flows straight into client work, monday is often the better fit; that is what the platform was built for. Two, highly complex enterprise processes with deep custom objects and strict forecasting requirements, then we recommend Salesforce, and there we work with partners who build it. Three, organisations that only need a marketing tool without connecting sales or service, then HubSpot is too heavy and something lighter such as ActiveCampaign or Customer.io may suffice. Four, if your organisation already sits entirely inside the Microsoft stack and your commercial process is tied to ERP, Microsoft Dynamics 365 wins on that point; our HubSpot and Dynamics comparison explains exactly why.

For a clean HubSpot implementation without migration, a mid-market engagement typically takes 6 to 10 weeks: 1 week strategy and data model, 2 to 3 weeks setup, 1 week integrations, 1 week testing and go-live, then 2 weeks of parallel support. A migration from Salesforce or Pipedrive typically adds 3 to 5 weeks, depending on data volume and number of integrations. We do not work with big-bang go-lives, always in phases with a go-live checklist and parallel support from Kim.

The data strategy is a separate step before the migration itself. We map fields, identify duplicates, assess which history has value and which contamination is better left behind, and decide which objects migrate as 1-to-1 and which we redesign. Pipeline history can be retained in 100 per cent of cases, even when deal stages change, as long as we define the mapping upfront. At Saysimple we went from 12 to 7 deal stages without any loss of history.

Carsten leads the architecture and data work, he is HubSpot certified on Marketing, Sales, Service and Operations Hub. Kim runs the adoption side, sales enablement and the parallel support after go-live. Carel joins as RevOps architect at kick-off and remains involved in the strategic decisions. For enterprise engagements with Salesforce we work with partners. For monday engagements Carsten and Kim build it together.

Adoption is half the work, which is why it is a separate step in the engagement, not something mentioned once after go-live. Kim runs the hands-on sessions on your own pipeline, not a demo environment, and is available daily in a chat channel plus weekly office hours for two weeks after go-live. After that we embed it in a retainer or close the engagement with an internal CRM owner who takes it over. If you want to invest more in adoption, take a look at CRM training.