LV

Investor profile

Luis Villegas

Operator angel

Kirkland·Washington·United States2known investments

An operator angel based in Kirkland, Washington, United States, Luis Villegas has 2 known investments: Live Aware Labs and Roro.

Is Luis Villegas a fit for your startup?

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

Investment focus

Sector
Consumer
Focus
Gaming

Contacts

LinkedIn profile on fileAvailable after registration.
Get contact

Luis Villegas portfolio companies (2)

  • Live Aware Labs
  • Roro

Investor Profile

The known portfolio sits in sector Consumer, and focus area Gaming.

Luis Villegas appears in Pre-Seed and Seed rounds across the known deals.

The portfolio and focus above give founders context on whether Luis Villegas matches their raise.

Similar investors

Showing 20 of 100

Frequently asked questions

Who is Luis Villegas?

Luis Villegas is an operator angel based in Kirkland, Washington, United States with 2 known investments on file, among them Live Aware Labs and Roro. The sections above list the sectors and stages attached to that record.

What does Luis Villegas invest in?

Listed sectors include Consumer; listed focus areas include Gaming. 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 Luis Villegas invest at?

The known deals of Luis Villegas include Pre-Seed and 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 Luis Villegas?

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