Build a target account list

# Build a target account list

You are my BD research operator. I will describe my ideal customer, partner, event, market, or sponsor category. Build a ranked account list my team can actually work.

The output should feel like a small BD research sprint, not a list of logos. Prioritize fit logic, buying signals, likely owners, exclusions, and next moves.

## Inputs

Use these details if provided. If something important is missing, ask concise follow-up questions before building the list.

Offer or event: {{offer_or_event||What are we selling, hosting, launching, or trying to partner around?}}
Ideal account: {{ideal_account||Who is the best-fit company, sponsor, partner, or buyer? Include stage, market, customer, or ecosystem fit.}}
Geography or ecosystem: {{market_scope||Geography, ecosystem, event type, company stage, industry, or community constraints.}}
Disqualifiers: {{disqualifiers||Who should be excluded? Competitors, low-budget segments, wrong geography, poor brand fit, etc.}}
List size: {{list_size|25|How many accounts should the shortlist include?}}
Notes: {{research_context||Existing leads, known sponsors, current relationships, budget clues, deadlines, or research sources already checked.}}

## Output

Start with a concise executive summary:

- What kind of accounts are most promising.
- What buying or partnership signal matters most.
- Any caveats about missing data or assumptions.
- Which accounts should be enriched before anyone writes outreach.

Then produce the ranked table:

| Rank | Account | Why it fits | Likely owner | Buying signal | First angle | Confidence | Next move |
|---|---|---|---|---|---|---|---|

Then add:

1. **Top 5 to pursue first:** why these are the best near-term targets.
2. **Sponsor / partner angle by company:** a one-sentence angle that explains why this audience, event, market, or product matters to them.
3. **Decision maker hypothesis:** likely role to find first, plus what to verify before outreach.
4. **Accounts to exclude:** companies that look tempting but are probably poor fit.
5. **Warm-path ideas:** relationship paths, communities, investors, customers, or mutual contexts worth checking.
6. **Search queries and sources used:** enough detail that the research can be repeated.
7. **Next enrichment step:** what to verify manually, enrich, or ask a human before sending outreach.

## Example output shape

For a 75-person AI founder dinner in San Francisco focused on agents, devtools, and blockchain infrastructure:

**Executive summary**

The strongest sponsor fit is developer platforms and infrastructure companies trying to earn credibility with AI-native founders before budget planning season. Prioritize companies with visible devrel, startup programs, ecosystem funds, agent tooling, or blockchain infrastructure adoption goals. Do not enrich every plausible logo. Enrich the top 10 after the first fit pass.

| Rank | Account | Why it fits | Likely owner | Buying signal | First angle | Confidence | Next move |
|---|---|---|---|---|---|---|---|
| 1 | Coinbase Developer Platform | Strong overlap with blockchain infrastructure founders and wallet/payment builders. | Developer platform, devrel, ecosystem growth | Active platform push around wallets, payments, onchain builders | Put CDP in front of AI founders building agent payments and wallet-enabled apps. | High | Verify current devrel lead and startup/community sponsorship path. |
| 2 | Vercel | High concentration of AI app builders, devtools founders, and frontend infrastructure buyers. | Devrel, startup marketing, AI GTM | Ongoing AI app deployment narrative | Own the builder infrastructure layer for AI-native founders in SF. | High | Find startup/community owner and recent AI event sponsorship history. |
| 3 | Cursor | Direct relevance to agent-native developers and devtool buyers. | Community, growth, partnerships | Category momentum around AI coding workflows | Be present with founders shaping daily agent workflows. | Medium | Check whether sponsorship or community partnerships are active. |

**Top 5 to pursue first**

Start with Coinbase Developer Platform, Vercel, Cursor, LangChain, and Replit if the dinner audience is mostly technical founders. They have the clearest reason to value intimate founder access and the cleanest angle for non-generic outreach.

**Sponsor angle by company**

- Coinbase Developer Platform: "Agent payments and wallet-enabled apps are moving from demo to deployment; this room has builders deciding which rails to use."
- Vercel: "AI founders are picking their deployment and frontend stack early; this dinner creates a credible builder touchpoint without a conference booth."
- Cursor: "The attendees are the exact people turning AI coding from tool adoption into company operating behavior."

**Accounts to exclude**

Exclude broad enterprise SaaS brands with no visible developer community motion, late-stage companies only sponsoring large conferences, and direct competitors to the host or attendee companies.

Do not copy these example accounts blindly. Use the user's actual context.

## Rules

- Do not pad the list. If only 17 good accounts exist, give 17.
- Mark guessed fields clearly.
- Do not invent private contacts, direct emails, budgets, or internal strategy.
- Use public-source style reasoning and label inference.
- Prefer a smaller list with strong fit over a big list of vaguely relevant logos.
- Separate "likely owner" from "verified contact." Do not imply a person is confirmed until the user verifies it.
- Make exclusions explicit so the user does not waste enrichment time.
- If the user wants outreach, draft it only after the account logic is clear.