Roofing is a trade where demand shows up in two very different guises. On one side, urgency: a tile ripped off by a windstorm, water staining a ceiling after a hailstorm, a gutter overflowing during the spring snowmelt. On the other, the carefully considered project: a full re-roof of an ageing cover, a new underlay, external insulation, waterproofing a flat roof, or preparing a roof before a solar installation. A leads marketplace has to handle both realities, because they carry neither the same value nor the same response window.
A marketplace isn't a static contact list you buy once. It's a two-sided system: on one side, roofing and sheet-metal companies looking for qualified requests; on the other, referral partners — specialised sites, renovation comparison platforms, local networks — who produce those requests and feed them into the same platform. leads-qualifie.ch acts as the intermediary between both sides, applying shared rules for verification, scoring and matching. This guide walks through the full mechanism for the "roofing" category: how a request enters, how it gets scored, what separates an exclusive lead from a shared one, how to compare several providers, and which Swiss data protection rules govern the exchange.
How the roofing leads marketplace works
On a marketplace, a roofing request follows a structured path. A homeowner or a property manager expresses a need — fixing a leak, replacing broken tiles, redoing a whole roof, laying new waterproofing on a flat roof, insulating an attic, or de-mossing a fouled surface. The request gets tagged with the "roofing" category and a precise geographic zone, then it's offered to roofers active in that area. Unlike a single reseller selling you its own list, the marketplace aggregates several sources under one roof — widening the available volume and letting you compare rather than depend on a single channel.
On the buyer side, a roofing company browses the dedicated category and picks its coverage area — radius matters especially in roofing, because a distant job means hauling scaffolding and a lift — then receives matching requests as they come in. On the supply side, referral partners (renovation quote forms, works comparison sites, local networks) feed the same category under shared quality rules. Many platforms further segment roofing by type of need — emergency repair, re-roofing, flat-roof waterproofing, insulation, sheet metal — to avoid sending a de-mossing request to a company that only does structural carpentry. It's this double discipline, on both the demand and supply sides, that sets a real marketplace apart from a plain resold list.
- Every request is tagged with the roofing category and a type of need (leak, re-roof, flat-roof waterproofing, insulation, de-mossing).
- The geographic zone is strict: in roofing, coverage radius weighs heavily because of scaffolding and lift logistics.
- The marketplace aggregates several sources of requests rather than a single opaque feed.
- Referral partners are themselves rated on the quality of what they submit.
Lead quality and scoring for roofing
Every request entering the marketplace is assessed before being offered to a company: validity of the Swiss phone number, coherence of the e-mail, a description of the need, and proof of explicit consent to be contacted. In roofing, the precision of the need weighs heavily in the score, because two requests both tagged "roofing" can be completely different animals: a one-off leak to patch has nothing in common with re-roofing 200 m² of tile cover, and a roofer doesn't want to waste time on a need outside its specialty. Good scoring therefore tries to capture the type of roof (tile, slate, metal, flat), the approximate surface, the age, and whether there is an emergency.
The difference from a single provider lies in scale: on a marketplace, this score also factors in the track record of the source that produced the request. A partner who regularly submits unreachable contacts, requests already worked elsewhere, or tenants with no mandate from the owner sees its flow downgraded, while a reliable source gains visibility. In roofing this last point is decisive: a request from a tenant who isn't the decision-maker, or from a condominium unit where the decision rests with the owners' assembly, rarely turns into a job. Rigorous scoring accounts for this decision-maker status before circulating the request.
- Verified details: valid Swiss phone number, active and coherent e-mail.
- Qualified roofing need: roof type, approximate surface, re-roof or repair, urgency level.
- Requester status factored in: decision-making owner, property manager or condominium rather than a tenant with no mandate.
- Source track record factored in: an unreliable partner gets downgraded.
Exclusive or shared leads: how the marketplace arbitrates
On a marketplace, exclusivity isn't a hidden option — it's explicitly chosen by the roofer when setting up its intake profile. An exclusive lead is sent to a single company only; a shared lead goes to a limited number of professionals, disclosed in advance — never distributed without a cap. This transparency about the number of recipients is what separates a serious marketplace from a list resold multiple times with no traceability.
In roofing, the type of need strongly shapes the trade-off. An active leak after a storm creates very strong intent: the owner wants it patched fast, even calling several firms in parallel — a shared lead can stay relevant if the company calls back within the hour. Conversely, a full re-roof is a project worth tens of thousands of francs, with a technical visit, measurements and a detailed quote: the owner compares few firms but expects genuine advice. On that kind of request, exclusivity limits the split, leaves time to draw up a serious quote, and is often justified. Many companies take repair work as shared leads to keep crews busy, and reserve exclusivity for big re-roofs where the technical appointment makes the difference.
How to compare roofing lead providers
Within the same category, several lead providers can coexist with very different practices. Before committing, it's worth comparing where requests originate (the platform's own forms, verified partners, or bulk-bought data with no traceability), the replacement policy for invalid leads, and how fine the filtering is — because in roofing, a platform that doesn't distinguish repair, re-roofing and flat-roof waterproofing will send you plenty of off-target requests.
A marketplace that works well is happy to share these details openly: the proportion of urgent requests versus planned projects, how quickly a complaint is handled, the share of exclusive versus shared leads, and above all the ability to target the roof type you handle. Be wary of a provider that won't disclose where its requests come from, offers no recourse for unreachable contacts, or lumps all roofing into one catch-all category with no qualification of the need. On a transparent marketplace, this information is part of the service, not an optional bonus.
- Declared origin of requests: own forms, verified partners, never bulk data.
- Fine filtering by type of need: repair, re-roofing, flat-roof waterproofing, insulation, sheet metal.
- Clear replacement policy for invalid, unreachable or out-of-zone leads.
- Urgent versus planned-project split disclosed, not just promised.
Legal framework: Swiss data protection on a leads marketplace
A marketplace involves three parties in data handling: the end customer, the partner who collected the request, and the roofing company that receives it. The Swiss federal data protection act (nLPD) applies at every step: the customer must have given explicit consent to be contacted by a professional in the sector, and that consent must be traceable — not simply asserted by the platform. In roofing, a common subtlety deserves attention: when a request comes from a property manager or a condominium, the consenting person must actually hold the mandate to solicit quotes for the building concerned.
As the receiving company, check that the marketplace can demonstrate the origin of consent (form, checkbox, timestamp) and that it holds its own providers to this standard, rather than just relaying data with no oversight. You remain responsible for how you handle the contact details once received: keep them only as long as needed to process the request and the relationship that follows, then respect the customer's right to opt out of further contact.
