UK B2B outbound for RegTech
Pipepoint watches the FCA Register and Companies House for the events that create new compliance obligations, ranks the firms behind them, and runs the outreach that references the event by name and date.
FIG 01 — Signal feed
Live
Source: FCA Financial Services Register · Companies House
New authorisation
Baron Securities Ltd
Authorised 4 weeks ago — advising on and arranging investments
Signal score 94
Variation of permission
Northwind Payments
Added e-money issuance to existing permissions
Signal score 88
Restriction
PayAlto UK
FCA restriction on new client onboarding
Signal score 91
Appointed representative
Calder Wealth Partners
Third AR added under existing principal permissions
Signal score 76
Officer change
Meridian Credit Ltd
New director appointed — compliance function
Signal score 72
Illustrative examples. Firm names are fictional.
FIG 02
The problem
The standard approach picks a job title and a company size, then sends the same message to everyone who matches. That tells you a firm could buy. It says nothing about whether they are buying now.
Fit is static. Timing is not. A firm that was authorised last month, added a permission, or picked up a restriction has a new obligation and usually a deadline attached to it. That is the window where a compliance tool stops being a nice idea and becomes a line item.
In UK financial services those events are public, dated, and specific enough to write about.
FIG 03
Three steps. I run all of them, and you approve the messaging before anything is sent.
01
I track the FCA Financial Services Register and Companies House daily. New authorisations, variations of permission, requirements and restrictions, appointed representative changes, and the director and PSC changes that sit behind them.
02
Every event is ranked by how live it is: how recent, what obligation it creates, the firm's size and permissions, and whether it maps to what you sell. You get a ranked list with the source and date on every row, not a scrape.
03
Each message references the specific event, so the first line could only have been written to that firm. Sent from a domain we agree on, with replies coming straight to you. I handle sending infrastructure, follow-ups and list hygiene.
Baron Securities — authorised 12 March
You were authorised on 12 March for advising and arranging. Firms at that stage usually pick their transaction monitoring before the first audit rather than after it.
Worth fifteen minutes next week?
FIG 04
Who it's for
Pipepoint fits if a regulatory event is a real reason for someone to talk to you.
Onboarding, screening, ongoing due diligence.
Financial crime, fraud and payments risk tooling.
RegData, transaction reporting, prudential returns.
Policy, registers, attestations, audit readiness.
Products with no UK regulatory angle. Teams that need thousands of contacts a month rather than a few hundred correct ones. Anything where the compliance function is not part of the buying decision.
FIG 05
Tell me what you sell and who you sell it to. I will come back with the event types that apply to you and what the first list looks like.
max@pipepoint.ioMax — Pipepoint
