Lead generation networks budget template: five tabs

This lead generation networks budget template is deliberately empty. For lead generation networks, it sets out five tabs: a scoped cost register, payment and VAT calendar, acceptance and dispute evidence, controls and sensitivities, and decision and change history. Record approvals in the final tab; it does not provide England price benchmarks.

Build it for one service journey and one contract window, including mobilisation and exit. Set the currency, reporting period and scenario label at workbook level.

What to take away

Tab A: scoped cost register

Use one row for every distinct activity or charge, including lead prices or cost per lead (CPL), ping/post charges, marketplace fees, validation and fulfilment.

Calculate line cost = fixed amount + quantity x unit amount. Retain the quote currency. Convert only through the finance team's documented rate and date. Do not populate an industry average where the evidence cell is empty.

Add buyer labour as role, task, hours and approved loaded hourly cost. Keep internal effort apart from supplier fees so procurement can see whether apparent outsourcing moves work back to validation, complaint or technical teams.

Tab B: payment and VAT calendar

Create dated columns for net charge, invoiced VAT, gross payment, expected credit and actual receipt. HMRC's charge, reclaim and record VAT guide explains why invoice and account records matter. A named tax or accounting reviewer must decide the treatment of the actual purchase.

Use period cash need = gross payments + payroll cash + other purchases - credits received. Units are the recorded currency for the dates shown. Include deposits, minimum commitments and termination payments. Exclude unapproved refunds. Test late credits, changed invoice timing and foreign exchange.

Tab C: acceptance and dispute evidence

For each billed unit, store the source identifier, collection context, destination, validation version, acceptance state, decision time and any rejection reason. Keep personally identifiable data out of the finance view unless necessary and approved.

The ICO's data sharing agreement guidance recommends recording purposes, roles, stages, standards, review and termination arrangements. It also warns that an agreement provides no immunity from a breach. Handle lead data under the UK GDPR and Data Protection Act 2018, and link the budget evidence to the controlled operational record rather than copying unrestricted lead data into a workbook.

Tab D: controls and sensitivities

Give each assumption a base, lower and higher input supplied by its owner. These are conditional cases, not predictions. Vary volume, accepted-unit share, staff effort, complaint demand, implementation delay, security remediation, accessibility defects and exit effort. Show the switching input that changes the commercial choice.

Add fields for authorised commitment, variance tolerance, approval level, review date, renewal notice and reforecast trigger. Use blank entries such as [amount and currency], [unit tolerance] and [named condition]; the template does not invent universal limits.

Security and accessibility are separate gates. NCSC's SaaS security guidance directs risk owners towards due diligence while noting that services change. The WCAG 2.2 standard provides criteria against which qualified testers can examine the configured route. Budget the work, evidence and retest; do not treat either link as approval.

Tab E: decision and change history

List finance, tax, commercial, legal, privacy, PECR, security, accessibility, consumer and advertising decisions separately. A fail or unresolved item holds the relevant commitment even when the cash total is acceptable.

In the decision and change history, log each approval and update with previous and new value, reason, evidence, author, approver and effect.

Reforecast after scope, price, tax, volume or recipient changes, and after data use, complaint pattern, security evidence or accessibility status changes.

Before renewal, reconcile modelled and actual invoices, internal hours, credits and exceptions, and archive the signed version so reviewers see forecast error, not rewritten history.

Before you act

Common questions

How should line cost be calculated in the cost register?

Calculate line cost as fixed amount plus quantity multiplied by unit amount. Retain the quote currency and convert only through the finance team's documented rate and date. Do not populate an industry average where the evidence cell is empty, and keep internal effort apart from supplier fees.

What does the ICO guidance say about data sharing agreements?

The ICO recommends recording purposes, roles, stages, standards, review and termination arrangements. It also warns that an agreement provides no immunity from a breach. Link budget evidence to the controlled operational record instead of copying unrestricted lead data into a workbook.

When should a reforecast be triggered?

Trigger a reforecast after scope, price, tax, volume, recipient, data use, complaint pattern, security evidence or accessibility status changes. Before renewal, reconcile modelled and actual invoices, internal hours, credits and exceptions. Archive the signed version so later reviewers can see forecast error rather than a rewritten history.