An off-the-shelf CRM such as HubSpot, Salesforce, or Pipedrive can be running within a week and handles a standard sales process well. A custom system costs more up front, but it follows your process instead of forcing you to bend around it. Here is how to decide.
The problem
A company rolls out a ready-made CRM, and six months later half the data lives in spreadsheets again. The pipeline does not match how the business actually works, key fields are missing, and the sync with accounting depends on manual exports.
Why it happens
Off-the-shelf CRMs are designed for the average case: lead → deal → payment. Once your process involves anything else — properties, production batches, installation stages, contracts with payment schedules, partners with their own roles — you end up faking it with custom fields and tags. The further your process is from the template, the more manual work it creates.
Your options
- An off-the-shelf CRM as is. A good fit when the sales process is standard, the team is under 10–15 people, and you need to start fast.
- An off-the-shelf CRM plus integrations. The core stays packaged and the gaps are filled through the API: QuickBooks sync, pricing calculators, automated tasks.
- A custom CRM. Your own data model, roles, and permissions, screens built for specific operations, and integrations without plan limits.
How to decide
Ask yourself a few questions:
- How many entities besides "contact" and "deal" are really part of the process?
- Which data currently lives outside the CRM — in spreadsheets, chat apps, email?
- What will per-seat pricing cost for the whole team three years from now?
- Do customers or partners need access — a portal, order statuses?
If the answers are full of "outside the system" and "external access", custom development usually pays for itself.
Technical details
We design a custom CRM starting from the data model: entities, relations, statuses, and events. Then come roles and permissions, an audit log, an API for integrations, and background jobs for reminders, syncs, and reports. A typical stack is React or Next.js on the front end, Node.js or PHP on the back end, PostgreSQL, a job queue, and an admin panel where reference data is managed without a developer.
Example
Consider a manufacturer with the stages "request → quote → production → shipping → installation". In a packaged CRM, production and installation do not fit the sales pipeline, and quotes are built in spreadsheets. In a custom system each stage becomes its own entity with owners, deadlines, and documents, and pricing becomes a built-in calculator that generates the proposal.
Takeaway
An off-the-shelf CRM is a good start for a standard sales process. A custom one makes sense when the process itself is your competitive edge and should not be simplified to fit someone else's template. The middle path — a packaged core with integrations — often delivers most of the value for less money.