A safer first week
Move from the starter apartment to one self-running store without exhausting working capital.

Decision first
Do not expand until the first store survives a complete week without your labor and remains profitable after every recurring cost.
Big Ambitions left Early Access on August 28, 2026, and Build 3674 is the latest documented public hotfix at this review date. It fixes the date and evidence standard before any advice is applied.
Label each claim by evidence type.
Complete operating playbook
- ARTICLE LENGTH
- 6,442 words
- DEEP-DIVE SECTIONS
- 14
- RESEARCH LEDGER
- 8
Scope, version, and evidence hierarchy
Big Ambitions left Early Access on August 28, 2026, and Build 3674 is the latest documented public hotfix at this review date. It fixes the date and evidence standard before any advice is applied.
Official notes define the current feature set, developer replies clarify a few mechanics, and version-labelled tests supply hypotheses where no formula is published.
Procedure: confirm the Steam build; read current objectives and F1 requirements; note the selected difficulty; create a dated baseline; reject advice that cannot name its version
Example: A 2023 video says the tutorial forces two particular shops, while the current objective asks for any wholesaler-supported business. The live objective and the 0.9 progression notes outrank the video.
If a guide and the game disagree, stop importing its numbers. Inspect build number, objective text, difficulty modifiers, and active warnings before moving to a costlier branch.
Record the build, save type, difficulty, date, cash balance, objectives, and every assumption taken from outside the game in BizMan, and pair it with the neighborhood demand and provider snapshot from Market Insider plus the matching cost period in EconoView. Use build number, objective text, difficulty modifiers, and active warnings as the decision signal only when the recorded controls remain comparable.
Build 3674 mainly fixes post-launch defects; major early-game progression changes arrived in 0.9 and remain part of 1.0.
Try to falsify the section's working assumption before funding it. For Scope, version, and evidence hierarchy, deliberately hold build number, objective text, difficulty modifiers, and active warnings steady while testing label each claim by evidence type. If the expected signal does not move, the proposed cause is weak; return to prefer current F1 text and document the conflicting observation instead of rescuing the theory with another purchase.
Create a research note before day one ends: record the exact build shown by Steam, whether the save is Story or Custom, and every modifier that changes customers, costs, training, or sourcing; those fields decide whether another player's result is comparable.
Action checklist
- Label each claim by evidence type.
- Prefer current F1 text.
- Reproduce disputed advice.
- Discard universal profit claims.
- Recheck after patches.
| Checkpoint | Pass evidence | Failure response |
|---|---|---|
| label each claim by evidence type | The record for build number, objective text, difficulty modifiers, and active warnings supports the intended condition. | prefer current F1 text |
| reproduce disputed advice | The comparison includes the build, save type, difficulty, date, cash balance, objectives, and every assumption taken from outside the game and contains no unexplained outage. | discard universal profit claims |
| recheck after patches | The downside remains affordable and the next trigger is written. | Pause the plan and repeat the smallest disputed test for scope, version, and evidence hierarchy. |
Day one: stabilize the character
The player character must sleep, eat, and maintain happiness, and 1.0 makes energy drain faster when hunger or happiness is low. Treat these needs as operating inputs because they consume the same hours used to build the company.
These needs are operating constraints because exhaustion or hospitalization consumes time that could have been used for courses, stock movement, recruiting, or opening a store.
Procedure: accept practical housing; establish a bed and food supply; plan errands geographically; avoid prestige purchases; reserve energy for time-critical trips
Example: A player who saves a small furniture cost but makes three extra grocery trips loses more opening time than the saving justifies. A stocked home converts those trips into one planned errand.
If the first week feels like endless travel, examine needs and route planning before blaming business balance. Inspect energy, hunger, happiness, travel time, hospital events, and missed appointments before moving to a costlier branch.
Record morning need levels, planned errands, actual return time, transport used, and any task postponed because the character ran out of energy in BizMan, and pair it with the neighborhood demand and provider snapshot from Market Insider plus the matching cost period in EconoView. Use energy, hunger, happiness, travel time, hospital events, and missed appointments as the decision signal only when the recorded controls remain comparable.
Exact need drain varies with conditions and may change; do not publish a universal number of hours between meals or sleeps.
Build a small ledger for this decision. Put energy, hunger, happiness, travel time, hospital events, and missed appointments in the result column and morning need levels, planned errands, actual return time, transport used, and any task postponed because the character ran out of energy in the control column. The comparison is usable only when the controls describe the same operating conditions. This prevents a busy day, a supplier arrival, or a staffing improvement from being credited to bundle nearby errands.
Plan the morning around need bars rather than reacting after they turn critical. Eat before a supplier circuit, sleep before a scheduled opening, and postpone optional happiness spending whenever it would consume the cash reserved for a register, primary stock, or wages.
Action checklist
- Bundle nearby errands.
- Keep food at home.
- Sleep before critical delivery days.
- Delay luxury furniture.
- Protect business cash.
| Checkpoint | Pass evidence | Failure response |
|---|---|---|
| bundle nearby errands | The record for energy, hunger, happiness, travel time, hospital events, and missed appointments supports the intended condition. | keep food at home |
| sleep before critical delivery days | The comparison includes morning need levels, planned errands, actual return time, transport used, and any task postponed because the character ran out of energy and contains no unexplained outage. | delay luxury furniture |
| protect business cash | The downside remains affordable and the next trigger is written. | Pause the plan and repeat the smallest disputed test for day one: stabilize the character. |
Learn through the current objectives
The rebuilt tutorial teaches systems while allowing a wider wholesaler-supported first-business choice than old fixed walkthroughs. The live objective text is the safest map through progression gates.
EA 0.9 explicitly changed progression and item access, while Build 3672 corrected tutorial product detection and added references to help files.
Procedure: read the objective literally; inspect F1 before buying; complete required courses; use the job phase to fund necessities; pause before an irreversible lease
Example: An old guide instructs the player to buy equipment for a fast-food store. The current save shows stronger flower demand and permits a florist, so following the old shopping list would create sunk cost.
When an objective fails to advance, compare its exact noun and quantity with the item placed, stocked, or assigned. Inspect objective state, course completion, permitted business types, and required product category before moving to a costlier branch.
Record objective wording before the action, the item or employee used, completion response, and any Build 3674 bug message in BizMan, and pair it with the neighborhood demand and provider snapshot from Market Insider plus the matching cost period in EconoView. Use objective state, course completion, permitted business types, and required product category as the decision signal only when the recorded controls remain comparable.
Custom-game settings can alter progression and availability, so a story-mode sequence is not a universal sandbox schedule.
Define the stop condition in advance: abandon or redesign the test when objective state, course completion, permitted business types, and required product category remains unfavorable after follow current prompts and open F1 before purchasing have been verified. A written stopping rule protects opening cash from escalation, especially when sunk rent or furniture makes the player emotionally committed to the original plan.
When an objective names an item, open F1 and compare the item's displayed category before purchasing. If the objective does not advance, transcribe its wording, confirm placement and stock state, then advance time only after ruling out a requirement mismatch.
Action checklist
- Follow current prompts.
- Open F1 before purchasing.
- Verify course gates.
- Capture failed-objective details.
- Avoid obsolete walkthrough sequences.
| Checkpoint | Pass evidence | Failure response |
|---|---|---|
| follow current prompts | The record for objective state, course completion, permitted business types, and required product category supports the intended condition. | open F1 before purchasing |
| verify course gates | The comparison includes objective wording before the action, the item or employee used, completion response, and any Build 3674 bug message and contains no unexplained outage. | capture failed-objective details |
| avoid obsolete walkthrough sequences | The downside remains affordable and the next trigger is written. | Pause the plan and repeat the smallest disputed test for learn through the current objectives. |
Cash runway before the lease
Opening cash must cover more than rent: required equipment, initial inventory, transport, wages, cleaning, and mistakes all arrive before stable profit. The calculation decides whether the first setback can be survived.
The official loop includes financing, stocking, hiring, and supply management; 1.0 also tightened loan qualification around demonstrated income.
Procedure: list unavoidable setup costs; reserve payroll and restock cash; price transport alternatives; define a stop-loss; sign only when residual cash remains positive
Example: Two leases have similar traffic, but the larger unit requires twice the fixtures to remove bottlenecks. The cheaper-looking rent becomes the more expensive opening once equipment and stock are included.
If cash falls after a strong sales day, distinguish inventory purchases and loan payments from the accounting profit shown for the shop. Inspect cash balance, daily fixed costs, setup commitments, inventory outlay, and days of runway before moving to a costlier branch.
Record starting cash, lease cost, one-time equipment cost, opening stock, projected weekly wages, marketing commitments, and debt service in BizMan, and pair it with the neighborhood demand and provider snapshot from Market Insider plus the matching cost period in EconoView. Use cash balance, daily fixed costs, setup commitments, inventory outlay, and days of runway as the decision signal only when the recorded controls remain comparable.
Published starter budgets age quickly and differ by difficulty, so this guide uses categories and live quotes rather than a fixed dollar package.
Cross-check two screens rather than trusting one summary. BizMan should explain the operating result through cash balance, daily fixed costs, setup commitments, inventory outlay, and days of runway; Market Insider or EconoView should explain the market or cost context through starting cash, lease cost, one-time equipment cost, opening stock, projected weekly wages, marketing commitments, and debt service. A disagreement is a diagnostic lead, not permission to average the numbers until they look plausible.
Use a downside runway worksheet with five entries: liquid cash, unavoidable daily rent, scheduled wages, minimum food and transport, and the next required stock purchase. Divide cash by that conservative outflow to see how many failed opening days the plan can absorb.
Action checklist
- Cost the complete opening.
- Reserve payroll.
- Reserve one restock.
- Set a stop-loss.
- Delay optional decoration.
| Checkpoint | Pass evidence | Failure response |
|---|---|---|
| cost the complete opening | The record for cash balance, daily fixed costs, setup commitments, inventory outlay, and days of runway supports the intended condition. | reserve payroll |
| reserve one restock | The comparison includes starting cash, lease cost, one-time equipment cost, opening stock, projected weekly wages, marketing commitments, and debt service and contains no unexplained outage. | set a stop-loss |
| delay optional decoration | The downside remains affordable and the next trigger is written. | Pause the plan and repeat the smallest disputed test for cash runway before the lease. |
Market Insider reconnaissance
Demand and competition are neighborhood-specific, and the correct first choice must be read from the current save rather than a global ranking. This snapshot defines the market hypothesis that the store will test.
Developer explanations identify demand and competition as inputs to realized customer volume, while Build 3672 fixed Market Insider opening on the wrong neighborhood.
Procedure: select the intended neighborhood; list primary products for candidate businesses; record demand and providers; compare several baskets; revisit immediately before leasing
Example: One product shows very high demand but its companion products are weak and several rivals sell them. Another business has three solid products and no provider. The balanced basket is the safer experiment.
If opening sales are weak despite a functioning shop, confirm that reconnaissance was performed for the leased neighborhood, not the previously viewed district. Inspect demand by product, provider count, rival price context, neighborhood, and business basket coverage before moving to a costlier branch.
Record a timestamped candidate table with every primary product, displayed demand, providers, source tier, and whether the product can be obtained immediately in BizMan, and pair it with the neighborhood demand and provider snapshot from Market Insider plus the matching cost period in EconoView. Use demand by product, provider count, rival price context, neighborhood, and business basket coverage as the decision signal only when the recorded controls remain comparable.
Demand can change through new providers, rivals, hype, shortages, and player expansion; a screenshot is evidence for that moment only.
Use a counterfactual question: what would be observed if verify the neighborhood were not the bottleneck? If that alternative predicts the same demand by product, provider count, rival price context, neighborhood, and business basket coverage, the proposed intervention cannot distinguish the causes. Choose a test whose success and failure produce visibly different records.
For each candidate basket, copy every primary product row from Market Insider, not merely the highest percentage. Beside demand, record providers, current source access, and the intended opening quantity; a blank source cell disqualifies the product from the week-one revenue forecast.
Action checklist
- Verify the neighborhood.
- Compare complete baskets.
- Count providers.
- Check sourcing.
- Refresh.
| Checkpoint | Pass evidence | Failure response |
|---|---|---|
| verify the neighborhood | The record for demand by product, provider count, rival price context, neighborhood, and business basket coverage supports the intended condition. | compare complete baskets |
| count providers | The comparison includes a timestamped candidate table with every primary product, displayed demand, providers, source tier, and whether the product can be obtained immediately and contains no unexplained outage. | check sourcing |
| refresh | The downside remains affordable and the next trigger is written. | Pause the plan and repeat the smallest disputed test for market insider reconnaissance. |
Choose a sourceable starter business
Standard wholesalers support fast food, coffee, fruit and vegetables, supermarkets, florists, hairdressers, and cheap gifts under the 0.9 progression model retained in 1.0. Source access removes attractive but impossible opening plans.
The source split is official and exists to prevent immediate access to every high-margin product; custom settings may relax it.
Procedure: identify available supplier products; match them to business requirements; estimate fixture burden; estimate labor burden; rank candidates by operational simplicity and local demand
Example: A gift shop can open around accessible cheap gifts, while a plan dependent on a product available only through later infrastructure cannot trade as designed during week one.
If BizMan warns that primary products are missing, verify the business type and source access rather than filling random secondary shelves. Inspect source tier, primary-product availability, required stations, staffing roles, and estimated daily stock volume before moving to a costlier branch.
Record supplier name, product availability, units purchasable, fixture list, employee roles, and any warning about inaccessible products in BizMan, and pair it with the neighborhood demand and provider snapshot from Market Insider plus the matching cost period in EconoView. Use source tier, primary-product availability, required stations, staffing roles, and estimated daily stock volume as the decision signal only when the recorded controls remain comparable.
Do not infer that every product associated with a business is available at the same progression tier; inspect F1 and the supplier UI.
Translate the choice into an opportunity-cost comparison. Time or cash spent on filter to sourceable formats is unavailable for compare labor complexity. Include the owner's travel and waiting time when it changes whether the next course, recruitment call, supplier trip, or store inspection can be completed that day.
At the wholesaler, verify the actual products and weekly limits against F1 before leasing. A business that needs an importer or factory to deliver its intended margin is a later-stage project even when the storefront itself appears inexpensive.
Action checklist
- Filter to sourceable formats.
- Verify primary products.
- Cost required stations.
- Compare labor complexity.
- Exclude later-chain dependencies.
| Checkpoint | Pass evidence | Failure response |
|---|---|---|
| filter to sourceable formats | The record for source tier, primary-product availability, required stations, staffing roles, and estimated daily stock volume supports the intended condition. | verify primary products |
| cost required stations | The comparison includes supplier name, product availability, units purchasable, fixture list, employee roles, and any warning about inaccessible products and contains no unexplained outage. | compare labor complexity |
| exclude later-chain dependencies | The downside remains affordable and the next trigger is written. | Pause the plan and repeat the smallest disputed test for choose a sourceable starter business. |
Lease and fit-out discipline
A store must satisfy functional requirements before cosmetic ambition can create value. A closed-door inspection is cheaper than diagnosing customers after launch.
Official updates made bathrooms consequential, changing rooms mandatory for clothing, and uniform lockers necessary for uniforms; Competitive blueprints demonstrate complete layouts.
Procedure: keep the business closed; place required capacity fixtures; place payment and customer-flow items; create storage and sanitation areas; test every warning before opening
Example: A beautiful store lacks a staffed register and bags. Customers cannot complete purchases, so another sofa cannot repair the failure. A plain but complete shop can produce a valid baseline.
When no customers or sales appear, inspect BizMan requirements and schedule coverage before buying advertising. Inspect required-item warnings, structural customer capacity, staffed stations, stock, cleanliness, and customer feedback before moving to a costlier branch.
Record each requirement, quantity installed, capacity contribution, employee assigned, inventory loaded, and warning state in BizMan, and pair it with the neighborhood demand and provider snapshot from Market Insider plus the matching cost period in EconoView. Use required-item warnings, structural customer capacity, staffed stations, stock, cleanliness, and customer feedback as the decision signal only when the recorded controls remain comparable.
Blueprints can save labor but may be versioned, oversized, or unaffordable; understand one manual layout before automating design.
Run the inexpensive branch first. Confirm close during construction, then inspect required-item warnings, structural customer capacity, staffed stations, stock, cleanliness, and customer feedback; only after those observations support the hypothesis should the player commit to clear all blocking warnings. This ordering is valuable in week one because errors in identity, assignment, or stock often resemble expensive market problems.
Walk the closed shop as two separate routes: customer entrance to basket, product, checkout, and exit; delivery spot to storage and every selling fixture. Any crossing that blocks queues or forces boxes through customers should be corrected before the first measured shift.
Action checklist
- Close during construction.
- Satisfy required items.
- Staff every active station.
- Stock primary goods.
- Clear all blocking warnings.
| Checkpoint | Pass evidence | Failure response |
|---|---|---|
| close during construction | The record for required-item warnings, structural customer capacity, staffed stations, stock, cleanliness, and customer feedback supports the intended condition. | satisfy required items |
| staff every active station | The comparison includes each requirement, quantity installed, capacity contribution, employee assigned, inventory loaded, and warning state and contains no unexplained outage. | stock primary goods |
| clear all blocking warnings | The downside remains affordable and the next trigger is written. | Pause the plan and repeat the smallest disputed test for lease and fit-out discipline. |
Opening stock without trapping cash
Inventory enables sales but excess slow stock consumes cash and storage, while thin stock creates lost demand and emergency trips. Working capital belongs to the products that can sell before the next replenishment.
EA 0.9 exposes units sold and ordered last week, uses unit-based supplier orders, and imposes weekly delivery timing and limits.
Procedure: buy a focused initial basket; observe one full trading day; calculate daily units by SKU; add a measured buffer; reduce products that obstruct faster sellers
Example: A shop sells eighty units of one item and eight of another. Reordering equal quantities fills storage with the slow item and can prevent the bestseller from arriving.
When a store reports a stockout, identify whether warehouse stock, store storage, fixture loading, supplier timing, or an undersized target is the first failure. Inspect units sold per SKU, on-hand units, shelf capacity, storage occupancy, stockouts, and next replenishment time before moving to a costlier branch.
Record opening quantity, closing quantity, delivered units, sold units, wasted trips, and each hour a primary product was unavailable in BizMan, and pair it with the neighborhood demand and provider snapshot from Market Insider plus the matching cost period in EconoView. Use units sold per SKU, on-hand units, shelf capacity, storage occupancy, stockouts, and next replenishment time as the decision signal only when the recorded controls remain comparable.
Hype, shortage, backorder, weekend weighting, and a new competitor can invalidate a simple average.
Mark the test contaminated if any event changes the comparison: an uncovered shift, closed hour, stockout, supplier delivery, rival move, hype, shortage, backorder, or patch. Keep the data for operational learning, but do not use it to estimate the isolated effect of measure sell-through.
Calculate each opening order from coverage, not shelf appearance: expected daily units multiplied by days until the next feasible restock, plus a named safety allowance. Keep the allowance smaller on slow items so they cannot occupy storage needed by the bestseller.
Action checklist
- Start with primary SKUs.
- Measure sell-through.
- Calculate coverage days.
- Add a modest buffer.
- Cut dead stock.
| Checkpoint | Pass evidence | Failure response |
|---|---|---|
| start with primary SKUs | The record for units sold per SKU, on-hand units, shelf capacity, storage occupancy, stockouts, and next replenishment time supports the intended condition. | measure sell-through |
| calculate coverage days | The comparison includes opening quantity, closing quantity, delivered units, sold units, wasted trips, and each hour a primary product was unavailable and contains no unexplained outage. | add a modest buffer |
| cut dead stock | The downside remains affordable and the next trigger is written. | Pause the plan and repeat the smallest disputed test for opening stock without trapping cash. |
The first controlled trading cycle
One complete operating cycle is a measurement exercise, not proof that the concept has permanently succeeded or failed. The first shift should create a baseline, not a victory story.
BizMan exposes hourly customers, satisfaction, inventory and finance views needed to separate execution problems from market weakness.
Procedure: freeze price and marketing; verify stock before opening; observe the full schedule; capture closing data; change only the largest confirmed constraint
Example: The store earns little because the cashier is absent for two hours. Changing prices after that day would attribute a scheduling failure to demand and damage the next test.
If revenue is zero, follow the chain open status, required equipment, staffed station, primary stock, customer arrival, queue completion, and payment consumables. Inspect hourly customers, completed sales, queue complaints, pricing satisfaction, service, cleanliness, interior, and stockouts before moving to a costlier branch.
Record opening and closing cash, hourly customer graph, SKU sales, employee schedule, all customer complaints, and net profit components in BizMan, and pair it with the neighborhood demand and provider snapshot from Market Insider plus the matching cost period in EconoView. Use hourly customers, completed sales, queue complaints, pricing satisfaction, service, cleanliness, interior, and stockouts as the decision signal only when the recorded controls remain comparable.
The visible in-store animation is not a precise accounting sample; use BizMan and EconoView records as the measurement source.
Convert the observation into a trigger. Continue the present plan while hourly customers, completed sales, queue complaints, pricing satisfaction, service, cleanliness, interior, and stockouts stays inside the chosen range; invoke capture hourly results when it crosses the boundary; reconsider the underlying business only after repair the first bottleneck also fails. Triggers make later decisions consistent instead of mood-driven.
During the first shift, note the exact hour of every queue complaint, empty fixture, cleanliness warning, and schedule transition. These timestamps let the Yesterday chart distinguish a genuine weak hour from an hour damaged by an operational interruption.
Action checklist
- Freeze major variables.
- Verify opening readiness.
- Capture hourly results.
- Repair the first bottleneck.
- Rerun the baseline.
| Checkpoint | Pass evidence | Failure response |
|---|---|---|
| freeze major variables | The record for hourly customers, completed sales, queue complaints, pricing satisfaction, service, cleanliness, interior, and stockouts supports the intended condition. | verify opening readiness |
| capture hourly results | The comparison includes opening and closing cash, hourly customer graph, SKU sales, employee schedule, all customer complaints, and net profit components and contains no unexplained outage. | repair the first bottleneck |
| rerun the baseline | The downside remains affordable and the next trigger is written. | Pause the plan and repeat the smallest disputed test for the first controlled trading cycle. |
Replace the owner at the counter
The early strategic objective is a business that operates while the player researches, buys, recruits, and expands elsewhere. Owner replacement converts a job into a managed business.
The official game loop emphasizes hiring and management, while customer service quality depends on employee capability and schedule execution.
Procedure: recruit for the required role; inspect demands; schedule complete coverage; train when cash permits; verify the shop remains functional without the player
Example: The owner produces sales during an eight-hour shift but performs no supplier reconnaissance. A competent employee may cost wages yet release the owner to prevent stockouts and prepare the next decision.
If profit falls after replacement, compare employee skill, station assignment, schedule gaps, queues, and demands before firing or extending hours. Inspect employee skill, wage, satisfaction, demands, assigned station, worked hours, and customer-service score before moving to a costlier branch.
Record candidate terms, schedule, training periods, uncovered intervals, service rating, wage cost, and revenue before and after replacement in BizMan, and pair it with the neighborhood demand and provider snapshot from Market Insider plus the matching cost period in EconoView. Use employee skill, wage, satisfaction, demands, assigned station, worked hours, and customer-service score as the decision signal only when the recorded controls remain comparable.
Employee demands and labor economics vary; an old recommendation about age bands or fixed wages is not reliable evidence for Recheck the live F1 panel after any patch that changes the relevant requirement or interface.
A useful scenario pair is a conservative day and an upside day. In both, keep candidate terms, schedule, training periods, uncovered intervals, service rating, wage cost, and revenue before and after replacement explicit. The conservative case tests survival after hire the exact role; the upside case tests whether after and value released owner time has room to create value. A plan that works only in the upside case is not yet beginner-safe.
Compare owner-operated and employee-operated shifts using the same prices, hours, and stock. The relevant question is whether lost contribution under the employee is smaller than the value of owner time released for purchasing, hiring, courses, and expansion research.
Action checklist
- Hire the exact role.
- Read demands.
- Cover every open hour.
- Compare service before.
- After and value released owner time.
| Checkpoint | Pass evidence | Failure response |
|---|---|---|
| hire the exact role | The record for employee skill, wage, satisfaction, demands, assigned station, worked hours, and customer-service score supports the intended condition. | read demands |
| cover every open hour | The comparison includes candidate terms, schedule, training periods, uncovered intervals, service rating, wage cost, and revenue before and after replacement and contains no unexplained outage. | compare service before |
| after and value released owner time | The downside remains affordable and the next trigger is written. | Pause the plan and repeat the smallest disputed test for replace the owner at the counter. |
Price and promotion sequencing
Price, promotion, satisfaction, demand, and capacity interact, so changing them simultaneously prevents diagnosis. Sequence price and promotion so each result has one plausible cause.
Developer replies confirm district-sensitive prices and multi-factor customer volume; EA 0.11 shows campaign effectiveness before purchase.
Procedure: establish a functioning no-change baseline; tune obvious price resistance; confirm spare capacity; test one campaign; compare contribution profit rather than revenue
Example: A store already reaches its twenty-customer equipment limit at peak. Adding advertising raises cost but cannot pass that bottleneck; adding the missing equipment may be the rational first move.
When a campaign produces no profit increase, check whether customers, station capacity, product availability, or pricing satisfaction was already limiting the business. Inspect price by SKU, pricing satisfaction, hourly customers, effective capacity, promotion, campaign cost, and contribution per customer before moving to a costlier branch.
Record baseline and test prices, campaign type and effectiveness, units sold, average contribution, peak customers, and complaint changes in BizMan, and pair it with the neighborhood demand and provider snapshot from Market Insider plus the matching cost period in EconoView. Use price by SKU, pricing satisfaction, hourly customers, effective capacity, promotion, campaign cost, and contribution per customer as the decision signal only when the recorded controls remain comparable.
No verified complete 1.0 promotion equation is public, so reject confident formulas that translate traffic and marketing directly into exact customers.
Separate reversible and irreversible actions. baseline without changes can be tested with a short observation window, whereas lease commitments, broad fit-outs, and large stock purchases persist. Resolve reversible uncertainty first and preserve enough cash to act on what the evidence reveals.
Do not test a billboard and a price increase on the same day. First establish stable pricing satisfaction and unused capacity; then add one campaign and calculate whether additional completed customers cover both their inventory contribution and the campaign's daily charge.
Action checklist
- Baseline without changes.
- Fix price resistance.
- Verify spare capacity.
- Test one campaign.
- Compare incremental profit.
| Checkpoint | Pass evidence | Failure response |
|---|---|---|
| baseline without changes | The record for price by SKU, pricing satisfaction, hourly customers, effective capacity, promotion, campaign cost, and contribution per customer supports the intended condition. | fix price resistance |
| verify spare capacity | The comparison includes baseline and test prices, campaign type and effectiveness, units sold, average contribution, peak customers, and complaint changes and contains no unexplained outage. | test one campaign |
| compare incremental profit | The downside remains affordable and the next trigger is written. | Pause the plan and repeat the smallest disputed test for price and promotion sequencing. |
End-of-week operating review
A good week-one decision uses a consistent evidence window and distinguishes cash movement from business profitability. Weekly totals need reconciliation before they justify expansion.
The game's management screens separate sales, inventory cost, wages, rent, marketing, and other expenses, while supplier timing can distort daily cash.
Procedure: close the measurement window; reconcile revenue and costs; inspect hourly and SKU detail; list unresolved alerts; decide stabilize, resize, or exit
Example: Monday shows a large cash outflow because stock arrived, yet the store's sales performance is unchanged. Reading the bank balance alone falsely labels Monday unprofitable.
If accounting profit and cash movement disagree, trace stock purchases, loan movements, investments, taxes, and delivery timing. Inspect seven-day revenue, cost of goods, wages, rent, marketing, finance cost, net profit, cash change, and owner hours before moving to a costlier branch.
Record daily and weekly totals, exceptions such as closed hours, deliveries, stockouts, rival events, and changes introduced during the window in BizMan, and pair it with the neighborhood demand and provider snapshot from Market Insider plus the matching cost period in EconoView. Use seven-day revenue, cost of goods, wages, rent, marketing, finance cost, net profit, cash change, and owner hours as the decision signal only when the recorded controls remain comparable.
One week is enough to expose setup defects, not enough to prove every weekday, rival, or shortage condition.
Audit the denominator whenever a ratio is used. Customer utilization needs effective capacity, margin needs selling price, runway needs conservative daily outflow, and return on a campaign needs campaign cost. For End-of-week operating review, write the denominator beside seven-day revenue, cost of goods, wages, rent, marketing, finance cost, net profit, cash change, and owner hours so a changing scale is not mistaken for improvement.
Reconcile the weekly business result with bank movements line by line. A Monday supplier payment can reduce cash while the income statement still shows a sound retail margin, whereas a large sales total can conceal wages, marketing, and expensive emergency deliveries.
Action checklist
- Reconcile cash and profit.
- Review hourly demand.
- Review SKU sell-through.
- Resolve alerts.
- Choose a documented next step.
| Checkpoint | Pass evidence | Failure response |
|---|---|---|
| reconcile cash and profit | The record for seven-day revenue, cost of goods, wages, rent, marketing, finance cost, net profit, cash change, and owner hours supports the intended condition. | review hourly demand |
| review SKU sell-through | The comparison includes daily and weekly totals, exceptions such as closed hours, deliveries, stockouts, rival events, and changes introduced during the window and contains no unexplained outage. | resolve alerts |
| choose a documented next step | The downside remains affordable and the next trigger is written. | Pause the plan and repeat the smallest disputed test for end-of-week operating review. |
Beginner diagnostic decision tree
Most early failures can be found by tracing the customer transaction from legal opening through stocked fulfillment and economic conversion. Follow the transaction chain until the first failed node is visible.
Developer capacity explanations and official requirement changes support a sequence that checks function before demand-generation spending.
Procedure: verify open status; verify mandatory items; verify staff; verify primary stock; inspect arrivals; inspect completed purchases; inspect economics
Example: Customers enter but leave. The decision tree finds missing checkout coverage, so the remedy is scheduling. If no customers entered despite spare capacity, the investigation would move to hours, demand, traffic, price, and promotion.
Do not skip from low profit directly to marketing or a larger lease. Inspect the first stage in the transaction chain that fails before moving to a costlier branch.
Record pass or fail for each node, the supporting screen, time observed, and action taken in BizMan, and pair it with the neighborhood demand and provider snapshot from Market Insider plus the matching cost period in EconoView. Use the first stage in the transaction chain that fails as the decision signal only when the recorded controls remain comparable.
Several failures can coexist; correcting the first may reveal the next rather than immediately producing ideal profit.
Use exception notes instead of smoothing unusual days away. A stockout or rival action may reveal the fragility of test staffing and stock, even though it invalidates a clean average. Report the ordinary result and the exception separately, then decide whether the operating buffer should be redesigned.
For a zero-sales store, test nodes in this order: business open, required rooms, required fixtures, correct employee at each station, primary stock on a configured display, baskets and bags, customer arrival, queue completion, then price and promotion.
Action checklist
- Test opening and requirements.
- Test staffing and stock.
- Test arrivals and queues.
- Test pricing.
- Promotion and test full economics.
| Checkpoint | Pass evidence | Failure response |
|---|---|---|
| test opening and requirements | The record for the first stage in the transaction chain that fails supports the intended condition. | test staffing and stock |
| test arrivals and queues | The comparison includes pass or fail for each node, the supporting screen, time observed, and action taken and contains no unexplained outage. | test pricing |
| promotion and test full economics | The downside remains affordable and the next trigger is written. | Pause the plan and repeat the smallest disputed test for beginner diagnostic decision tree. |
Final beginner audit
The first week is complete when the operation is independently functional, measurable, and financially survivable. Passing the audit means the store can operate and be measured without improvisation.
This standard follows the verified management loop without relying on a specific profit target or mandatory second business.
Procedure: confirm needs and transport; confirm source and lease; confirm fixtures and inventory; confirm employees and hours; confirm records and runway
Example: A modest florist that remains staffed, stocked, and measurable is a better beginner result than a glamorous high-revenue shop that requires the owner to cover every shift and emergency delivery.
Any unresolved blocking alert, repeated stockout, uncovered hour, or unexplained negative margin means stabilization is unfinished. Inspect independent operation, clean alerts, positive contribution, replenishment coverage, cash runway, and documented next action before moving to a costlier branch.
Record the final checklist, seven-day metrics, current targets, known risks, and the exact condition that will trigger expansion in BizMan, and pair it with the neighborhood demand and provider snapshot from Market Insider plus the matching cost period in EconoView. Use independent operation, clean alerts, positive contribution, replenishment coverage, cash runway, and documented next action as the decision signal only when the recorded controls remain comparable.
This audit is intentionally business-neutral and remains useful if future balance patches change which starter format is fashionable.
Before accepting the conclusion, ask whether another player could reproduce it from the recorded fields alone. If the final checklist, seven-day metrics, current targets, known risks, and the exact condition that will trigger expansion omits the business, neighborhood, hours, stock state, staffing, or costs needed to repeat the test, add the missing condition rather than adding decimal precision.
The beginner audit should end with explicit triggers: minimum cash runway, reorder point for every primary SKU, maximum tolerated uncovered hours, and the date of the next Market Insider check. Expansion begins only after all four remain stable without owner intervention.
Action checklist
- Confirm autonomous opening.
- Confirm reliable stock.
- Confirm positive contribution.
- Protect runway.
- Document expansion triggers.
| Checkpoint | Pass evidence | Failure response |
|---|---|---|
| confirm autonomous opening | The record for independent operation, clean alerts, positive contribution, replenishment coverage, cash runway, and documented next action supports the intended condition. | confirm reliable stock |
| confirm positive contribution | The comparison includes the final checklist, seven-day metrics, current targets, known risks, and the exact condition that will trigger expansion and contains no unexplained outage. | protect runway |
| document expansion triggers | The downside remains affordable and the next trigger is written. | Pause the plan and repeat the smallest disputed test for final beginner audit. |
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
What is the safest first business in Build 3674?
There is no universal winner. Restrict the candidate list to products you can currently source, then compare complete primary-product demand, competition, fit-out cost, labor burden, and remaining cash. Cheap-gift retail is a clear learning format, while coffee, florist, supermarket, fruit and vegetables, hairdresser, and fast food are also wholesaler-supported under the standard progression.
Should I follow an old gift-shop and fast-food walkthrough?
Use it only for basic interface orientation. The 0.9 tutorial and sourcing progression changed the early route, so current objectives, F1 help, Market Insider, and supplier availability must control the choice.
How long should I work my own register?
Long enough to complete any objective and obtain a clean operating baseline. Replace yourself when an employee can preserve service and the released time can be used for supply, recruitment, measurement, or expansion work.
Should I advertise during the first trading day?
Usually establish a functional baseline first. If the shop is missing stock, staff, or capacity, marketing makes diagnosis harder and may pay to send customers into a bottleneck.
When is the first store ready for expansion?
After a comparable multi-day window shows repeatable positive contribution, complete staffing, stable replenishment, no blocking warnings, and cash remaining after the next setup without consuming payroll or stock reserves.