Sell Smarter with CRM Module 4 Ā· Lesson 1

Connecting Your CRM to Accounts, Website and Ads

Module 4: Advanced CRM

Quick answer

Connect the CRM to the systems your team retypes into most: website and ad lead forms first, so enquiries arrive in a minute with their source; then accounts, so won deals become draft invoices and payment status flows back; then calendar and email. Decide which system owns each fact, sync in one direction only, alert a named person when a connection fails, and match on phone or email to avoid duplicates.

Key takeaways

  • Every retyped fact is late, sometimes wrong, and costs someone hours a week.
  • One fact, one home: decide which system owns each piece of information before connecting anything.
  • Order by hours saved: lead forms in, won deals to accounts, payment status back, then calendar and email.
  • Avoid two-way sync of everything, silent failures, duplicates and long chains of connector tools.

By the end of Module 3 the CRM runs your sales week: enquiries arrive, rules remind, the review takes twenty minutes, and the reports are on one screen. Then a familiar thing happens. Someone retypes an invoice from the CRM into the accounts software. Someone copies ad leads from a spreadsheet into the CRM. Someone checks the calendar, then the CRM, then the calendar again.

Every time information is retyped between two systems, it is late, it is sometimes wrong, and it costs someone an afternoon a week.

Integrations fix that. This lesson is about which ones are worth doing first, and where they go wrong.

The Rule: One Fact, One Home

Before connecting anything, decide which system owns each kind of information. The customer’s name and contact details live in the CRM. The invoice amount and whether it was paid live in accounts. The appointment time lives in the calendar.

An integration then copies a fact from its home to wherever else it is needed, in one direction, automatically. Problems start when two systems both think they own the same fact and both let people edit it. That is how a customer ends up with two phone numbers and nobody knows which is right.

Connection 1: Accounts and Invoicing

This is usually the one that pays back fastest, because the retyping happens on every single sale.

CRM to accountswhen a deal is won, the customer and the agreed amount go to the accounts software as a draft invoice. No retyping of names, GST numbers or addresses.
Accounts to CRMwhen the invoice is paid, or goes overdue, the CRM record shows it. The salesperson sees “payment overdue 12 days” before calling the customer about a new order.

A manufacturing distributor that connected the two stopped two embarrassing patterns at once: salespeople offering new credit to dealers with unpaid invoices, and the accounts team chasing payments from dealers the salesperson had just agreed extended terms with.

Connection 2: Website and Landing Pages

Module 2 covered getting website forms into the CRM. The advanced version adds two things.

  • The page and campaign the enquiry came from. Not just “website” but which service page, which landing page, which ad. This is what makes the enquiries-by-source report precise enough to move budget on.
  • What the customer already did. Downloaded a template, read three lessons, used a calculator. A salesperson who knows this starts the call in a different place.

Both are captured silently by the form, so the customer types nothing extra.

Connection 3: Ads and Lead Forms

Ad platforms and property portals collect leads in their own forms and hold them in their own dashboards. Somebody downloads a file once a day, or once a week, and imports it. By then the lead has been called by three competitors.

A direct connection creates the CRM record within a minute of the form being submitted, with the campaign name as the source and an owner assigned by your rules. The first-response target from Module 2 becomes possible for ad leads too.

The connection also works the other way. Telling the ad platform which leads became customers lets it find more people like them, instead of more people who fill in forms. For a real estate agency spending every month on portal and social ads, this is the difference between paying for enquiries and paying for buyers.

Connection 4: Calendar, Email and Phone

The everyday tools the team already lives in.

Calendara site visit, an eligibility call or a sample review booked in the CRM appears in the person’s calendar, and a booking made from a scheduling link appears on the CRM record.
Emailemails to and from a customer attach to their record without forwarding. The history from Module 2 fills itself in.
Phone and WhatsAppcalls and chats through the business number log against the record, as covered in Module 2. Listed here because it is the connection with the most visible effect on the team’s day.

Write Each Connection Down First

Like automation rules, every integration should be one sentence before anyone builds it:

When a deal is marked Won in the CRM — create a draft invoice in accounts with customer, GSTIN, items and amount — when that invoice is paid or 7 days overdue, update the deal’s payment status in the CRM. Owner of customer details: CRM. Owner of payment status: accounts.

The last line matters most. It is the “one fact, one home” rule written into the connection, and it is what stops the two-phone-numbers problem before it starts.

Where Integrations Go Wrong

  • Two-way sync of everything. Sounds complete, creates conflicts. Sync the few facts that need it, in the direction they flow.
  • Silent failures. A connection that stops working on a Friday and nobody notices until the month-end report. Every integration needs an alert when it fails, sent to a named person.
  • Duplicates. The same customer arriving from the website, an ad and WhatsApp as three records. Match on phone number or email before creating anything new, as Module 2 said for manual entry.
  • Chains of connector tools. Form to one service to another service to the CRM. Each link is a monthly fee and a place to break. Fewer hops is better.

Which to Do First

Count the retyping. Whichever connection removes the most hours of copying per week goes first. For most SMEs that order is: website and ad leads into the CRM, then won deals into accounts, then payment status back, then calendar and email.

An immigration consultancy reversed it. Its biggest time cost was case coordinators copying client details into document checklists and fee invoices, so accounts and documents went first. The principle is the same: follow the hours, not the feature list.

Ready-Made Connectors and Their Limits

Subscription CRMs advertise hundreds of integrations. Most connect the standard fields well: name, email, deal amount. They struggle with the fields that make your business yours: visa type and decision date, unit number and site visit outcome, dealer tier and order cycle. Those are exactly the facts that need to flow between your systems, and they are where a CRM built around your process earns its cost, because the connection is designed around your fields from the start rather than mapped onto someone else’s.

Next lesson: roles, permissions and keeping customer data safe, which matters more the more systems the CRM talks to.

Check what you learned

3 quick questions. Pick an answer and see why.

  1. What does "one fact, one home" mean for CRM integrations?

  2. Which integration usually pays back first for a small business?

  3. A connection stops working on a Friday and nobody notices for three weeks. What was missing?

You finished Lesson 1

Up next Ā· Lesson 2 Roles, Permissions and Keeping Customer Data Safe Read the next lesson Previous: Lesson 5 Ā· After the Sale: Using a CRM for Customer Service and Repeat Business
Share this lesson

Written by

Kulwinder Kohli

Planning a CRM for your business?

We design and build CRMs around the way your team already works. Tell us about your process and we will suggest the simplest setup that fits.