Jan Hichert

Investor profile

Jan Hichert

Angel, Operator angel

Berlin·Germany1known investment

An angel investor and operator angel based in Berlin, Germany, Jan Hichert has one known investment, Boxcryptor.

Is Jan Hichert a fit for your startup?

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

Investment focus

Contacts

jhi***@***.dePhone number on fileLinkedIn profile on fileAvailable after registration.
Get contact

Jan Hichert portfolio company (1)

  • Boxcryptor

Investor Profile

The known portfolio sits in sectors FinTech and SaaS, and focus areas Cybersecurity, Enterprise SaaS and Productivity.

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

The portfolio and focus above give founders context on whether Jan Hichert matches their raise.

Similar investors

Showing 20 of 99

Frequently asked questions

Who is Jan Hichert?

Jan Hichert is an angel investor and operator angel based in Berlin, Germany with one known investment on file, Boxcryptor. The sections above list the sectors and stages attached to that record.

What does Jan Hichert invest in?

Listed sectors include FinTech and SaaS; listed focus areas include Cybersecurity, Enterprise SaaS and Productivity. 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 Jan Hichert invest at?

The database lists Jan Hichert for 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 Jan Hichert?

An email address, a phone number and a LinkedIn page are on file for Jan Hichert. The address stays masked on this page and is readable inside RaiseHunt after you create an account.

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