Results for “customers”

Uncover customer jobs, pains, and gains in a structured JTBD format to clarify unmet needs, reposition products, or improve discovery and messaging.

Create data-backed customer personas with market research, demographics, psychographics, jobs-to-be-done, journey mapping, and avatar generation.

Conduct and synthesize customer research into actionable insights from interviews, surveys, reviews, and online communities.

Build detailed ideal customer profiles with pain points, objections, buying triggers, and messaging angles. Includes community research to find where ICPs gather online and extract their exact language. Use when researching audiences, creating buyer personas, or developing targeted messaging.

Create a working customer profile from existing research, market signals, and team knowledge before deeper validation.

Coleta a linguagem literal do público em avaliações, fóruns, redes sociais, tickets de suporte e transcrições de vendas para gerar um banco de frases verbatim que orienta a escrita de copy.

Use to reconstruct what actually happened to one customer across every conversation, channel and handoff, for an escalation, complaint, post-mortem or goodwill decision. Trigger for "build a timeline for this customer", "what happened on this case", "summarize the back-and-forth before I decide", "when were they first told", escalation summaries, complaint investigations, or a case spanning several tickets.

Create an end-to-end customer journey map with stages, touchpoints, emotions, pain points, and opportunities to identify friction points and improve user experience.

Identify and analyze 3-5 distinct customer segments with demographics, jobs-to-be-done, pain points, and product fit analysis for market opportunity evaluation.

When the user wants to find, qualify, and build a list of prospects to reach out to — across B2B SaaS, general B2B, or local small businesses. Also use when the user mentions "prospecting," "build a prospect list," "find prospects," "find leads," "lead gen list," "find SaaS companies that," "find B2B companies," "find local businesses," "ICP-fit accounts," "who should we go after," "outbound list," "target account list," "find clients near me," "businesses without websites," "prospect research," "qualified leads," "find my first customers," "early adopters," "design partners," "beta users," or "who has this problem." Use this for the list-building and qualification phase. For writing the outbound copy after the list is built, see cold-email. For deep competitive research on specific accounts, see competitor-profiling.

Use to CREATE or REVIEW a Job to be Done (JTBD) in Alan Klement's demand-side, progress-based sense — a job is the progress a customer is trying to make, never a task or feature. Trigger whenever someone wants to write or draft a JTBD, job statement, or job story; figure out the real motivation, struggle, or progress behind a feature, request, or product; understand why customers switch, adopt, or churn; turn interview notes or research into jobs; or pressure-test, sharpen, or rewrite existing JTBDs into proper jobs. Also trigger on "grill my JTBD", "is this a real job or just a task/feature", "what's the actual job here", "why would they switch". In an A-Team target repo, jobs are durable artifacts — this skill writes docs/product/jtbd/NN-<slug>.md per CONTRACT.md and never deletes or silently rewrites a job. Do NOT use for writing PRDs, roadmaps, tickets, or acceptance criteria (those consume a finished JTBD), or for implementation user stories.