SO

Investor profile

Sean O`Leary

Angel

1known investment

An angel investor, Sean O`Leary has one known investment, Backupify.

Is Sean O`Leary a fit for your startup?

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

Investment focus

Sector
SaaS
Focus
BackupBoard MemberCloud BackupData ProtectionEnterprise SaaS

Contacts

sol***@***.comLinkedIn profile on fileEmail and phone open on the Raise plan.
Get contact

Sean O`Leary portfolio company (1)

  • Backupify

Investor Profile

The known portfolio sits in sector SaaS, and focus areas Backup, Board Member, Cloud Backup and Data Protection.

The stage tags on this profile are Pre-Seed, Seed and Series A.

The portfolio and focus above give founders context on whether Sean O`Leary matches their raise.

Similar investors

Showing 20 of 100

Frequently asked questions

Who is Sean O`Leary?

Sean O`Leary is an angel investor with one known investment on file, Backupify. The sections above list the sectors and stages attached to that record.

What does Sean O`Leary invest in?

Listed sectors include SaaS; listed focus areas include Backup, Board Member, Cloud Backup and Data Protection. 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 Sean O`Leary invest at?

The database lists Sean O`Leary for Pre-Seed, Seed and Series A 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 Sean O`Leary?

An email address and a LinkedIn page are on file for Sean O`Leary. The address stays masked on this page and is readable inside RaiseHunt after you create an account. The database holds 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 2 October 2026 · How this data is built · Report a correction or request removal