Megan Lawlor works as a Managing Partner at ML Capital. The firm's known portfolio counts 1 company.
Is Megan Lawlor a fit for your startup?
Paste your website. AI checks the fit and scores every other investor too.
Investment focus
- Stage
- Late-Stage
- Sector
- AI
Contacts
Affiliated funds' portfolios
Managing Partner at ML Capital, whose known portfolio counts 1 company
- Beagle
Investor Profile
The listing covers sector AI. Startups operating in that area may find Megan Lawlor relevant.
Megan Lawlor is listed for Late-Stage rounds in the database.
What the affiliated firm has backed is the closest available signal on whether Megan Lawlor is worth approaching.
Frequently asked questions
Who is Megan Lawlor?
Megan Lawlor is a family office investor based in Chicago, Illinois, United States, listed as Managing Partner at ML Capital. The known portfolio of that firm is one company. That portfolio belongs to the firm, not to Megan Lawlor personally.
What does Megan Lawlor invest in?
Listed sectors include AI. Those tags come from the portfolios of the firms this profile is attached to, so they read as a record of what has been backed rather than a stated preference for what comes next.
What stage does Megan Lawlor invest at?
ML Capital is listed for Late-Stage rounds in the database, and Megan Lawlor is listed there as Managing Partner. Stage is the strongest single filter when you build a target list: an investor with no record at your stage rarely starts with you.
Which firm is Megan Lawlor listed at?
Megan Lawlor is listed as Managing Partner at ML Capital, whose known portfolio is one company.
How do I contact Megan Lawlor?
A LinkedIn page is on file for Megan Lawlor. 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 5 September 2026 · How this data is built · Report a correction or request removal