Draft · LeadScale Website 0.5.3 · S-AGY-01 · /solutions/agencies/white-label-demand/ · not for publication

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

Running demand under your own brand

Commission the sourcing, record processing and delivery behind a client programme. LeadScale brings managed demand experience and its own Engine to the work, with responsibilities agreed around your agency's brief and client relationship.

LeadScale runs managed demand programmes, translating a client's requirements into a specification for sourcing, record processing and delivery. For an agency, the starting point is the work it needs delivered and the responsibilities it will retain. Agree branding, client contact and reporting alongside the programme requirements before delivery begins.

Make the client promise a delivery specification

A brief may name an audience and lead target. Delivery also needs the fields, acceptance conditions, checks and receiving systems. LeadScale translates those requirements into the programme's specification and processing flow.

  1. Agree the requirement. Define the audience, territories, fields and acceptance criteria from the client brief.
  2. Plan the sourcing. For syndication, LeadScale assesses publishers and agrees the mix with you.
  3. Configure processing. Agree the criteria, technical sequence and handling of exceptions. The Engine applies that flow before onward delivery.
  4. Establish the hand-over. Confirm the client systems and delivery route. Where supply is against an order, delivery is reconciled against it.

A delivery brief your account team can stand behind

The written specification connects the client's request with the work done on the record. For example, a demand for contacts in a territory needs usable criteria and supporting fields. A requirement to avoid unwanted repeats needs explicit repeat rules. Agree those details before they become client-facing promises.

Records created through the Engine carry source, timestamp, lineage and consent audit information. Processing and delivery have an audit trail. Establish which evidence your agency needs for a client review and which it needs for a specific investigation.

The agency evidence page explains how to examine a challenged lead.

The sourcing work behind a programme

The CRM-company case describes a syndication programme using vetted publishers. LeadScale assessed and managed the supply to meet the programme's requirements.

Design the working arrangement alongside the programme

Set out who gives instructions, who speaks to the end client and whose name appears in client-facing material. Agree the reporting format, escalation route and commercial terms. These decisions make the division of work clear to your delivery and account teams.

Questions from agencies

What can we hand over to LeadScale?

Discuss managed sourcing, agreed record processing and delivery. Bring the responsibilities you need covered and the work your agency will retain, then build the arrangement around the client brief.

Can records go into the client's systems?

Delivery can use a configured integration, the receiving system's API or files. Identify the destinations so the routes can be assessed during setup.

How do we agree the publisher mix?

LeadScale assesses publishers against the programme and agrees the mix with the client. Include any audience, source or presentation requirements in the planning discussion. For content syndication bought as one line and priced the next working day, see LeadScale ONE.

Bring the brief and the work you need covered

We'll discuss the sourcing, processing and hand-over, then the client-facing arrangement your agency needs around them.