Big Ambitions Product Pricing: Test Better Prices

Choose a local starting price

Check the product's current selling price and the competitor information available in BizMan. The developer confirmed in March 2024 that the business page can show the lowest competitor price. This is a comparison point, not an instruction to undercut every competitor. Your costs and the response of your customers still decide whether a price is useful.

Record the neighborhood with the price. A developer pricing explanation distinguishes products and districts, so do not copy a successful branch's entire price list into another area without testing it there. Include the current game version in your notes if you intend to reuse the result after an update.

Run a single-product price test

The developer's March 2023 procedure is to raise a price gradually, wait a day or two, and inspect pricing satisfaction in BizMan > Insights. A separate developer reply recommends changing one item at a time because store-level feedback otherwise makes the offending product hard to identify. This is a practical experiment, not proof that a satisfaction threshold always maximizes profit.

Choose a product with stable availability. Keep opening hours, staffing, advertising, and the rest of the price list as steady as possible. If stock runs out during the test, mark that day as disrupted: the missing sales cannot tell you cleanly whether shoppers rejected the new price.

• 1. Note the original price, unit purchase cost, units sold, and pricing feedback.
• 2. Change only the chosen product by a modest amount you can compare easily.
• 3. Let completed trading days pass before inspecting the result.
• 4. Compare units sold and gross contribution alongside pricing satisfaction.
• 5. Keep or reverse the change, record the result, and only then test another product.

Compare money earned after product costs

A higher selling price can earn less if too many sales disappear. For retail stock, compare units sold × (selling price − unit purchase cost). This is ordinary bookkeeping for your experiment, not a hidden formula for the game's complete profit calculation. Rent, wages, marketing, and other expenses still need to be deducted to assess the business.

Consider an invented example: selling 100 units at a price of 12 with a cost of 7 gives 500 before other expenses. Selling 75 units at 14 gives 525. The higher price improves that product's contribution in this example despite fewer sales. Use your own numbers; the example is not a recommendation for any particular item.

Office services need a different cost check because payroll matters more than a purchased retail unit. Compare service revenue with the staff needed to deliver it. A fee that attracts extra clients can disappoint if serving them requires more wages than the additional income covers.

Keep supplier costs and customer prices separate

When a product's margin changes, inspect the amount you pay as well as the amount you charge. The developer's April 2023 importing explanation connects contract pricing with the import index and Purchasing Agent skill when the contract is created. A copied sales price therefore does not imply that two businesses have identical margins.

Our practical recommendation is to note the supplier cost on every pricing comparison. If a new contract changes that cost during the test, split the results into before and after. Otherwise a purchasing improvement can look like a successful retail price increase, or a cost rise can disguise one.

Use the Pricing Manager after establishing your baseline

The official 1.0 changelog introduces a headquarters Pricing Manager who can change item prices across an entire neighborhood. Higher-skilled managers also offer daily price suggestions. Check which businesses a change will affect, then compare the results with your recorded baseline before accepting another broad adjustment.

In June 2023, the developer explicitly described the earlier cheat sheet as out of date and invited community price suggestions. That history is a reason to date reference tables and retest them, not a reason to publish their old amounts as current maximums. Product mix, neighborhood, employee state, and later balance changes all deserve checking.

Repeat a targeted test when pricing feedback changes materially, a supplier contract changes, or a branch moves. Avoid resetting every price at once simply because one product performs badly. Preserving a known baseline makes the next decision easier to explain.

Product pricing questions

Should pricing satisfaction always be perfect? It is useful feedback, but it does not by itself show the highest profit. Compare the income and costs of the alternatives.

Should I copy the lowest competitor? Use it to understand the local market, then test. Matching a rival is not evidence that your costs are covered.

Why did sales fall after a price change? Check stock, staff cover, trading hours, and local competition before attributing the entire decline to price.