Migration Guide · CI
A practical playbook for moving competitive intelligence from Klue (or Crayon) to PYRAMYD, where battlecards are built from your product, the rival's, and your deals. 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 builds each card from your product, the rival's, and your deals, and rebuilds it when you ask.
A graph you can refresh on demand narrows the freshness gap.
Side-by-side
| Dimension | Klue | PYRAMYD |
|---|---|---|
| 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 | Collects intel on the competitors you track (klue.com) | 250K+ products typed in the graph; coverage extends beyond the named-competitor list |
| Source of competitor data | Continuously collects intel on the competitors you track and delivers it to sellers (klue.com) | A catalog of 2,000+ registered sources across press, changelogs, hiring, pricing pages, and filings, plus 2.4M+ public reviews |
| AE deal-stage query | Compete Agent surfaces deal-specific guidance before a competitive call and answers competitive questions with cited sources (klue.com) | Ask APEX: "In this deal vs Competitor B in Inventory Management at Acme Corp scale, what do I need to know?" · one answer that lists the records it used, with links to their sources |
| Win/loss feedback loop | Competitive intel and win-loss in one platform (klue.com) | Win/loss sits in the same graph (Competitors › Win/Loss) once your CRM deals are synced |
| AI | Compete Agent for competitive research and deal support, plus Ignition, an agentic AI platform for product marketers (klue.com) | APEX's agents answer from your product, competitors, customers, and deals in one graph and list the records behind each answer |
| 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) | Published per-seat prices: Starter is Workspace plus one hub you choose; Growth and Enterprise add all four hubs, with live prices on the pricing page |
The timeline
Assumes an existing Klue deployment with 5-7 named competitor cards out of up to 25 tracked competitors, and a Salesforce + Highspot integration footprint. Smaller deployments can move faster.
Week 1 · Discovery
Week 2 · Library port
Week 3 · Cutover to PYRAMYD battlecards
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 as Studio documents. They stay on file as your hand-written positioning. The new battlecards are generated from the graph, and you rebuild one, or rewrite a single section with AI, whenever it needs the latest releases and 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 (each card's Usage and readers shows who opens it), (2) deal-stage CI usage — how often AEs open a battlecard or ask APEX about a rival, (3) win rate against named competitors.
It changes. Document-stitching work · building battlecards by hand from scratch — shrinks to reviewing and editing generated cards. Strategic CI work — disruption-curve analysis, win-loss pattern identification, executive-level briefings — gets the time back.
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.