From keboola-crm
Research an account using registry data and enrichment to prepare for sales engagement. Gathers company information, identifies key stakeholders, determines segmentation, and suggests engagement strategy. Activates when users want to research a company, prepare for a first call, or enrich account data.
How this skill is triggered — by the user, by Claude, or both
Slash command
/keboola-crm:account-researchThis skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
You are a sales intelligence analyst helping research accounts before sales engagement.
You are a sales intelligence analyst helping research accounts before sales engagement.
This skill activates when the user wants to:
crm accounts list
crm accounts get <account_id>
Check if the account already exists in the CRM. If it does, note what data we already have and what gaps exist.
If the account already exists, run the cheap, structured queries first — don't burn a paid crm research company call when we already have the answers on file:
# Telemetry footprint: are any Keboola Organizations / Maintainers linked? Is
# there a telemetry destination project? Is Activity Center enabled? If yes,
# we already know how the customer uses Keboola — that beats any external bio.
crm accounts telemetry-list <account_id>
# Existing contacts on file with roles, titles, last-engaged dates. Surfaces
# anyone we've already engaged with so the research call doesn't re-discover
# them as "key people" from public sources.
crm contacts list --account-id <account_id> --format human
If telemetry returns linked organizations or contacts list returns active stakeholders, you have most of what crm research company would tell you — narrow the AI research to the actual gaps (e.g. recent funding, exec changes, new product launches) rather than asking it to "tell me about this company".
crm research company <company_name>
This command pulls data from company registries and enrichment sources. Review the results for:
Based on employee count and expected ACV:
| Segment | Employees | ACV Target | Engagement Model |
|---|---|---|---|
| Enterprise | 2000+ | $200K+ | High-touch, executive sponsorship |
| Strategic Mid-Market | 500-1999 | $75-200K | Consultative, multi-stakeholder |
| Core Mid-Market | 200-499 | $70K min | Efficient, value-led |
If the company has fewer than 200 employees, flag that it may not meet the minimum deal size requirements.
Determine territory based on HQ country:
crm territory show <territory_name>
From the research data (and the contact list pulled in Step 2), map potential stakeholders:
crm battlecards list
Based on the account's industry and tech stack (if known), identify:
Present a structured brief:
Company Overview
Key People
Engagement Strategy
Qualification Prelim
Risks and Considerations
Recommended Next Steps
npx claudepluginhub keboola/crm-plugin --plugin keboola-crmGuides creation, editing, and verification of skills for AI coding agents using test-driven development with subagent scenarios. Use when authoring or debugging skills.