← Library
Methodology · Author

Behind the Library

The coverage philosophy, valuation frameworks, data sources, and AI workflow behind every dashboard in this library.

Coverage Philosophy

Eight categories mapped to where technology valuation is contested

The library is organised into eight categories that intentionally mirror the most contested areas of the technology sector right now: generative AI infrastructure (compute silicon, memory & storage, infrastructure software), the hyperscalers funding it, early stage quantum, the security stack absorbing AI driven attack surfaces, the physical AI / robotics layer, and the underlying networking & server hardware that runs everything.

CategoryWhy it's in scope
Quantum ComputingLong duration, pre revenue. Valuation needs a fundamentally different lens (TAM × probability × time, not DCF). High dispersion of outcomes.
Compute Silicon & FoundriesThe full chip stack: merchant GPUs, custom XPUs, AI networking, foundries, and semiconductor capital equipment. AI workloads are the marginal driver but the cycle covers all of compute.
Memory & Storage HardwareHBM is the supply constrained bottleneck of AI training; DRAM / NAND cycle dynamics are the most predictable in semis if you read the bit math. Storage hardware sits one layer above.
HyperscalersThe capex source funding the entire AI infrastructure stack. Microsoft, Google, Amazon, Meta, Oracle together drive ~$420B+ of 2026 AI capex. Their disclosures set the demand backdrop for every silicon, memory, and networking thesis below; their own valuation is increasingly an AI platform question (Azure, GCP) on top of legacy software / consumer franchises.
CybersecurityRecurring revenue software with structural tailwinds; the right valuation lens varies by subsegment (endpoint vs network vs identity vs cloud).
Robotics & AutonomyEarliest stage of the seven. Many names are still proving unit economics. Differentiating real product traction from narrative is the alpha.
Infrastructure SoftwareThe application layer above the silicon. Includes observability, virtualization, databases, data clouds. Net dollar retention is the key metric.
Networking & Server HardwareDatacenter switches and routers, server / appliance OEMs, and the PC supply chain. Cycle dynamics + customer concentration risk are the recurring debates; AI buildouts dominate the near term thesis for the networking subset.

Valuation Framework

Different asset classes get different models

One of the biggest tells of weak research is forcing every name into the same valuation model. I use four primary frameworks, picked per company based on business stage and earnings quality:

FrameworkBest forUsed in
DCF + sensitivity gridCompanies with predictable cash conversion and a defined steady state. Required when terminal year economics are the dominant driver of value. Segment level DCF when the business is a multifranchise compounder where each segment has materially different cash dynamics.Micron (memory cyclical); Microsoft (segment level: Productivity, Intelligent Cloud, More Personal Computing)
Sum of the Parts (SOTP)Multiline companies where blended multiples obscure the underlying business mix. Each franchise valued on its own EBITDA × multiple.Broadcom (AI semis × non AI semis × VMware software)
EV/Sales + scenario treePre profit names where EBITDA is uninformative. Anchor on revenue, attach probability weighted scenarios for the path to profitability.IonQ (quantum pre profit)
Comp matrix (EV/EBITDA, EV/Sales, P/E)Cross checking primary models against peer multiples. Forces the primary model to defend its inputs against the market's pricing of similar businesses.Across all dashboards (in development)

Scenario discipline

Every dashboard frames Bull / Base / Bear with explicit price targets and probability weights. The weights live in data.js (pBull, pBase, pBear) and the shared engine renders the resulting probability weighted blended fair value directly under the summary KPI grid on every dashboard. Two outcome checks are visible on the same line:

The reader does not have to take the headline PT on faith. They can see the math behind it and judge for themselves whether the probability assignments are credible.

Data Sources

What I use and where the curated figures come from

Every figure that isn't from the live feed is curated in a per-dashboard data.js file with an asOf field. Curated figures are reviewed on a quarterly cadence (after each earnings print) and on material developments.

AI Workflow

Where AI tools accelerate the research, and where they don't

I use AI tools as an analyst force multiplier, not a substitute for judgment. Specific places they're integrated into this library:

What I deliberately do not use AI for: the rating decision, the price target, and the scenario probability weights. Those are author judgements. The AI tools accelerate the inputs to those decisions; they don't make the decisions.

Update Cadence

When dashboards refresh and what triggers a re-publish

The "Data as of" stamp on each dashboard, and on every hub card, carries a colored freshness badge so a reader can see at a glance how current the underlying snapshot is:

Live price driven values (last trade, YTD %, market cap, forward P/E) are independent of this badge, they refresh on every page load via the quote feed. The badge applies only to curated, point in time figures.

Disclaimers

Read before relying on anything in the library

Not investment advice. The research in this library is the author's personal analytical work, prepared for portfolio and educational purposes. Nothing in it constitutes a recommendation to buy, sell, or hold any security. Past performance does not predict future results; forward looking statements are subject to material risk and uncertainty.

All third party trademarks, company names, and product names referenced in the library are the property of their respective owners. The author has no affiliation with any company covered unless explicitly disclosed within a specific dashboard.