B2B sales leaders are the audience most consistently caught off guard by PECR. The cadence tool does not flag corporate numbers as risky, the lead-data vendor does not ship a TPS verdict, and the prevailing assumption is that the rules apply to consumer marketing only. None of that is true. Corporate direct dials are exposed under CTPS, sole-trader numbers are exposed under TPS, and the ICO has fined for B2B-only outbound activity. If your stack assumes B2B is out of scope, the exposure is already live.
The "we are B2B, doesn't apply" myth
PECR contains no general carve-out for business-to-business marketing calls. Regulation 21 covers unsolicited live marketing calls to any UK number where the subscriber is on the relevant register. Regulation 21A points the same prohibition at corporate subscribers via the CTPS. The route to compliance is the same in both directions: prior specific consent, or the number is not on the relevant register. "We only call businesses" is a screening policy in practice, not an exemption. See the deeper treatment in B2B CTPS rules explained.
CTPS scope: corporate direct dials are exposed
The dangerous data on a B2B list is not the switchboard. It is the direct dial. Once a corporate subscriber has registered the organisation on CTPS, every line under that subscription is protected for the purposes of regulation 21A, including direct extensions and PBX-routed mobiles. Sales tools that surface a prospect's mobile do not show whether the subscription is on CTPS, because they cannot. The verdict has to come from a screening service.
The mixed-register problem
A typical B2B list contains numbers that look corporate but legally are not. The plumber, the freelance consultant, the single-director services firm, the retired-partner advisor on their personal mobile: these are individual subscribers, and their working numbers belong on the TPS, not the CTPS. A team screening only against CTPS will miss this entire population. The fix is to screen every UK number against both registers in a single pass and store the verdict per phone field on the contact record.
See TPS vs CTPS for the register split, including the subscription rules that determine which register a number actually sits on.
Salesloft and Outreach cadences do not check
Cadence tools were not built for PECR. They consume a list, execute the steps, and report on activity. The fields they understand are owner, segment, sequence and stage. The fields they do not understand are TPS status, CTPS status and screened-at timestamp. If you want a cadence to skip a flagged number, the cadence tool has to read a property on the contact record that says "skip", and that property has to be kept current by something else. The cadence tool will not maintain it for you.
The CRM as the source of truth
The contact record is the only place where TPS and CTPS status can sit alongside owner, lifecycle stage, ICP fit and consent evidence. The cadence tool, the dialler, the call-recording platform and the reporting layer all need to read from the same field. If the screened status lives in a separate compliance tool that the rest of the stack does not read, the gap is open by default and only closes by accident. The lead vendors do not close it either; see the ZoomInfo, Lusha and LeadIQ comparison for what they ship and what they do not.
The TPSClear pattern
TPSClear writes a screened status against every phone field on the contact record, not a single record-level flag. A contact with a switchboard, a direct dial and a mobile gets three verdicts, refreshed independently. This matters in practice because the same contact can have a clean switchboard and a flagged mobile, and a record-level flag forces the cadence tool to choose between blocking everything or dialling everything. Per-property verdicts let the cadence tool dial the safe numbers and skip the registered ones, automatically.
Hide vs flag
Two operating modes work for B2B teams, depending on appetite:
| Mode | Behaviour | Best for |
|---|---|---|
| Flag | Property set to registered, cadence steps skip the dial, email and other channels continue. Rep sees the flag in the record. | Default for most B2B teams. Preserves the contact for email, social and inbound, removes only the dial risk. |
| Hide | Property set to registered, contact is excluded from outbound views and cadence enrolment entirely. | Regulated firms, very high-volume teams, or accounts where the rep workflow benefits from not seeing the record at all. |
The cost angle for the CFO
The financial argument is short. ICO PECR fines run to a statutory cap of £500,000 per breach pattern. The cost of screening a B2B database against TPS and CTPS continuously is an order of magnitude smaller than the cheapest reported fine. The reputational drag of the alternative, a published ICO finding against the company name, is significantly worse than the fine itself for any firm selling into compliance-sensitive accounts.
Where to start
Connect TPSClear to the CRM, run an initial backfill, and let the cadence tool read the resulting properties. The CRM integrations page covers HubSpot today and Salesforce, Dynamics 365, Pipedrive, Zoho and Capsule in build. The screening regime is in place inside a working afternoon, and the audit trail begins from the first run.