Question answered on this page: How do I find companies that need Drupal development now?
Field guide / Drupal demand
How do I find companies that need Drupal development now?
Find the need before you find the contact.
Start with explicit need evidence—Drupal, Drupal Commerce, migration, upgrade, support, or a validated integration stack—then verify the source, timing, agency fit, and contact route before outreach. A keyword alone does not prove buying intent.
Evidence / checklist
A record is ready only when the source survives every relevant check.
Use the checklist as a stop rule. An unavailable fact remains unavailable; it does not become a convenient assumption.
- Platform evidence
Does the source explicitly name Drupal, Drupal Commerce, or a validated complete stack?
- Owned outcome
Is the requested work a build, migration, upgrade, support engagement, integration, rescue, or another clear finish line?
- Current source
Can you open the original source, and does it still describe the same need and timing?
- Agency suitability
Does the language allow company or team delivery, rather than clearly requiring one individual employee?
- Delivery fit
Can the agency credibly deliver the scope, stack, location, timing, and operating requirements?
- Appropriate route
Is there a source-approved application or contact route, with no do-not-contact or suppression conflict?
Workflow / in order
A complete Drupal lead workflow.
Follow the sequence in order. Later research cannot repair a failed source or platform-evidence check.
Define the Drupal offer
Write down the exact outcomes the agency can own, including any Commerce, migration, integration, performance, or support boundaries.
Configure exact matching
Select Drupal, Drupal Commerce, or a validated complete stack. Avoid a generic CMS catch-all.
Open the original source
Verify technology, scope, date, engagement type, location, and whether the opportunity is still available.
Classify the engagement
Separate project delivery, procurement, contract work, employment, and unclear language before assessing agency fit.
Record the decision
Accept, reject, or hold the record with evidence and a reason. Preserve unknown fields rather than filling them with guesses.
Use the approved route
Apply at the source or contact through an appropriate available route, honoring suppression and do-not-contact evidence.
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 opportunity page
- Leadiy sourceDrupal aggregate data
- Leadiy sourceData removal and suppression
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.
- Current Drupal usage is not the same as current Drupal demand.
- A technology match does not establish budget, authority, timing, or response likelihood.
- The public Drupal data page contains aggregates only and owns any publishable count.
- Examples on public pages must be aggregate or clearly synthetic, never exposed personal records.
Use the checklist before writing the message.
The Drupal data page establishes aggregate context. The methodology explains classification, deduplication, verification, and suppression.