Case studies
Paid campaigns, content syndication and customer enquiries: see the problem each programme addressed, the work LeadScale did and what the case study reports.
Copia Automation's case covers Google and LinkedIn campaigns aimed at a new customer profile. An anonymous CRM company's case explains how vetted publishers were added, existing partners were managed and cost per lead fell. Everest's case describes phone-number checks on an enquiry form. Each account explains the work and the reported result.
Find a case close to your problem
Your campaigns convert, but the people responding do not fit.
Copia wanted its paid search and social activity to reach more managers and higher-level decision-makers while retaining a wider audience.
You keep buying from the same few publishers.
The CRM company struggled to onboard alternatives. Its case follows the work involved in expanding that set and managing existing partners.
People enquire, but your team cannot reach them.
Everest's contact centre encountered incorrectly entered phone numbers. Its case shows what changed when visitors were prompted on the form itself.
The first two cases concern business audiences. Everest's concerns homeowners enquiring about home improvements. Choose the account closest to the work your team needs to do.
Results at a glance
Copia Automation: paid search and social
Copia sells a cloud-based industrial DevOps platform. LeadScale audited its Google and LinkedIn activity, then managed both channels from March to May 2024. The case study reports a shift in the LinkedIn lead mix towards manager level and above.
Read the Copia Automation case study for the audit, campaign changes and the measures used to describe the results.
A CRM company that cut its cost per lead
LeadScale vetted and introduced new content syndication publishers alongside the client's existing partners, then took over management of the existing relationships. The case study reports a fall in cost per lead in the UK and France.
Read the CRM company case study to see how the onboarding constraint, publisher mix and management workload were connected.
Everest: accurate data at the first touch
The LeadScale Engine™ checked phone numbers as visitors entered them on Everest's enquiry form. Visitors could correct a flagged number or submit anyway. The case study reports increased contact rates.
Read the Everest case study for the two checks, the optional correction prompt and the contact centre's experience.
The work behind the cases
The paid search and PPC service page and paid social service page explain the campaign work behind Copia's engagement.
The content syndication service page covers the service used by the CRM company, including work with publishers.
The lead validation page explains the Engine's checks. Everest's phone-number check is a specific example of how checking at capture was used on a consumer enquiry form.
What each account reports
Copia:
lead mix, marketing-qualified-lead reporting, conversion rate and paid-search opportunity counts. The page distinguishes their different comparison periods and limitations.
The CRM company:
the change in cost per lead after additional publishers joined the programme, and the effect of partner management on the client's workload.
Everest:
contact rates and reported incremental revenue per pound spent on the phone-number-checking solution.
Talk through your programme
A case study records a particular engagement. Tell us where your situation is similar and what would need to work differently.