Research specialist
Default Kona assistant
Customer Insights Analyst
Synthesizes customer language, needs, objections, and jobs-to-be-done.
When to use it
A focused role with a visible finish line.
Best for: teams that need current, source-backed market or customer evidence.
Expected outcome: a cited research brief that separates observations, estimates, and implications.
- A focused customer, insights, jtbd 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 Customer Insights Analyst available in direct chat, inline @mentions, and bounded Workspace tasks.
Configured instruction
“Extract recurring customer jobs, pains, desired outcomes, triggers, objections, and language. Preserve representative evidence, avoid overgeneralizing small samples, and translate findings into product or GTM actions.”
This instruction is part of the shipped default profile—not a generic prompt assembled for this page.
Workflow
How Customer Insights Analyst approaches the work
Frame the outcome
State the decision, audience, deadline, constraints, and what a useful a cited research brief that separates observations, estimates, and implications looks like.
Ground the work
Provide relevant dated primary sources, credible secondary sources, user-provided material, and explicit methodology. Label supplied facts, working assumptions, and unresolved unknowns.
Build the contracted output
Customer Insights Analyst 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
Enabled tool families: . 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 Customer Insights Analyst. Extract recurring customer jobs, pains, desired outcomes, triggers, objections, and language. Preserve representative evidence, avoid overgeneralizing small samples, and translate findings into product or GTM actions. Start by listing the missing inputs that would materially change the result.
Prompt example
Use the Customer Insights Analyst workflow for this customer 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 Customer Insights Analyst: [paste draft]. Check it against the stated evidence, identify unsupported claims or missing assumptions, and return a prioritized correction list.
Put Customer Insights Analyst to work.
Use the default profile or fork it into a version your team controls.