If you’re tired of sales enablement tools that promise the moon but leave your team digging through three platforms and a dusty folder of battlecards, you’re not alone. This guide is for sales ops folks, competitive intel leads, and anyone who just wants Kompyte and Salesforce to talk to each other—without drama or mystery.
Why bother integrating Kompyte and Salesforce?
Let’s keep it real: the whole point is to get actionable competitive insights in front of your sales team, right where they already live—Salesforce. If you’re still sending PDFs or Slack messages about what competitors are up to, you’re probably seeing that info ignored or lost. Integration means:
- Salespeople see up-to-date competitor info right in their workflow.
- Battlecards don’t get stale and dusty.
- Marketing/CI folks don’t have to play “copy and paste” all day.
- You get some hope of measuring whether enablement is actually working.
But there are also things integration won’t do for you:
- It won’t magically make reps care about competitive intel.
- It won’t fix bad data or outdated battlecards.
- It won’t solve Salesforce adoption problems.
With that out of the way, let’s get you set up.
Step 1: Prep work—Get your accounts and access sorted
Don’t skip this. The number one reason integrations fail is someone missing permissions or trying to “figure it out” with a basic Salesforce license.
You’ll need: - An active Kompyte account with admin privileges. - Salesforce admin access (not just a regular user or “view only”). - A clear idea of where in Salesforce you want Kompyte content to show up (Opportunities, Accounts, Leads, etc.)
Pro tips: - Before you start, check with your Salesforce admin about sandbox vs. production. Testing in sandbox is a lifesaver. - If your security team is picky, get a list of what data Kompyte will access in Salesforce. Saves headaches later.
Step 2: Map out what you actually want to sync
Kompyte can push a lot of stuff into Salesforce: battlecards, competitor profiles, win/loss insights, and sometimes alerts. More isn’t always better. Decide:
- Which battlecards or competitor data are worth syncing?
- Should reps see all competitors, or just the ones relevant to their deals?
- Do you want Kompyte to create new objects in Salesforce, or just embed info in existing records?
What works:
Start simple. Sync your top 3-5 competitors’ battlecards first. If you try to dump everything in, it’ll get ignored.
What to ignore:
“Automate everything” promises. Too much data = noise. You want clarity, not clutter.
Step 3: Connect Kompyte to Salesforce
Here’s the meat and potatoes. Kompyte’s integration is usually “out of the box,” but only if you’ve got the right permissions.
In Kompyte: 1. Go to your Integrations tab (usually under Settings or Admin). 2. Find Salesforce from the list of available integrations. 3. Click “Connect” or “Add.” You’ll be prompted to log in to Salesforce. 4. Log in as a Salesforce admin. Grant the requested permissions—Kompyte needs access to push data and sometimes read records. 5. Choose your Salesforce environment (production or sandbox).
In Salesforce: - You may need to approve a new app or connected integration. Your admin will see this as a “connected app” in Salesforce Setup. - Set permission sets so the right users can see Kompyte data.
If you hit snags: - Most issues are permission-related, or because Salesforce API access isn’t enabled on your license. Double-check. - Sometimes, pop-up blockers or browser privacy settings can mess with the auth process.
Pro tip:
If your org uses Single Sign-On (SSO), expect to spend extra time with your IT team making sure things play nice.
Step 4: Configure what shows up and where
This is where most integrations fall down: dumping a wall of text into every opportunity record is a sure way to make reps ignore it.
Decide: - Do you want Kompyte battlecards as a custom object, a Lightning component, or embedded in record pages? - Should all users see the same battlecards, or should they be filtered by region, product line, etc.?
Recommended setup (for most teams): - Add a Kompyte “Competitive Insights” widget or Lightning component to Opportunity and Account records. - Configure it so only relevant competitors (the ones in a deal) show up, not the whole list. - Make sure the widget is above the fold—not buried at the bottom where nobody will scroll.
Customizing the integration: - Use field mapping to control what data flows where. - If possible, set up filters so only certain types of intel (e.g., “recent updates” or “top objection responses”) are visible. - Test with a few pilot users before rolling out org-wide.
What works:
Short, focused battlecards. “How to beat them” bullets, not essays.
What doesn’t:
Auto-pushing every Kompyte update into Salesforce chatter. You’ll annoy everyone.
Step 5: Test, tweak, and train
Don’t assume it’s done because there’s a widget in Salesforce. You need to check:
- Do the right reps see the right data on the right records?
- Is the Kompyte info actually visible and helpful in live deals?
- Are updates from Kompyte flowing into Salesforce as expected?
How to test: - Walk through a mock sales cycle: open an opportunity, check the battlecard, use the content. - Ask a couple of reps for honest feedback. (Bribe with coffee if you have to.) - Try updating a battlecard in Kompyte and make sure it syncs.
Training tips: - Show reps how to find and use the Kompyte info—don’t assume they’ll just discover it. - Point out that this means less hunting for docs and more time selling. - Keep the “training” short. One quick video or a cheat sheet beats a 60-slide deck.
Step 6: Measure and adjust
You won’t get this perfect on day one. The real value comes from seeing what’s actually used, what isn’t, and tweaking over time.
What to track: - Are reps actually opening or viewing the Kompyte component? - Does competitive win rate improve in deals where Kompyte info is used? - Is the data staying fresh, or is it going stale?
What’s worth ignoring:
Vanity metrics like “number of battlecards created.” Focus on usage, not volume.
Iterate: - Trim unused battlecards. - Update content regularly based on rep feedback. - If something gets in the way or causes confusion, kill it.
Wrapping up
Integrating Kompyte with Salesforce isn’t rocket science, but it’s also not “set it and forget it.” The key is to start simple, focus on what your sales team actually needs, and keep tuning as you go. Don’t be afraid to cut features or data that cause clutter. Less is more—especially when you want reps to actually use what you’ve built. Get the basics working, watch how it’s used in real deals, and keep it lean. That’s how you make sales enablement something people want, not just another checkbox.
Get started, keep it simple, and don’t buy the hype—just make it work for your team.