Migration Guide · CI
A practical playbook for moving competitive intelligence from a document-centric Klue (or Crayon) deployment to a graph-grounded PYRAMYD workspace. Library port, integrations, KPIs, and the timeline.
Why teams move
Hand-curated battlecards in document-centric tools age faster than the competitive landscape they describe. By the time PMM curates the next refresh, pricing pages, hiring patterns, and shipped features have already moved on. PYRAMYD's substrate is a live graph, not a document library.
A graph you can refresh on demand narrows the freshness gap.
Side-by-side
| Dimension | Klue (document-centric) | PYRAMYD (graph-grounded) |
|---|---|---|
| Battlecard refresh cadence | Collects intel on the competitors you track; your team curates the cards (klue.com) | Rebuilt on demand from the graph |
| Competitor coverage | Formal cards for the named-competitor list a PMM team can maintain by hand | 250K+ products typed in the graph; coverage extends beyond the named-competitor list |
| Source of competitor data | Analyst input + manual web research + customer-uploaded docs | A catalog of 2,000+ sources: G2, TrustRadius, GetApp, Capterra, SEC, Crunchbase, vendor changelogs, press, hiring |
| AE deal-stage query | Search the battlecard library for the closest pre-written content | Ask APEX: "In this deal vs Competitor B in Inventory Management at Acme Corp scale, what do I need to know?" · cited multi-hop answer in seconds |
| Win/loss feedback loop | Separate win/loss tool, manual entry, separate analytics layer | Win/loss is a node type in the same graph; patterns surface in the same workspace |
| AI substrate | Vector search over the document library + LLM summarization | Answers drawn from a typed graph of the market; Microsoft Research's GraphRAG paper (arXiv:2404.16130) found graph-built answers more comprehensive on whole-corpus questions |
| Annual contract value | Not published. Vendr's median buyer pays about $30,000 a year ($16,000 to $60,000, 106 purchases; vendr.com, checked 7 Oct 2026) | A free Workspace to start; paid plans priced per seat, with live prices on the pricing page |
The timeline
Conservative timeline assumes existing Klue deployment with 5-7 named competitor cards and a Salesforce + Highspot integration footprint. Faster cutovers are routine on smaller deployments.
Week 1 · Discovery
Week 2 · Library port
Week 3 · Live graph cutover
Week 4 · Cutover + Klue sunset
Migration FAQ
No. There is no Klue importer, so you export your cards and we help you bring them into the PYRAMYD workspace. They become baseline content; the graph layer adds live signal-grounded supplements that don't go stale. Most teams keep their existing cards as 'human-edited' canonical positioning and let the graph layer generate the freshness-sensitive sections (recent releases, current reviews, last 30 days of news).
PYRAMYD has connectors for Highspot and Seismic that bring their content in. Publishing battlecards back into them is not switched on, so share links or exports carry cards to sellers for now.
We recommend three metrics: (1) battlecard freshness — median time-since-update on cards your sales team actually opens, (2) deal-stage CI usage — frequency of AE queries against live competitive context, (3) win rate against named competitors.
It changes. Document-stitching work · building and maintaining battlecards manually — disappears. Strategic CI work — disruption-curve analysis, win-loss pattern identification, executive-level briefings — expands. Most teams see this as a positive transition. Some need to re-hire against the new job description.
Yes. The Crayon migration playbook is functionally identical — same library export pattern, same enablement-tool connectors, same timeline. Reach out for the Crayon-specific brief if it applies.
Book the 30-minute migration call. We'll walk through your Klue deployment, scope the library port, confirm enablement-tool compatibility, and set the cutover date.