Use Cases
Portfolio managers
Venture studio, fund admin, accelerator, or family office running ten to a hundred companies for other people. Cohort formation, one compliance rollup, fleet filings, scoped delegation.
Last updated
An operator of many companies for other people — a venture studio incubating a cohort, a fund admin running back-office for forty portfolio companies, an accelerator batch-forming a class, a family office holding a dozen vehicles. The founder personas measure one entity's lifecycle; this persona measures the fleet. The whole surface is built around the Portfolio resource: batch formation into it, one compliance rollup across it, fleet filings over it, and scoped keys delegated against it.
Create
Bring the entity into existence — formation, founder equity, EIN, registered agent.
Create at fleet scale means creating the container first, then the cohort inside it. One portfolio per fund, batch, or client engagement; up to 25 entities per batch call, each one an independent formation that reports its own success or failure.
POST /v1/portfoliosOne management context per fund or cohort. Set shared_registered_agent_id so every member defaults to one RA contract, and shared_compliance_calendar so every member's deadlines land on one timeline. metadata carries your own keys — fund number, vintage, client reference.
POST /v1/portfolios/{id}/entities/batchUp to 25 formations in one call, each an independent Intent with its own filings and events. Partial successes report per-item — a failed sibling never rolls back the batch. Membership lands together; the per-entity work proceeds in parallel.
POST /v1/portfolios/{id}/entitiesMigrating a back-book? Attach existing entities one at a time — idempotent, with move semantics: an entity belongs to at most one portfolio, and attaching from elsewhere moves it. The entity itself is untouched; membership is organizational, never legal.
Manage
Operate the live entity — equity programs, board cadence, compliance, qualifications.
The operating cadence is read-one-rollup, file-everything-due, delegate-narrowly. Per-entity reads still exist underneath — GET /v1/portfolios/{id}/entities pages through full member envelopes — but the morning starts with the rollup, not forty open tabs.
GET /v1/portfolios/{id}/complianceOne read returns per-entity obligation counts, portfolio-wide totals, and a critical_actions triage queue — every overdue obligation first, then the soonest due-soon items. Computed on read, never stale.
POST /v1/workflows/file_all_dueThe compliance sweep — franchise tax, annual reports, BOI updates due in the window. Pass portfolio_id and it sweeps every member of the cohort in one call; pass entity_id for a single company, or neither for the whole account. within_days widens the due window forward.
POST /v1/tokensMint a token bound to one portfolio. The holder operates that portfolio's members end-to-end; operations outside the delegation return 403 portfolio_scope_denied, and resources in sibling portfolios are invisible — 404, indistinguishable from ids that never existed.
Exit
Wind the entity down — dissolution cascade or M&A envelope.
Fleet operators wind down companies routinely — one failed bet should not disturb the other eleven. Detach first so the rollup and the shared calendar stop counting it, then run the standard dissolution cascade on the member.
DELETE /v1/portfolios/{id}/entities/{entity_id}Clears the entity's portfolio_id and returns the updated portfolio. Idempotent; detaching never dissolves, archives, or otherwise mutates the member — it only removes it from the rollup and the shared calendar.
POST /v1/entities/{id}/dissolveForm 966, final franchise tax, Certificate of Dissolution, BOI closure — the same cascade every founder persona uses, run against one member while the rest of the fleet keeps operating.