The lead generation platform and operating system for lead generators

A request can arrive in many ways: via a form on one of your landing pages, via a direct API call, via a connected publisher or via an autonomous AI agent. The platform normalizes all of those channels into a single structured data format, so that every request, regardless of source, is processed and assessed in exactly the same way.

On arrival, the platform immediately records the technical context: the source channel, the campaign or label, the timestamp and the raw payload as it was delivered. That first record is the foundation of the audit trail and can no longer be overwritten afterwards, only supplemented. Everything runs under your brand and on your domains.

Before a request moves further down the chain, consent is recorded and timestamped. The platform stores which consent text the requester was shown, at what moment it was given and from which channel, accompanied by an immutable timestamp. That way consent is not a checkbox after the fact, but a demonstrable fact attached to the request.

In the same step, the platform checks quality and provenance: are the required fields present and plausible, is the format of phone and email correct, and is the source traceable? Requests that do not pass are flagged or held back, so that your buyers only receive requests that have cleared verification.

Verified requests are then matched in a privacy-safe way to the most suitable buyer. The matching uses signals such as the nature of the request, the region or postal code, the intent and the current capacity and preferences of buyers. Personal data is not shared more broadly than necessary: matching happens on the basis of derived characteristics, not by sending the full request around.

Because matching runs on rules and signals instead of manual work, the outcome stays consistent and reproducible. Every match decision is logged with the criteria that applied, so afterwards you can verify why a request ended up with a particular buyer.

After the match, routing determines where the request actually goes. Routing rules work on the basis of priority, quality thresholds, daily caps, exclusivity and region: you define which buyer may receive which requests and under what conditions. If a buyer is declined or has hit its limit, the request automatically falls back to the next in line.

Routing stays entirely in your own hands: you set the rules yourself and adjust them in real time without interrupting the chain. The handover to the buyer happens in a structured way via API or CRM integration, together with the associated provenance and consent data, so the recipient immediately knows what they have in hand.

Every step a request goes through (intake, verification, match, routing, acceptance and payout) is recorded in a continuous audit trail. That log is append-only: events are added, never erased or rewritten. As a result, at any moment you can reconstruct what happened to a request, when and by whom.

On top of that log run the dashboards: volume, quality, acceptance rate and payout at a glance, plus exportable overviews for your own records or a regulator. Transparency is not a separate report you assemble afterwards, but a direct consequence of how the platform records the data.

As soon as a buyer accepts a request, that forms the basis for settlement. The platform tracks per request which fee applies, who delivers and who receives, and on that basis assembles clear, verifiable payouts. Your publishers see exactly which requests count and why.

Not every request is flawless, which is why dispute handling is built in. A buyer can dispute a request within the agreed conditions; that dispute is linked to the original audit trail, assessed on the basis of the recorded facts and settled neatly. No back-and-forth, but a decision based on what demonstrably happened.