What a CRM should connect to, and what it should not

A CRM sits in the middle of a small business's tools, and every connection it makes is a commitment to keep two systems agreeing. That commitment lasts as long as both systems do. Three connections repay it. Most of the others get bought with enthusiasm and maintained with resentment, until somebody notices they stopped working in March.

Email is the one that matters most

The record of what the business promised lives in email. A CRM without it holds a contact list rather than a relationship. Our guide to getting customer email out of one inbox covers filing the thread against the record. Diract CRM files email from inside Gmail or Outlook, which matters more than it sounds. A connection that makes somebody leave their mail program is a connection they will use twice.

The calendar, in one direction

A job, a site visit or a meeting created in the CRM should appear in somebody's calendar, because the calendar is where they look. Two way syncing sounds better and produces duplicate events, deleted appointments and arguments about which side is right. A business with jobs in the CRM and appointments in a calendar has two views of one day. People trust whichever one their phone shows them. Sending the CRM's work into that calendar completes the phone view, and it needs no second entry.

Invoicing, because the money closes the loop

A quote that becomes an invoice without retyping removes the most common source of billing errors in a small business. Our guide to quote to invoice without retyping covers why that gap costs more than it looks. Accounting is the next question, and the answer is a handoff rather than a merge. An accounting package is the source of truth for the ledger, and a CRM trying to be a second one creates reconciliation work forever. Sending invoices and payments across in one direction stays maintainable.

A one way copy beats a two way sync

Two systems both allowed to change the same record will eventually disagree. Somebody then has to decide which one wins, usually while a customer waits. Naming one side as the source of truth for each field removes that argument before it happens. The rule reads as a limitation and behaves as a feature. A field with one owner is a field nobody has to reconcile.

Every connection needs an owner

A connection breaks when a token expires, a permission changes or somebody leaves, and it breaks silently. A named person who checks it monthly is the difference between a working integration and one that stopped in March. The useful question about any integration is not what it does. It is what the business sees when it stops working. A connection that fails visibly is safe, and one that fails quietly loses data for weeks.

Resist the integration nobody requested

A connection somebody built because it existed, rather than because anybody needed it, still needs maintaining forever. The test is whether a named person would notice within a day if it stopped. Anything failing that test was decoration. A small business with three working connections is in better shape than one with nine, four of which are broken.

The cheap connections worth making

A website form that writes an enquiry record does more for a small business than most integrations, and it needs nothing maintained. Diract CRM takes the form's destination as a setting, so the enquiry arrives as a record rather than an email. A text message confirming a booking earns its place too. Diract CRM sends one from the job or the contact, which keeps the message on the record rather than in somebody's phone.

Data should be able to leave

Every integration decision gets easier when the business knows it can export what it holds. Our guide to getting your data back out covers checking that before anything gets connected. Diract CRM exports every table as CSV, and documents can stay in your own SharePoint or Google Drive. The record lives in Diract CRM while the files stay where the business already keeps them.

What to change first

• Filing email comes first, ahead of every other connection
• The calendar receives events rather than syncing both ways
• Quotes become invoices without retyping
• Accounting receives invoices and payments in one direction
• Each connection has a named owner who checks it monthly
• Every integration fails visibly rather than quietly
• One side is the source of truth for each field