Use Case 1
Quarterly Plan Refresh
Trigger: New quarter or account-planning cycle
1.Pull accounts, opportunities, contacts, and prior plans
2.Rebuild goals, risks, opportunities, and next steps
3.Diff each plan against the prior quarter
4.Surface material changes explicitly
5.Preserve human-edited sections
6.Write the new versioned plan back to the CRM
✓
Account plans stay current with a clear record of what changed, instead of going stale in a doc.
Use Case 2
Change-Driven Prioritization
Trigger: Team needs to know where to focus this quarter
1.Compute the diff across all account plans
2.Rank changes by risk and opportunity size
3.Flag new renewal risks and expansion openings
4.Surface overdue goals carried from prior quarters
5.Recommend the highest-priority action per account
✓
Teams act on what changed, not on re-reading static plans.
Integrations
CRM (Salesforce, HubSpot)
Account Plan Records
Opportunity & Contact Data
Document Generation (Word, PDF)
Dashboards & Charts
Industries
all
See It In Action
A sample conversation with this agent
Refresh the account plans for my strategic accounts.
Pulling accounts, opportunities, contacts, and last quarter's plans. For each account I rebuild a structured plan—goals, risks, open opportunities, and next steps—then diff it against the prior version so you see what moved: a new risk that appeared, an expansion opportunity that opened, a stalled goal. New plans write back to the account-plans table with the version preserved. Which accounts do you want the diff summary for first?
What actually changed on the Northside plan since last quarter?
The diff shows three material shifts: a renewal risk appeared—their champion changed roles and the new contact is unengaged; an expansion opportunity opened around a second product line mentioned in a recent note; and last quarter's goal to reach the economic buyer is still open and now overdue. I flag the champion change as the highest-priority item because renewal risk compounds if it's not addressed early.
Don't rewrite the parts a human edited manually.
Understood—I treat manual edits as intentional. When I detect a section the team hand-edited since the last generation, I preserve it and note it in the diff as 'human-edited, retained' rather than overwriting it with a fresh generation. I only refresh the data-driven sections. If a manual edit now conflicts with new CRM data, I flag the conflict for you instead of silently choosing one.