integracoes

Custom CRM or integration? Decide before adding another system

An opportunity starts in a message, moves into a spreadsheet and is entered again in the commercial tool. A custom CRM seems like the answer to lost context.

An opportunity starts in a message, moves into a spreadsheet and is entered again in the commercial tool. A custom CRM seems like the answer to lost context. First establish whether the gap is a missing capability, a missing integration or an unmanaged process. New software does not automatically take responsibility for follow-up.

Write the current workflow

Identify entry points, owners, stages, agreed next steps and closure criteria. Use an anonymised example to show where information disappears. If qualification has no definition, selecting a tool will not provide it.

OptionDecision question
Configure the current CRMDoes the necessary capability already exist?
Connect toolsDoes rework happen during exchange?
Build a focused moduleCan the specific rule be isolated?
Build a CRMIs maintaining the whole operation justified?

Compare maintenance, training, migration, access and recurring costs without invented prices. A small connector can carry important operational duties; an existing product can have restrictions absent from its feature list.

Test how context is lost

In a hypothetical form-to-CRM workflow, save a request, retry it and check that one record retains origin and service. Then test stage updates and conflicting changes. Synchronisation requires precedence rules rather than copying every field in both directions.

Start by defining states, owners and minimal fields in the current tool. Standardise identifiers and remove information without a purpose. Do not transfer entire private conversation histories merely to experiment with another provider.

Identify a reason for custom development

Specific approvals, unusual permissions or deep internal integrations may justify a tailored module. Frequency, rules and maintenance capacity matter. A specialised entry point can coexist with the contracted CRM as the commercial source of truth.

My API integration service can compare these alternatives. A genuinely custom workflow can enter a separate software scope. The proposal should identify the authoritative record and ownership of each update.

Bring a repeated task, existing systems and rules you cannot represent. This evidence supports choosing configuration, integration or development around the process instead of adding another place for repeated typing.

Sources and further reading

About the author and editorial process

Rafael de Sanzio Nonato develops websites, web applications and integrations independently. Scope and responsibilities are agreed for each engagement.

Prepared with AI assistance. Examples are hypothetical unless explicitly documented. Publication is subject to the author's editorial approval.

Approach and responsibilities →

Choose the commercial workflow before building another CRM

Explain the workflow and tools you already use. I can compare configuration, integration and development against the work that actually needs support.

Choose the commercial workflow before building another CRM ↗