What is a capital formation OS?

A capital formation OS is a single operating system for the whole job of raising money on behalf of clients: knowing who to pitch, what to fix in the story, and when to reach out. It exists because fundraising advisors have been running that job across a CRM built for sales teams, a data subscription built for VCs, a deck tool, a spreadsheet, and an inbox, with none of them talking to each other.

Lunra's version is built on one asset and three engines.

The asset: a verified investor graph

Everything sits on a graph of 39,000+ investor profiles with 22,000+ verified emails, built from an SEC Form D filing spine and layered enrichment. Every profile carries evidence for how we know what we claim: a Verified badge (email and identity confirmed), Contact on file, or SEC-filed. See where the investor data comes from for the full provenance story.

Engine 1: Match answers "who"

Match scores every profile on the graph against a specific deal: thesis fit, stage, check size, capital freshness, and reachability. The output is a tiered shortlist, not a 5,000-row export. Tier A means on-thesis, fresh capital, right check size, and a way to actually reach them.

Engine 2: Deal Read answers "what"

Deal Read evaluates a client's deck the way an investor would: objections ordered by severity, each with a reframe, plus a raise-readiness band and a deck score that climbs measurably from version to version. The deliverable ships under your name, which is the point: it is the premium work product that justifies your mandate.

Engine 3: Signal answers "when"

Investor Signal follows the investors on your raise across X and fresh filings, hourly, and flags the moment one of them touches your deal's world. Timing stops being luck.

Why one system beats five tools

The three answers compound only when they share state. The shortlist knows what the deck fixed. The outreach knows who was matched and why. The timing layer knows who you are courting this week. That shared state is what makes it an operating system rather than a stack of tools, and it is why the pipeline runs on opinionated 15-stage playbooks instead of a generic kanban.

If you are new, start with creating your first raise, then read how advisors run a raise stage by stage.