For revenue leaders
Your reps already live in Claude. Clinch is how Claude knows your deals.
Pre-call briefs in Claude, post-call notes written back to Clinch, per-rep win/loss numbers a rep can ask Claude for in plain English. No new dashboard for the rep to forget. 149 dollars per month per workspace.
The pain
You already know the problem.
You are accountable for the number. Your win rate against specific competitors is a metric you could quote in your sleep, except you cannot, because the data lives in your reps' heads and ten different Notion pages. Your battlecards are probably a PDF from Q2 that nobody has opened this month, and you have considered Klue but the 20,000 dollar price tag and six-week implementation have killed the conversation four times already. Meanwhile your best reps are quietly using Claude all day; you have no system to bring competitive memory into that workflow.
- No per-rep view of who loses to which competitor and why
- Reps walking into competitive calls underprepared because the battlecard is stale or invisible
- Lost deal context disappearing because the rep typed half a Salesforce note and called it done
- Approving a 20K Klue contract your team will not actually use
- Watching reps already use Claude for prep, but with no connection to your real competitive data
What Clinch does for vps of sales
The system, not another dashboard.
01
Pre-call briefs inside Claude, in 60 seconds
Reps ask Claude for a brief on the prospect plus the competitor in play. The Clinch skill produces a one-pager grounded in your real battlecard, the prospect's homepage, and your most recent diffs. Read before the call, share into Slack after.
02
Post-call capture without opening the dashboard
After a call, the rep says one sentence to Claude: 'we lost to Klue, integration story was thin.' The Clinch skill logs the outcome with the right competitor, auto-tags the reason, and writes back to your workspace. Your dashboard fills itself.
03
Per-rep competitive record on tap
Any rep can ask Claude 'how am I doing against Klue?' and Claude pulls their own win rate, last loss reason, and recent talk-track gaps from Clinch. The 'where is each rep weak' question now has an answer.
04
Auto-updating battlecards your reps actually read
Battlecards regenerate when a competitor moves. Public share links work on any device with no login. Tracked views show you who is prepping for competitive calls and who is not.
The economics
149 dollars per month per workspace, 25 sales seats on Pro. Less than 1 percent of a typical Klue contract. Reps adopt it because Claude is already on their dock, not because you mandated a new tab.
Common objections
The questions we hear most.
- Will my team actually use this?
- Your reps are already using Claude. Clinch is the connector that makes Claude useful for competitive work. Adoption is opening Claude, which they already do. No new app to learn. View counts on every battlecard prove who is prepping.
- Why not Klue?
- Klue is 15K to 25K per year, six weeks to implement, designed for a 3 to 10 person CI team to own. Clinch is 149 per month, live in 5 minutes, designed for a sales team using Claude. If you have a CI team and the budget, Klue still might be the fit. If you have a PMM and a sales team that already lives in Claude, Clinch is.
- Does this integrate with Salesforce?
- Not natively, and we are not building that integration. Reps log calls in Salesforce; reps log competitive context in Clinch via Claude. Both surfaces stay clean. The public battlecard link works inside Salesforce or anywhere else without integration.