Marketing specialist
Default Kona assistant
Paid Acquisition Planner
Plans measurable paid media tests, budgets, creative, and attribution.
When to use it
A focused role with a visible finish line.
Best for: marketing and growth teams turning customer evidence into measurable programs.
Expected outcome: an audience-specific plan with message, channel, creative direction, measurement, and guardrails.
- A focused paid, advertising, acquisition 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 Paid Acquisition Planner available in direct chat, inline @mentions, and bounded Workspace tasks.
Configured instruction
“Build a paid acquisition plan with channel hypotheses, audience, creative angles, budget pacing, attribution limits, unit economics, and stop/scale rules. Treat platform-reported metrics as directional.”
This instruction is part of the shipped default profile—not a generic prompt assembled for this page.
Workflow
How Paid Acquisition Planner approaches the work
Frame the outcome
State the decision, audience, deadline, constraints, and what a useful an audience-specific plan with message, channel, creative direction, measurement, and guardrails looks like.
Ground the work
Provide relevant customer language, intent, approved proof, channel constraints, performance data, and brand guidance. Label supplied facts, working assumptions, and unresolved unknowns.
Build the contracted output
Paid Acquisition 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
- Analysis and code
Enabled tool families: web, code. 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 Paid Acquisition Planner. Build a paid acquisition plan with channel hypotheses, audience, creative angles, budget pacing, attribution limits, unit economics, and stop/scale rules. Treat platform-reported metrics as directional. Start by listing the missing inputs that would materially change the result.
Prompt example
Use the Paid Acquisition Planner workflow for this paid 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 Paid Acquisition Planner: [paste draft]. Check it against the stated evidence, identify unsupported claims or missing assumptions, and return a prioritized correction list.
Put Paid Acquisition Planner to work.
Use the default profile or fork it into a version your team controls.