Skip to main content
PYRAMYD
Solutions

Product hub

GA

Taxonomy Browser

Build your taxonomy from the systems you already run, then map every feature onto the canonical graph — with the aggregated review and AI scores for that feature across every vendor instance.

4 top capabilitiesIn the Product Graph

What it is

Taxonomy Browser.

Taxonomy Browser lets you navigate the universal product taxonomy as an interactive graph or a structured library, scoped to a chosen vendor, and surfaces both your own taxonomies and the job taxonomy. It brings graph and library views, vendor scoping, personal taxonomy management, and the jobs view together so you can see exactly how categories, modules, capabilities, and features are organized.

See it in the product

Taxonomy Browser in the workspace.

Taxonomy Browser screenshot from the production workspace

Top 4 capabilities

The most impactful capabilities.

Each capability is the parent of dozens of typed features in the production taxonomy. Hover any feature in Studio to drill into the underlying nodes.

01

Your feature mapped onto the canonical node

Mapping a feature you own onto its canonical node returns the aggregated vendor count, scored count and sentiment for that capability across the market. Your internal taxonomy stops being a private spreadsheet and starts carrying external evidence.

02

Vendor features matched by a three-tier cascade

A scraped vendor feature is adjudicated against the canonical taxonomy by normalised exact match, then a trigram band that strong-merges or skips, and a model judgement only for the genuinely ambiguous middle. The resulting match confidence is stored on the row, so a weak link is visible as a weak link.

03

The grader is allowed to abstain

When the scorer judges it has too little evidence, the rubric score is withheld instead of shown. That matters because the rubric is the fallback whenever a feature has no review coverage — precisely the case where a weak number would go unchallenged and end up quoted in a comparison.

04

Built from the systems you already run

Jira epics, repositories, service catalogues and product lines are classified into a starting taxonomy, and a second pass hangs tickets, headcount, cost and usage off each node — turning a product taxonomy into something you can ask what a capability costs.

See Taxonomy Browser running against your category.

30-minute walkthrough. We'll filter the workspace to your category and walk through the top capabilities live.