IL

Investor profile

Ian Lurie

Operator angel

Seattle·Washington·United States1known investment

Ian Lurie is an operator angel based in Seattle, Washington, United States. The known portfolio is one company, SparkToro.

Is Ian Lurie a fit for your startup?

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

Investment focus

Sector
SaaS
Focus
Audience IntelligenceMarketing Technology

Contacts

LinkedIn profile on fileAvailable after registration.
Get contact

Ian Lurie portfolio company (1)

  • SparkToro

Investor Profile

The known portfolio sits in sector SaaS, and focus areas Audience Intelligence and Marketing Technology.

Ian Lurie is listed for Pre-Seed rounds in the database.

Reviewing the investment history helps decide whether there is a realistic fit before reaching out.

Similar investors

Showing 20 of 100

Frequently asked questions

Who is Ian Lurie?

Ian Lurie is an operator angel based in Seattle, Washington, United States with one known investment on file, SparkToro. The sections above list the sectors and stages attached to that record.

What does Ian Lurie invest in?

Listed sectors include SaaS; listed focus areas include Audience Intelligence and Marketing Technology. 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 Ian Lurie invest at?

The database lists Ian Lurie for Pre-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 Ian Lurie?

A LinkedIn page is on file for Ian Lurie. 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 6 September 2026 · How this data is built · Report a correction or request removal