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 30-day timeline.
Why teams move
Klue's own data shows battle cards refresh every 60-90 days while competitors change material things every 11 days. The 6-to-8× mismatch is the structural failure of document-centric CI. PYRAMYD's substrate is a live graph, not a document library.
Source: Klue, State of Competitive Enablement 2024.
Side-by-side
| Dimension | Klue (document-centric) | PYRAMYD (graph-grounded) |
|---|---|---|
| Battle-card refresh cadence | 60-90 days median (Klue State of CI 2024) | Continuous via live signal graph + on-demand re-assembly |
| Competitor coverage | Formal cards for 5-7 named competitors (Forrester 2024) | All 251,835 products + 84 vendors in named categories typed in the graph; coverage is universal |
| Source of competitor data | Analyst input + manual web research + customer-uploaded docs | 1,000+ live sources auto-ingested: G2, TrustRadius, GetApp, Capterra, SEC, Crunchbase, vendor changelogs, press, hiring |
| AE deal-stage query | Search the battle-card 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 an entity type in the same graph; patterns surface in the same workspace |
| AI substrate | Vector search over the document library + LLM summarization | GraphRAG over typed knowledge graph; 70-80% accuracy lift on multi-hop questions per Microsoft Research benchmark |
| Annual contract value | $50K-$100K typical | From $50K — and replaces RFX + Product Ops tools at the same time |
The 30-day 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. The library imports cleanly into the PYRAMYD workspace. The cards 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 ships connectors for both Highspot and Seismic. The migration replaces Klue as the upstream content source; the surfaces your sellers see (battle cards inside Highspot, etc.) keep working — they just point at PYRAMYD instead.
We recommend three metrics: (1) battle-card 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. Loopio's 2024 data shows live competitive intel drives 15-30% win-rate lift; we target the midpoint at the named-competitor segment by day 90.
It changes. Document-stitching work — building and maintaining battle cards 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 30-day timeline. We've run both with design partners. 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.
