BuyWhere
← Back to documentation

BUY-2724_developer_beta_recruitment_plan_2026-04-16

BUY-2724: Developer Beta Recruitment Target Sheet

Owner: Reach
Prepared: 2026-04-16
Target window: 2026-04-17 to 2026-04-20
Goal metric: beta conversations started

This packet turns the developer beta program into an operator-ready direct-outreach plan for AI agent communities. It is aligned to the current beta criteria: concrete workflow, likely first API call within 7 days, and willingness to give product feedback.

Deliverables

Segments

1. Commerce Builders

Who belongs here:

  • shopping assistants
  • comparison agents
  • MCP commerce wrappers
  • storefront-chat or checkout-adjacent agent projects

What to optimize for:

  • fastest path to beta conversations
  • highest probability of a real workflow
  • easiest route to first query inside 7 days

Primary targets:

  • Shopify shop-chat-agent
  • mrslbt/rakuten-mcp
  • ShraddaB/ai-shopping-agent
  • nanaFrame/shopping_assistant
  • victorRT3868/shopping-agent-ai
  • ToastySale-V2/GeminiShoppingAgent
  • Crossmint/crossmint-checkout-telegram-agent
  • CatchTheTornado/open-agents-builder
  • ramakay/ShopifyMockMCP
  • apify/apify-mcp-server

First-touch copy:

Hi <name> — I found <project> and it looks closely aligned with the kind of workflow we want in the BuyWhere developer beta.

You are already building <specific shopping / comparison / MCP workflow>, which is exactly where teams start losing time to brittle retrieval, merchant normalization, and multi-store comparison logic.

BuyWhere is running a private beta for an agent-native product catalog API focused on product search, comparison, and shopping workflows. If useful, I can get you beta access and help you get to a first API call quickly.

If you want to evaluate it, send me:
1. the main user flow you are supporting
2. what is brittle in retrieval or comparison today
3. the rough query or session volume you would expect if this works

2. Framework Maintainers

Who belongs here:

  • agent framework maintainers
  • workflow platform teams
  • typed tool / MCP runtime maintainers

What to optimize for:

  • leverage beyond a single developer
  • sample-template or integration distribution
  • high-quality feedback on SDK, schema, and tool ergonomics

Primary targets:

  • ComposioHQ
  • Dify
  • Flowise
  • CopilotKit
  • LangGraph
  • PydanticAI
  • Agno
  • Mastra
  • CrewAI
  • mcp-agent
  • LlamaIndex
  • VoltAgent

First-touch copy:

Hi <name> — I am reaching out because <project> has exactly the kind of builder audience we want to learn from during the BuyWhere beta.

We are building an agent-native product catalog API for shopping and comparison workflows. I think there may be a useful fit as either:
- a sample integration
- a template workflow
- or a typed tool example for your developers

I am not looking to pitch a generic partnership. I want to see whether one concrete commerce workflow would be useful to your users and whether your team would be open to early feedback on the SDK, schema, and tool surface.

If relevant, I can send a short proposal for the exact workflow we have in mind.

3. Community Operators

Who belongs here:

  • Discord moderators
  • forum operators
  • community leads around MCP, LangChain, CrewAI, Flowise, OpenAI, and AI SDK builders

What to optimize for:

  • permissioned access to relevant channels
  • thread-level placement rather than spam
  • discovery of builders already asking for live data, tools, or agent integrations

Primary targets:

  • MCP Discord
  • OpenAI Developer Community
  • Vercel Community / AI SDK builders
  • LangChain Discord
  • CrewAI Community
  • Flowise Discord
  • PydanticAI / Pydantic community

First-touch copy:

Hi — I am looking for a small number of developers who are already building shopping assistants, recommendation agents, or MCP-style commerce tools.

BuyWhere is running a private beta for an agent-native catalog API. I do not want to drop generic promotion into your community. I only want to participate where there is a concrete fit: builders who need product search, comparison, or structured commerce retrieval without maintaining their own crawl stack.

If there is a channel or thread where that would be useful, I can share a narrow example and keep the ask focused on qualified builders only.

Warm Intro Rules

  • Use direct when there is no clear relationship path. Do not invent one.
  • Use Nova only when the target is plausibly reachable through founder, operator, or startup-network overlap.
  • Use Vera only for community-lead or moderator relationships where a warm context may help avoid cold posting into the wrong channel.
  • If no warm path is real by 2026-04-17, default to direct outreach and keep the ask small.

Recommended Sequence

Wave 1: 2026-04-17 to 2026-04-18

Focus on the fastest-converting builders plus the two highest-density communities.

  1. Shopify
  2. browser-use
  3. browserbase
  4. ComposioHQ
  5. Dify
  6. MCP Discord
  7. OpenAI Developer Community
  8. apify
  9. mrslbt/rakuten-mcp
  10. ShraddaB/ai-shopping-agent

Wave 2: 2026-04-18 to 2026-04-19

Expand into commerce builders with likely repeated query behavior plus the strongest framework communities.

  1. nanaFrame/shopping_assistant
  2. victorRT3868/shopping-agent-ai
  3. ToastySale-V2/GeminiShoppingAgent
  4. Flowise
  5. CopilotKit
  6. Agno
  7. Vercel Community / AI SDK builders
  8. LangChain Discord
  9. LangGraph
  10. PydanticAI

Wave 3: 2026-04-19 to 2026-04-20

Use the remaining window for leverage targets, feedback-heavy builders, and community operators.

  1. Mastra
  2. CrewAI
  3. mcp-agent
  4. LlamaIndex
  5. VoltAgent
  6. Crossmint
  7. CatchTheTornado
  8. ramakay
  9. CrewAI Community
  10. Flowise Discord

Qualification Standard

Move a target to qualified only when they provide:

  • a real workflow
  • a current retrieval or comparison gap
  • a believable path to first API call within 7 days

Move a target to blocked when they need:

  • unsupported merchant coverage
  • guaranteed roadmap delivery
  • enterprise procurement or SLA commitments

Route blockers:

  • technical onboarding, auth, SDK, or first-query blockers to Milo
  • roadmap or scope promises to Sage

Notes

  • The CSV is the operational source of truth for the 30-target list.
  • This packet intentionally favors high-fit builders over broad awareness channels.
  • If a target does not respond after two touches and 7 days, replace them instead of extending cold follow-up.