Custom CRM or an existing CRM?
Start by testing whether an existing CRM can handle your essential workflow with clear records, ownership and follow-up. Extend it when the core fits but a specific connection or task is missing. Consider a custom CRM when important operational rules cannot be handled cleanly and you are ready to fund ongoing maintenance.
The decision is about the work your team needs to do. A longer feature list does not tell you whether staff can finish a real task without switching between inboxes and spreadsheets.
Three ways to solve the problem
Configure an existing CRM
Use the product's fields, stages, permissions, reports and supported automations. This is a sensible starting point when your process fits the product and the main problem is inconsistent setup or adoption. Check the exact edition and limits before committing.
Extend an existing CRM
Keep the CRM for the records and processes it handles well, then add a connection, specialist workspace or custom interface for a defined gap. Be clear about which system owns each piece of data and who will maintain the connection.
Build a custom CRM
Design the records, screens and operational rules around your process. This can be worth exploring when the work goes well beyond a standard sales pipeline. Your scope should include migration, testing, access controls, training, support and future changes.
A custom system does not have to mean starting with an empty codebase. Business platforms can also support tailored applications. For example, Microsoft's model-driven Power Apps combine related tables, forms, views and dashboards. The practical question remains whether the platform and its constraints fit your workflow.
Compare the tradeoffs
| Decision | Configure | Extend | Custom build |
|---|---|---|---|
| Workflow fit | Work within the product's supported model | Keep the core and address a specific gap | Design around the agreed operational rules |
| Ongoing work | Administration, licences and vendor updates | Administration plus maintaining the added connection or app | Hosting, support, monitoring and planned improvements |
| Main risk to test | Staff still need workarounds for essential tasks | The connection fails or two systems disagree | Scope grows before the core workflow is proven |
| Ownership to clarify | Data export and account administration | Data ownership across systems and responsibility for integrations | Source code, data, hosting access and handover rights in writing |
A workflow test you can run before buying
Pick one ordinary piece of work and one exception. Use fictional or anonymized records in a safe demonstration, not private customer information.
- Capture the enquiry. Where does it arrive, and can the team find the same person or company again?
- Assign an owner and next step. Can everyone tell who is responsible and when follow-up is due?
- Complete the handoff. Move the work from sales to delivery or service without retyping information.
- Handle an exception. Try a missing document, a changed requirement or a reassigned case.
- Report the result. Can the owner see what is waiting, what is overdue and where work has stalled?
For each step, record one of three results: works directly, needs configuration, or needs a workaround. Then write down the workaround and the person who would have to keep doing it.
Illustrative example: if a salesperson can move an enquiry through a normal pipeline but delivery staff must recreate it in a separate spreadsheet, the gap may be the handoff or integration. That alone does not establish that the whole CRM needs replacing.
What our client work illustrates
For Innovating Insurance Services, SkillGroup built an operations platform that connects client records, broker ownership, conversations and follow-up tasks with a group-benefits workspace. The group-benefits work includes employee and dependent coverage, plan information and contribution calculations.
That is an example of operational requirements extending beyond a contact list. The implementation continues to be refined with the agency's team; measured time savings and financial results are not yet available. Read the case study for the scope and its limits.
Questions to settle in the proposal
- Which essential workflows are included, and which are explicitly outside the scope?
- Which records will be migrated, how will they be checked, and what will stay in the old system?
- Which system is the source of truth for each shared field?
- Who can see or change records, and how will those permissions be tested?
- Who handles failed automations, support requests and vendor changes?
- What training and documentation will the team receive?
- What are the ongoing fees, maintenance responsibilities and exit arrangements?
Compare the full operating commitment. Include licences or hosting, setup or build, migration, training, integrations, support and future changes. A subscription price and a build quote are not equivalent comparisons.
Choose the smallest change that solves the essential workflow
If the demonstration works after reasonable configuration, improve the existing CRM. If the core works and one defined gap remains, explore an extension or system integration. If several essential rules still rely on fragile workarounds, scope a custom approach and test the riskiest workflow early.
If nobody can yet explain the process or own its data, clarify those responsibilities first. New software cannot decide them for you.
Talk through the workflow with SkillGroup
Bring one workflow that keeps getting stuck and the tools your team uses today. We will review whether configuration, integration or a custom system is worth exploring. Our custom CRM service page and implementation process explain how we scope and deliver the work.
Book a discovery callยท SkillGroup