Capital Company

Opens a Capital Company workspace for someone who has none: their account and their firm’s team. Needs no sign-in. They then sign in from the link the login page emails them, and connect this assistant to have it set things up.

Starts creating a fund for the user: an SPV or a blind pool, with its legal name, expected allocation, strategy, classes and fees, manager and documents. Capital Company’s assistant asks for what is missing and, when it has everything, puts the fund to the user for confirmation before anything is created.

For internal Capital Company admins: starts or resumes the published document workflows for a migration case after confirmation. Processing continues in the background. It does not create fund records or send invitations.

For internal Capital Company admins: retries or cancels one current migration document job after confirmation. It uses the existing workflow controls and does not change fund records or send invitations.

For internal Capital Company admins: opens or starts a read-only statement preview from the migration case’s eligible evidence after confirmation. The published workflow runs in the background. It does not change fund records or send invitations.

Starts inviting investors to one of the user’s funds by email address. The assistant resolves the fund, asks for what is missing, and puts the invitations to the user for confirmation before any is sent.

Starts sending subscription agreements for signature to investors of one of the user’s funds. The assistant resolves the fund and the commitments and puts the requests to the user for confirmation before any is sent.

Starts sending capital call notices to the investors of a fund class. The assistant resolves the class and its commitments and puts the notices to the user for confirmation before any is sent. It never moves money.

Starts changing settings of one of the user’s funds: the fields they name, nothing else. The assistant puts the change to the user for confirmation before anything is written.

Starts editing an existing commitment in one of the user’s funds: the fields they name. The assistant puts the edit, and anything it changes about sent capital calls, to the user for confirmation before anything is written.

Starts recording a new commitment by an investor in one of the user’s funds. The assistant resolves the fund and the investor, asks for what is missing, and puts the commitment to the user for confirmation before anything is written.

Answers a question about the user’s team and funds in Capital Company from its records, in Capital Company’s words. Changes nothing.

Relays the user’s answer to the question Capital Company’s assistant asked last, in their own words, and returns what the assistant says next: another question, or a proposal for the user to confirm.

Relays the user’s own answer, confirm or decline, to a Confirmation Capital Company’s assistant put to them. Confirming runs the operation; declining lets the assistant ask what to change.

Shows the user a Confirmation named in Capital Company’s reply on Capital Company’s card, where they confirm or decline it themselves. Changes nothing.

For someone who started without a Capital Company account and said yes to a proposal: emails a link to the address they will sign in with. Opening it verifies the address and creates what they said yes to.

Reads the user’s current conversation with Capital Company’s assistant, including the outcome of anything they confirmed, and whether it is waiting on them.