Running several projects at once is normal for a small operator. Running them from one account in one currency is where the trouble starts. The moment two activities with different clients and different currencies share a pool, both become harder to measure and each is exposed to the other's problems. The fix is structural, and it is easier to apply early.

Separate containers

The first move is to give each project its own business unit. SUPA SPC is a segregated portfolio company (Cayman Islands, CR-430549) under Part 14 of the Companies Act, in which each unit's assets answer only to its own liabilities, with no cross-recourse. Separate units mean separate obligations, so a dispute or a shortfall in one project does not reach into the others.

One workspace for all of them

Separation does not have to mean fragmentation. Each unit lives inside the same workspace, so you are not logging into a different system per project. Around ten currencies are supported, accounts, FX, payouts, cards and card acceptance sit behind one interface, and payouts run on local rails. You keep one place to work while keeping the projects apart.

  • A unit per project, each with its own balances and obligations.
  • One workspace across all units — not one login per project.
  • Around ten currencies, with reporting per unit.
  • Policy applied per unit, below any agent that executes.

Keeping the admin down

The administrative load in multi-project setups usually comes from duplication: the same documents, the same reviews, the same reconciliation, repeated per provider. A single perimeter checks each operation once — reliance confirmation, sanctions screening, agent mandate, client-profile fit and network anomaly signals — and produces signed, verifiable documents per unit. Rather than assembling records across vendors, you retrieve them.

One caveat worth stating: cross-border reliance is not permitted everywhere and local-law limits are checked per jurisdiction, so structure should be confirmed for your cases. Balances sit with licensed partners; SUPA is not yet a bank.

In short:

  • Give each project its own unit to separate obligations.
  • Keep all units in one workspace to avoid fragmentation.
  • Reporting and documents are produced per unit.
  • Confirm local-law limits for your jurisdictions.

Structure your projects in one place: business.