AS

Investor profile

Alex Sacerdote

Angel

Alex Sacerdote is an angel investor based in Boston, Massachusetts, United States. The known portfolio is one company, Tomo.

Is Alex Sacerdote a fit for your startup?

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

Investment focus

Sector
Consumer

Contacts

LinkedIn profile on fileAvailable after registration.
Get contact

Alex Sacerdote portfolio company (1)

  • Tomo

Investor Profile

The listing covers sector Consumer, and focus areas Entertainment, Media, Messaging and Social Media. Startups operating in these areas may find Alex Sacerdote relevant.

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

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

Similar investors

Showing 19 of 96

Frequently asked questions

Who is Alex Sacerdote?

Alex Sacerdote is an angel investor based in Boston, Massachusetts, United States with one known investment on file, Tomo. The sections above list the sectors and stages attached to that record.

What does Alex Sacerdote invest in?

Listed sectors include Consumer; listed focus areas include Entertainment, Media, Messaging and Social Media. 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 Alex Sacerdote invest at?

The database lists Alex Sacerdote for 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 Alex Sacerdote?

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