When your team keeps retyping the same information, the problem may be the handover between systems. Before replacing the tools, look closely at what needs to move between them.
An accepted quote becomes a job. The job becomes an invoice. The customer’s name, contact details and reference are copied at every stage. Eventually two records disagree, and someone has to work out which one is right.
It is tempting to respond by asking for one new system that does everything. Sometimes that is justified. Often a smaller change can remove the awkward part while keeping tools people already know.
Follow one piece of work
Take a recent job and trace it from the first enquiry to completion. Note where information is entered, where approval happens and where someone switches applications. Ask the people doing the work which step causes mistakes or waiting.
Keep the map grounded. “Improve integration” is difficult to scope. “Create a draft job when an approved quote reaches this status, using this customer reference” gives you a boundary, a trigger and a result to check.
Choose the smallest useful intervention
| What you find | What to explore first |
|---|---|
| The current product has an unused feature that fits | Configuration and a clearer working process. |
| Two useful tools need to share a defined set of information | A supported connector or focused integration. |
| A distinctive workflow does not fit the available products | A small custom application around that workflow. |
| The existing system is unsupported or unsuitable | A replacement assessment, including migration and ongoing care. |
A native connector can reduce custom development, but check its limits: supported fields, trigger timing, permissions, subscription requirements and what happens when it fails. A demonstration that copies one record is only the beginning of that assessment.
Decide which system is right
For every shared field, agree where the authoritative value lives. Perhaps your CRM owns contact details, while finance owns invoice status. If somebody edits both, what should happen? Avoid a two-way sync simply because it sounds more complete.
Use a stable reference to match records where possible. Names and email addresses can change, and two customers may share a name. Agree how duplicates, missing references and corrections will be handled before connecting live records.
These are business decisions as much as technical ones. The person responsible for customer records should help decide how a mismatch is resolved.
Design the failure path too
Systems go offline and requests time out. Your integration needs a way to distinguish work that has failed from work that succeeded but did not return a confirmation. Otherwise, trying again could create a duplicate invoice or job.
Microsoft’s retry pattern guidance describes why retry behaviour needs to account for the operation being repeated. In business terms, the integration should recognise a job it has already done, avoid repeating its effect, and give unresolved work to someone who can act.
Ask for a visible queue or report of failures, a named person who receives alerts and a safe way to retry. Monitoring should reveal enough to troubleshoot without unnecessarily exposing customer information or credentials.
Scope one connection before the whole operation
Start with a small, representative flow in a test environment. Include a normal record, a missing field, a duplicate, an unavailable destination and a correction. Define what a person will see in each case.
A useful integration brief contains
- The starting event and the result you want.
- The systems, fields and record owner involved.
- Who can approve changes and access the connection.
- How duplicates, failures and corrections are handled.
- How you will test, monitor and maintain it after launch.
Compare the cost of that work with the cost of leaving the process alone: time spent re-entering information, checking mistakes and following up. Include ongoing licences and maintenance in the comparison.
Custom software earns its place when it solves a real gap. A good first conversation should leave you clearer about that gap—and about whether you need a new tool, a better connection or simply a better use of what you already have.