Build a Phone Empire lets you set the price before handing a product to the team and watching live sales. No official public source publishes a universal best margin or demand formula. Build your own current-version curve: record product cost, choose a reasonable starting price, launch, observe review and sales, then change the price in small steps on a closely matched device.
Establish the cost baseline
Record the total product or part cost displayed by the current designer and any launch commitment that matters to your comparison. Keep the same design, parts, in-game year, region, and marketing when testing price. If any of those change, label the result as a new baseline instead of a pure price test.
Cash cost and sale price are not the only factors in profit, but they are the fields you can control and record directly. Do not publish an exact margin formula unless the live interface exposes every required term and repeated tests reproduce it.
Choose the first price
Pick a price above the displayed product cost that leaves room for profit while remaining plausible for an unproven design. The purpose is not to hit perfection; it is to create a measured point. Save the price before launch.
If the game previews demand or another response, record the exact label and value, but still compare it with the actual live sales. A preview can change with the product state or update.
Run matched price tests
- Save the complete design, parts, year, region, and campaign.
- Launch at the baseline price and wait for a meaningful sales direction.
- Record critic feedback, sales, and cash outcome shown by the game.
- Rebuild or reuse a closely matched product.
- Change only the price by a small, clear step.
- Observe the same amount of game context where practical.
- Compare demand and ability to fund another cycle.
Two or three controlled points are more useful than a dozen unrelated launches. They show whether the current market tolerates a higher price or responds to a reduction.
Diagnose the result
Strong review, weak sales
Price or launch reach is a useful next test. Keep the product design stable.
Weak review, weak sales
Repeated discounting may not solve the product. Improve one design or part choice.
Healthy sales, thin return
Test a small increase or reduce a cost that does not improve the result.
Healthy sales, funded next cycle
Preserve the baseline before testing one improvement.
Use the actual current labels. “Strong” and “healthy” describe whether the result supports your next decision; they are not permanent thresholds.
Price new device families carefully
Tablets, smartwatches, earbuds, foldables, and laptops are research unlocks. Do not copy a phone margin directly to a new family without reading its current costs and market response. Build a conservative first device and create a fresh baseline.
Record unlock state, year, parts, development cost, region, and review. A later family may operate under a different market context even if the price control looks similar.
Marketing and price
Marketing can change launch reach, so keep the campaign stable during a price test. If you switch to a stronger campaign at the same time as a lower price, higher sales cannot be assigned to one choice.
After a price range is understood, run a separate campaign test at the most useful baseline. The Marketing Guide explains that sequence.
Regions and rivals
A price that works in one region may not prove the same result elsewhere. When a new region unlocks, bring a known design and baseline price first. Observe the result before adjusting. Record the current rival state and any displayed regional effect.
The public description confirms regions and rivals but not a demand modifier table. Leave those values unset until the current interface or repeated live tests support them.
Passes and comparisons
The official 2x Money pass doubles money from every phone sold. It can change cash outcome without proving that demand or price acceptance changed. Record ownership and compare sales units or the game’s other demand indicators when available.
Hyper Speed can make observations arrive faster, but use comparable game time or state. Extra Design Slot can support parallel tests, but keep records separate so the products do not become mixed.
Common pricing mistakes
- Using one universal percentage for every year, device, region, and update.
- Changing product quality and price together, then claiming price caused the result.
- Reading one sale tick as the full demand curve.
- Comparing doubled income with a free account without disclosing 2x Money.
- Ignoring marketing or region changes during a price test.
- Raising price after one good review without preserving the successful baseline.
- Discounting a weak product indefinitely instead of responding to critic feedback.
Pricing record
Save: date; in-game year; device family; design and parts; total shown cost; price; campaign; critic review; live sales direction; region; rival state; 2x Money status; cash before and after; and next test. Unknown demand coefficients stay blank.
This record lets you answer the practical question—what price should I try next?—without claiming a permanent formula the developer has not published.