How to Sell to a Startup Founder (and Reach Them by Region)

Sell to a startup founder by proving a result in one email, to the one person who can say yes. This guide covers what founders weigh, how to size your reachable list by region for free, and how to write the first line. It takes about 20 minutes and spends 11 LeadOcean records.

TL;DR

• A startup founder is the budget holder, the user and the champion at once. One email to them can close the deal.
• As of 2026-10-21, 1,583,993 founders at companies of 1 to 50 people have a mailable email in LeadOcean (verified, catch_all_valid or catch_all). The split by region is in the output below.
• The run takes about 20 minutes and spends 11 records: 10 search rows and 1 enrichment. Every count is free.

Prerequisites

• A LeadOcean API key in $LEADOCEAN_API_KEY. The Free plan covers this guide: 1,000 records for life, no card, 5 requests a second.
• curl and jq.
• One sentence on the result your product gives a small team, with a number in it.

What a startup founder weighs

A founder weighs time, cash and risk, in that order. Write to those three and nothing else.

• Time. They do sales, hiring and product in the same week. An email that needs a call to understand loses.
• Cash. Runway is the budget. A price in the first reply helps. A "contact sales" wall hurts.
• Risk. A bad tool costs weeks they do not have. Offer a free plan, a short trial of the work, or a refund path.

Where they sit in the buying committee matters less than at a large company. Under 50 people, the founder is usually the economic buyer and the technical evaluator. Past 50, a head of sales or engineering often takes the evaluation, and the founder signs. Aim at the founder first when the company is small, and at the function lead when it is not.

How founder behavior shifts by stage

The stage of the company changes who answers and how fast.

• Pre-seed and seed (1 to 10 people). The founder reads every email and decides alone. Replies come in hours. Price and speed to value decide it.
• Series A (11 to 50 people). The founder still signs, but a first sales or ops hire now filters inbound. Name the function lead in your second email.
• After 50 people. Procurement, security review and a champion appear. Treat it as a team sale and start with the function lead.

A founder also forwards. If your email is short and self-contained, they paste it to a cofounder with one line of context. Write every email so it survives being forwarded: company name, result and ask in the first three lines.

What to avoid

Founders ignore three things quickly: vague claims ("grow faster"), unrequested calendar links, and fake familiarity ("loved your recent post" with no post named). One true, specific detail beats three warm ones.

Step 1: Size the reachable list by region

Count before you pull anything. The count call is free and spends no records. Send count=true as a query parameter with limit 1.

for region in NORAM EMEA APAC LATAM; do
  echo -n "$region: "
  curl -s -X POST "https://api.leadocean.io/v1/people/search?count=true&limit=1" \
    -H "x-api-key: $LEADOCEAN_API_KEY" \
    -H "Content-Type: application/json" \
    -d "{
      \"seniority\": [\"founder\"],
      \"employeeRange\": [\"1-10\", \"11-50\"],
      \"salesRegion\": [\"$region\"],
      \"emailStatus\": [\"verified\", \"catch_all_valid\", \"catch_all\"]
    }" | jq '.meta.total'
done

meta.total is capped at 100,000 on the REST search count. The MCP tool leadocean_count_leads returns an exact total for the same filters, which is how the figures below were taken.

Pick your first region from the numbers, not from habit. If you sell in English with US pricing, start with NORAM. If you sell to a local market, count the country alone with country set to an ISO code.

To compare countries inside a region, repeat the loop with country instead of salesRegion, for example ["US"], ["GB"], ["DE"] and ["IN"]. Run one count per country and keep the table. It tells you where a local-language or local-pricing pitch has enough volume to be worth writing.

Narrow further with jobFunction or industry when the list is still too large to personalize. A list you can write 50 real first lines for beats a list of 50,000 you cannot. Use GET /v1/enums to get the exact industry strings, because industry has 534 values and a near match returns nothing.

Step 2: Pull verified founders

Search with the same filters, add the mailable statuses, and page through with the cursor. The first run takes 10 rows.

curl -s -X POST "https://api.leadocean.io/v1/people/search" \
  -H "x-api-key: $LEADOCEAN_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "seniority": ["founder"],
    "employeeRange": ["1-10", "11-50"],
    "salesRegion": ["NORAM"],
    "emailStatus": ["verified", "catch_all_valid"],
    "limit": 10
  }' | tee page1.json | jq '.meta'

Two rules keep the run clean. Read email_status on every row and send only to verified first. Bounced emails are not refunded, so a catch_all address is a second-wave send.

To read one founder in full, enrich by person_id (each row carries it at meta.source_ids.person_id) and ask for the email. This is the one enrichment in the 11-record budget.

PERSON_ID=$(jq -r '.data[0].meta.source_ids.person_id' page1.json)

curl -s -X POST "https://api.leadocean.io/v1/people/enrich" \
  -H "x-api-key: $LEADOCEAN_API_KEY" \
  -H "Content-Type: application/json" \
  -d "{\"person_id\": \"$PERSON_ID\", \"reveal_email\": true}"

Since October 2026 the enrich response also carries career history: past roles, education and awards. A past employer you share with the founder is a stronger first line than anything on their company site. Past employers carry no company_id yet, so match them by name.

Step 3: Write a first line that fits a founder

Open with one fact about their company, then one result, then one small ask. Keep the whole email under 90 words. These examples use placeholders.

Subject: Acme's onboarding emails

Jane, saw Acme moved to usage-based pricing last month.
We cut onboarding drop-off by {X}% for teams of {N} by tying the first
email to the first failed action. Want the 3-step setup, no call needed?

Subject: before your next hire

Jane, you are likely doing outbound yourself at Acme. We pull a verified
list of 200 founders in your niche in one request, so the hour you spend
on lists goes back to calls. Send the niche and I will reply with the count.

Three patterns worth testing on founders:

1. Shared history. A past employer or school from the enrich response.
2. Their own trigger. A funding round, a hire, a pricing change.
3. A free count or sample. Cheap for you, concrete for them.

Three to skip: a feature list, a "quick call" ask in the first line, and "I help companies like yours".

Send plan

Send in two waves. Wave one is verified only: one email and two follow-ups spaced four days apart. Wave two is catch_all_valid and catch_all, after you have seen the bounce rate from wave one. If wave one bounces more than your mailbox provider tolerates, stop and re-check the list. LeadOcean does not send email, so use your own sending tool. The CSV export or the API response feeds it.

Track one number: replies per 100 sends by region. After a week, put the region with the best rate first and write a region-specific line for the next batch.

What you get

The counts below come from leadocean_count_leads, run on 2026-10-21. Filters: seniority founder, employeeRange 1-10 and 11-50, salesRegion as shown, and the tool's default email filter (verified, catch_all_valid or catch_all). These are mailable counts, not everyone with a founder title.

Distinct company figures are estimates (distinctCompaniesIsExact was false). The mailable total across the four regions is 1,583,993.

Response shape from the API reference, with placeholder values:

{
  "success": true,
  "data": [
    {
      "profile_data": { "profile_full_name": "Jane Doe" },
      "contact_data": {
        "has_email": true,
        "email_status": "verified",
        "contact_current_experiences": [
          { "job_title": "Founder", "company_name": "Acme", "company_domain": "acme.com" }
        ]
      },
      "meta": { "source_ids": { "person_id": "1234567890" } }
    }
  ],
  "meta": { "count": 1, "credits": 1, "nextCursor": "..." }
}

The full person schema is in the enrich docs.

Troubleshooting

FAQ