Blog
Research-grounded notes from the graph.
One post per persona we serve. Every claim cited — Microsoft Research, McKinsey, Gartner, Forrester, Loopio, Klue, IDC, and Melissa Perri's Product Operations book among them.
Published
Long-form notes from the graph.
Foundations, Graph RAG, methodology, and one substantive post per persona PYRAMYD serves — primary sources cited, the substrate argument made every time.
Game Theory · Engineering
9 min
Your Competitor's Next Move Is a Probability Distribution, Not a Headline.
Feeds tell you what happened. A decision needs three more numbers: how likely each next move is, how much of it you can take, and how wrong it can go. The imperfect-information engine that computes all three — posterior, exploitability, blind-spot amplification, Monte-Carlo band — and runs live in your browser.
READ THE POST →
Analyst Relations · Engineering
8 min
You Shouldn't Find Out Where You Land in the Magic Quadrant From the Magic Quadrant.
The report drops once a year; the evidence it scores accumulates every day, in public. How placements across six analyst frameworks become graph data, the grain law that keeps product evidence out of vendor-axis scores, and the next edition's movement — projected before the briefing cycle starts.
READ THE POST →
AI Grounding · Architecture
11 min
Context Is the Missing Layer in Enterprise AI.
Enterprise AI fails not because of data scarcity but because the data lacks embedded context. Adapted with attribution from Andreas Blumauer (Graphwise) on the CDO Matters podcast. The pattern that already runs PubMed, EuroVoc, and SNOMED CT in production — applied to enterprise software product data.
READ THE POST →
Foundations
16 min
Why Enterprise Software Needed a Product Graph (and Why Nobody Built One Until Now).
Why earlier enterprise-software knowledge graphs stalled (shape drift, unresolved duplicates, missing constraints) and the 91-node-type backbone PYRAMYD built instead.
READ THE POST →
Graph RAG
13 min
Microsoft GraphRAG, Anthropic MCP, and the Convergence Pattern Nobody Is Talking About.
Three independent research teams arrived at the same substrate conclusion within 18 months. We trace the citations, the benchmark deltas, and the architectural primitives that show up in every published GraphRAG variant.
READ THE POST →
Methodology
10 min
What 'Evidence-Grounded' Actually Means: A Field Guide for Buyers Tired of LLM Wrapper Demos.
Every vendor says 'cited.' We dissect what a real citation looks like, what model-grounded vs. graph-grounded responses actually return, and the 7 disclosure controls a procurement team should require before signing.
READ THE POST →
Product Management
11 min
Why Product Roadmaps Miss, and How a Knowledge Graph Closes the Gap.
Roadmaps don't fail because PMs are bad at prioritization. They fail because the inputs to prioritization sit in seven disconnected systems. The graph substrate solves that.
READ THE POST →
Architecture
9 min
The Five Enrichment Scopes: Taxonomy, Row, Column, Group, Cell.
Why one number on a dashboard can be refreshed without paying to refresh the other million — and how that keeps every answer current at a cost your finance team will sign. The runner architecture behind it: how one pipeline serves a full-taxonomy refresh and a single-cell fix, why one advisory lock keeps bulk runs from colliding, and why you only pay for the scope you run.
READ THE POST →
APEX · Copilot
11 min
APEX: 20 Specialist Agents, One Supervisor, 150+ Tools.
Why one mega-model loses to 20 routed specialists on enterprise software tasks. The orchestration architecture inside APEX — supervisor + specialist pattern, delivery over MCP (coming soon), and the verification loop that catches hallucinated claims before they leave the system.
READ THE POST →
Markets · Taxonomies
10 min
Taxonomy Pages: Every Category, Country, and Role Has Its Own Live URL.
More than 7,600 live dashboards · 2,546 Categories, 463 Industries, 249 Countries, 4,349 Roles. Each one is the materialized view of the typed graph at query time. The Bloomberg Terminal pattern, adapted for enterprise software.
READ THE POST →
Studio · Sheets
11 min
Studio Sheets: Live Joins, Cell-Level Provenance, and Why VLOOKUP Is Dead.
The spreadsheet your team already knows — except every cell can defend itself in a review, because columns are typed graph joins, every cell carries provenance, and any cell can run an APEX query. The 25-column CSV stack Ops teams build by hand, replaced by a live graph view.
READ THE POST →
Signals · Live Data
12 min
The 2,000-Source Signal Feed: How the PYRAMYD Graph Stays Live.
How a competitor move reaches your battlecard the day it lands instead of next quarter. Inside the pipeline — 2,000+ source feeds, per-source refresh cadences, content-hash dedup, resolving names to nodes, and the audit chain that makes every signal traceable back to its source. The engineering that closes the battlecard refresh gap.
READ THE POST →
Product Operations
14 min
Product Operations Needs a Knowledge Graph: Reading Perri and Tilles' Three Pillars Through a Graph Lens.
Perri and Tilles' Three Pillars — Business Data & Insights, Customer & Market Insights, Process & Practices — are each structurally graph problems. The substrate change is the unlock.
READ THE POST →
Product Development · Engineering
13 min
Stop Building What Already Exists: Graph-Grounded Feature Discovery.
Microsoft Research's GraphRAG benchmark and the wider knowledge-graph literature point the same way: questions that span many systems need a graph, not a pile of documents. Here's the mechanism.
READ THE POST →
Competitive Intelligence
12 min
Battlecards Are Stale by Design: Why CI Needs a Knowledge Graph.
In Crayon's 2024 survey of 700+ CI professionals, 58% said keeping battlecards up to date is a struggle. The structural cause: CI is a relationship problem. The substrate fix is a graph.
READ THE POST →
Sales Enablement · RFX
13 min
Why Sales Enablement and RFX Belong on a Knowledge Graph.
Loopio's 2026 benchmark: almost 80% of RFP teams now use generative AI, yet a response still takes 33 hours. The substrate underneath proposal tools has to change from document libraries to knowledge graphs.
READ THE POST →
AI Context Management
14 min
The Grounding Layer Every Agentic AI Project Needs — Or Joins the 40% Gartner Says Get Cancelled.
Gartner predicts more than 40% of agentic AI projects will be cancelled by the end of 2027, citing escalating costs, unclear business value and inadequate risk controls. GraphRAG and MCP point to the same fix: a typed context layer under the agent.
READ THE POST →
Procurement · Strategic Sourcing
12 min
Buyers Are Using Knowledge Graphs Too: How Procurement and Strategic Sourcing Teams Negotiate with Live Vendor Data.
6sense's buyer research finds B2B buying groups are about 70% through their buying journey before they contact a seller. Procurement is best placed to turn that into leverage, with the same knowledge graph sellers use.
READ THE POST →
The list
Get every post in your inbox.
Long-form research delivered as it ships — zero blast emails, every post substantive, every claim cited.
The graph dispatch
One email. Every Friday. Built from the live graph.
Last week's competitor releases, new vendors entering your category, and one APEX-grounded answer to a hard CI question. No fluff.
Want to run these queries against your own data?
Book a demo. We'll filter the same questions to your category, your competitors, and your accounts · with citation-grounded answers in seconds.