What a CRM must solve in an SME
A CRM solves three problems: knowing who each customer is, knowing the state of each opportunity and never forgetting the next step. Everything else (automations, advanced reports, exotic integrations) is secondary until this works.
Before comparing tools, write your process on one page: how a contact arrives, which stages it follows, who takes part and what winning or losing an opportunity means. If you cannot write it down, no CRM will fix it for you.
When a standard CRM wins
A standard product (HubSpot, Salesforce, Pipedrive or similar) is usually the best option when your process resembles thousands of companies': a linear pipeline, email follow-up and activity templates. Timelines depend on scope, data migration and integrations; you also inherit the vendor's maintenance, security and evolution.
It also wins when your team already knows a particular tool or when you need integrations that only exist in its ecosystem. Reshaping a working process to fit a new CRM rarely pays off.
- Your pipeline is standard and configuration covers it
- You can start with a standard configuration and a bounded implementation
- Nobody on your side will maintain a custom system
- The integrations you need already exist in its catalogue
When building custom pays off
A custom CRM can pay off when you pay for much you never use, when your process has stages no standard product reflects or when data lives in proprietary systems to connect. Also when, depending on the chosen plan and tier, per-user licences punish growth: in many standard plans, each person can add a fee every month. A custom CRM is not automatically cheaper: compare the full cost of each option.
Building does not mean reinventing everything: a good custom CRM imports your current data, reflects your real stages, sets clear permissions per role and keeps your data exportable at all times.
- Your stages fit no standard pipeline
- You pay licences for features nobody opens
- You need the CRM connected with your internal systems
- You need exportable data and a comparison of portability and total cost
The real cost of each option
Compare the two-year total cost: per-user subscriptions and tiers, implementation and configuration, data migration, training, integrations and internal adaptation time. A cheap standard product per user can turn expensive as the team grows or needs the higher tier.
In a custom CRM, cost concentrates in the initial project with later maintenance that varies with complexity and dependencies. Always ask for the breakdown: build, hosting, third-party services, evolution and how users, workload and support affect it. Without a breakdown there is no honest comparison.
How to decide in a week
Spend a week deciding with data: write your process, trial a standard product with authorised synthetic or anonymised examples for a few days and request a written scope proposal for the custom option. The trial reveals frictions no demo ever shows.
Define what would need to be true for each option before trialling. Compare the mandatory workflows, total costs and data portability: if the standard product covers them at an acceptable cost, buy it. If it forces you to deform how you sell, build or integrate.
- Your process written on one page
- A trial of a standard product with authorised synthetic or anonymised examples
- A written scope proposal for the custom option
- Decision criteria defined before trialling