Skip to content

gooseworks-ai/goose-skills / skills/marketing/research-audience

research-audience

Verified

Audience research: who the buyers are, in their own words, where they gather and how to reach them — plus named prospect lists when asked. Use when the marketer says "research our audience", "who should we target", "mine our reviews", "why do people buy us or leave", "where does our audience hang out"; or for lists: "find 50 right-fit leads with emails", "find retailers or accounts to pitch", "score these leads / who do we call first", "who's looking for an alternative to X", "tell me when a past champion changes jobs". Reads the brand's own customer data first and delivers a readable report saved to the brand. Never contacts anyone. Not for market size or trends — use research-market; not for writing the messages — use write-outreach.

references/audience-research.md

View on GitHub
# Audience research — the craft

Load at steps 1–5. The question a founder brings is "who are our buyers, and how do we reach them?" A great answer lets them write a better ad, pick the right community and send the right first message *this week* — and it rests on real buyers, not on whichever websites happened to load. A weak one is a persona with a stock-photo name and no evidence.

## Customer data — the best source, asked for once

When the brand has customers, its own data beats any public read. Ask once, up front, for the export that fits the company type (never all of these — pick the one or two that matter):

| Company type | Ask for | What it settles |
|---|---|---|
| B2B SaaS / services | a customer list or CRM export: company, role or title, plan, signup date, active or cancelled — and win/loss notes, cancel reasons | who actually pays, which roles buy, who stays, why deals are won and lost |
| DTC / consumer brand | an order or customer-segment summary (no names needed): repeat vs one-time, top products, regions — and post-purchase survey answers, return reasons, support themes | who buys again, why they buy, why they return or stop |
| Consumer app | active vs churned users by plan, cancel-survey answers, in-app feedback | who sticks, why they leave |
| Marketplace | both sides' top accounts and churn reasons | which side is short, why |
| Local business | booking or visit data by occasion, "how did you hear" answers, review export | who comes back, from where |

Reading it: cluster paying customers by the situation they're in (company type × role, or life situation × trigger) and count them; read cancel and loss reasons as their own theme list (why they leave is the most under-used finding in audience work); keep only counts and patterns — never personal data — in anything saved to the brand. Customer data outranks every public source: when it disagrees with the site, the brain or the web, it wins, and the report says so.

## 1. Buyer groups that are real

- **Name each group by situation, not demographics.** "In-house growth leads at consumer brands spending $20k+/month on Meta" beats "Marketing Mary, 34". Demographics only when they change the message (a parent buying for a teen).
- **2–5 groups.** More than five means you haven't merged; one means you haven't looked.
- **How you'd recognise one** — the job title, company type, situation or behaviour that marks a person as in the group, specific enough to use as ad targeting or list criteria.
- **Buying roles** — who uses it, who pays, who approves (B2B: champion, economic buyer, user, blocker; consumer: the buyer vs the user, the gift-giver).
- **Size in buyers, not followers.** Count people or companies: directory and store counts, company counts by size band, job-post counts for the role, industry figures, the brand's own customer mix scaled up. Each input sourced or labelled an assumption, with the arithmetic shown in words ("~4,200 US Shopify stores in skincare with 10+ staff (source) × ~1 growth lead each"). A subreddit or community's member count is **reach**, never group size — most members of a big community aren't in the group. **Every group gets at least an order of magnitude** (~1,000 / ~10,000 / ~100,000 companies or buyers) whenever any proxy exists — a directory count, a job-post count, a category total — labelled "rough"; "size unknown" only when no proxy exists at all, and then that is a decision.
- **Rank** on stated criteria: size, pain, fit with what we sell today, reachability. Price fit counts — a group whose budget matches our price is a fit, not a stretch.
- **When the brand's own facts disagree** (the site sells one story, the saved brand text another): customer data decides; without it, rank on who actually talks about and buys this kind of product, say which story the research supports, and make the choice the first decision.
- **B2B:** role × company type × situation. **Consumer:** life situation × trigger. **Marketplace:** both sides, separately. **Local:** radius × occasion.

## Evidence bar — before naming a lead group

Name a lead group only when at least one holds:
- the brand's own customer data shows it (the largest or best-retained paying group), **or**
- first-hand evidence from **at least 5 distinct people in the group**, from **at least 2 kinds of source** (e.g. a review site and a community), mostly from the last 18 months — none of it vendor, agency, case-study or job-post text. **At least one kind must not be reviews of a rival**: rival reviews show what people hate about a rival, not that this group would buy us, and five Trustpilot complaints about rivals plus one other reviewer is one kind of source, not two. The second kind is the brand's own customers or reviews, a community thread, interviews, or job-post counts that show the role exists in numbers.

Otherwise the top-ranked group is still named as the lead, labelled **"provisional — <what's missing>"**; say what evidence would settle it (the customer export, a paid read of the forums they use, five interviews) and make that the first decision. A provisional lead never sits in "In short" as a settled finding. A lead that rests on two people and a company's own blog is a guess, and the report says so.

## 2. What they want

The outcome they are hired or living for, in their terms — "launch more ads without hiring", "clear skin without a 10-step routine". Read it from customer data and win/loss notes first, then their own posts and talks, review headlines ("finally I can…"), community threads asking for help, and job posts (what a role is measured on — the employer's view, labelled so). One or two lines per group, with the evidence.

## 3. Their problems — and how we solve them

| Problem (their words) | How often / how bad | How we solve it | Proof |
|---|---|---|---|
| "I spend Sunday nights making 20 ad variations" | 14 threads, 6 reviews | Batch ad generation from a product page — solved | A signed-off claim — or "you'd need proof of hours saved first" |

- At least three problems per top group, in their words, with a count and a link. Problems come from what they say, not what we sell; map honestly: solved, partly solved, not solved (that's a product note, not an ad).
- Rank by frequency × intensity. A problem only rivals mention is a rival's framing, not the audience's.
- **Why they leave** (cancel reasons, churn notes, "went back to X" reviews) and **why we win or lose** (win/loss notes) get their own short table when the brand has them.

## 4. Their language — the quote bank

The rules for who counts as their voice, sampling, integrity and tagging are in [quote-bank.md](quote-bank.md). In the report: at least five first-hand quotes for the lead group and three for each other top group, each linked, dated and with who's speaking — or "thin" said plainly, with why (e.g. the forums they use were unreadable). Never pad with vendor, agency, trade-press, case-study or job-post text. Add a short **their words vs ours** table (what we say on our site vs what they say).

## 5. Where they gather

Name the actual places, each with **evidence of activity** (members, posts per week, episode count, attendees, last post date) **and evidence that this group is there** (a post by someone in the group, a speaker list, a sponsor page naming the audience) — at least four for the lead group:

| Kind | Examples to look for |
|---|---|
| Communities | subreddits, Slack and Discord groups, Facebook and LinkedIn groups, forums, Indie Hackers, Hacker News threads |
| Channels | which platforms they post and read on (and which they don't) |
| Publications | newsletters, trade publications, blogs they cite |
| Podcasts and YouTube | shows they mention, guests they follow |
| Events | conferences, meetups, webinars, trade shows — with dates |
| People they follow | the voices they quote and reshare (not for paying — that's the creator work) |

"LinkedIn" alone is not an answer; "the r/PPC weekly thread (110k members, 40 posts this week; three growth leads asked about creative fatigue on 12 Oct)" is. A big community where the group is a small minority is reach, not a home.

## 6. How to find and reach them

Three first moves per group (inside the group's section — the report's "What to do" list is the separate, capped list of at most six), each with the channel, the message in their words, the first ask, **who does it**, **what it needs**, and **a success check with a number and a date** ("10 replies or 3 demo asks by 15 Nov"). For lower-ranked groups the moves are small and cheap (a test, a listen, one post) and labelled lower priority.

- **Moves rest on what this run read.** A move on a channel the run couldn't read (a blocked forum, a login-only group) is labelled "unverified — read the community and its rules before posting", and is never the first move. "Do this first" always rests on sources read and cited in the report.
- **To find them:** ad targeting that matches "how to recognise one" (titles, interests, lookalike seeds from the customer data, keywords), search terms they type, directories that hold them.
- **To reach them:** the channel and format they respond to (an answer in a thread, not an ad; a newsletter sponsorship; a talk), the message (their words, our proof), the low-friction first ask.
- **Named people** only in list mode — offer it as a decision, not a default.

## 7. You vs them, and the sibling reports

How rivals talk to this audience (their homepage words, ad hooks, the communities they're active in): where we're ahead (say it louder), behind, and where everyone sounds the same (don't lead with it). Then read the brand's latest market and competitor reports: say in one line where this report agrees or differs — especially the lead group and the first move — and why.

## 8. By company type

| Type | Group dimension | Best evidence (after the brand's own customer data) | Where they hang out — look first |
|---|---|---|---|
| B2B SaaS | role × company type × trigger | job posts, G2/Capterra reviews of tools they use, LinkedIn posts, community threads | role communities (Slack groups, subreddits), newsletters, podcasts, conferences |
| Agencies / services | buyer role × client type | client reviews, RFPs, LinkedIn posts, industry roundups | trade groups, LinkedIn, events |
| DTC / consumer brand | life situation × trigger | product reviews, Reddit, TikTok/IG comments | subreddits, TikTok and IG niches, creators they follow, forums |
| Consumer app | situation × habit | app reviews, Reddit, TikTok | subreddits, TikTok, Discord |
| Marketplace | each side separately | reviews and Q&A on both sides | seller forums, buyer communities |
| Local business | radius × occasion | Google and Yelp reviews, local groups | local Facebook groups, Nextdoor, local events |

## 9. The report — this shape, these headings, in this order

Write through write-report (read it first). Body under **3,000 words** — budget it: lead group ~900, each other group ~350, everything else ~900. Cut detail no decision needs; long quote tables go to the saved quote bank, not the report.

1. **Title** — "<Brand> — audience research, <D Mon YYYY>".
2. **In short** — at most 150 words, in write-report §1's order. "**What we looked at:**" the sources (the brand's own data or not), the dates, and the main limit (forums that needed a login, one review site). Then 2–3 numbered findings, each with how sure in the body's own word: the lead group (with "provisional — <what's missing>" if it is; never "your most likely paying group" while provisional), the biggest surprise in their words. Then "**So, do this first (because of <1 and 2>):** <move> — <who> — <by when>", resting on sources this run read; with a provisional lead, the first move is the one that closes the evidence gap. Then one line on agreement with the market and competitor reports (a different lead group or first move: settled, per write-report). Nothing here stronger than the body.
3. **Decisions for you** — 1–4 rows: decision, our recommendation, what it changes.
4. **Who the audience is** — one table: group · how you'd recognise one · size in buyers (inline source link and date, or "assumption") · uses / pays / approves · evidence (people, kinds of source, customer data) · rank.
5. **One section per group, lead first, each with the same five parts** — lower-ranked groups shorter, never missing a part:
   - **What they want** — 1–3 lines, their words, linked.
   - **Their problems, and how we solve them** — the §3 table: problem in their words · how often (posts, people) · quote + link and date · solved / partly / not solved · proof (a signed-off claim, or "you'd need proof of X first").
   - **In their words** — quotes inline: "…" — <who> ([site, date](link)). Five for the lead, three for others, or "thin" with why.
   - **Where they gather** — places with activity and evidence the group is there, linked and dated (four+ for the lead).
   - **How to reach them** — three moves: channel · message in their words · first ask · who · needs · success check (number, date). An unread channel is labelled unverified and never first.
   End each group with **For you:** one line, or "nothing to do here".
6. **Why they buy, why they leave** — from the brand's data; without it, from switch and churn evidence, said so.
7. **How rivals talk to them** — one table: rival · their words to this audience · where they show up · where we differ.
8. **What to do** — at most 6 ranked moves across all groups (the group moves feed it; don't repeat them all), each with who, what it needs, and a success check with a number and a date.
9. **What we're not doing** — the tempting moves for *this brand* you decided against, one line each with why (e.g. "Ads to agencies yet — they churn without white-label"). Never a scope list, never names of other reports' owners.
10. **What we couldn't check** — every source that failed in this run, one line each: what, why, what it would change.
11. **Sources** — dated links; then the source-skew line.

**Naming other work:** "the market report (18 Oct)", "the competitor report", "your campaign plan" — never a playbook name, file path or folder. **Every fact** carries its own link and date inline; "via secondary sources" or a bare domain is not a source, and the source named must match the link's site.

**Before handing over, count** (a miss blocks delivery — write-report §3): In short words, and each In short sentence against the body's certainty word; body words; quotes per group and the lead's share from the last 18 months; three moves per group, each with who, needs and a dated number; the banned list in write-report §3 plus "worker", "free pass", "corpus", "maker", "segment-pass", "quote bank file". Fix, then deliver.

Fictional example of the top (never reuse its values):

```
# Acme Creative (fictional) — audience research, 18 Oct 2026

## In short
**What we looked at:** your customer export and cancel notes ([17 Oct](…)), plus three public forums where growth leads talk, 12–18 Oct. Two forums needed a login and weren't read.
1. **Lead group: in-house growth leads at consumer brands** — 31 of your 52 paying customers, and the group that stays longest (confirmed, your export).
2. **Agencies leave after 2–3 months** — 9 of 14 cancel notes say no white-label output (confirmed). Don't aim at them yet.
3. **They don't say "AI creative".** They say "more variations", "fresh ads every week" (likely; 11 people, one forum).
**So, do this first (because of 1 and 3):** you answer three of this week's "creative fatigue" threads on the Meta ads forum we read ([12 Oct](…)), in their words — 30 minutes, by Friday.
Agrees with the market report's lead group; moves its first step from ads to forum answers.

## Decisions for you
| Decision | We recommend | What it changes |
|---|---|---|
| Is the export the full customer list? | Yes → keep the lead | The lead group |
| Sign off "a week of variations in an hour"? | Sign off with the test data | The headline proof |
```
add-product-e2e-evalpaperclipai/paperclipAdd or extend a Paperclip full-stack runner E2E workflow, fixture, matcher, or report evidence path for local or Daytona execution.Stars: 115kUpdated Claude CodeCodexVerifiedInstall
add-runner-evalpaperclipai/paperclipAdd or extend a Paperclip Runner protocol evaluation definition, roster, assertion, or report fixture with provenance and narrow validation.Stars: 115kUpdated Claude CodeCodexVerifiedInstall
diagnose-why-work-stoppedpaperclipai/paperclipCompatibility entry point for failed, stalled, looping, or over-recovered Paperclip work. Use fix-failed-paperclip-run for the full diagnosis, regression, repair, real verification, and green-PR workflow; honor an explicitly requested diagnosis-only scope.Stars: 115kUpdated Claude CodeCodexVerifiedInstall
fix-failed-paperclip-runpaperclipai/paperclipDiagnose and fix failed, stuck, slow, or incorrectly blocked Paperclip tasks and runs. Use with a task/run URL or failure report to trace the root cause, prove a regression red then green, check second-order effects, verify the real workflow, and deliver a PR with passing checks.Stars: 115kUpdated Claude CodeCodexVerifiedInstall