Question answered on this page: How do I find qualified software-development leads without wasting time on stale or irrelevant listings?
Field guide / software opportunity qualification
How do I find qualified software-development leads without wasting time on stale or irrelevant listings?
Build a qualification system, not a bigger inbox.
Use a repeatable sequence: define the service and stack, collect current signals, deduplicate them, verify the original source, qualify fit and engagement type, respect suppression, and move accepted records into a pipeline. Freshness narrows timing; it does not guarantee fit or response.
Evidence / checklist
Eight checks separate a visible signal from an accepted lead.
The checklist makes failure useful: a rejected record leaves a reason that improves the next search.
- Service definition
Can the team name the outcome and stack it is prepared to deliver?
- Stable identity
Has the signal been deduplicated against the same source, organization, and opportunity?
- Source authority
Is the original source available, current, and consistent with the structured record?
- Engagement type
Is this a direct lead, vacancy, project, contract, procurement item, or an unclear signal?
- Technology evidence
Does the direct technology or complete-stack evidence satisfy the selected profile?
- Agency and delivery fit
Can a company or team credibly deliver the scope under the stated constraints?
- Contact permission
Is the route appropriate, and has suppression or do-not-contact evidence been checked?
- Recorded next action
Does the accepted record have an owner, pipeline state, reason, and source-linked next step?
Workflow / in order
The end-to-end software lead workflow.
Each stage produces an artifact the next stage can inspect. No hidden leap converts a mention into a buyer.
Define
Specify services, direct technologies, complete stacks, geographies, engagement types, and hard exclusions.
Observe
Collect current public signals and preserve source platform, URL, source timing, and first-observed time where available.
Normalize and deduplicate
Map comparable fields and refresh an existing stable record rather than multiplying copies of the same opportunity.
Verify
Reopen the source, record the verification time, and keep the last good state visible if a later check fails.
Qualify
Assess service, technology, source, agency, timing, evidence, and contact-route fit. Preserve unknowns.
Act and learn
Move accepted records into the pipeline, honor suppression, and use rejection reasons to refine the profile.
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 sourceFreshness and provenance
- Leadiy sourceHow Leadiy works
- 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.
- Opportunity, vacancy, and direct lead are different records and should not be collapsed into one claim.
- Direct leads are excluded from the public aggregate dataset because they can contain personal or restricted contact data.
- A scheduled refresh does not guarantee source availability, fit, status, or response.
- No minimum lead volume or commercial outcome is promised.
Make every accepted lead explain why it survived.
Use the freshness page to understand timing, the product page to configure matching, and the methodology as the shared qualification contract.