Holding Company Structure for Bootstrapped Founders: Why I Skipped the Delaware C-Corp

holding-company bootstrapping llc taxes startups
Holding company structure for a bootstrapped founder, one holdco above separate operating LLCs

Every guide to holding companies is written for someone who isn't you. They open with Johnson & Johnson, walk through a hypothetical $10M raise, and end by telling you to hire a lawyer. If you're one person running a couple of small products that actually make money, none of that maps to your life.

So here's the version I wish I'd had when I started stacking projects under one roof: what a holding company is, why a bootstrapper would bother, and how I'd set one up without paying for machinery built for companies chasing venture money.

What a holding company actually is

Strip away the theater and it's simple. A holding company owns things. It doesn't sell anything, doesn't have customers, doesn't run day-to-day operations. It just holds: ownership of your other companies, plus assets worth protecting like intellectual property, domains, or equipment.

The operating work happens one level down, inside separate LLCs that each do one thing. The holdco sits on top and owns them.

That separation is the whole point. When a project lives in its own entity, a problem inside that project stays inside that project.

Why a bootstrapper would bother

Big companies use holdcos for tax games and succession planning. Those aren't your reasons. Yours are smaller and more practical.

You're running more than one thing. The moment you have two projects that both touch money, you want them in separate boxes. If one gets sued, hit with a chargeback storm, or racks up a debt it can't cover, the other one shouldn't go down with it.

You might sell one someday. Selling a product that's tangled up with three of your other projects is a mess. Selling a clean, self-contained LLC is a transaction. Structure buys you a clean exit before you need one.

Your IP and domains are worth protecting. Park the valuable, hard-to-replace stuff (brand, trademarks, the domain portfolio) up in the holdco, away from the operating entity that's out in the world taking risks.

If you're running exactly one project and have no plans for a second, you probably don't need any of this yet. A single LLC is fine. Come back when you start a second thing.

The structure I'd actually use

The corporate examples love to silo everything: a separate LLC for real estate, one for equipment, one for IP, one for employees. That's real, and it's also wildly overbuilt for someone doing five figures a month.

Keep it boring when you're small:

That's it. One holdco, one LLC per real revenue stream. You add silos when a specific project gets big or risky enough to earn its own. A project holding physical property or signing serious contracts might deserve the extra separation. Until then, more entities just means more bank accounts, more filings, and more ways to forget something.

The unsexy part matters more than the diagram: each entity needs its own bank account, its own records, and real agreements between them when they interact. Money moving between your companies has to look like it's moving between actual companies. Blur that line and a court can blur it too, which collapses the liability protection you set all this up for in the first place.

Where to form it: Wyoming over Delaware, if you're not raising

Every startup guide points you at a Delaware C-corp. That advice was written for companies raising venture capital, and it quietly assumes you're one of them.

A Delaware C-corp earns its cost when you're raising. Investors know the case law, they want preferred stock, and you get access to things like QSBS treatment on an eventual equity sale. You pay the franchise tax and swallow the double taxation (the company pays corporate tax, then you pay again on whatever you take out) because the fundraising upside covers it. Skip the fundraise, and you're paying the bill for a party you're not attending.

For a bootstrapped holdco, I'd form a Wyoming LLC. Why:

Then, once a project clears roughly $40k to $50k in net profit, that LLC can elect S-corp taxation. That lets you split your take into a reasonable salary (which pays payroll tax) and distributions (which don't), shaving the roughly 15.3% self-employment tax off the distribution portion. Worth knowing: this is a federal election that sits on top of the LLC. It has nothing to do with the state you formed in; a Wyoming LLC can be taxed as an S-corp.

Two catches I won't skip, because the Wyoming-hype posts always do.

Forming in Wyoming doesn't move your taxes out of the state you live and work in. If you're operating out of California, California still taxes you and makes you register there as a foreign LLC, with its own $800/year minimum. Wyoming's benefits are real for location-independent founders and for pure holding entities that just sit on assets. They're mostly a mirage if you've got a physical presence in a high-tax state.

The S-corp election has strings. Every owner has to be a US person, and it only pays off once profit is high enough to cover the payroll admin. Below that threshold, don't bother.

I'm not your accountant, and your situation has details this post can't see. Confirm the specifics with one before you file. But that's the shape of it.

Taxes, without the jargon

Two things carry most of the weight for a bootstrapper.

Pass-through is the default, and it's good. With LLCs, profit and loss flow straight to your personal return. There's no separate corporate tax sitting in front of it. That alone dodges the double-taxation problem that makes C-corps painful for anyone not raising.

The S-corp election is your main lever. Above that $40k to $50k profit line, the salary-plus-distributions split is the single biggest legal tax saving most solo founders have available. Below it, the payroll overhead eats the benefit, so leave it alone.

Everything beyond those two (dividend received deductions, income shifting between entities, the deep holdco tax strategies) is real, but it's aimed at operations far larger than a bootstrapped portfolio. Reaching for it early just buys you complexity and an IRS-shaped headache.

What to skip while you're small

The complexity gets sold to you because complexity is billable. Here's what you can leave on the shelf until you've genuinely outgrown simple:

Structure should track your actual risk and revenue. Build the next piece when a project earns it, not before. And if part of what you're holding is software you built to replace your own subscriptions, that IP belongs up in the holdco too; I make that argument in Stop renting your tools.

FAQ

Do I need a holding company for one project?

No. One LLC covers you. The holdco starts making sense at your second revenue-generating project, or when you've got IP worth walling off from an operating business.

Wyoming or Delaware for a bootstrapper?

Wyoming, if you're not raising: lower cost, no state income tax, better privacy, and pass-through by default. Delaware is for the fundraising path.

Can I put my domains in the holding company?

Yes, and it's one of the better reasons to have one. The holdco owns the brand and domains; the operating LLCs license or use them. If an operating entity ever goes down, the valuable stuff sits safely one level up.

When does the S-corp election actually save money?

Roughly north of $40k to $50k in net profit, and only if every owner is a US person. Under that, the payroll and filing overhead cancels out the savings.

Recommended

Stop renting your tools: the case for replacing the software you pay for with software you own @jameslcowan product-engineering, ai
What is the difference between product engineering and \"just development\"? @jameslcowan product-engineering, startups
Anthropic Trained Its Replacement @jameslcowan anthropic, ai

Recommended

Stop renting your tools: the case for replacing the software you pay for with software you own @jameslcowan product-engineering, ai
What is the difference between product engineering and \"just development\"? @jameslcowan product-engineering, startups
Anthropic Trained Its Replacement @jameslcowan anthropic, ai

Search by title, tag, description, or the prose itself. Results appear as you type.