The Founder's Guide to Not Getting Screwed by Your Own Structure

I was sitting in a conference room in Nairobi when a founder slid a stack of documents across the table. Three companies. Two jurisdictions. One operating entity in Kenya, one holding company in Delaware, and a mysterious third entity in the British Virgin Islands that his previous lawyer had insisted on "for tax efficiency."

The founder had no idea why the BVI company existed. He was paying $4,000 a year to maintain it. It had never held an asset, never received revenue, and never served any structural purpose whatsoever. But it was costing him real money and creating real compliance obligations in a jurisdiction he'd never visited.

"My lawyer said I'd need it eventually," he told me.

Eventually never came. What came instead was a $12,000 bill for three years of unnecessary registered agent fees, annual filings, and compliance work for an entity that did absolutely nothing.

This is what happens when founders let lawyers design their corporate structure without understanding why each piece exists. And it happens far more often than you'd think.

The Delaware myth

Let me be clear about something. Delaware is a brilliant jurisdiction for incorporating companies. The Court of Chancery is exceptional. The corporate law is flexible, well-developed, and predictable. There's a reason the majority of US-listed companies are incorporated there.

But Delaware is not a magic spell. And for many founders — especially those building companies in Africa, Latin America, or Southeast Asia — incorporating in Delaware as your primary entity is often the wrong move.

I worked with an edtech founder in Bogota who incorporated in Delaware because a Y Combinator blog post told him to. His entire team was in Colombia. His customers were in Colombia. His revenue was in Colombian pesos. But his company was a Delaware C-Corp. Which meant he needed a Colombian subsidiary to actually operate. Which meant transfer pricing documentation between the two entities. Which meant US tax filings for a company that had zero US revenue. Which meant double the legal and accounting fees, every single year.

When he came to me, he was spending nearly $15,000 a year on compliance for a structure designed to attract Silicon Valley investors he'd never actually pitched.

Delaware makes sense when you're raising from US investors. When your path leads to a US listing or US-based acquisition. When the majority of your investor base expects Delaware governance. For everyone else, it's often an expensive detour.

When you actually need a holding company

The holding company question is where things get interesting. And where I see the most confusion.

A holding company is a separate legal entity that sits above your operating company and owns shares in it. Sometimes it owns shares in multiple operating companies across different countries. It's the structural layer that separates ownership from operations.

You need a holding company when you're operating in multiple jurisdictions and want a single point of ownership. When you're bringing in investors who need a familiar legal framework. When you need to manage intellectual property across borders. When tax treaties between jurisdictions make a specific holding structure advantageous.

You don't need a holding company when you're a single-country operation with local founders and local investors. When you're pre-revenue and still figuring out product-market fit. When someone tells you that you need one but can't explain specifically why.

I structured a school network that operates across Kenya, with a Delaware parent for US investors and a Kenyan subsidiary for operations. That structure made sense because the investor base was primarily American, the IP needed to be held separately, and the capital flows required a clean pathway between jurisdictions. Each entity had a clear purpose.

Contrast that with a solo founder in Lagos who was told to set up a Mauritius holding company for his pre-revenue marketplace. Mauritius. For a company with no international investors, no cross-border IP, and no revenue. The holding company cost him $6,000 to establish and $3,000 a year to maintain. It served no purpose other than making a lawyer's fee quote look sophisticated.

The "I'll fix it later" trap

This is the one that hurts the most because by the time founders feel the pain, the damage is already done.

The pattern is always the same. Founder starts a company. Incorporates quickly and cheaply. Maybe uses an online service. Maybe uses a friend who's a lawyer but doesn't specialise in corporate structuring. The company grows. Revenue comes in. Investors show interest. And suddenly the structure that was "good enough for now" becomes a serious liability.

I worked with a fintech in Rwanda that needed to restructure before its Series A. The company had been incorporated as a local entity with a share structure that couldn't accommodate the preference shares the lead investor required. Restructuring meant creating a new holding company, transferring assets and contracts, getting consent from existing shareholders, dealing with tax implications of the transfer, and re-negotiating employment agreements that were tied to the original entity.

Total cost: $85,000 and four months. The round almost fell apart twice during the process.

Had they set up the right structure from the beginning? Maybe $8,000 and two weeks.

The most expensive corporate structure is the one you have to rebuild while investors are waiting.

I'm not saying every pre-seed company needs a multi-jurisdiction holding structure. That would be absurd. What I am saying is that every founder needs to think — for thirty minutes, with someone who does this for a living — about where the company is headed and what structure will support that trajectory. Not what's cheapest today. What won't need to be torn down tomorrow.

Venture architect vs lawyer

This distinction matters and most founders don't know it exists.

A lawyer will incorporate your company. They'll draft your articles of association. They'll file the paperwork. Good lawyers will ask you thoughtful questions about your plans and tailor the documents accordingly.

A venture architect thinks about the structure as a system. Where does IP sit? How does capital flow between entities? What happens at Series A, Series B, exit? What are the tax implications of different holding structures? How do you set up the corporate architecture so that adding a new country is an operational decision, not a structural rebuild?

The difference matters most when you're building something cross-border. I've seen too many companies where a lawyer in Country A set up Entity A, a lawyer in Country B set up Entity B, and nobody thought about how the two entities relate to each other, how profits flow between them, or what happens when you need to add Country C.

I worked with a logistics company operating in three East African countries. Each country had its own entity, set up by a local lawyer, with no coordination between them. The Kenyan entity owned the IP. The Ugandan entity had the best revenue. The Tanzanian entity held the key government contracts. No holding company connected them. No intercompany agreements governed the relationships. When an acquirer came looking, they had to value and diligence three completely independent companies that happened to share a brand name. It took eight months. A coordinated structure from the start would have made that a two-month process.

The questions you should be asking

Before you incorporate anything, sit down with someone who understands multi-jurisdiction structuring and work through these questions:

Where is your revenue? Incorporate where your money is. Not where a blog post told you to.

Where are your investors? If they need Delaware governance, give them Delaware governance. If they're local, keep it local.

Where is your IP? Intellectual property should sit in the entity that makes the most sense from a tax and protection standpoint. This isn't always obvious.

What does your structure look like at Series A? Not today. In 18 months. If the answer is "completely different from what we have now," you're building on sand.

What's the annual cost of compliance? Every entity you create has a carrying cost. Registered agents, annual filings, audits, tax returns. Add it up. If you can't justify the cost, you don't need the entity.

Corporate structure isn't the exciting part of building a company. I know that. But it's the part that determines whether your exciting ideas can actually scale, raise money, and exit cleanly. I've seen too many brilliant companies trapped inside structures that their own founders built. Don't be one of them.