business-dev
Full-cycle revenue engine — prospecting, CRM pipeline management, closing deals, partnerships, and engineering-as-marketing. External sales via GitHub and web.
What this skill does
# Business Development Skill
Nuclear-grade sales, partnerships, and revenue generation for autonomous agents. Manages CRM pipelines, executes multi-touch follow-up cadences, closes deals organically, and operates across the agent network AND the open internet (GitHub, web, communities).
This skill teaches any agent to: find prospects, build relationships, close deals, retain customers, grow partnerships, and track success — without ever feeling like sales.
## Usage
```
bun run business-dev/business-dev.ts <subcommand> [options]
```
## Subcommands
### pipeline
View and manage CRM pipeline state across all deal stages.
```
bun run business-dev/business-dev.ts pipeline [options]
```
**Options:**
- `--type` (optional, string): Filter by pipeline type — `customers`, `partners`, `contributors`, `marketplace`. Default: all.
- `--stage` (optional, number 0-6): Filter by stage. Default: all.
- `--stale` (optional, boolean): Show only deals with no activity in 7+ days.
**Output:**
```json
{
"pipeline": "all",
"deals": [
{
"prospect": "Stark Comet",
"identifier": "stark-comet",
"pipeline": "customers",
"stage": 3,
"stage_name": "Solution Shown",
"last_touch": "2026-03-01T12:00:00Z",
"next_action": "Follow up with case study",
"next_date": "2026-03-04",
"value_sats": 2000,
"touches": 3,
"days_in_stage": 2
}
],
"summary": {
"total_deals": 8,
"total_value": 15000,
"by_stage": { "0": 2, "1": 3, "2": 1, "3": 1, "4": 1, "5": 0, "6": 0 },
"coverage_ratio": "2.5x"
}
}
```
### prospect
Research and add a new prospect to the pipeline.
```
bun run business-dev/business-dev.ts prospect --name <name> --source <source> [options]
```
**Options:**
- `--name` (required, string): Prospect identifier (agent name, GitHub handle, etc.)
- `--source` (required, string): Where you found them — `inbox`, `github`, `signal`, `referral`, `web`, `bounty`, `leaderboard`.
- `--pipeline` (optional, string): Which pipeline — `customers`, `partners`, `contributors`, `marketplace`. Default: `customers`.
- `--notes` (optional, string): Initial research notes — their pain, your angle, their tools.
- `--value` (optional, number): Estimated deal value in sats.
**Output:**
```json
{
"success": true,
"prospect": "Stark Comet",
"pipeline": "customers",
"stage": 0,
"stage_name": "Research",
"message": "Prospect added. Research their pain + your angle within 24h."
}
```
### qualify
Run BANT+ qualification check on a prospect. Moves them from Stage 1 to Stage 2 if they pass.
```
bun run business-dev/business-dev.ts qualify --name <name> [options]
```
**Options:**
- `--name` (required, string): Prospect identifier.
- `--budget` (optional, number): Their estimated budget in sats.
- `--authority` (optional, string): Can they decide? `yes`, `no`, `unknown`.
- `--need` (optional, number 1-10): How urgent is their problem?
- `--timeline` (optional, number): Days until they need a solution.
- `--pain` (optional, string): Their specific pain in one sentence.
- `--competition` (optional, string): Who else are they evaluating?
**Output:**
```json
{
"prospect": "Stark Comet",
"qualified": true,
"score": 8,
"bant": {
"budget": 5000,
"authority": "yes",
"need": 8,
"timeline": 7
},
"recommendation": "Strong qualification. Move to Stage 2 and present solution.",
"next_action": "Send solution overview tailored to their yield scanning needs"
}
```
### close
Record a closed deal and update pipeline metrics.
```
bun run business-dev/business-dev.ts close --name <name> --revenue <sats> [options]
```
**Options:**
- `--name` (required, string): Prospect identifier.
- `--revenue` (required, number): Deal value in sats.
- `--pipeline` (optional, string): Pipeline type. Default: `customers`.
- `--notes` (optional, string): Deal notes — what was sold, terms, next steps.
- `--recurring` (optional, boolean): Is this a recurring deal? Default: false.
**Output:**
```json
{
"success": true,
"prospect": "Sonic Mast",
"revenue": 400,
"pipeline": "customers",
"stage": 5,
"stage_name": "Closed",
"total_revenue_this_week": 1200,
"deals_closed_this_week": 3,
"message": "Deal closed! Move to Stage 6 (Retained) for upsell/referral tracking."
}
```
### follow-up
Get scheduled follow-ups due today with suggested content.
```
bun run business-dev/business-dev.ts follow-up [options]
```
**Options:**
- `--limit` (optional, number): Max follow-ups to return. Default: 5.
- `--pipeline` (optional, string): Filter by pipeline type. Default: all.
**Output:**
```json
{
"due_today": [
{
"prospect": "Sly Harp",
"pipeline": "customers",
"stage": 2,
"touch_number": 3,
"last_content": "Shared order book stats",
"suggested_approach": "Social proof — show how many agents posted bids this week",
"days_since_last": 3,
"cadence_status": "on_track"
}
],
"overdue": [
{
"prospect": "Dual Cougar",
"pipeline": "partners",
"stage": 1,
"touch_number": 2,
"days_since_last": 5,
"cadence_status": "overdue"
}
],
"total_due": 1,
"total_overdue": 1
}
```
### review
Run pipeline health check. Identifies bottlenecks, stale deals, and coverage gaps.
```
bun run business-dev/business-dev.ts review
```
**Output:**
```json
{
"health": "yellow",
"stale_deals": 2,
"unqualified_in_pipeline": 1,
"pipeline_coverage": "2.1x",
"target_coverage": "3.0x",
"bottleneck_stage": "Stage 1 (Contacted)",
"bottleneck_reason": "Low response rate — 2/8 prospects responded",
"deals_at_risk": ["Dual Cougar (5 days stale)", "Wild Osprey (unqualified)"],
"recommendations": [
"Add 3 more qualified prospects to reach 3x coverage",
"Re-engage or drop 2 stale deals in Stage 1",
"Improve cold outreach messaging — response rate below 15%"
],
"metrics": {
"outreach_to_response": "25%",
"response_to_qualified": "50%",
"qualified_to_close": "33%",
"avg_time_to_close_days": 8
}
}
```
### report
Generate success metrics for agent copilot and project manager.
```
bun run business-dev/business-dev.ts report [options]
```
**Options:**
- `--period` (optional, string): Reporting period — `week`, `month`. Default: `week`.
- `--audience` (optional, string): Report format — `copilot` (operational detail), `manager` (strategic overview). Default: `copilot`.
**Output (copilot):**
```json
{
"period": "week",
"deals_closed": 3,
"revenue_sats": 1200,
"revenue_trend": "+40% vs last week",
"pipeline_value": 8500,
"new_prospects": 5,
"response_rate": "25%",
"close_rate": "33%",
"avg_time_to_close_days": 8,
"top_pipeline": "customers",
"energy_efficiency": "1200 sats revenue / 400 sats spent = 3.0x ROI"
}
```
**Output (manager):**
```json
{
"period": "week",
"revenue": 1200,
"active_partnerships": 2,
"referral_revenue": 300,
"free_tool_usage": 12,
"external_contributions": 3,
"retention_rate": "80%",
"ecosystem_health": "growing"
}
```
### templates
Get ready-to-use message templates for any sales situation.
```
bun run business-dev/business-dev.ts templates --type <type>
```
**Options:**
- `--type` (required, string): Template type — `cold-outreach`, `follow-up`, `partnership`, `soft-close`, `graceful-exit`, `objection-response`.
**Output:**
```json
{
"type": "cold-outreach",
"template": "[Name] — saw your [specific work]. [Specific compliment]. I built [tool/service] that helps with [their problem]. Given [observation about their situation], thought it might save you time. Happy to share details, no pressure.",
"variables": ["Name", "specific work", "Specific compliment", "tool/service", "their problem", "observation about their situation"],
"max_chars": 500,
"tips": [
"Research them first — mention something specific they built or said",
"Lead with genuine compliment, not flattery",
"Frame around THEIR benRelated in Sales & CRM
process-mapper
IncludedUse when a BizOps lead, COO, or process-improvement owner needs to document an end-to-end business process (procurement, employee onboarding, incident handoff, customer-onboarding, claims adjudication) in BPMN-style notation, measure cycle times by stage, surface where work spends most of its time waiting vs. being worked, and quantify the gap between processing time and total elapsed time. Pairs Lean / Six Sigma / Theory-of-Constraints canon with deterministic stdlib-only Python tools to produce a process map, a ranked bottleneck list (with severity + root-cause hypothesis), and a cycle-time analysis (P50, P90, value-add ratio, Little's-Law throughput). Distinct from sales-pipeline, system-reliability (SLO), and strategic-OKR work — this is tactical process documentation for internal operations.
payment-integration
IncludedIntegrate payments with SePay (VietQR), Polar, Stripe, Paddle (MoR subscriptions), Creem.io (licensing). Checkout, webhooks, subscriptions, QR codes, multi-provider orders.
customer-success-manager
IncludedMonitors customer health, predicts churn risk, and identifies expansion opportunities using weighted scoring models for SaaS customer success
sales-engineer
IncludedAnalyzes RFP/RFI responses for coverage gaps, builds competitive feature comparison matrices, and plans proof-of-concept (POC) engagements for pre-sales engineering. Use when responding to RFPs, bids, or proposal requests; comparing product features against competitors; planning or scoring a customer POC or sales demo; preparing a technical proposal; or performing win/loss competitor analysis. Handles tasks described as 'RFP response', 'bid response', 'proposal response', 'competitor comparison', 'feature matrix', 'POC planning', 'sales demo prep', or 'pre-sales engineering'.
customer-success-manager
IncludedMonitors customer health, predicts churn risk, and identifies expansion opportunities using weighted scoring models for SaaS customer success
sales-engineer
IncludedAnalyzes RFP/RFI responses for coverage gaps, builds competitive feature comparison matrices, and plans proof-of-concept (POC) engagements for pre-sales engineering. Use when responding to RFPs, bids, or proposal requests; comparing product features against competitors; planning or scoring a customer POC or sales demo; preparing a technical proposal; or performing win/loss competitor analysis. Handles tasks described as 'RFP response', 'bid response', 'proposal response', 'competitor comparison', 'feature matrix', 'POC planning', 'sales demo prep', or 'pre-sales engineering'.