How to Use Your CRM for Account Planning

Account planning is the difference between a sales team that hunts and a sales team that farms. Hunters close new logos and move on. Farmers build deep relationships with existing accounts, understand the business, map the stakeholders, and systematically expand. Farmers win on retention and expansion ARR — the metrics that compound.

DenchClaw gives you a local-first CRM where account plans live alongside your contacts, deals, and communications — not in a separate PowerPoint that nobody updates after the initial QBR.

What Account Planning Actually Is#

Account planning is the structured process of understanding a key account deeply enough to grow it. That means:

• Stakeholder mapping — who are the decision-makers, champions, blockers, influencers?
• Business objectives — what is this company trying to achieve in the next 12 months?
• Current footprint — what products/services do they use, what's the ARR, what's the renewal date?
• White space — where can you expand? What problems are they facing that you could solve?
• Success metrics — how do they measure value from your solution?
• Action plan — what are the concrete next steps, who owns them, what's the timeline?

A CRM that supports account planning doesn't just store contacts. It becomes a living strategic document for each key account.

Setting Up Account Plans in DenchClaw#

Step 1: Extend Your Company Object#

Add account planning fields to your company or accounts object:

"Add these fields to the company object: Account Tier (Strategic/Key/Growth/Standard), Annual Revenue (number), Employee Count (number), Industry (text), Business Objectives (richtext), White Space (richtext), Success Metrics (richtext), Executive Sponsor (relation to people), Account Owner (text), Last QBR Date (date), Next QBR Date (date), Strategic Notes (richtext)"

fields:
  - name: Account Tier
    type: enum
    options: [Strategic, Key, Growth, Standard]
  - name: Annual Revenue
    type: number
  - name: Employee Count
    type: number
  - name: Industry
    type: text
  - name: Business Objectives
    type: richtext
  - name: White Space
    type: richtext
  - name: Success Metrics
    type: richtext
  - name: Executive Sponsor
    type: relation
    related_object: people
  - name: Account Owner
    type: text
  - name: Last QBR Date
    type: date
  - name: Next QBR Date
    type: date

Step 2: Use Entry Documents as Living Account Plans#

Each company entry has its own document — a full markdown page that serves as the account plan. This is where the strategic narrative lives.

For a key account, the document structure might be:

# Acme Corp Account Plan
 
## Company Overview
Acme is a Series B fintech company (~200 employees) focused on B2B payments infrastructure...
 
## Current Footprint
- Product: [Your Product] — Core tier ($48k/year)
- Users: 23 (out of 200 employees)
- Renewal: June 15, 2026
 
## Key Stakeholders
| Name | Role | Relationship | Notes |
|------|------|--------------|-------|
| Sarah Chen | VP Engineering | Champion | Loves the API, attends webinars |
| James Liu | CFO | Economic Buyer | Data-driven, focused on ROI |
| Tom Park | Head of IT | Blocker | Concerned about security compliance |
 
## Business Objectives (FY2026)
1. Launch their new payments API product by Q3
2. Reduce engineering team size by 15% through tooling
3. Achieve SOC2 Type II compliance
 
## White Space & Expansion Opportunities
- Enterprise tier: They qualify, would add $24k ARR
- API add-on: Fits their product build; $18k ARR
- Additional seats: IT team (12 people) not yet using product
 
## Success Metrics They Care About
- API response time (they track this religiously)
- Time to implement new integrations
- Support ticket resolution time
 
## Action Plan
- [ ] Schedule security review for Tom Park — owner: Account Exec — due: April 10
- [ ] Send Enterprise tier ROI analysis — owner: Account Exec — due: April 5
- [ ] Intro call with new CTO (TBD) — owner: CS Manager — due: April 30
 
## QBR History
**March 2026**: Covered Q1 usage, introduced Enterprise tier, Sarah positive, Tom raised compliance Q
**September 2025**: Strong quarter, usage up 40%, discussed API add-on

The agent can help write and update this document. After a customer call:

"Add to Acme Corp's account plan: Met with James Liu (CFO) on March 25. He wants an ROI analysis showing time savings before approving Enterprise tier upgrade. Action item: deliver by April 5."

Step 3: Build Stakeholder Maps#

Beyond the document, create structured stakeholder data in your people object linked to the company:

For each contact at a key account, add fields:

• Influence Level: Decision Maker, Champion, Influencer, Blocker, User
• Relationship Strength: Advocate, Neutral, At Risk, Unknown
• Last Interaction: date
• Engagement Score: number

Create a view showing all contacts at your strategic accounts organized by influence:

- name: Strategic Account Stakeholders
  filters:
    - field: Company Tier  # pulled from related company
      operator: equals
      value: Strategic
  sort:
    - field: Influence Level
      direction: custom
      order: [Decision Maker, Champion, Influencer, Blocker, User]

Step 4: Track White Space in Deals#

Create deal entries for each expansion opportunity in a key account. Link them to the company with type "Expansion":

"Create an expansion deal for Acme Corp: Enterprise Tier Upgrade, $24,000, linked to James Liu and Sarah Chen, expected close Q2 2026"

Now your white space is tracked as real pipeline — not just notes in a document. Your expansion ARR is visible in your deals pipeline alongside new business.

Step 5: QBR Workflow#

Quarterly Business Reviews are the flagship moment in an account plan. DenchClaw helps you prepare and follow up.

Before the QBR, ask the agent:

"Prepare a QBR brief for Acme Corp: their contract value, current usage stats, support history, health score, and key milestones from the last quarter"

The agent pulls everything from DuckDB and their entry documents in 30 seconds.

During the QBR, take notes directly in Telegram:

"Add QBR notes for Acme Corp: Sarah Chen and James Liu attended. Q1 API usage up 38%. James approved Enterprise upgrade in principle pending ROI analysis. Tom raised SOC2 audit timeline. Action: deliver audit documentation by April 15. Next QBR scheduled for June 18."

After the QBR:

• Update the Last QBR Date field
• Set Next QBR Date
• Create action items in your tasks object
• Update any expansion deals

Step 6: Build an Account Portfolio Dashboard#

For account managers with multiple key accounts, build a dashboard showing portfolio health:

const accountPortfolio = await dench.db.query(`
  SELECT 
    ef_name.value as company,
    ef_tier.value as account_tier,
    ef_cv.value::decimal as contract_value,
    ef_health.value as health_tier,
    ef_renewal.value as renewal_date
  FROM entries e
  JOIN entry_fields ef_name ON e.id = ef_name.entry_id
  JOIN fields f_name ON ef_name.field_id = f_name.id AND f_name.name = 'Company Name'
  -- ... additional joins
  WHERE ef_tier.value IN ('Strategic', 'Key')
  ORDER BY ef_cv.value::decimal DESC
`);

This gives you an instant view of your most important accounts — their health, renewal dates, and contract values — before a Monday morning stand-up.

Frequently Asked Questions#

How many accounts can I actively plan for at once?#

Account planning is resource-intensive — most enterprise AEs deeply plan 10-20 Strategic accounts at a time. DenchClaw can store plans for thousands of accounts, but the question is your team's bandwidth. Use the Account Tier field to prioritize: Strategic = deep planning, Key = lighter planning, Growth/Standard = standard CRM workflow.

Can I use DenchClaw for account planning in a team where multiple people own different accounts?#

Yes. The Account Owner field tracks who owns each account. If multiple team members share access to the same DenchClaw instance, they can all update their respective accounts. For true multi-user collaboration, DenchClaw Cloud (coming soon) will offer shared workspaces.

How do I keep account plans updated without it becoming a chore?#

The key is making updates frictionless. Use the Telegram integration: after every customer call, dictate your notes to the DenchClaw agent from your phone in 30 seconds. The agent parses them and updates the relevant document and fields. The account plan stays current because updating it takes no effort.

Can I import existing account plans from a PowerPoint or Google Doc?#

The browser agent can access your Google Drive (using your existing Chrome session) and extract text from Google Docs. Ask the agent to import your existing account plan documents into DenchClaw entry documents for each account.

Is there a standard account plan template I can use?#

DenchClaw doesn't ship with a built-in template, but you can create one. Write a template document, then ask the agent to use it as the default structure when creating new account plan documents. The template becomes part of your workspace documentation.

Ready to try DenchClaw? Install in one command: npx denchclaw. Full setup guide →