Few companies limit themselves to a single trade in a single territory. A building contractor often works in heating, plumbing and renovation at once; a broker covers several insurance branches; an agency spans several municipalities or several cantons. On the supply side, a single request generator can feed multiple categories from separate forms. On a marketplace that covers more than sixty categories across the whole of Switzerland, this plurality isn't an exception to handle case by case: it's the most common situation. Managing "several sectors and zones" therefore isn't a matter of stacking separate sign-ups, but of steering a portfolio of perimeters inside a single two-sided system.
This dossier explains, independent of any single category, how the marketplace is structured to absorb this reality: why a company often operates across several sector/zone pairs, how to configure a distinct intake profile for each, how scoring and traceability work when they're spread across several perimeters, how to avoid overlaps and duplicates between adjacent zones, and how to steer and then arbitrate this portfolio over time. The aim isn't to maximise a buyer's return, but to understand the shared mechanics that apply symmetrically to both sides of the market as soon as a participant is present in more than one segment.
Why a company often operates across several sectors and zones
Single-trade activity in a single territory is the exception rather than the rule. One building company frequently handles heating, plumbing and energy renovation at once, because those trades overlap in the field and its customers move naturally from one to the next. A broker covers several branches — personal insurance, pensions, property — and several cantons at the same time. On the supply side, a request generator often runs several specialised forms, each feeding a different category. This plurality simply reflects how economic activity actually unfolds, straddling neighbouring trades and adjacent zones.
A two-sided marketplace is built to absorb this reality without forcibly simplifying it. The structuring principle is that each request is tied to exactly one category and one geographic zone: a company present across several segments therefore doesn't receive a mixed flow, but as many distinct flows as it has active perimeters. That granularity is what makes multi-sector presence manageable rather than confusing. Where a single provider would tend to dump a heterogeneous stock of contacts, the marketplace keeps each request in a queue identified by its sector/zone pair, which lets a multi-present participant keep each activity legible on its own instead of watching them dissolve into one another.
Setting up a distinct intake profile per sector and per zone
On the marketplace, an intake profile is defined not globally but per (sector, zone) pair. A company handling heating in Geneva and plumbing in the canton of Vaud sets up two distinct profiles, each with its own desired monthly volume, its own coverage area, and its own preference between exclusive and shared leads. This separation isn't an administrative constraint: it follows from the fact that a request belongs to only one queue at a time. Setting a single, global volume would be meaningless, since a Geneva heating request and a Vaud plumbing request never travel through the same distribution queue.
This per-perimeter configuration has a concrete consequence: each segment can be tuned independently of the others. A company can request a high volume in a zone where its response capacity is strong, and stay cautious in a category it has just opened. It can choose exclusivity in a highly competitive trade and accept sharing in another. The profile's granularity is therefore the basic tool of multi-sector operation: it's what turns a scattered presence into a set of perimeters each tuned one by one, rather than a global flow impossible to adjust finely. A poorly framed profile penalises only its own segment, without contaminating the other active perimeters of the same account.
Scoring and traceability across several perimeters
The scoring system that sorts requests before distribution applies per category and per zone, not in aggregate. A company's track record — response time, dispute rate, consistency — is measured segment by segment: strong performance in heating in Geneva doesn't mask weak responsiveness in plumbing in the canton of Vaud, and vice versa. This per-perimeter measurement is what keeps multi-sector steering honest. Each request also carries the metadata of its origin — the source that captured it, the category, the zone, the timestamp — and this information stays attached to the request throughout its journey, from capture to matching.
This per-perimeter traceability benefits both sides symmetrically. For a multi-present company, it makes it possible to read real performance per segment rather than an indistinct average, and to contest a disputed case with the precise track record of the sector/zone pair involved. For a source active in several categories, the same principle applies: its flow is scored independently in each category, so that a good flow of renovation requests doesn't offset a weak flow in insurance. The operator thus has, for arbitration, a record at the perimeter level rather than a global average — a necessary condition for each segment to be treated on its own merits.
Avoiding overlaps and duplicates between adjacent zones
As soon as a company covers neighbouring zones or perimeters that partly overlap, a duplicate risk appears: the same request might seem to match two of its own profiles, or the same contact might reach it both via exclusivity in one zone and sharing in another. The marketplace prevents this risk by de-duplicating at the level of the request itself: a given request belongs to a single sector/zone pair and is offered only once to any one company, regardless of how many profiles that company has configured on neighbouring perimeters. A multi-zone participant therefore doesn't end up receiving — or working — the same contact twice.
The same principle governs transparency about distribution. The cap on the number of receiving companies is applied per request, not per account: when a request is marked exclusive, it's passed to a single company only, and the fact that other profiles of the same participant cover adjacent zones doesn't circumvent that cap. Managing several zones therefore largely comes down to setting clear boundaries between perimeters, so as not to compete against oneself at the margins or count the same opportunity twice. The platform's structural de-duplication does this work upstream, but a well-partitioned portfolio makes it all the more legible.
Steering and arbitrating a multi-sector portfolio over time
Managing several sectors and zones isn't a fixed setting made once and for all: it's ongoing steering. By comparing performance segment by segment, a company can redeploy volume from a saturated zone to an under-served perimeter, pause a category where its response capacity is momentarily stretched, or open a new sector/zone pair when it expands its activity. It's precisely the per-perimeter traceability described above that makes this steering possible: without a segmented reading, adjustment would be guesswork; with it, it rests on the real track record of each perimeter.
The operator's arbitration role also extends across all of a participant's segments. Disputes, source audits and scoring adjustments are handled at the sector/zone-pair level, and the operator settles contested cases with the record specific to the perimeter involved rather than with an account average. A source active in several categories is audited category by category, following the same logic. This framework ensures a multi-sector portfolio remains a set of separately arbitrated perimeters and not an undifferentiated mass. The other dossiers explore each of these mechanisms in isolation: the two-sided model in detail, lead scoring, arbitrated exclusivity, the three-party FADP legal framework, and how to compare providers.