AI materiality
AI must be a material component of the product value proposition, not incidental marketing.
- Output
- ELIGIBLE / HOLD_AI_RELEVANCE
- Cadence
- At discovery
- Sources
- Primary preferred
- Review impact
- None until verified
Research establishes facts. Review makes evidence-bounded editorial judgments. Commercial terms are kept outside the rating engine.
AiToolMap Research Methodology v2.0
AI must be a material component of the product value proposition, not incidental marketing.
Product must be usable autonomously by the public or by a clearly defined customer class.
Require a stable official destination or official repository/store record sufficient to identify the product.
Exclude ordinary products with a minor AI feature unless the AI functionality has a materially autonomous product proposition.
Do not publish as an active tool if only announced, waitlisted without usable product, or represented by a landing page only.
Rebrands, relaunches and versions must update the canonical tool record rather than create duplicates unless they are genuinely separate products.
Official site, pricing, documentation, changelog, release notes, official GitHub, app stores, security/privacy, affiliate pages and official announcements establish factual claims.
Credible editorials/tests, Reddit, Hacker News, professional communities, user reviews and credible demonstrations can corroborate performance and market experience.
Product Hunt, AI directories, newsletters, social and launch sites are lead sources only; factual claims require independent verification.
Scan launches, newly public products, new products from known companies, relevant open-source projects and emerging vertical AI.
Track meaningful features, model changes, integrations, modalities, APIs, rebrands, acquisitions and product pivots.
Track pricing, free tier, trial, plans, API pricing and affiliate/referral program terms.
Track shutdowns, archived projects, inaccessible sites, acquisitions, rebrands and material privacy/security events.
Track fast-growing tools, new task clusters and category emergence to inform taxonomy and coverage priorities.
Shutdown, major pricing/free-tier removal, acquisition/rebrand, radical product pivot, or serious privacy/security event.
Important capability, model, integration, API or material workflow/performance change.
Small feature, UI update, template or copy change with no material effect on user proposition.
Run discovery and update scan at least once every day.
Check duplicate identity, stale URLs, missing key fields and taxonomy consistency.
Deep review of taxonomy, category boundaries and competitive coverage.
Collect affiliate/referral and sponsorship data for monetization, but never use commercial terms as an editorial rating or ranking input.
Only dimensions supportable from public evidence enter the standard Desk score.
Breadth and completeness of documented capabilities for the core task and target workflow.
Documented benefits and usable capacity relative to price, limits, credits, free tier and relevant alternatives.
Observed or clearly documented onboarding friction, availability, interface accessibility and technical requirements.
Evidence of operational maturity, support, documentation, update cadence and organizational continuity.
How well documented integrations, APIs, export/import and collaboration features fit real workflows.
Clarity of pricing, limits, terms, privacy, data handling, ownership and security information.
Definition
DESK uses public evidence only. HANDS_ON is allowed only when direct product testing was actually performed.
Never imply direct testing in a DESK review.Values: NOT_ASSESSED, LIMITED_EVIDENCE, STRONG_EXTERNAL_EVIDENCE, HANDS_ON_VERIFIED.
Not a default weighted Desk criterion.A tool may be listed but unrated when evidence is insufficient. Never fill missing evidence with inferred pseudo-precision.
LISTED ≠ RATED ≠ RANKEDWeighted average of the six v1.1 criteria only when enough evidence exists to support the component scores.
0–10 internal scalePublic-facing rating is rounded/assigned in 0.5 increments to avoid false precision. Internal score may remain granular for ordering.
Example: 8.0 / 8.5 / 9.0Requires a valid v1.1 rating and sufficient comparative evidence. Mere listing does not imply ranking eligibility.
YES / NODirect testing and/or unusually strong multi-source evidence supports the scored dimensions.
HIGHStrong official/public evidence exists, but no sufficiently deep direct product test.
MEDIUMEvidence is sparse, partial, secondary-led or materially uncertain.
LOW / UNRATED if too weakRun rating recalibration at least weekly and at each new entry. MAJOR/CRITICAL research updates set NEEDS_REVIEW_UPDATE; MINOR updates do not force full review.
Operational ruleAffiliate commission, referral economics, sponsorship and vendor promotion never enter rating or editorial ranking.
MandatoryNever state or imply hands-on testing unless it was actually performed.
Mandatory