JL

Investor profile

John Lefebvre

Operator angel

John Lefebvre is an operator angel based in San Francisco, California, United States with one known investment, SMASHsolar.

Is John Lefebvre a fit for your startup?

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

Investment focus

Contacts

LinkedIn profile on fileAvailable after registration.
Get contact

John Lefebvre portfolio company (1)

  • SMASHsolar

Investor Profile

The listing covers sectors Climate and Energy, and focus areas Renewable Energy and Solar Energy. Startups operating in these areas may find John Lefebvre relevant.

John Lefebvre is listed for Pre-Seed rounds in the database.

The portfolio and focus above give founders context on whether John Lefebvre matches their raise.

Similar investors

Showing 20 of 100

Frequently asked questions

Who is John Lefebvre?

John Lefebvre is an operator angel based in San Francisco, California, United States with one known investment on file, SMASHsolar. The sections above list the sectors and stages attached to that record.

What does John Lefebvre invest in?

Listed sectors include Climate and Energy; listed focus areas include Renewable Energy and Solar Energy. 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 John Lefebvre invest at?

The database lists John Lefebvre 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 John Lefebvre?

A LinkedIn page is on file for John Lefebvre. 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