Running Money for Friends Without Taking Their Money
The Fluxy Team
-Running Money for Friends Without Taking Their Money
There's a conversation almost every successful retail trader eventually has. A friend, a sibling, a colleague: "Can you just… do what you do, but with some of mine?" It's flattering, it's genuine, and the way most people act on it is quietly disastrous: the friend sends coins to the trader's exchange account, and now there's an informal pooled fund with no accounting, no agreement, and a custody arrangement that would horrify both parties if they wrote it down.
This post is the architecture for doing it without any of that. Not legal advice — a description of the operational structure that removes the worst risks by construction.
Rule one: their money stays theirs
The single decision that matters most: the friend's capital never leaves an account they own. They open their own exchange account, they hold the login, they create a trade-only API key — withdrawals disabled at the venue level — and that key is what connects their account to your strategies. You can trade their account; you cannot empty it. They can watch every fill on their own exchange app, and they can fire you in one minute by deleting the key.
Compare that to the coins-in-your-wallet default, where you have become an unlicensed custodian with total control of someone else's assets, and the best-case outcome is that nothing ever goes wrong. The non-custodial structure doesn't just reduce the risk — it deletes the category. It's the same model our managed accounts run on, for exactly this reason.
Rule two: accounting from day one, even for one person
The second killer of informal arrangements is arithmetic. The friend adds money mid-month. The book draws down, they add more, it recovers — what's their return? If you're marking a spreadsheet by memory, the honest answer is nobody knows, and "nobody knows" curdles friendships when money is involved.
The clean answer is unitized accounting: every deposit converts to units at that day's NAV-per-unit, every withdrawal redeems units at the current one, and each person's return is exactly their own regardless of when they joined. It's how real administrators account for real funds, and there is no participant count too small for it — one friend deserves the same arithmetic as fifty LPs. (If you charge fees at all, the high-water-mark worked example shows the calculation that avoids quietly overcharging them through a recovery.)
Rule three: statements they don't have to ask for
Trust decays in silence. The friend who has to ask how it's going starts wondering; the friend who gets a statement — balance, units, P&L, their cashflows, monthly — doesn't. The discipline of producing a statement also protects you: it forces the accounting to be reconcilable while the numbers are fresh, not reconstructed a year later during a disagreement.
Where the legal lines sit (in plain terms)
Somewhere between "managing your spouse's account" and "running a public fund" sits a line where regulators become interested, and it moves by jurisdiction. The rough shape: managing assets for others, for compensation, as a business, is regulated activity in most places; a small number of friends-and-family arrangements often fall under exemptions — but pooling money in your own accounts is treated far more harshly everywhere than advising on or trading accounts your clients own themselves. Which is one more argument for the non-custodial structure: it keeps you on the defensible side of the worst line while you do the real homework (the launch checklist maps it) with an actual lawyer if this grows into a business.
The upgrade path
The pleasant surprise of doing it right from the first friend: nothing has to be rebuilt at the tenth. Their accounts, trade-only keys, unitized NAV, statements — that's the same machinery a real managed-account business runs on, just with more rows. Start with the architecture that scales, and the dinner-table favor can become a track record instead of a cautionary tale.
Client-owned accounts, trade-only keys, unitized NAV, and statements — the friends-and-family stack, ready-made. See managed accounts →
Related reading