Taxonomy 360 Pages: Every Category, Country, and Persona Has Its Own Live URL

Most analytics platforms ship dashboards. Forrester's 2025 state-of-BI research[1] found that self-service dashboard adoption has stalled at 32% of analyst seats · the gap isn't more dashboards, it's governed data with opinionated views. PYRAMYD ships opinionated views by default · one for every node in every taxonomy, refreshed weekly, addressable by URL.

2,606 Category 360s. 163 Industry 360s. 249 Country 360s. 4,329 Persona 360s. Every node in every taxonomy is a live URL · so "how is the CRM category doing" resolves to a page load, not a research project.

The architecture is borrowed from a place most enterprise software companies don't think to look · the Bloomberg Terminal. Every ticker on Bloomberg has its own page; every page is the entry surface for analysts working on that ticker. PYRAMYD does the same thing for enterprise software entities. This is the engineering and the workflow story behind it.

Section 1: What a 360 page actually contains

Every 360 page is structured around the same 10 field-group tabs · the canonical enrichment schema PYRAMYD uses across every taxonomy. For a Category 360:

• Overview · definition, scope, parent/child relationships in the taxonomy tree, top vendors, vendor count, total review count, time-series of category traction.
• Demand · search trends, hiring signals, RFP frequency, buyer intent indicators by region and industry.
• Market · market sizing, growth rate, top-5 player share, fragmentation index, M&A activity, funding flow.
• Landscape · competitive map · who fits where on the feature/price grid, leaders/challengers/niche players, recent positioning shifts.
• Trends · product release velocity, feature additions, integration announcements, pricing changes, AI-feature density shift.
• Operations · representative implementation timelines, integration complexity, common workflows, peer benchmarks.
• Compliance · SOC 2 / ISO 27001 / GDPR / HIPAA / EU AI Act status across the cohort, regulated-industry suitability, certifications by vendor.
• Economics · pricing per seat / per active user / per workspace, contract term distributions, average discount achieved at typical seat counts.
• Capabilities · canonical capability map, feature presence/absence per vendor, feature-market-fit scoring.
• Pulse · this-week diffs · what shipped, what changed, what got covered in the press, what got reviewed.

Every tile on every tab is graph-grounded · clicking a tile drills to the underlying nodes and their citations. The page is not a dashboard with a list of static charts. It's the materialized result of dozens of saved queries over the typed graph, refreshed weekly.

Section 2: Why one page per node beats one dashboard per query

The Pendo / Mind the Product benchmarks[8] report PMs spending 33% of their time on data wrangling · the same number flat since 2021. The bottleneck isn't analyst availability, it's the cost of every new question becoming a new research project. If every CRM-related question has to start from "let me pull the data," the organization's velocity is set by the SQL queue.

A 360 page collapses the wrangling. When a CI analyst, a PM, an AE, or an Ops lead all need to understand "the CRM category" for different reasons, they all start at /categories/crm · same URL, same data, same provenance. The fact that they ask different next-questions from there doesn't require any of them to rebuild the data layer. This is what Gartner's 2026 BI MQ[2] calls "composable analytics" · entity-centric pages with embedded queries.

Section 3: How the pages stay current

Every 360 page reads from the underlying typed graph. When the graph refreshes · weekly by default, on-demand via the enrichment runner · the page reflects the new values on the next load. The page doesn't have a static build artifact. The page is the graph view at the time of request.

Cell-level provenance is rendered inline. Hover any field and the provenance popover shows: Freshness (how recently this cell was verified), Quality (signal strength), Confidence (model score), Sources (the URL list), Raw (model payload), History (audit log of prior values). Every score is real · not a generated badge. The cell that's 4 days old shows 4 days old; the cell that's 4 months old (because its source is slow-moving) shows 4 months.

Section 4: The four 360 types and what they're for

Category 360 · 2,606 pages

The dominant analyst surface. Category 360s are how CI analysts, PMs, and AEs start nearly every cross-vendor question. The page surfaces the canonical taxonomy ancestry (market → functional → product), the top vendors with their core metrics, the competitive landscape view, and the field-group tabs above.

Industry 360 · 163 pages

For vertical-specific buyers and sellers. Industry 360s aggregate vendor adoption by GICS sector and sub-industry, surface industry-specific compliance overlays (HIPAA for healthcare, FedRAMP for federal, FINRA for capital markets), and rank vendors by deployments in that vertical. Sales teams use them as ICP-discovery surfaces; product teams use them as market-sizing references.

Country 360 · 249 pages

For geographic-aware buyers and sellers. Country 360s surface data-residency requirements, regulatory regimes (EU AI Act, GDPR, China's PIPL, India's DPDP, etc.), local vendor presence, hiring activity by region, M&A flow, and currency-adjusted pricing. Critical for enterprise buyers running multi-region rollouts. UN M49 region hierarchy (region → sub-region → intermediate region) is enforced for traversal.

Persona 360 · 4,329 pages

For ICP-driven workflows. Persona 360s are built on the RMCD (Role · Module · Capability · Discipline) schema · every persona is a unique combination of those four dimensions, and the 360 surfaces the tools that persona uses, the workflows they own, the pain points the research signals are flagging, and the messaging that resonates per the review/intent corpus. AEs use them as "who am I selling to" cheat sheets; product marketers use them as ICP-message-test surfaces.

Section 5: The provenance that makes them trustable

Every cell on every 360 page carries the same provenance schema · source URL, retrieval timestamp, model used, prompt hash, quality score, confidence. The provenance is queryable too · an APEX answer can include "the 18 strongest cells for this claim were retrieved in the last 14 days from these 7 sources." This is what makes the page survive a procurement audit, an EU AI Act Article 50 disclosure check, or a CFO who wants to know where a number came from.

OECD's 2024 data-governance reference[9] notes the gap: most enterprise analytics surfaces don't carry retrieval-timestamped provenance, so claims that look authoritative are actually un-auditable. The 360 page treats that gap as the design starting point · provenance is the first-class field on every cell, not an afterthought.

Telemetry from Q1 2026[7] shows the median analyst opens 8.3 Category 360 pages per session and 0.7 freeform dashboards. The 360 is winning the analyst's attention because it's designed for the work, not for the demo. Every URL load is one more Monday morning where the answer was already there · no SQL queue, no data-wrangling tax.