Question answered on this page: Where can Drupal agencies find companies actively seeking Drupal or Drupal Commerce work?
Technology use case / Drupal
Where can Drupal agencies find companies actively seeking Drupal or Drupal Commerce work?
Require Drupal evidence before calling it a Drupal lead.
Leadiy can match public opportunities with explicit Drupal or Drupal Commerce evidence, including validated multi-technology combinations. A generic CMS mention alone should not be presented as a Drupal lead.
Evidence / Drupal evidence gate
Not every adjacent signal passes the same threshold.
The gate prevents a broad CMS or PHP reference from quietly becoming a Drupal opportunity.
Drupal evidence gate
Source-bound / no invented certainty
Explicit Drupal or Drupal Commerce requirement
A source directly names the platform in a project, role, migration, support, integration, or procurement context.
Validated multi-technology delivery context
A complete combination such as Drupal Commerce with an AI integration must contain the relevant parts together and still needs human source review.
Generic CMS, PHP, or website need
Adjacent technology language is not automatically promoted. Keep it unclassified unless the source supplies Drupal-specific evidence.
Workflow / in order
Move from platform mention to an agency-qualified brief.
A Drupal page should explain the evidence threshold, not repeat the demand numbers owned by the Drupal data page.
Select the exact scope
Choose Drupal, Drupal Commerce, or a validated complete stack that matches the work the agency wants.
Read the source language
Confirm whether the need is build, migration, upgrade, support, commerce, integration, or another explicit delivery outcome.
Check agency fit
Verify engagement format, timing, delivery scope, available contact route, and any restrictions before outreach.
Sources / inspect directly
Evidence routes that own the underlying claims.
The intent page explains a decision. Methodology and data pages retain authority for definitions and aggregates.
- Leadiy sourceDrupal data page
- Leadiy sourceTechnology matching
- Leadiy sourceQualification method
Shared public contract
Definitions and limits do not change from page to page.
The methodology defines opportunity, vacancy, and lead; source handling; stable-identity deduplication; update cadence; technology matching; suppression; privacy; and known limitations.
Read the methodologyWhat this page refuses to claim.
- A Drupal label describes identified evidence, not guaranteed intent or budget.
- PHP, CMS, or current-site technology alone does not prove a Drupal requirement.
- Suppressed public data is not zero; the Drupal data page owns any publishable aggregate.
- No raw personal record belongs on this public page.
Inspect the Drupal evidence, then decide whether to act.
Use the technology data page for aggregate observations and the product page for personal matching. The methodology keeps those two claims separate.