LEADIY Current section: Use cases

Question answered on this page: What is the fastest way to find newly published software-development leads with source evidence?

Use case / freshness and provenance

What is the fastest way to find newly published software-development leads with source evidence?

Freshness is a timestamp, not a promise.

Leadiy checks configured sources every 30 minutes and makes source and freshness evidence visible, but that cadence is not a real-time guarantee: every opportunity still needs source and fit verification.

Evidence / Freshness clock

Four moments answer four different questions.

Collapsing these moments into one “updated” label creates false certainty. The methodology keeps observation and verification separate.

Freshness clock

Source-bound / no invented certainty

Published

When the source says the opportunity appeared

This can be known, approximate, or missing. It belongs to the source, not to Leadiy’s observation process.

First observed

When Leadiy first recorded the signal

This establishes the beginning of the record’s observed history without rewriting the source publication time.

Observed through

How far the dataset’s observation window extends

This describes data coverage and belongs beside any aggregate derived from that window.

Verified at

When the source or snapshot last passed its verification check

Verification can lag observation. A failed check should preserve the last good snapshot and expose the delay.

Workflow / in order

Use freshness to order work, then use evidence to decide.

A new record earns attention first; it does not automatically earn outreach.

01 / 03

Sort by the right time

Distinguish source publication, first observation, change time, and last verification before prioritizing.

02 / 03

Reopen the source

Confirm the opportunity still exists and that material scope, timing, or contact details have not changed.

03 / 03

Qualify and record the decision

Accept, reject, or hold the record with a reason so freshness does not cause repeated low-quality work.

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.

Source → evidence → decision

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 methodology

What this page refuses to claim.

Make the next source check explainable.

The product page explains the operational flow. The methodology defines observation, verification, deduplication, and source authority.