The same template across every account produces the same plan
Account planning templates ask the same questions of a two-person startup and a global enterprise. Representatives fill them out because they have to. The finished plans are identical, so nobody opens them again.
Which criterion matters varies. For an enterprise account, multi-threading is essential. For an account with a single decision-maker, it does not matter. A fixed template produces the same result in both cases.
The output worth having is narrower than a plan. It is the single action that would most change the course of this account this quarter. The rest of the document is only context for that statement.
When the weighting is visible, a manager can disagree in a useful way. You can accept or reject a conclusion. You can correct a line of reasoning.
How the agent is built in Agent Studio
The judgment is the weighting itself. The system prompt sets out the criteria and when each becomes important, then asks the agent to state the weights it chose and why.
Prompt skills carry your plan structure and your account tiers, so the document lands in a shape your team already reads.
The flow assembles the inputs. Salesforce or HubSpot provides CRM history. An HTTP Request node gathers product usage data, and the Agent Chat node passes the package on.
Notion receives the plan. A Start Scheduled flow updates it every quarter rather than continuously, because a plan that changes weekly is not really a plan, and constant change undermines the document's authority.
The rep owns the plan; the agent drafts it. That distinction is worth stating inside the document itself, because a generated plan nobody feels responsible for is worse than a thin one a rep wrote.
A durable session lets a rep walk through the draft in conversation, challenge a weighting, and have the rest of the plan reworked from the amended assumption.
What this agent is built from
- System prompt: the available criteria, when each becomes decisive, and the requirement to show the weights.
- Prompt skills: your plan structure and account tiers.
- Salesforce (Integration): supplies CRM history. HubSpot fits the same slot.
- HTTP Request (Util): pulls product usage alongside the CRM record.
- Agent Chat (Util): a quarterly scheduled flow hands over the assembled inputs.
- Notion (Integration): receives the plan with its weighting rationale visible.
- When an ActionFlow is enough: If you have a standard mid-market book where accounts genuinely resemble one another, a template workflow does the job.
Frequently asked questions
Start building AI workflows
Create a free account, open a template or a blank canvas, and run your first ActionFlow.
Newsletter
Get product updates
New nodes, agents, and product notes. We send mail only when we have something worth opening.