How three founders built a venture capital OS on Nylas

Impact at a Glance

• Cross-provider email threading, meeting bots, and scheduling handled by a single integration, so a three-person team stays focused on the vertical product.
• Notetaker wired straight into the calendar via Nylas webhooks and the Scheduler integration, so meetings booked through Lighthouse get recorded automatically.
• An all-in-one platform for venture capital investors, built by three founders without a Series A round.

About Lighthouse

Lighthouse is an AI-native CRM and deal-sourcing platform built for venture capital investors, and increasingly, for the AI agents working alongside them. It unifies sourcing, startup intelligence, relationship mapping, and diligence into one system, so a fund’s data compounds instead of scattering across a dozen disconnected tools.

“We’re basically an all-in-one platform for venture capital investors,” says co-founder Alberto Marzetta. “Everything that is productivity. So here you have the CRM, all your conversations, all your LinkedIn chats, all your meetings, all your files, everything in one place. Plus all these productivity tools.”

We’re basically an all-in-one platform for venture capital investors. Everything that is productivity. So here you have the CRM, all your conversations, all your LinkedIn chats, all your meetings, all your files, everything in one place. Plus all these productivity tools.

Alberto Marzetta

Co-Founder

The pitch is consolidation. Instead of one tool to source, another to send email, a CRM, a separate workflow engine, and yet another product for LinkedIn campaigns, Lighthouse folds the whole stack into a single vertical product. As Alberto puts it: “It’s very vertical for venture capital investment, because you can do everything.”

The bet: you don’t need the round anymore

The category Lighthouse operates in used to require serious capital and a real engineering org. It doesn’t anymore.

The economics used to rule this out. “Ten years ago, no one would have invested in this, because the market is too niche,” Alberto says. “No one is going to give you five, six million. But now you just need a coding agent, and if you have the right testing environment, you can do it.”

That’s the thesis in one line: the tooling that used to demand a large seed round and a team of ten or twenty engineers now fits inside three founders and a coding agent. Lighthouse builds against APIs by handing its coding agent documentation directly. “Copy as markdown and just go.” When a client asks for a feature, the turnaround is measured in days, not quarters. A workspace-wide migration that used to be a project becomes ‘tomorrow.’

Part of that comes down to the testing setup itself. Nylas lets Lighthouse spin up entirely separate applications per environment, so staging is a total, ground-up mirror of production: its own connectors, its own webhooks, its own test grants, completely walled off from anything live. New Notetaker or Scheduler behavior gets validated end-to-end in staging first, real webhook events, real calendar syncing, real booking flows, before anything touches a live client account or investor’s calendar. For a platform sitting on top of active fundraising conversations, that clean split between test and production is what lets the Lighthouse team move as fast as it does.

Building lean only works if you don’t have to build everything yourself. Communications infrastructure, email threading, calendar-aware meeting bots, scheduling are exactly the kind of deep, unglamorous work that eats a small team alive.

The problem: the plumbing you can’t afford to build

Lighthouse lives on communication data. The CRM only earns its keep if every conversation lands in the right place automatically, whether it’s email, meeting, or LinkedIn thread. That means the platform needs email that threads correctly, meetings that get recorded and summarized, and scheduling that just works. Building any one of these reliably is weeks of work with sharp edges. Building all of them, as a small team, wasn’t realistic.

Take email threading. Every provider handles it a little differently. “Outlook doesn’t group by conversation,” Alberto says. “Nylas does it.” Nylas’s connectors normalize those quirks into one standard format off the shelf, so a reliable conversation ID comes through the same whether the account is Google, Microsoft, IMAP, or Yahoo, the difference between a usable CRM inbox and a mess.

What they built

Lighthouse uses Nylas as its communications layer. Nylas covers email, meetings, and scheduling; the rest, Lighthouse builds itself.

On email, Lighthouse built its own email client on top of the Nylas Email API, leaning on normalized conversation threading, so an investor sees clean, grouped conversations regardless of whether the underlying account is Google, Microsoft, IMAP, or Yahoo.

On meetings, Lighthouse shipped Notetaker to its clients. The Notetaker API is calendar-aware: one call attaches a bot to an event, and Nylas keeps it in sync as the event’s time or link changes. “We already shipped it, and our clients are using it,” Alberto says. Lighthouse also implemented the Scheduler integration for Notetaker, so meetings booked through Lighthouse get recorded automatically.

Lighthouse didn’t stop at the Scheduler integration. It built its own custom booking page on the Nylas Scheduler API, and used Nylas webhooks to drive the booking emails. The result is a fully white-labeled booking experience investors get inside Lighthouse: branded pages, branded confirmation and reminder emails, no Nylas branding anywhere in the flow. A fund runs its scheduling from the platform instead of bolting on a separate booking tool. The API powers the pages; the webhooks power the emails (see it live). It’s the pattern the whole product runs on: Nylas handles the hard mechanics, Lighthouse owns the entire experience on top.

Why Nylas

Lighthouse’s differentiator is the vertical product, the sourcing, the CRM, and the workflows built specifically for how VCs operate. It is not email plumbing or meeting bots. Nylas lets the team stay on the part that’s theirs.

Four things kept Nylas at the center of the stack. First, breadth: email with cross-provider threading, Notetaker, and Scheduler behind a single integration, so Lighthouse didn’t have to stitch together separate vendors for each. Second, depth on the hard parts, calendar-aware bot joining, conversation IDs, and the edge cases that are expensive to get right in-house. Third, the commercial model. Notetaker is pay-as-you-go, which for a young company scaling into larger contracts is a real advantage. Fourth, environment isolation: separate Nylas apps per environment lets you test against production-grade infrastructure without touching the production environment.

The workflow also suits how Lighthouse builds. Nylas docs pull straight into a coding agent as markdown, so adding or migrating a feature is mostly a matter of pointing the agent at the reference and letting it work.

What’s next

Lighthouse is closing larger contracts, and Agent Accounts are next on the roadmap, giving each fund’s AI agents their own identity inside the platform.

The throughline is the same one the whole company is built on: solve the hard communications problems once, on someone else’s infrastructure, so three founders and a coding agent can build the product a fund actually wants.