A venture firm’s software stack is usually the product of real constraints. Relationships live in one system, founder updates in another, and official fund records with an administrator. Replacing those systems is not automatically progress.

Uranus begins with the work between those records: an unresolved question, a condition attached to an investment decision, or a founder-approved support request that still needs an owner. Its promise is to make that work explicit and preserve the evidence behind its resolution.

What the existing platforms already do well

Relationship CRMs capture history and organize pipelines. Portfolio platforms collect metrics and generate reporting. Fund systems maintain specialized records and administration. Several already offer AI extraction, citations, approval controls, agents, and MCP connections. We do not claim those individual features are exclusive to Uranus.

The question for a firm is whether one continuous evidence-to-work trail is useful across its chosen systems. That is a hypothesis to validate with a configured incumbent, including its available agents.

Four concrete product promises

  • Finish the follow-up: each internal work item has a named owner and date; a reviewed resolution requires a note and evidence.
  • Keep the reason: retain thesis, assumptions, dissent, conditions, source references, and prior record versions.
  • Keep the stack: bring authorized exports through mapping and validation, retain originals and identifiers, and export canonical records and history again.
  • Bound the agent: extraction and draft reasoning remain proposals, with source access checked before the run and before applying its output.

What is working in this release

The application supports companies, deals, relationships, explicit fund-planning inputs, documents, candidate observations, human review, work, outcomes, decision versions, and dated partner packets. OpenRouter powers bounded extraction, review questions, and IC drafts. A scoped MCP endpoint allows approved clients to read permitted evidence and propose internal work.

The import workbench accepts common structured files and documents. Thirteen provider guides explain documented export paths and scope. Attio and HubSpot additionally have owner-triggered company-read adapters, limited to one page of 100 records. No customer connection is described as verified until its own read succeeds. Other provider guides are not live connectors.

A small pilot with a real finish line

Choose one reporting cycle and a limited set of companies. Agree who can export the source material and who may read the target workspace. Compare the current complete cycle with the same cycle in Uranus: gathering inputs, correcting definitions, chasing answers, preparing partner review, and closing follow-ups.

Measure time, corrections, false alerts, outstanding questions, and whether the team wants to continue paying for the workflow. A 50 percent reduction is a proposed pilot target, not a measured customer result. Keep authoritative accounting and legal records with their original systems, and count observed outcomes separately from claimed attribution.

Permission and portability are part of the product

An agent may help export data only through an approved account, documented access route, and selected scope. It must not recover browser cookies, bypass export restrictions, or assume a team member’s board access authorizes redistribution. Imported sources begin private, and sharing a derived record does not bypass a private source.

An authorized file import produces a receipt, candidate metrics, and retained source references. It does not silently overwrite a reviewed fact. Exported canonical records include work and decision history; original files remain individually downloadable subject to current permission. That makes coexistence a reviewable workflow rather than a vague promise of universal integration.