Draft · LeadScale Website 0.5.3 · A-07 · /solutions/ · not for publication

25 yearsFounded in the UK in 2001Programmes run on the LeadScale Engine™

The lead problems LeadScale solves

For teams whose leads go wrong somewhere between capture and the moment sales acts on them.

Most of these problems share a cause: nobody wrote down what an acceptable lead is, or records are checked against that definition too late. LeadScale Services writes the definition into a specification with you before anything is bought, and the LeadScale Engine™, LeadScale's own software, checks each record against it before delivery.

Where leads go wrong

  • Sales will not accept the leads.

    Some rejections are about the record and some are not, and each needs its own fix. Getting sales to accept your leads

  • Syndicated leads arrive but do not convert.

    Faulty and off-brief records can be caught before delivery; a buyer who is not ready cannot. Syndicated leads that convert

  • Consent has to be proved months later.

    Each record carries its source, a timestamp, the consent given and its lineage, the trail of where it came from. Consent and provenance

By organisation

Advertisers

You carry a pipeline number, and the leads arriving against it are argued over. Usually more than one fault is at work.

Agencies

Your clients set the acceptance criteria. On a LeadScale programme they go into the specification before anything is bought, and each record carries its source and the consent given.

Publishers

Audience data has to carry consent that holds up, stay accurate, and arrive in a state a buyer's systems accept.

Data owners

You hold records collected for one purpose that could support another, and need to know what state they are in and what is missing.

By role

Demand generation

Accountable for the number and for the sources feeding it.

Signing off how records are handled before a programme starts, including whether what a person agreed to at capture can be shown later.

CMO

Judging whether a supplier can carry the programme: how long it has done this work, whether it owns its technology, and what its client work shows.

Buying groups

When a marketer, an operations lead and a data protection reviewer buy together, the specification is what they have to agree before any buying starts.

By sector

What every programme rests on

  • A written specification.

    What counts as an acceptable lead, agreed before anything is bought.

  • Checks before delivery.

    Contact data and programme criteria, tested on the Engine.

  • A record of origin.

    Where each record came from and what the person agreed to, carried into your systems.

  • Delivery into your systems.

    By file, API or native integration. All integrations

Case studies

Bring the problem in your own words, and we will work out which part of it LeadScale can help with.