Tej Pandey is an operator angel based in Bengaluru, Karnataka, India. The known portfolio is one company, Kommunicate.
Is Tej Pandey a fit for your startup?
Paste your website. AI checks the fit and scores every other investor too.
Investment focus
- Stage
- Pre-Seed
- Focus
- Conversational AICustomer Support PlatformsEnterprise SaaSMessaging InfrastructureReal-Time SystemsSMB SaaS
Contacts
Tej Pandey portfolio company (1)
- Kommunicate
Investor Profile
Founders in the listed sectors AI and SaaS, and focus areas Conversational AI, Customer Support Platforms, Enterprise SaaS and Messaging Infrastructure will recognize the pattern in this portfolio.
The stage tag on this profile is Pre-Seed.
The portfolio and focus above give founders context on whether Tej Pandey matches their raise.
Similar investors
Showing 20 of 100
Frequently asked questions
Who is Tej Pandey?
Tej Pandey is an operator angel based in Bengaluru, Karnataka, India with one known investment on file, Kommunicate. The sections above list the sectors and stages attached to that record.
What does Tej Pandey invest in?
Listed sectors include AI and SaaS; listed focus areas include Conversational AI, Customer Support Platforms, Enterprise SaaS and Messaging Infrastructure. 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 Tej Pandey invest at?
The database lists Tej Pandey 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 Tej Pandey?
An email address, a phone number and a LinkedIn page are on file for Tej Pandey. 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