Build an account plan from CRM data
AI account planning is an Agent Skill: a written method your AI applies on demand, in Zealos or in any client that reads SKILL.md.
AI account planning is an Agent Skill: a written method your AI applies on demand, in Zealos or in any client that reads SKILL.md.
An account plan is worth the hour only if it names the one unknown that would most change your approach — everything else in a plan template is decoration you will never re-read.
| name | our-icp |
|---|---|
| description | Who we sell to, the signals that indicate fit, and the disqualifiers. Use when scoring a lead, deciding whether to pursue an account, building a prospect list, or writing targeting copy. |
| allowed-tools | get_icp_context score_lead_against_icp research_account search_companies |
| compatibility | Zealos, Claude Code, Cursor, Codex and any client that reads SKILL.md |
| license | Free to use and edit |
--- name: our-icp description: Who we sell to, the signals that indicate fit, and the disqualifiers. Use when scoring a lead, deciding whether to pursue an account, building a prospect list, or writing targeting copy. --- # Our ICP Start by calling `get_icp_context` — the workspace's configured profile is the source of truth, and this skill is how to *reason* about it, not a copy of it. ## How to score Weight in this order. Later signals cannot rescue a failure on an earlier one. 1. **Pain we actually solve.** Do they have the problem, today, at a size that hurts? Not "could benefit from". 2. **Trigger.** Something changed recently: new leader in the function, funding, a public commitment, a competitor switch, a hiring spike in the team we serve. Without a trigger, a good-fit account is still a cold one. 3. **Reachability.** Can we get to the person who feels the pain, not just to someone adjacent? 4. **Firmographics.** Size, industry, geography, stack. Last, not first — firmographics are a filter, not a reason. ## Disqualifiers These end the evaluation regardless of anything else: - No budget owner in the function we serve. - Bought a direct competitor in the last 6 months. - The pain is real but owned by a team we cannot reach. - Requires a feature we do not have and are not building. ## Output A score, the two strongest signals with evidence, the strongest counter-signal, and the recommended next action. If the counter-signal is a disqualifier, say "disqualified" plainly — do not average it away against strong firmographics.
The plan gets built from the CRM in minutes rather than being the slide you assemble the night before a QBR and never open again.
You inherit an account and can see the map — who left, who arrived, what was promised — instead of reconstructing it from a year of email.
Account reviews compare plans that all answer the same four questions, so you can tell a thin plan from a thorough one at a glance.
Who decides, what they are measured on, what is already in flight, and the single unknown that would most change your approach. Anything else is filler.
On events rather than on a schedule — a leadership change, funding, or a competitor appearing. A quarterly refresh cadence produces quarterly-stale plans.
Yes. Run it as a scheduled agent across the book and read the diffs rather than the plans.
Post-call automation turns a recorded conversation into the three things that outlive it: the commitments each side made, the fields that changed, and the follow-up that has to go out today.
/call-recap-formatA pre-call brief is worth writing only if it changes what you ask: who is in the room, what they are measured on, what happened last time, and the one question you cannot afford to leave without answering.
/discovery-questionsAn AI SDR agent is only as good as the definition of a good customer it is working from, which is why the fit criteria belong in a written skill rather than buried in a prompt nobody can find.
/our-icpAI email triage is worth having only when it sorts by consequence rather than by recency: what blocks a deal, what someone is waiting on you for, and what can be read at the end of the week.
/email-rulesCRM data hygiene survives AI only if one rule is written down first: a field left blank is a known unknown, while a field filled in by inference is an unknown unknown that will be reported on as fact.
/crm-field-conventionsAccount research earns its time only when it changes the first sentence you write, which means looking for what recently changed rather than assembling a profile anyone could have found.
/our-icp