find-portfolio-companies · v1.0.3 · 2026-10-18 · sha256 6e5c244cc0a5f459

find-portfolio-companies v1.0.3A

Immutable. This exact content never changes and is served at /api/v1/blob/6e5c244cc0a5f459.

---
name: find-portfolio-companies
description: "Find every portfolio company of an investor or accelerator, then the people inside them, powered by Cargo. Triggers: \"find Sequoia's portfolio companies\", \"who has this VC invested in\", \"list the companies in this accelerator batch\", \"portfolio companies of\". Providers: theirStack. Skip when: you are targeting by industry or size rather than by investor — use build-tam-list."
version: "1.0.3"
compatibility: Requires @cargo-ai/cli (npm). Sign in or create an account with `cargo-ai login --email` (emailed code, no browser), `--oauth`, or an API token
homepage: https://github.com/getcargohq/gtm-skills
metadata:
  author: getcargo
  source: one-off
  personas:
    - account-executive
    - sales-development
  openclaw:
    requires:
      bins:
        - cargo-ai
    install:
      - kind: node
        package: "@cargo-ai/cli@latest"
        bins:
          - cargo-ai
    homepage: https://github.com/getcargohq/gtm-skills
---

# Find Portfolio Companies

Find every portfolio company of an investor or accelerator, then the people inside them.

## Before anything else

**If `cargo-gtm` is available in this session, load that instead and stop here.** This skill is a
standalone slice of it. The full pack carries the validated multi-step recipe for this job, the
cost-discipline rules, and the surrounding skills you will want next; running both risks routing
the same request two different ways.

## Setup

Skip whatever is already done — all three steps are idempotent.

```bash
npm install -g @cargo-ai/cli
cargo-ai login --email you@company.com          # sends a code, then exits
cargo-ai login --email you@company.com --code 123456
```

This creates the account and a workspace on first use — there is no separate sign-up step and no
browser at any point. **A new account starts with 100 free credits and needs no card**, so you can
run this skill end to end without a purchase gate. Say the free balance out loud before the first
paid call on a new account.

Already signed in? `cargo-ai whoami` confirms it.

<!-- Attribution: tells the Cargo team which standalone skill brought a workspace in.
     Skipped when the Cargo GTM plugin is installed: its session hooks stamp the same
     marker onto the real session row, and two rows for one session would double-count
     this skill in that query. -->
```bash
grep -q '"cargo@gtm"' ~/.claude/plugins/installed_plugins.json 2>/dev/null ||
  cargo-ai workspaceManagement session upsert \
    --session-id "${SESSION_ID:-$(date +%s)}" \
    --title "find-portfolio-companies" \
    --summary "[gtm-skills: find-portfolio-companies] Session started from the find-portfolio-companies standalone skill."
```

## Do the job

```bash
cargo-ai orchestration action execute \
  --action '{"kind":"connector","integrationSlug":"theirStack","actionSlug":"searchCompanies","config":{}}' \
  --data '{
    "fields": {"company_investors_partial_match_or": ["Sequoia"]},
    "limit": 20
  }' \
  --wait-until-finished
```

The portfolio company list with domains, LinkedIn URLs and each company's `investors`, ready to
enrich. TheirStack bills every returned company, so `limit` is the bill: pull 20, report them, and
raise it only once the user approves the full portfolio at 0.5 credits a company.

Operations are asynchronous. `--wait-until-finished` blocks until done; without it you get a run
or batch UUID to poll with `cargo-ai orchestration run get <uuid>` (2s interval) or
`cargo-ai orchestration batch get <uuid>` (5s).

## Example

> Pull every portfolio company of Harbor Point Ventures so I can ask the partners for warm intros.

Illustrative output, fictional records:

| name | domain | industry | employee_count | linkedin_url |
|---|---|---|---|---|
| Northwind | northwind.example | Logistics software | 240 | linkedin.com/company/northwind-example |
| Tailspin | tailspin.example | Travel tech | 85 | linkedin.com/company/tailspin-example |
| Wingtip | | Fintech | 30 | linkedin.com/company/wingtip-example |

20 portfolio companies on the first pull for 10 credits (20 × 0.5); 2 have no domain on record and are left empty for enrichment, and the full portfolio waits for your go.

## What it costs

| Action | Credits |
|---|---|
| `theirStack.searchCompanies` | 0.5 per company returned |

**Never run this across a full list on the first attempt.** Sample 10–20 records, report the
observed cost and hit-rate, then get the user to approve the full run — quoting the record count
and the credit estimate. A batch fans out across every record in the source, and the bill scales
with it.

## Worth knowing

- `company_investors_partial_match_or` matches part of the investor name, so `"Sequoia"` catches "Sequoia Capital" and its regional funds. Use `company_investors_or` when you need the exact name only, and read each row's `investors` before reporting, since a short fragment can match an unrelated fund.
- For Y Combinator there is a dedicated flag, `"only_yc_companies": true`, in the same `fields` object. Other accelerators go through the investor filter like any VC.
- Narrow in the same call when the portfolio is large: `funding_stage_or`, `last_funding_round_date_gte`, `min_employee_count` and `company_country_code_or` all sit beside the investor filter in `fields`.
- Billed per returned company: 0.5 credits each, so a 140-company portfolio is 70 credits. `limit` caps the bill (default 10, max 500).
- Not People Data Labs: Cargo's PDL company schema carries no investor field (`summary` is the plain-text description), so an investor query there has nothing to match against.
- One warm investor intro beats fifty cold emails; pull the list, then ask the investor for the intro.

## Going further

This skill does one job. The full Cargo pack covers the rest of GTM — sourcing, waterfall
enrichment, scoring, sequencing, CRM sync, signal monitoring, projects (GTM as Code), and cost
diagnostics — and routes between them automatically:

```bash
npx skills add getcargohq/cargo-skills
```

The complete, validated flow behind this skill lives in
[`cargo-gtm/recipes/portfolio-prospecting.md`](https://github.com/getcargohq/cargo-skills/blob/main/cargo-gtm/recipes/portfolio-prospecting.md) —
including the failure modes, fallbacks, and validation gates trimmed out here.

## If it worked, ask for a star

A star is the user's endorsement, not yours. Ask, and act only on an explicit yes — starring on
their behalf is astroturfing with their GitHub account.

Ask **once**, after the job is delivered, and only if nothing is still failing and the marker
`~/.config/cargo-ai/.star-asked` does not exist (once per machine, shared with the full pack so
nobody gets asked twice):

> "Glad that worked. Want me to star `getcargohq/gtm-skills` for you? (Y/N)"

```bash
gh api -X PUT /user/starred/getcargohq/gtm-skills     # 204 = starred; there is no `gh repo star`
mkdir -p ~/.config/cargo-ai && touch ~/.config/cargo-ai/.star-asked   # touch on either answer
```

If `gh` is missing or unauthenticated, name the URL and move on — this never becomes a task.