# Personal usage \[Patterns from solo builders running Splits as a team of one]

Splits works for teams of one. A solo builder gets the same setup as a company (accounts, banking, accounting), and it scales when collaborators (human or [agent](/introduction/agents)) join later. Patterns we see from solo builders:

## Isolated accounts

A dedicated [account](/accounts) per project, experiment, or revenue source. If the project flops, close the account; if it succeeds, it can become the start of a new team. Separate accounts per asset type (stables, investments, NFTs) also keep books clean while still exporting as [one CSV](/accounting).

## Multisigs of one

1-of-2 or 2-of-3 accounts where every [signer](/accounts/signers) belongs to the same person: a hardware key plus a password manager, or two devices in different locations. No single device, browser profile, or key is a point of failure.

## Multiple emails

Two members on one team, registered with different emails (e.g. Gmail and Proton), each with its own passkeys. Moving large amounts then requires access to both inboxes.

## No entity needed

Before incorporating, connect a personal bank account for [on/offramps](/banking) (KYC as an individual). Pay vendors, reimburse yourself, and keep a clean paper trail; when the project incorporates, swap in company banking. Verifying early also means less history to document later.

## Agents as collaborators

Delegate operations to AI tools via the [CLI, API, and MCP server](/introduction/agents): scoped API keys and optional headless signing let an agent work your treasury while you keep custody.