JL

Investor profile

Jeremy Lizt

Angel, Operator angel

An angel investor and operator angel based in San Francisco, California, United States, Jeremy Lizt has 4 known investments: Airbyte, Datavant, TravelJoy and Ternary.

Is Jeremy Lizt a fit for your startup?

Paste your website. AI checks the fit and scores every other investor too.

Investment focus

Stage
Seed
Sector
SaaS

Contacts

LinkedIn profile on fileAvailable after registration.
Get contact

Jeremy Lizt portfolio companies (4)

  • Airbyte
  • Datavant
  • TravelJoy
  • Ternary

Investor Profile

The known portfolio sits in sector SaaS, and focus area Developer Tools.

Stage-wise, the known deals cluster around Seed rounds.

The portfolio and focus above give founders context on whether Jeremy Lizt matches their raise.

Similar investors

Showing 19 of 99

Frequently asked questions

Who is Jeremy Lizt?

Jeremy Lizt is an angel investor and operator angel based in San Francisco, California, United States with 4 known investments on file, among them Airbyte, Datavant and TravelJoy. The sections above list the sectors and stages attached to that record.

What does Jeremy Lizt invest in?

Listed sectors include SaaS; listed focus areas include Developer Tools. Those tags come from the companies attached to this profile, so they read as a record of what has been backed rather than a stated preference for what comes next.

What stage does Jeremy Lizt invest at?

The known deals of Jeremy Lizt include Seed rounds. Stage is the strongest single filter when you build a target list: an investor with no record at your stage rarely starts with you.

How do I contact Jeremy Lizt?

A LinkedIn page is on file for Jeremy Lizt. It is readable inside RaiseHunt after you create an account. The database holds no email address and no phone number for this profile.

Skip the browsing. Let AI find your ideal investors in one minute.

Paste your startup website and AI picks your best-fit investors out of 135,000+ profiles.

Data: RaiseHunt investor dataset · Snapshot 5 September 2026 · How this data is built · Report a correction or request removal