Your best rep's account research routine, the one everyone borrows before big calls.
An approved research skill every rep runs in Claude before a first call, current by default.
The method one person already has
Enterprise research quality varies wildly by rep. Some people know exactly which signals matter, which customer language to use, and how to connect the account's current reality to your offer. Others produce generic summaries. A skill lets the team reuse the best research logic.
With knacks, the best researcher publishes the method, the enablement lead approves it, it ships to every rep's Claude with nothing to install, the skill library is its home, and the owner keeps it current. That is the knacks loop: Publish, Approve, Ship, Use, Improve.
Anatomy of the skill
| Method | Take a company domain and CRM record, scan the public website, recent news, LinkedIn signals, and tech stack, then write the account thesis: triggers, ICP fit, stakeholder hypotheses, likely pain, talk track, discovery questions. Run it when a target account is added, before outbound, or ahead of a discovery call. |
|---|---|
| Reference files | ICP, qualification rules, vertical pain points, approved positioning, objection handling, persona map, customer examples. |
| Examples | Account theses from your best rep, paired with the raw signals that produced them. |
| Tests | The thesis prioritizes buyer-relevant signals over generic facts, cites its sources, uses approved positioning, and ends with sharper discovery questions rather than a script. |
| Owner | RevOps, sales enablement, or revenue strategy owner. |
| Version | Version history with a one line changelog, so reps see when the ICP or positioning last changed. |
What the team lead reviews
Does the skill prioritize buyer-relevant signals over generic company facts?
Can the rep see which sources created the thesis?
Does the output use current market language and approved claims?
Does it create sharper questions instead of a script to blindly read?
Example output
This account is likely standardizing revenue operations after rapid team growth and fragmented AI usage across sales and success.
New RevOps hire, expansion into enterprise segment, tooling consolidation language, and public hiring for sales enablement.
Repeated research, inconsistent call prep, private AI methods, and no approved path from rep experimentation to team standards.
Which AI methods do your top reps use privately today, and how do you decide which ones become team-wide standards?
Kept current
When the go-to-market changes, the owner updates the skill once and every rep researches against the new standard the same day. Example: new ICP criteria land.
No capture and no usage tracking, ever. knacks never sees chats, screens, or who runs what.
Why it matters
Account research is often the first place revenue teams feel the loss of control: every rep rediscovers the same signals, ten different ways, and nobody stands behind any of them. An approved skill gives the team a better baseline without removing seller judgment.
Turn account research into a company skill.
Book a walkthrough and we will map the first research method your revenue team should publish.
Book a walkthrough