On a leads marketplace, the quality of the requests you receive doesn't depend on the sources capturing them alone: it depends just as much on how well you've configured and maintained your intake profile. That profile is the interface between the demand side — your company — and the matching engine that decides which requests reach you. A vague profile returns generic matches; a precise profile, kept up to date and fed by regular feedback, returns requests far closer to what you can actually handle. Optimising this profile isn't a question of price: it's a relevance lever, mirroring the scoring work applied to sources on the other side of the market.
This dossier explains, independent of the category you follow, how to get the most out of your buyer profile on leads-qualifie.ch: what each intake criterion means, which signals the matching engine actually reads, why your responsiveness and feedback feed the scoring system just as much as the quality of the request generators, how the traceability of your qualifications sharpens later matches, and how to adjust your profile over time so it stays a faithful reflection of your business. The goal is never to receive more requests at any cost, but to receive better-fitting ones, more closely aligned with your trade, your area and your real capacity to process them.
The intake profile, the interface between you and matching
The buyer profile — or intake profile — is the set of parameters the marketplace's matching engine reads to decide which requests to send you. It's not the same as a mere account: it's the translation, into criteria the system can read, of what your company can really do, where it operates and how fast it can absorb requests. On a two-sided marketplace, this profile plays, on your side, the mirror role of the score assigned to sources on the other side: request generators are assessed on the quality of what they submit, and you are matched according to the precision of what you declare.
This symmetry has a direct consequence: a blurry profile produces blurry matches. If you declare a category that's too broad, an area that's too wide, or an unrealistic volume, the engine has no choice but to offer you heterogeneous requests, part of which will fall outside your actual trade. These poorly fitted requests aren't without consequence: when you mark them off-topic or out of area, they feed the system's traceability and flag a gap between your profile and your business. Conversely, a profile whose every criterion faithfully matches the reality on the ground mechanically narrows the flow to the requests you're best placed to handle. Optimising your profile therefore starts with a simple principle: describe it as your company truly is, not as you'd like it to be.
Setting each intake criterion with precision
An intake profile is made up of several criteria, and each deserves careful setting rather than being left at its broadest default. The category first: it should reflect your effective skills, not the full range of services you might one day consider offering. Declaring a category where you only occasionally operate means receiving requests you'll rarely convert, which degrades your reception track record. The geographic area next: it should match the perimeter where you can genuinely intervene quickly, because proximity and freshness weigh heavily on turning a request into an appointment. An artificially inflated area attracts requests that are too distant, which you'll end up declining.
Then come the monthly volume and the preference between exclusive and shared. Volume should be calibrated to your team's real capacity to call back and process requests: over-declaring a volume you can't absorb leads to requests left unhandled, degraded feedback and, over time, less favourable matching. A modest volume handled seriously beats an ambitious one served poorly. The exclusive-or-shared preference, finally, steers the type of requests that reach you and the number of companies receiving them at the same time. Each of these settings acts as a filter: the more they match your operational reality, the denser the resulting flow is in genuinely usable requests, and the more reliable the cues the marketplace has to send you what suits you.
Responsiveness, a strong signal read by the marketplace
On a marketplace, the speed and consistency with which you engage the requests you receive aren't just good internal practice: they're signals the system observes and factors in. A request contacted quickly, while it's still fresh, converts far more often than one called back several days after capture. The matching engine, which seeks to steer the hottest requests towards the companies that will use them well, takes this behaviour into account: a responsive, consistent reception builds a profile to which it's logical to send fresh, well-fitted requests as a priority.
Optimising your profile therefore means preparing the organisation that makes this responsiveness possible, and it has nothing to do with paying more. In concrete terms, it means configuring notifications so you're alerted without delay, clearly designating who handles incoming requests, and setting an internal callback deadline your team commits to respecting. This discipline pays off twice: it directly raises the conversion rate of the requests you already receive, and it strengthens the readability of your profile in the system's eyes, exactly as a source that regularly submits good contacts sees its flow valued. Responsiveness is thus the signal most directly under your control: it depends on no complicated technical setting, only on the consistency with which you handle what reaches you.
Traceability: qualifying each lead sharpens the matches
Every request you receive can, and should, be given feedback: reachable or unreachable, on-topic or off-topic, in your area or outside it, a possible duplicate, turned into an appointment or not. These qualifications aren't an administrative formality: they form the traceability on which the whole marketplace mechanism rests. Regular, honest feedback serves two functions at once. It first lets the operator arbitrate: a source submitting too many unreachable or off-topic contacts is spotted and downgraded precisely thanks to the feedback from receiving companies. It then sharpens your own future matches, because the system learns, request after request, what actually fits your profile and what doesn't.
A profile that never returns qualifications stays opaque to the marketplace: the engine has no cue to correct course, and keeps sending you requests without knowing which ones suit you. Conversely, a company that qualifies its requests consistently teaches the system the exact shape of its need, and sees its matching tighten gradually around the most relevant requests. This traceability also protects you directly: should you contest a clearly defective request — invalid contact details, obviously out of area, a duplicate — it's your documented feedback that serves as the basis for handling the claim. Qualifying is therefore not a one-way effort: it's the investment in information that makes the marketplace fairer, both for you and for all participants.
Reception reputation and continuous profile adjustment
Just as sources build a track record over time, receiving companies build a reception reputation. This reputation is measured not by what you declare but by what the system observes: do you actually process the requests you receive, do you respond within reasonable times, are your qualifications consistent with the recorded data? A profile whose observed behaviour confirms its declared criteria earns the matching engine's confidence, which then has every interest in continuing to steer fresh, well-fitted requests towards it. This reputation is therefore no decorative badge: it's a relevance asset, built slowly and quick to erode when reception is neglected.
Maintaining this profile finally means treating it as a living instrument, never frozen. It's worth reviewing periodically in light of your own feedback: if you mark too many requests out of area, tighten the perimeter; if the volume received stays below your capacity, cautiously widen the category or area; if your team is saturated, cut the declared volume rather than leaving requests unhandled; if your business is seasonal, adjust your settings accordingly. This continuous adjustment keeps what you declare aligned with what you experience on the ground — the first condition of quality matching. The other dossiers in this hub detail the neighbouring mechanisms: how the two-sided marketplace works, lead scoring, arbitrated exclusivity, the three-party FADP framework, and how to compare providers.