A crypto staking platform brought users, investment activity, yield and cross-border money flows together. Keeping everything inside one company looked simpler. It also meant one problem could affect the entire business.
CHALLENGE
One problem could put the entire business at risk
THE WIN
A structure built to contain problems before they spread
Request a Review
Based on a real Ape Law matter. Client identities and certain details have been anonymized.
The difference
Same product. Two very different ways to carry the risk.
Without the review
Put users, the product and revenue inside one company
Allow investment and operating risks to sit together
Route every obligation and money flow through one entity
Let one problem affect the wider business
With the review
Map each risk before choosing the entities
Separate operating and investment activity
Give each entity a clear purpose
Design the product around safer risk boundaries
Client type
Matter type
Core issue
Too much risk in one entity
Main lesson
Separate risk before drafting
What founders see
“Keeping everything in one company is simpler.”
The users deal with one company. The product sits inside that company. The revenue flows through it. Everything stays together and the structure looks clean. But simplicity is not always safety. When customer funds, investment activity, yield, regulatory obligations and operational liability all sit in one place, the risk becomes concentrated too.
The hidden risk
One problem in one part of the business could affect everything else.
Customer funds
Investment activity
Yield
Regulation
Operations
This business was not carrying one type of risk. It was carrying several. The same structure had to deal with users, investment activity, yield distribution, regulatory obligations and day-to-day operating liability. If all of those risks sat inside one company, there was no clear boundary between them. An operational problem could reach the investment side of the business. A regulatory issue could affect the wider product. A problem with money flows could create consequences across the whole structure. The real question was not how many companies to create. It was which risks should sit together and which needed to be separated.
The method
Strategic Structure Review: map the risk, then design the entities
We started by mapping the users, activities, obligations and money flows. Once the risks were clear, the right entity structure became much easier to see.
Risk map
Where did the customer, investment, regulatory and operational risks sit?
Entity roles
What should stay together, and what needed to be separated?
Money flows
How would capital, revenue and yield move through the structure?
Product design
How could the product work within clearer risk boundaries?
The founder lesson
Do not build one company that carries every risk.
Full lesson notes
The full breakdown
We worked with a crypto staking platform that involved users, investment activity, yield distribution and cross-border money flows. The simple option was to place everything inside one company. The users would interact with that company. The product would sit inside it. Revenue would flow through it. The same entity would also carry the investment, regulatory and operational obligations. On paper, that looked clean. In practice, it concentrated several different risks in one place.
Simplicity can concentrate risk
This business was not exposed to one type of problem. It had customer-related risk, investment activity, yield distribution, regulatory obligations, money movements and day-to-day operational liability. If every part of the business sat inside one company, one issue could spread much further than it needed to. A problem affecting the operating business could reach the investment activity. A regulatory concern could affect the wider product. An issue involving funds or yield could create consequences for everything else the company was doing. Keeping the structure simple did not remove the risk. It placed more of the risk in the same place.
Why we started with the risk
We did not begin by preparing documents or incorporating entities. We started by mapping how the business actually worked. Who interacted with the users? Where did the investment activity take place? Which entity received revenue? How did funds move? Where was yield calculated and distributed? Which parts of the business created the greatest exposure? Those questions helped us understand which activities belonged together and which needed a clear boundary between them. Once the risk map was clear, the entity structure became much easier to design.
Designing the structure around the business
The final structure separated the major areas of risk. The operating business did not carry every obligation. The investment activity sat where it made commercial and legal sense. The movement of funds was carefully mapped. Each entity had a clearer role. The product was then designed around that structure. This was important. Trying to force a legal structure around an already finished product often creates gaps, awkward money flows and responsibilities that sit in the wrong place. Here, the structure and product were designed to work together. The objective was not to create more companies for the sake of it. It was to stop every risk from landing in the same company.
The takeaway
Putting everything inside one company can feel simpler. It can also mean that one problem reaches the whole business. A good structure creates boundaries. It helps separate different activities, obligations and exposures before something goes wrong. The lesson is simple. Do not build one company that carries every risk.
Where this shows up
Related services
Carrying too much risk?
Build the structure before one problem reaches everything.
If your product combines users, investment activity, yield or cross-border money flows, a Strategic Structure Review can help map the risk and decide what should stay together and what should be separated.
Request a Review
Confidential · Founder focused legal team · No obligation past the first call
