Designing a late-game portfolio
Group stores, supply chains and management layers so growth does not recreate manual work.
Decision first
Add the next business only when existing managers, routes and factories have spare capacity or a funded upgrade plan.
A late-game portfolio is one in which the next decision is constrained by coordination as much as money. Buildings, district demand, trained specialists, warehouse throughput, delivery windows, management attention, taxes, debt, and liquidity all compete for the same expansion plan.
Write one primary objective for the next expansion cycle.
Complete operating playbook
- ARTICLE LENGTH
- 5,801 words
- DEEP-DIVE SECTIONS
- 15
- RESEARCH LEDGER
- 14
Define late game by constraints, not net worth
A late-game portfolio is one in which the next decision is constrained by coordination as much as money. Buildings, district demand, trained specialists, warehouse throughput, delivery windows, management attention, taxes, debt, and liquidity all compete for the same expansion plan.
Version 1.0 broadens the endgame with the Hamptons, mansions, private driving, revised finance systems, more assertive rivals, and headquarters pricing management. Earlier public updates added factories, real estate, large entertainment venues, travel agencies, and event planning. All are live systems, but none creates a universal progression order. The best next asset depends on what the current portfolio can supply, staff, monitor, and finance without weakening proven operations.
Replace the vague goal of making more money with an explicit portfolio objective. Examples include reducing manual delivery time, diversifying away from one district, adding factory control over a high-value product, building stable rental income, completing a prestige venue, or accumulating a mansion fund. Objectives can conflict. A factory may increase control but consume management and warehouse capacity; a mansion may deliver personal value while reducing liquid expansion capital.
Create a constraint register before ranking opportunities. For each proposed business or property, record capital required, days to recruit and train, rare building need, district demand, expected station and building capacity, logistics units, vehicle and driver hours, headquarters work, tax effect, debt exposure, and the player's review time. The most attractive revenue screenshot is irrelevant if the opportunity fails a constraint that cannot be repaired quickly.
Action checklist
- Write one primary objective for the next expansion cycle.
- List capital, labor, property, demand, logistics, and management constraints separately.
- Distinguish lifestyle, income, control, and diversification goals.
- Reject a universal business ranking that ignores current portfolio limits.
| Late-game objective | Typical asset | Constraint to test first |
|---|---|---|
| More supply control | Factory and warehouse chain | Inputs, machines, trained shifts, and delivery throughput. |
| District diversification | New branch or service | Local demand, competition, and specialist depth. |
| Lower manual workload | HQ, managers, drivers, repeatable routing | Whether the automation covers the real bottleneck. |
| Prestige or lifestyle | Mansion, chauffeur, flagship venue | Protected liquidity after the non-income objective. |
Build a four-bucket capital policy
The cash balance should be divided before an acquisition is evaluated. A practical policy separates operations, taxes and debt, emergencies, and discretionary expansion. Only the fourth bucket is genuinely free for the next project.
Operations include payroll, rents, recurring marketing, supplier orders, factory ingredients, vehicle and logistics costs, and enough replenishment to cross the longest normal delivery interval. Calculate them from conservative recent days, not a record sales day. If a business has volatile demand or expensive inputs, hold a longer runway. The number of days is a risk policy rather than a game constant and should be disclosed in any worked plan.
Taxes and debt deserve their own account. Version 1.0 rebalanced taxes and deductions, added partial tax payment, displayed projections in Econoview, and applies a ten percent fee to late taxes. Loans now require more income, charge higher interest, have minimum daily payments, and support partial repayment. Read the current projection and contract; do not reuse a pre-1.0 tax percentage or assume a loan can wait without a cash consequence.
Emergency capital covers one failed supplier cycle, an employee gap, a broken route, a bad occupancy period, or a patch-related interruption. Expansion capital is what remains after those three protections. Daily auto-investing should be paused when a near-term purchase is planned, because invested funds can be withdrawn partially but are still exposed to market movement. The policy prevents a mansion or license from being financed invisibly by tomorrow's payroll.
Action checklist
- Calculate operations from a conservative period and the longest delivery interval.
- Ring-fence the current Econoview tax projection and every minimum debt payment.
- Keep an emergency reserve sized to a real portfolio failure mode.
- Pause auto-investing before a near-term capital commitment.
| Bucket | Purpose | May fund expansion? |
|---|---|---|
| Operating runway | Keeps existing businesses staffed and supplied | No. |
| Tax and debt | Covers projected tax and contractual minimums | No. |
| Emergency | Absorbs a defined disruption | Only by explicit risk decision. |
| Discretionary | Funds expansion, property, or lifestyle | Yes. |
Use stage gates for every expansion
Large projects should pass sequential gates so a weak assumption is found before the irreversible spend. The same framework works for a Hamptons branch, factory, rental block, office network, cinema, theater, or new headquarters layer.
Gate one is evidence: confirm the mechanic is live in the public build, the building exists, the business is permitted, and current demand or rent conditions are visible. Gate two is capability: prove that recruiting, training, supply, delivery, station capacity, and management can support it. Gate three is capital: protect the four buckets and fund launch plus revision. Gate four is pilot operation: collect comparable hourly and daily observations with one major change at a time.
Gate five is scale. Expand only when the pilot reveals a repeatable bottleneck that more capital can solve. If the venue reaches its lowest station category, add that category within the building cap. If a factory machine is saturated while demand and downstream storage remain healthy, add the constrained production step. If attendance is below capacity, do not answer with a larger property. If rental occupancy is weak, wait through the price-change lag before buying more units.
A failed gate is information, not an invitation to hide the project inside portfolio profits. Record why it failed and what would change the result. A scarce building may justify waiting; missing specialists may justify recruiting first; weak district demand may invalidate the concept. This preserves optionality. It also prevents prestige projects from being declared profitable merely because unrelated stores cover their losses.
Action checklist
- Pass evidence, capability, capital, pilot, and scale gates in order.
- Name the measurable condition required to pass each gate.
- Stop when an irreversible spend cannot solve the observed limit.
- Track each project as its own result rather than hiding it in group cash.
| Gate | Required evidence | Do not proceed when |
|---|---|---|
| Evidence | Current feature, property, and market verified | Plan depends on roadmap or stale database data. |
| Capability | Labor, stations, supply, routes, and oversight available | A critical resource has no lead-time plan. |
| Capital | Launch, runway, tax, debt, and revision funded | Optimistic sales are needed for solvency. |
| Pilot and scale | Repeatable result and solvable bottleneck | The problem is unclassified or demand remains weak. |
Map districts as separate markets
A citywide portfolio should not treat New York as one demand pool. Each district combines property stock, traffic, competition, local demand, rent, access, and supplier proximity differently. Expansion should add market reach rather than merely duplicate addresses.
Open MarketInsider and verify the selected neighborhood before recording demand. Build 3672 fixed the panel so it opens on the current neighborhood, but a manual check avoids contaminating analysis. Record active rivals and revisit the reading over time. A strong citywide brand or high product margin does not guarantee enough local visits. The Hamptons, for example, is officially mostly residential with only a small luxury retail strip, while Industry City was designed around larger industrial properties.
Create a map ledger for every branch: district, address, business type, building maximum, traffic index, required station ceiling, peak customers, opening hours, contribution, delivery route, and nearby same-brand or same-category locations. The Bigger Ambitions database is useful for finding candidate buildings, but it is an unofficial reference without a guaranteed current-build stamp. Confirm the property panel and route in the live save.
Assess cannibalization through total portfolio results. When a second branch opens, compare combined customers and contribution for both sites against the old baseline, controlling for day type and campaign changes. If the new branch gains exactly what the old branch loses, the project may have redistributed demand while adding rent and payroll. If total reach grows and logistics remain efficient, geographic diversification is working.
Action checklist
- Verify neighborhood in MarketInsider for every recorded market reading.
- Maintain a branch map ledger with capacity, peak, and route fields.
- Confirm unofficial property data in the current VoogleMaps panel.
- Measure combined old-plus-new performance when testing cannibalization.
| Map question | Evidence | Portfolio decision |
|---|---|---|
| Is demand local? | Neighborhood MarketInsider and comparable days | Select or reject the concept. |
| Can the building scale? | Hard cap and station categories | Choose format and fit-out. |
| Can it be supplied? | Real route, parking, delivery spot, distance | Assign vehicle and schedule. |
| Does it add reach? | Combined branch customers and contribution | Scale, relocate, or stop duplication. |
Capacity planning across the portfolio
Capacity is layered: property maximum, required station categories, eligible labor by hour, local demand, inventory, and logistics. Portfolio planning must know which layer limits each business before assigning money.
A January 2024 developer reply explains that required station categories have separate capacities, the lowest category limits the business, and the building maximum remains a hard cap. It also points to BizMan's hourly graph. This predates 1.0, so verify the current business requirements, but retain the diagnostic principle. Installed objects are not additive if they belong to different required links in one service chain.
Build a capacity register for every major site. Record the building cap, lowest physical category, eligible staffed capacity during peak, observed peak arrivals, stock-limited throughput, and route-limited replenishment. Then classify spare capacity. Physical spare capacity with low arrivals is a market or acquisition issue. Demand above a hard cap is a candidate for format expansion or another district. A stocked and staffed site with unused machines is not helped by more equipment.
At portfolio level, aggregate only comparable resources. Customer seats cannot be moved between districts, but trained relief employees, warehouse units, vehicles, cash, and management time may be shared. Shared capacity needs a reservation policy. If every branch assumes it can use the same backup driver or inventory buffer simultaneously, the portfolio has double-counted resilience and will fail during the first correlated peak.
Action checklist
- Record property, station, staffed, demand, stock, and route limits separately.
- Use the hourly graph to identify the actual peak ceiling.
- Do not add unlike station capacities together.
- Reserve shared relief, inventory, and vehicles instead of double-counting them.
| Capacity layer | Metric | Expansion only helps when |
|---|---|---|
| Property | Hard customer maximum | The site repeatedly reaches it and demand remains. |
| Stations | Lowest required category | That category is the active bottleneck. |
| Labor | Eligible staffed positions by hour | Existing workers cannot be rescheduled. |
| Supply | Units available through next delivery | Additional stock can arrive and be stored. |
| Market | Observed arrivals and local demand | Capacity, not acquisition, is limiting. |
Peak-demand diagnosis as a management routine
Late-game businesses should be reviewed by exception. A compact peak routine identifies acquisition, capacity, conversion, and interruption problems without forcing the player to watch every store all day.
For each business, record yesterday's hourly customers and mark the busiest interval. Compare that interval with building and station capacity, eligible roster, opening stock, closing stock, satisfaction, campaign, price, and any closure. Low arrivals below capacity indicate demand, traffic, marketing, hours, price context, or satisfaction. A repeated flat plateau indicates a throughput ceiling. Queues beside idle stations indicate staffing or pathing. Arrivals without completed value indicate inventory, price, or service completion.
Use matched comparisons. A Monday after a supplier failure is not a valid baseline for Saturday under a new campaign. Hold most variables constant and change the cheapest reversible factor first. Correct accidental closure and stockouts, move existing workers, adjust hours, then test promotion or price. Add permanent staff, equipment, or property only when the simpler test confirms the constraint.
Marketing is not a universal cure. A 2024 developer explanation described it as adding promotion and bringing customers into the store, not making them buy. The exact formula was not reconfirmed in 1.0, but the distinction remains valuable. If a site already reaches capacity, more promotion can buy unusable arrivals. If customers enter and leave unsatisfied, investigate the service and product loop rather than increasing reach.
Action checklist
- Mark one busiest interval for every material business.
- Classify its problem as acquisition, capacity, conversion, or interruption.
- Compare equivalent days with one major variable changed.
- Escalate from schedule and stock corrections to permanent capital.
| Pattern | Class | First response |
|---|---|---|
| Low arrivals and spare capacity | Acquisition | Check district, hours, demand, satisfaction, and one campaign test. |
| Hard repeated plateau | Capacity | Find the lowest station, labor, or building ceiling. |
| Visits without expected sales | Conversion | Inspect stock, price, needs, and service path. |
| Unexpected zero interval | Interruption | Check required role, delivery, closure, and pathing. |
Factories and expensive-product supply chains
Factories can shift value and control upstream, but they replace a purchasing problem with a production system. The late-game gate is not simply buying machines; it is balancing recipes, workers, shifts, ingredients, storage, exports, and downstream retail demand.
Official 0.9 material moved many high-value products, including certain jewelry, clothing, phones, and watches, toward factory-only production and added Industry City's large warehouse and factory spaces. Verify current recipes and product availability in the 1.0 interface, because exact balance can change. Never state that an expensive product is automatically the most profitable: unit margin, machine time, labor, ingredients, storage, delivery, demand, competition, and unsold inventory all matter.
Model each machine stage in units per shift and identify the slowest required step. A June 2026 community factory guide labels its tests for patch 0.11, easy mode, and fully trained employees, reporting one worker per machine. That is useful versioned evidence, not a universal 3674 rate sheet. Reproduce the recipe with the current training, difficulty, and build before sizing a portfolio around its numbers.
Protect downstream capacity. A factory can produce more than stores can sell, filling warehouse zones and locking working capital. Conversely, a popular chain can consume output faster than the slowest machine or driver can replace it. Track ingredients ordered, units produced, units delivered, units sold, and ending stock by cycle. Expand the measured slow link only after confirming there is profitable downstream demand for the additional output.
Action checklist
- Read current recipes and product channels in build 3674.
- Measure every machine step in units per staffed shift.
- Label community production rates with build, difficulty, and training.
- Cap production to profitable downstream sales and storage.
| Factory constraint | Measurement | Risk if ignored |
|---|---|---|
| Recipe stage | Units per current staffed shift | Upstream or downstream machine idles. |
| Ingredients | Units available before next order | Entire line stops despite spare machines. |
| Warehouse | Free zones and turnover | Capital becomes trapped in surplus. |
| Retail demand | Units sold by branch and day | Production expands without a market. |
| Distribution | Vehicle units and route hours | Finished goods cannot reach shelves. |
Warehouses, import cycles, and route capacity
The logistics portfolio is a timed network. Supplier limits, warehouse zones, smart-delivery rules, vehicle capacity, driver schedules, local storage, and branch peaks must all fit before another location is added.
Official 0.9 notes changed importer and wholesaler delivery to a weekly Monday cycle, removed minimum orders, added per-location weekly limits, and expressed quantities in units rather than boxes. These systems shipped before 1.0, but inspect the current order panel for exact limits and timing. A guide that repeats an old supplier number without checking the live interface should not control a high-value order.
Build a route-capacity table. For each vehicle and driver, record carrying capacity, departure, loading and unloading time, destination window, return, and slack. Group branches only when the combined units and route duration fit conservatively. A route that works on an average day can fail after a promotion or weekend peak. Keep enough local stock to survive the next dependable run plus one named disruption.
Smart delivery reduces clicks but does not create inventory or time. Define warehouse product zones, source stock, destination shelves, reorder targets, and schedules coherently. Prevent one branch from draining a shared item needed by another. Build 3674 fixed an employee quitting bug that could break imports and deliveries, so reproduce persistent failures on the current build before rebuilding the entire network, while remembering that a fixed bug is not proof that every configuration is correct.
Action checklist
- Confirm supplier day, unit limits, and current order status in the live panel.
- Calculate vehicle units and total route time with slack.
- Hold local safety stock through one missed run.
- Retest legacy delivery failures on build 3674 before redesigning.
| Network layer | Capacity question | Control |
|---|---|---|
| Supplier | Can enough units be ordered in the cycle? | Forecast early and diversify where current rules permit. |
| Warehouse | Are zones and stock adequate? | Reserve units by product and branch priority. |
| Vehicle | Can volume and route time fit? | Use measured loads and schedule slack. |
| Branch | Can local shelves survive to next run? | Set reorder targets and a disruption buffer. |
Headquarters, automation, and management span
Automation should reduce a known recurring workload. It should not be treated as proof that a business is healthy. Late-game headquarters systems can manage parts of pricing, purchasing, deliveries, and personnel, while diagnosis remains a portfolio responsibility.
Version 1.0 added an HQ pricing manager, a meaningful improvement for large chains. Use it to implement a deliberate pricing policy after a baseline is measured. Do not automate constant price changes while also testing marketing, hours, and staffing, because the results become impossible to attribute. Review exceptions: sharp demand movement, occupancy change, stockout, or contribution decline should trigger a manual check.
Assign managers and office capacity according to the current BizMan requirements. Office businesses are not exempt from location effects: a December 2025 developer reply says traffic index still matters even when customers are represented as online. This dated developer statement is useful but should be confirmed through current results. Do not move every office to the cheapest low-traffic site on the assumption that physical location is irrelevant.
Define management span as the number of businesses whose peaks, schedules, supply, and price experiments can be reviewed reliably. The game's maximum may be much larger than the player's effective span. Limit simultaneous launches, standardize weekly review fields, and escalate only material exceptions. A portfolio with fewer explainable businesses is stronger than one with many silent losses subsidized by a single factory or flagship.
Action checklist
- Automate only after the rule and baseline are explicit.
- Keep one major test variable stable while pricing automation runs.
- Include traffic when evaluating office locations.
- Limit concurrent launches to what can be reviewed by peak and supply cycle.
| Management function | Automate | Still review |
|---|---|---|
| Pricing | Routine implementation through HQ manager | Demand, contribution, and experiment attribution. |
| Deliveries | Repeatable routes and targets | Stockouts, route overload, and supplier failure. |
| Staffing | Stable schedules and assignments | Peak coverage, preferences, and critical-role relief. |
| Expansion | No | Evidence, capability, capital, and cannibalization gates. |
Real estate and occupancy
Rental property can diversify a portfolio away from store operations, but it remains a capacity and pricing system. Evaluate occupancy, net rent, capital lock-up, and response lag instead of treating property as guaranteed passive profit.
An April 2026 developer reply says occupancy generally increases as rent decreases, neighborhood factors also matter, a new price takes seven days to apply, and occupancy can take additional time to respond. This is current-era developer guidance but predates 1.0 and does not provide an exact formula. Record property, neighborhood, units, asking rent, occupied units, and net result over a period long enough to include the stated lag.
Change one price tier at a time. Repricing every day creates overlapping delays and no interpretable result. If occupancy is weak, wait for the active price to take effect, then compare a matched window. A lower rent can increase occupied capacity but still reduce net income; a higher rent can increase unit yield while leaving too many vacancies. Optimize the portfolio objective rather than occupancy percentage alone.
Include opportunity cost. Capital tied in a premium property cannot simultaneously fund taxes, factory inputs, licenses, or emergency stock. A personal mansion has lifestyle value but should not be reported as rental yield. Separate residence, rental, and speculative appreciation assumptions. Official 1.0 material says Hamptons mansions cost a few million dollars, but it does not promise appreciation or a universal return.
Action checklist
- Label property purpose as residence, rental, or commercial use.
- Wait through the documented seven-day price application lag and response period.
- Compare net rent and vacancy, not occupancy alone.
- Charge locked capital against the same expansion budget as other assets.
| Real-estate metric | Question | Misleading shortcut |
|---|---|---|
| Occupancy | How many units are filled after the pricing lag? | Judging the day after a rent change. |
| Net rent | What remains after relevant cost? | Maximizing occupancy without checking yield. |
| Capital lock-up | Which other project is delayed? | Calling property cost-free because it is owned. |
| Personal utility | Is the lifestyle objective worth the capital? | Presenting a mansion as automatic income. |
Loans, investments, taxes, and liquidity
Version 1.0 materially changed the finance layer, so late-game advice written around earlier negative-interest or loan behavior is unsafe. Use current contracts and projections, and manage liquidity separately from accounting wealth.
Official notes removed negative interest, tightened loan qualification, raised interest, added minimum daily payments, increased Vantander's maximum, and enabled partial repayment. A larger available maximum is not a recommendation to borrow it. Model the daily minimum under a weak portfolio scenario and compare the interest cost with a conservative project contribution. Avoid financing a long recruitment or construction lead time with cash flow that begins only after a perfect opening.
Investments gained daily auto-investing, more detailed growth information, and partial withdrawals. Set automatic contributions only after operating, tax, debt, and supplier obligations are reserved. Treat investments as risk capital rather than a checking account. If a scheduled tax or factory order will require the money, keep it liquid; otherwise a forced withdrawal can turn normal market movement into a realized loss.
Tax planning now includes a projection in Econoview, partial payment, rebalanced deductions, and a ten percent late fee. Read the current projection regularly, especially before a mansion, property, factory, or entertainment license. Do not infer the final tax bill from gross cash generation or an old guide's percentage. A profitable portfolio can still face a liquidity crisis when tax, supplier, and debt dates cluster.
Action checklist
- Read every current loan's rate, minimum payment, and remaining principal.
- Stress-test debt against weak rather than average operating days.
- Invest only cash beyond dated obligations and buffers.
- Use Econoview projection and avoid the documented late-tax fee.
| Finance tool | Useful purpose | Unsafe assumption |
|---|---|---|
| Loan | Fund a tested project with survivable debt service | Maximum approval equals affordable borrowing. |
| Partial repayment | Reduce principal while preserving needed liquidity | Every spare dollar should leave operations. |
| Auto-investing | Deploy true surplus consistently | Invested funds are guaranteed liquid at value. |
| Partial tax payment | Manage timing within current rules | Late payment has no penalty. |
Worked example: compare three late-game uses of cash
This example uses fictional round numbers to show portfolio reasoning. It is not a build-3674 price list or profit promise. Replace every amount with the current save's costs, obligations, difficulty, and observed contribution.
A portfolio holds 12,000,000 liquid. Conservative daily operations are 300,000 and the player selects a ten-day runway, reserving 3,000,000. Projected tax and near-term debt obligations total an illustrative 2,000,000, and the emergency supplier reserve is 1,000,000. Discretionary capital is therefore 6,000,000. The choices are a mansion, a cinema launch, or a factory expansion; none may consume protected buckets.
The mansion's current in-game cost plus setup is hypothetically 4,500,000 and delivers a stated lifestyle objective but no assumed cash flow. The cinema pilot requires 3,800,000 including license, fit-out, specialist runway, stock, and redesign allowance, but local demand and a suitable building are confirmed. The factory project requires 2,600,000, yet the warehouse is already near capacity and downstream shops have surplus inventory. That capacity evidence blocks the factory despite its lowest sticker price.
If the player's primary objective is income diversification, the cinema may pass evidence, capability, and capital gates, leaving 2,200,000 discretionary. If the primary objective is lifestyle completion, the mansion may be correct while explicitly accepting its opportunity cost. The factory waits until warehouse turnover and retail demand justify more output. The method does not declare one asset universally best; it aligns the chosen asset with objective and bottleneck.
Action checklist
- Replace all example amounts with live current-save figures.
- Keep the same protected buckets across competing proposals.
- Block projects that worsen an existing non-capital constraint.
- Choose by stated objective after every gate passes.
| Illustrative option | Capital request | Gate result |
|---|---|---|
| Mansion | 4,500,000 | Passes capital; choose only for explicit lifestyle goal. |
| Cinema pilot | 3,800,000 | Passes if building, demand, specialists, and logistics are verified. |
| Factory expansion | 2,600,000 | Fails current warehouse and downstream-demand capability gate. |
| Protected reserves | 6,000,000 | Unavailable to all three options. |
Worked example: diagnose portfolio-wide stockouts
A portfolio can look demand-constrained when it is actually distribution-constrained. This example is fictional and demonstrates how to separate supplier, warehouse, route, local storage, and shelf failures.
Four retail branches report lower sales after a weekend promotion. Warehouse stock shows 8,000 units of the affected product, so the manager initially assumes local staff are at fault. The route table reveals that all four branches share one van whose combined requested load is 1,400 units while its practical run carries only 900 within the driver's shift. Smart delivery cannot overcome that physical and time limit.
The manager records destination demand and prioritizes branches by hours until stockout. One second route is scheduled with an existing spare vehicle and trained driver, while local reorder targets are moved earlier. The next matched promotion weekend has no stockouts and customer throughput rises without more marketing. This confirms that prior low sales did not prove weak demand or bad pricing; observations were censored by missing shelf stock.
Before buying another warehouse, the manager checks whether supplier limits, warehouse space, loading time, vehicle capacity, or driver hours are now lowest. If the warehouse has space and supplier units are adequate, a larger building would not solve the route. If two routes still drain the warehouse before Monday delivery, supplier or safety stock planning becomes next. Portfolio fixes should follow the narrowest measured link.
Action checklist
- Trace units from supplier to warehouse, vehicle, local storage, and shelf.
- Compare combined route requests with practical vehicle and shift capacity.
- Treat stockout-period sales as an incomplete demand observation.
- Expand only the narrowest confirmed logistics link.
| Illustrative layer | Observed state | Conclusion |
|---|---|---|
| Warehouse | 8,000 units available | Not the immediate shortage. |
| Combined branch request | 1,400 units | Demand exceeds one run. |
| Practical route | 900 units in shift | Active distribution bottleneck. |
| Second matched test | No stockouts after added route | Prior sales were supply-limited. |
Live features, patches, and roadmap exclusions
Portfolio forecasts must use shipped systems only. Official roadmaps are valuable for direction, but future boats, ferries, Shanghai, or other planned content cannot be assigned present revenue, transport capacity, or property value.
Current evidence comes from public release notes through 1.0 and build 3674. The Hamptons, mansions, chauffeur, revised finance systems, factories, real estate, cinema, theater, travel agencies, event planning, Workshop, and HQ pricing manager are shipped. Exact prices, demand, building availability, product rates, and profit remain save-specific unless current official material publishes a value.
The December 2025 studio update described two free post-release content updates and shifted planned DLC attention to Shanghai, while acknowledging uncertainty about the future. The roadmap page has no dependable release guarantee embedded in its graphic. Treat every post-1.0 item as planned until a dated public-branch changelog confirms it. A dock on the current map does not prove an operating ferry system.
Patch state also needs precision. Build 3674 fixed an employee quitting bug that could make training, imports, and deliveries fail. The same September 1 notes say frame-rate drops and choppy gameplay were still being investigated. Update and reproduce a problem before restructuring the portfolio, but do not state that the current build is universally stable. Modded saves require a separate clean test because community code can introduce its own capacity or persistence failures.
Action checklist
- Require a dated public release note for every live-system assumption.
- Exclude roadmap mechanics from current return and logistics models.
- Reproduce old employee, import, or delivery failures on build 3674.
- Separate clean base-game defects from modded-save behavior.
| Item | Status | Portfolio treatment |
|---|---|---|
| Factories, real estate, venues, Hamptons | Shipped | Use current in-game values and constraints. |
| Boats, ferry, Shanghai | Roadmap or future plan | Assign zero current operational capacity. |
| 3674 employee hotfix | Shipped fix | Update and retest affected systems. |
| Performance resolution | Still under investigation in cited notes | Record and isolate; do not claim fully solved. |
Final portfolio audit
Run the audit weekly and before every large commitment. A healthy late-game portfolio is liquid, explainable, supplied, staffed, capacity-aware, and based on current features rather than gross revenue or roadmap optimism.
Capital audit: operating runway uses conservative outflow; Econoview tax projection and the ten percent late-fee risk are covered; minimum loan payments are stress-tested; emergency reserves correspond to real failure modes; automatic investing uses only true surplus; and the proposed acquisition fits entirely inside discretionary capital with a revision allowance.
Operating audit: every material branch has a known building cap, lowest required station category, peak staffed capacity, observed hourly peak, inventory interval, and route. Critical specialists have relief. Supplier limits and Monday timing are confirmed in the current interface. Factory output is tied to downstream sales. Rental changes have passed the pricing lag. New branches are checked for combined portfolio growth rather than customer transfer.
Evidence audit: claims identify build, difficulty, district, building, demand, traffic, campaign, hours, prices, training, and test period when relevant. Developer replies from older versions are labelled as dated models. Community guides are accepted only for transparent versioned tests. SEO rankings, stale Fandom pages, unexplained screenshots, and guaranteed-profit claims are rejected. Roadmap items remain excluded until shipped.
Action checklist
- Pass capital, market, capacity, staffing, supply, property, and evidence checks.
- Name the current portfolio bottleneck before approving expansion.
- Limit simultaneous experiments so results remain attributable.
- Fail the audit when protected cash or unreleased mechanics are required.
| Audit | Pass condition | Corrective action |
|---|---|---|
| Liquidity | All dated obligations and buffers remain funded | Pause investment or expansion and rebuild cash. |
| Capacity | Every site's active ceiling is measured | Collect hourly and station evidence. |
| Network | Supplier, warehouse, route, and shelf capacities align | Expand the narrowest link only. |
| Evidence | Current, versioned, reproducible, and caveated | Remove or relabel unsupported claims. |
Research ledger
These links establish mechanics or provide a reproducible lead. Any balance-sensitive number still has to be checked in the current save.
Questions answered
How much cash marks the late game?
No reliable source defines one threshold. Late game is better recognized when coordination constraints dominate: multiple districts, trained specialists, factories or warehouses, expensive venues or property, tax and debt exposure, and limited management attention. Divide cash into protected and discretionary buckets before deciding whether any balance is truly spendable.
What is the best late-game business?
There is no current universal best-business result supported by the reviewed evidence. Patches changed office, gym, product, finance, and venue balance. The best project is one that passes local demand, building, capacity, specialist, supply, capital, and management gates for the current save and advances the player's stated objective.
Should a profitable chain always open another branch?
No. Check whether the new district adds demand or merely shifts customers, whether a suitable building exists, and whether staff, warehouse units, vehicles, and management time are available. Compare combined old-plus-new contribution on matched days. A busy new branch can still reduce portfolio value if it cannibalizes an old one.
When should factory capacity be expanded?
Expand the measured slow production step only when ingredients, trained workers, warehouse space, distribution, and profitable downstream demand can absorb more output. Community rates labelled for 0.11 are hypotheses until reproduced on 3674 with the current difficulty and training. Expensive products are not guaranteed to be most profitable.
How much operating runway is enough?
Choose a disclosed stress period based on volatility and failure recovery; it is not a universal game constant. Multiply conservative daily outflow by that period, include the longest supplier interval, and reserve taxes, debt minimums, and emergencies separately. A complex factory-and-retail network generally needs more protection than a stable simple portfolio.
Are investments part of operating liquidity?
They should not be treated as guaranteed cash at value. Version 1.0 allows partial withdrawals and automatic daily investing, but market movement still matters. Keep dated payroll, supplier, tax, debt, and launch obligations liquid, and invest only genuine surplus that will not be forced out at an inconvenient time.
How quickly should rental rent changes be judged?
A developer reply from April 2026 says a new rental price takes seven days to apply and occupancy may need additional time to respond. Treat that as dated current-era guidance, change one tier at a time, and observe a matched period after the lag. Do not optimize occupancy without checking net rent.
Does automation remove the need to review businesses?
No. Headquarters pricing management, smart deliveries, schedules, and managers reduce repetitive work. They do not identify every stockout, demand shift, station bottleneck, route overload, or cannibalized branch. Use automation to implement explicit rules and review exceptions through hourly and cycle-level evidence.
Can future roadmap content be included in a long-term forecast?
It can be listed as an uncertain scenario, but it should contribute zero to the current build-3674 base case. Boats, ferries, Shanghai, timing, scope, and price can change until a dated public-branch release note confirms shipment. Do not buy current capacity solely for an unreleased mechanic.