The official Build a PC Empire description states that the game has 30 goals with cash rewards. It does not publish the 30 names, requirements, order, values, prerequisites, or repeatability. This page gives you a current-build method for recording and using those goals without inventing a checklist.
Build a goal record
If a field is hidden, leave it blank. Do not fill a reward with zero or assume a goal is one-time only because it has not reappeared yet.
Pair goals with normal company work
Read the active goal before planning the next product cycle. When it overlaps with a needed design, research unlock, hire, office upgrade, or launch, combine the work. This reduces the extra cash and time spent only for the reward.
If the goal requires a purchase or expansion that would break the recovery reserve, compare the displayed reward with the actual cost and the strategic value of the action. A cash reward is not automatically profitable when the company spends more to trigger it.
Verify progress triggers
Change one relevant action at a time and watch the goal counter. For a product goal, record when progress changes: design completion, development completion, launch, benchmark, sales, or another event. For research, note whether starting or completing the node matters. For hiring, distinguish candidate selection from the employee beginning work.
This approach prevents accidental credit from being assigned to the wrong step. It also reveals whether a goal description is broader or narrower than expected.
Record rewards separately
Write down company cash immediately before completion, the displayed reward, and cash immediately after. Avoid launching a product or making another purchase in the same moment. If several events happen together, mark the reward amount unverified rather than reverse-engineering a value.
Goal rewards should be treated as dated, one-time events until repeatability is demonstrated. Do not use them as recurring income in the money guide.
Handle hidden and sequential goals
The number 30 does not prove all goals are visible at once. Record the interface state and current active goal. When one completes, capture the next entry and any transition message. If a goal appears only after a year, research node, office, or go-public event, record that prerequisite.
Do not publish a 30-row list assembled from mixed saves or versions as one universal order. Different company states can reveal different conditions. Preserve the evidence attached to each row.
Goals and going public
Before going public, inspect active and completed goals. The official description confirms a reset with permanent perks but does not say whether goal progress resets, remains, or changes. Capture the goal screen before and after.
If the company is near completing a valuable goal, it may be sensible to finish and record it before resetting. The correct timing depends on the live reward and reset contract, not a universal threshold.
Goal mistakes to avoid
- Copying exact names or cash values from an undated list without seeing the current interface.
- Assuming all goals are visible or sequential in the same way for every save.
- Spending more than the reward only to mark an objective complete.
- Counting a goal reward as ordinary product revenue.
- Resetting without checking active and completed goal state.
- Treating the advertised total of 30 as evidence for any specific goal.
Current verified status
Only the count—30—and the reward type—cash—are supported by the current official public description. Every specific row remains Needs in-game testing until recorded from place 111955331745911 with date and company state.
That limitation does not make the guide empty. It keeps the goal system useful as a planning layer while protecting players from a fabricated list or stale reward table.