Bespoke CRM or off-the-shelf CRM?

Start with the operating process

A CRM is a model of customers, work and responsibility. Before comparing feature lists, document the records the team creates, the states they move through and the decisions people make at each handoff.

A generic sales pipeline may fit that process well. If it does, configuration is cheaper to buy and easier to maintain than custom software.

• Customer and company records
• Pipeline or delivery states
• Roles and approvals
• Reports used for decisions

Count the workarounds honestly

Off-the-shelf tools become expensive when staff re-enter data, export spreadsheets for every report or use shared admin access because permissions do not match the job. Those costs are easy to ignore because they sit in payroll and mistakes rather than the software invoice.

Custom CRM software can remove those constraints, but it introduces engineering, hosting, security and maintenance responsibility. The case for a bespoke system needs to exceed that ongoing cost.

• Duplicate entry per week
• Manual reconciliation
• Licence cost for unused features
• Errors and missed handoffs
• Cost of maintaining custom code

Examine integration and data ownership

List the website, email, billing, document and operational systems that need to connect. For each record, decide which system is authoritative and how failed syncs are recovered.

Ask where data is hosted, how it is exported and what happens when the supplier relationship ends. A convenient CRM can still create business risk if exit depends on a limited export.

• API and webhook access
• Import and export format
• Authentication and permissions
• Audit logs and deletion rules

Use a phased decision

Configure a standard CRM first when it meets the core process. Build a small custom layer when one missing workflow creates most of the friction. Commission a bespoke CRM when the process itself is distinctive and central enough to justify ownership.

Do not recreate a large commercial product feature for feature. Build the operating core your team will use, then add evidence-backed improvements.