# Do you need a custom CRM or a better connection?

> Decide whether to connect your existing CRM, configure it differently or commission custom software around a specific business process.

Published 1 October 2026 by noboringsites. https://noboringsites.com/blog/custom-crm-or-integration/

---

If staff are copying enquiries from your website into a CRM, begin by asking whether the two can be connected. Replacing a useful CRM may add a data migration and a new operating responsibility to a problem a smaller integration could address.

Custom software becomes worth scoping when you can name the process that existing tools cannot handle well. “We need one system for everything” is too broad to price. “A job needs a site visit, a quote approval and a deposit before we reserve a crew” gives you a process to examine.

## Follow one enquiry through the business

Choose a typical request and write down what happens from arrival to completion. Record who handles it, the details staff have to chase and every place information is copied. Distinguish decisions that require a person from those that follow a rule.

Then follow an exception: the customer changes the job, a staff member is away or the deposit does not arrive. The exception often reveals the real scope more clearly than the happy path.

Use anonymised examples and say which system holds the current record. If the CRM contains the customer details while another tool controls bookings, a new connection needs to respect both roles.

## Compare configuration, integration and custom work

| Route | What would justify it | What to check first |
|---|---|---|
| Configure the existing CRM | Its fields, stages or rules can represent your process | Whether the required feature is on your plan and who can maintain the configuration |
| Connect existing tools | Each tool does its job, but information is re-entered between them | Available integrations, permissions, data direction and failure handling |
| Build a focused custom tool | A specific quoting, approval or customer task does not fit the existing software | Users, rules, records, operator responsibilities and how it connects to the CRM |
| Replace the CRM | The current product cannot meet requirements that matter to daily work | Data export, migration, access rules, support and the work of operating the replacement |

Check these options against your supplier's documentation, then test the feature you would rely on. That will settle more than a feature comparison written in the abstract.

## Describe the connection precisely

“Send the form to the CRM” leaves several decisions open. Which fields should move? Should a repeat customer create a new contact or update an existing one? What identifies the same person? Where should the enquiry appear, and who should see it?

Decide what happens when a connected service is unavailable. An operator may need to see failed submissions and retry them without duplicating the customer record. If two tools can both change a value, agree which system takes precedence or whether a person resolves the conflict.

Your supplier should check the actual integration options before confirming the scope. Access to an API, a connector or a webhook may depend on the tool and subscription you use. An integration named on a marketing page is not proof that it supports your required fields or actions.

## Make permissions part of the brief

List the roles using the system and the records each needs. Sales staff, contractors and customers may need different views. Include what should happen when someone leaves or a customer asks for an export of their records.

Ask who will manage accounts and changes after handover. The ACSC's [small-business guidance](https://www.cyber.gov.au/business-government/small-business-cyber-security/small-business-hub/small-business-cyber-security-guide) explains why access control and removing unnecessary access matter. The practical question for your project is who can see or change each piece of information.

## Specify a result you can demonstrate

For an illustrative first scope, a website enquiry could create a contact and a job record, route it to the right person and show whether delivery succeeded. A repeat enquiry should follow the agreed duplicate rule. A failed connection should remain visible to someone responsible for it.

Put that proposed test in the scope and ask the supplier to demonstrate it using test records at the actual destination. If the workflow sends messages or charges customers, agree those tests separately.

Consider ongoing cost alongside the build: subscriptions, hosting, maintenance and changes to connected services. If the new tool saves manual work but creates an operating burden nobody owns, the brief is incomplete.

## Bring the process before choosing the software

At noboringsites, [business systems](/services/business-systems/) are scoped around the users, data, rules and connections the project needs. Our [AltSpeak case study](/case-studies/altspeak/) shows a website and SaaS application scope, including accounts and payment integrations. It is evidence of that project, not a claim that your CRM requirements are already solved.

Bring your current tools and one anonymised example of the process to a [free intro call](/book/). We can discuss whether the work belongs in configuration, a connection or a custom build.