beam-ai-team/lead-research

Lead Research & Fit Assessment

Research prospects and assess whether they fit Beam's focus on automating outsourced work (BPO/RPO, document processing, data extraction at scale).

Workflow

Step 1: Gather Context

Collect all available information:

• Email thread / initial outreach
• Company website
• LinkedIn profiles of attendees
• Any prior relationship history
• Meeting context (who initiated, why now)

Web search the company:

• What do they do? (business model)
• Who are their customers?
• What products/services do they offer?
• Recent news, funding, leadership changes

Step 2: Understand Their Problem

Parse the initial communication for signals:

• What problem are they describing?
• What language are they using? ("manual", "repetitive", "scale", "automate")
• Who reached out? (decision-maker, influencer, researcher)
• What's the urgency? (new mandate, pain point, exploratory)

Research their likely pain points:

• What work in their business is labor-intensive?
• What processes are document-heavy?
• Where might they use outsourcing or BPOs today?

Step 3: Assess Fit with Beam

Load fit criteria: See references/beam-fit-criteria.md

Score against key criteria:

| Criteria | Assessment | Notes | |----------|------------|-------| | High volume work? | ✅/⚠️/❌ | | | Repetitive/structured? | ✅/⚠️/❌ | | | Clear inputs/outputs? | ✅/⚠️/❌ | | | Manual labor today? | ✅/⚠️/❌ | | | Decision-maker access? | ✅/⚠️/❌ | | | Budget signals? | ✅/⚠️/❌ | |

Determine verdict:

• ✅ Strong fit — Pursue actively
• ⚠️ Potential fit — Worth exploring, need more discovery
• ❌ Poor fit — Politely decline or deprioritize

Step 4: Generate Call Prep Document

Create a dated file: {YYYY-MM-DD}-{company}-call-prep.md

Include sections:

1. Key Participants — Who's on the call, their roles
2. Context — Summary of the relationship/outreach
3. About the Company — What they do, their market
4. Their Problem — What we understand about their pain
5. Fit Assessment — Score against Beam criteria
6. Discovery Questions — Prioritized questions to ask
7. What to Share About Beam — Relevant proof points
8. Potential Use Cases — Hypothetical applications (don't pitch, discover)
9. Call Flow — Suggested timing and structure
10. Red/Green Flags — What signals to watch for
11. Checklist — Things to confirm before the call ends

Step 5: Prepare Discovery Questions

Discovery-first approach:

• Lead with understanding, not pitching
• Ask about the problem before proposing solutions
• Quantify the pain (volume, cost, time, quality)
• Understand decision process

Template questions:

• "Can you walk me through what [their process] looks like day-to-day?"
• "Where does the source data come from?"
• "How many people work on this today?"
• "What's the biggest bottleneck — speed, cost, quality, or finding people?"
• "Have you tried to solve this before? What happened?"
• "Who else would need to be involved if we found something promising?"

---

Output Location

Save call prep documents to: 04-workspace/ceo-office/ (or appropriate project folder)

Filename format: {YYYY-MM-DD}-{company-name}-call-prep.md

---

Related Skills

• expert-review — Get expert feedback on the call prep
• close-session — Save learnings after the call