All guides

Speed to lead: what CRM integration is actually for

Marketing7 min read

A form on your website that sends an email to sales@ is a notification. It is not a system, it does not know whether anyone replied, and it cannot tell you which of your marketing channels produced the enquiry that turned into a customer eight weeks later.

That gap costs more than most businesses think, and the research on it is unusually consistent.

The numbers are old and nobody has beaten them

James Oldroyd at MIT’s Sloan School studied lead response behaviour across six companies, more than 15,000 leads, and over 100,000 call attempts. Contacting a web lead within five minutes rather than thirty raised the odds of making contact by roughly 100 times, and the odds of qualifying that lead by 21 times.

Harvard Business Review published a larger version of the same finding in 2011, drawn from 1.25 million leads across 2,241 companies. Firms that made contact within an hour qualified leads at roughly seven times the rate of those who waited just sixty minutes longer. Wait a full day and you are 60 times less likely to qualify than the companies who called back inside the hour.

Those studies are more than a decade old. The behaviour they measure has not changed, because it is about human attention rather than technology. Somebody filling in your form is at that moment thinking about the problem you solve. An hour later they are doing something else. Two days later they have called three competitors and forgotten your name.

InsideSales tracked 5.7 million inbound leads across more than 400 companies in 2025 and found the average B2B response time was 47 hours. Almost two full working days, against research that says the useful window closes in about sixty minutes.

That gap between what the research says and what companies do is the opportunity. It is unusually cheap to fix.

What integration actually means

Wiring a form to a CRM means the submission creates a record, assigns an owner, starts a timer, and triggers whatever should happen next. Four things, and most implementations get one.

The record matters because email threads are not searchable in any useful way six months later. The owner matters because a lead assigned to everyone is assigned to nobody. The timer matters because it makes response time a number somebody is accountable for rather than a feeling. And the trigger matters because the first response can be automatic while the human one is still being written.

An immediate acknowledgement buys you time. It should say who will call, roughly when, and what they will ask, and it should come from a person’s name rather than noreply@. That single email moves you from the 47-hour cohort into something closer to instant, at least in the customer’s perception. It only works if it arrives, which is a separate problem covered in email that reaches the inbox.

Attribution is the second reason

The other half of CRM integration has nothing to do with speed. It is knowing which marketing spend produced which revenue.

Capture the source with the lead. UTM parameters, referrer, landing page, and the Google click ID if the visit came from paid search. Store them as fields on the record and carry them through to the deal. Do this and you can answer the question every marketing budget conversation eventually reaches, which is whether the channel that generates the most leads also generates the most money. Frequently it does not.

That click ID is what lets you push closed revenue back into Google Ads as an offline conversion, so bidding optimises against deals rather than form fills. We covered why that matters in where Google Ads budget leaks.

Without source capture at the point of submission, this is unrecoverable. You cannot reconstruct where a lead came from after the fact, and analytics sessions expire long before a B2B deal closes.

Where these projects go wrong

The most common failure is a form that posts to a third-party endpoint with no fallback. The endpoint has an outage, or a validation rule changes, and enquiries vanish silently for a week before anyone notices. Log every submission somewhere you control, independently of whether the CRM call succeeded. A row in your own database costs nothing and turns a silent failure into a recoverable one.

The second failure is field creep. Someone decides the CRM needs company size, budget range, timeline, and job title, so the form grows from three fields to nine and submissions fall off a cliff. Baymard’s research on checkout abandonment found 18% of users abandon when forced to create an account and 17% when the process feels too long, and enquiry forms obey the same psychology. Ask for what you need to make the first call. Get the rest on the call.

The third is treating the integration as finished at launch. Field mappings drift, someone renames a picklist value in the CRM, and suddenly every new lead lands with a blank source. Check it monthly by submitting a test enquiry and following it all the way through to the deal record.

Start smaller than you think

You do not need a full platform migration to fix response time. A form that writes to your CRM, assigns an owner, sends an acknowledgement, and records the source will get you most of the available value, and it is a few days of work rather than a quarter.

Pick the metric first. Median time from submission to first human contact, measured weekly. If that number is above an hour, everything else in your marketing is being taxed by it, including the ad spend covered in where Google Ads budget leaks.

We build these as part of development work, usually alongside the marketing side that generates the enquiries in the first place. If your forms currently email an inbox and nobody is quite sure what happens next, get in touch.

References