Live entity-stack desk for HoldCo + OpCo admin costs, with a benefit-vs-burden companion and setup-payback strip.
Educational planning sketch only. Not legal, tax, entity-formation, or investment advice. Confirm structure decisions with qualified professionals.
By Ahmet C. Toplutaş·Site owner & editor · Business tools
Last updated May 21, 2026 · Reviewed May 21, 2026 · Planning estimates only - not tax, medical, or investment advice
01
A holding company owns controlling interests in operating subsidiaries. This board treats the structure as an entity stack: one HoldCo plus your OpCo count, with an annual admin run-rate on every layer.
This page's framing is an entity-stack desk, with an admin cost peel, a benefit-vs-burden companion, and a setup-payback strip. It is not gross-margin markup literacy, not a sales-tax receipt, not a twelve-month cash-flow forecast, and not CAC or break-even volume heroes.
Decision framing: “If I add a HoldCo layer, does illustrative benefit clear the extra admin, and how long does setup take to earn back?”
Educational planning sketch only. Not legal advice, tax advice, entity-formation counsel, securities advice, or investment advice. Liability ring-fencing and tax outcomes depend on jurisdiction, capitalization, and formalities. Confirm with qualified professionals. See our disclaimers.
02
Annual admin multiplies (filing + insurance/compliance) by entity count. Entity count = OpCos + HoldCo, so the parent is never free in this sketch. One-time setup sits beside the peel and feeds the payback strip, not the annual run-rate.
Tip: load Admin-heavy. Watch five OpCos plus HoldCo push admin above a thin benefit sketch.
Real filings, registered-agent fees, bookkeeping, and insurance vary widely. Treat your inputs as placeholders until counsel and accountants quote local costs.
03
The companion subtracts annual admin from an illustrative annual benefit you enter. That benefit is your planning assumption for cash timing, centralization, or other expected value. It is not a deferred-tax engine and not proof of savings.
Admin share of benefit shows how much of the sketch benefit is eaten by stack overhead. A high share is a signal to simplify entities or revisit the benefit assumption, not a green light to skip counsel.
04
When net annual run-rate is positive, setup payback years = setup ÷ net run-rate. When admin exceeds benefit, payback does not close here. Compare that horizon to how long you expect the multi-entity structure to stay in place.
This is structure-cost literacy, parallel in spirit to CAC payback but aimed at entity overhead, not customer acquisition.
05
Stack size, admin, net run-rate, and payback.
Example: 3 OpCos → 4 entities; $400 filing + $600 insurance → $4,000 admin. Benefit $7,500 → net $3,500. Setup $2,500 → payback ≈ 0.7 years.
06
Sibling boards when the job is cash timing, margins, or unit economics.
07
Scenario A: 3 OpCos. Lean per-entity fees and a $7,500 benefit sketch leave a positive net and sub-year setup payback in the demo numbers.
Load Solo split: one OpCo still pays for two entities (OpCo + HoldCo). Check whether the benefit sketch clears that floor.
Scenario B: Admin-heavy. Five OpCos with richer compliance costs can make admin larger than benefit. The board flags admin-heavy instead of inventing savings.
Scenario C: Asset ring. A stronger illustrative benefit with two OpCos shows how payback shortens when overhead stays modest. Still not proof of veil protection.
Scenario D: Need monthly cash. Hand off to cash flow projection for operating month-by-month timing inside OpCos.
08
09
10
Stop here for a multi-entity admin vs illustrative-benefit sketch. Hand off for operating cash timing, margin definitions, or acquisition payback. Always hand off to legal and tax professionals before forming entities.
11
It sketches a HoldCo + OpCo entity stack, peels annual filing and insurance into an admin run-rate, compares that burden to an illustrative annual benefit you enter, and shows setup payback years when net run-rate is positive.
Entity count = subsidiaries (OpCos) + 1 HoldCo. Annual admin multiplies filing + insurance by that full stack so the parent company is not free in the sketch.
A user-entered planning number for cash timing, centralization, or other benefits you believe the structure might create. It is not a tax engine, deferred-tax schedule, or jurisdiction model.
One-time setup cost ÷ net annual run-rate (benefit − admin), when net is positive. If admin exceeds benefit, payback is not applicable in this sketch.
No. Ring-fencing and tax outcomes depend on jurisdiction, capitalization, formalities, and counsel. Veil-piercing risks rise with commingling and thin documentation.
No. It is an educational structure-cost sketch only. Not legal, tax, entity-formation, or investment advice. Confirm with qualified professionals in your jurisdiction. See our disclaimers.
LIVE HOLDCO STACK BOARD
Entity stack →Scene presets
HoldCo adds +1 entity
Your sketch, not a tax engine
ENTITY-STACK DESK
Annual admin run-rate
$4,000
4 entities · 3 OpCos + HoldCo
ADMIN COST PEEL
Setup sits outside the annual run-rate; payback uses net run-rate below.
BENEFIT VS BURDEN
SETUP PAYBACK STRIP
setup ÷ (benefit − admin). Illustrative only.
Updates as you type. Share writes board state; typing does not rewrite the address bar.
Net annual run-rate
$3,500
Admin $4,000 · payback 0.7 yrs
Net run-rate is your illustrative annual benefit minus HoldCo + OpCo admin. It is a structure-cost sketch, not a proof of tax savings or liability protection.
Copy the link to save or share your results.