Sales specialist
Default Kona assistant
Enterprise Account Planner
Maps complex accounts, stakeholders, use cases, and deal strategy.
When to use it
A focused role with a visible finish line.
Best for: revenue teams preparing account work, enablement, pipeline decisions, or customer follow-through.
Expected outcome: a practical revenue deliverable grounded in buyer context and approved evidence.
- A focused enterprise, accounts, stakeholders task where the expected decision or deliverable is clear.
- Recurring work that benefits from the same answer, assumptions, risks structure each time.
- A team that wants Enterprise Account Planner available in direct chat, inline @mentions, and bounded Workspace tasks.
Configured instruction
“Build an account plan covering business priorities, trigger events, stakeholders, power, process, competition, value hypothesis, mutual actions, and risks. Distinguish verified account facts from hypotheses.”
This instruction is part of the shipped default profile—not a generic prompt assembled for this page.
Workflow
How Enterprise Account Planner approaches the work
Frame the outcome
State the decision, audience, deadline, constraints, and what a useful a practical revenue deliverable grounded in buyer context and approved evidence looks like.
Ground the work
Provide relevant account facts, CRM context, buyer signals, product proof, stage definitions, and commercial constraints. Label supplied facts, working assumptions, and unresolved unknowns.
Build the contracted output
Enterprise Account Planner follows its markdown output contract and covers answer, assumptions, risks, next evidence.
Verify before use
Run the profile's quality checks, expose evidence gaps, and route high-impact low-risk conclusions to human review.
Capabilities
What the profile can use
- Knowledge grounding
- Structured deliverables
- Verification pass
- Current web research
Enabled tool families: web. Runtime availability still depends on account configuration, permissions, and the task.
Output contract
What a complete response must contain
The contract improves consistency; it does not make an answer automatically correct. Kona still marks assumptions, evidence gaps, and review requirements.
Prompt examples
Start with context and a decision
Prompt example
Act as my Enterprise Account Planner. Build an account plan covering business priorities, trigger events, stakeholders, power, process, competition, value hypothesis, mutual actions, and risks. Distinguish verified account facts from hypotheses. Start by listing the missing inputs that would materially change the result.
Prompt example
Use the Enterprise Account Planner workflow for this enterprise task: [describe the situation]. Audience: [who will use it]. Constraints: [time, budget, policy, or data]. Return answer, assumptions, risks, next evidence.
Prompt example
Review this draft as the Enterprise Account Planner: [paste draft]. Check it against the stated evidence, identify unsupported claims or missing assumptions, and return a prioritized correction list.
Put Enterprise Account Planner to work.
Use the default profile or fork it into a version your team controls.