saascode
education & learning·run 041 · Apr 2026

Lagscope

A methodology-first data product for learning and curriculum leaders that normalizes permitted learning-interest and job-posting sources by skill, region, seniority, and quarter, publishes uncertainty and revisions, and supports planning without predicting hiring or individual career outcomes.

Genesis score6.93/10
Make Lagscope real.0/500
500 more votes and Lagscope is authorized for build.
0%500 to authorize
Backing is the vote. When an idea crosses 500, we pull it into the build pipeline and ship it for real — the votes decide what gets built next, not an editor.
The opportunity
3Inbound connections
3Direct connections
2Confirmed job APIs
The case

Learning teams and technical programs need to decide which skills to teach before slow annual reports reveal a mismatch. Lagscope builds a quarterly index from sources the product is authorized to use, maps both sides to a versioned skills taxonomy, and exposes coverage, sample changes, uncertainty, and revisions. The input confirms accessible job-posting and skills-taxonomy sources but does not verify equivalent access to every named learning platform. Search, stars, courses, enrollments, completions, job postings, employer demand, hires, wages, curriculum decisions, and learner outcomes are different signals. A rising index is not a forecast, causal claim, hiring guarantee, or recommendation for an individual.

Who pays — and why

An L&D director, workforce-planning analyst, bootcamp curriculum committee, technical academy, training provider, or research team that needs a repeatable market-timing view.

What it unlocks
A versioned skill taxonomy linking aliases, categories, occupations, seniority, geography, source-specific labels, mapping confidence, and correction
A quarterly observation ledger preserving source rights, retrieval date, coverage, sample, deduplication, normalization, missingness, methodology version, and revision
A buyer-facing index that separates learning interest, course supply, job-posting mention, hiring outcome, wage signal, analyst interpretation, and curriculum decision
How Genesis scored it
6.93across seven criteria
tension 6temporal 8blindspot 6buyer 8leverage 6convergence 5why-not 8
8
Temporal window

The source describes a current learning-versus-posting mismatch, but the underlying headline percentages are not independently verified in the authoring input.

8
Buyer persona

L&D, workforce, and curriculum leaders are concrete, though their purchasing and planning cadences differ.

5
Convergence

Three inbound and three direct connections provide moderate convergence despite no cross-reference count.

Why it scored well

A clear institutional buyer, three inbound and three direct links, two confirmed job APIs, an attributable open skills taxonomy, and no identified recurring developer-specific lag index support a testable data-product thesis.

What's holding it back

Learning-side data access is not verified, source coverage and taxonomies can bias the index, free and annual reports are substitutes, willingness-to-pay is unproven, and observed interest cannot be treated as labor demand or outcome evidence.

Signals detected4 sources crossed
SignalAdzuna developer research

SignalUSAJOBS developer research

SignalLightcast documentation review

SignalSource-run market scan

Direction brieflagscope.md
lagscope.md
Want this pointed at your vertical?Point Genesis at your own market and constraints — it invents adjacent, fork-ready ideas, private to you before they hit the public feed.

Discussion

?

No comments yet — be the first to weigh in.