The official gameplay premise
Steam describes a small handyman business set in a Polish apartment block in the 1990s. The stated objective is not simply immaculate work: the game foregrounds cutting costs, improvising repairs, and facing consequences. That establishes the premise, but it does not document a universal best strategy for every job.
Examples Steam names
The full-game listing specifically mentions diluting paint, laying tiles, handling furniture, and buying inexpensive tools. It also gives repairing a flooded bathroom and completing a full remodel as examples of jobs. These are official description examples, not a promise that every activity appears in the demo or in a particular order.
Planned full-game activities
An official Steam news post lists painting, plastering, tiling, electrical work, wood paneling, furniture assembly, windows, and doors among the planned full-game activities. The same source should not be read as a step-by-step objective list or control map. Exact controls, tool inputs, job sequence, and scoring rules are Pending confirmation.
Choose the right version
The free Steam demo is a separate app and is described as selected jobs with basic renovation, cleaning, and improvisation. Steam says the full version will have more tasks and tools, so a demo observation should not be generalized to the complete game. Both Steam listings identify the experience as single-player.
Saving and practical limits
Steam lists Save Anytime for the full game and demo, while only the full-game listing currently lists Steam Cloud. The official sources do not state a save-file path, autosave behavior, cross-device timing, or demo-to-full transfer policy. Those details are Pending confirmation.
Read the official wording at the right level
Steam's store description is useful for understanding the game's stated premise, because it identifies the setting, the handyman-business role, and examples of cost-cutting work. It is not a manual: it does not map keys or controller buttons, define every objective, explain how money is calculated, or state which shortcuts succeed in every job. A reader can use the examples to recognize the intended play style, but a complete tutorial remains Pending confirmation until it is documented or reproducibly checked in the released build.
The evidence was collected from Valve's full-game metadata and its official news feed, rather than from a third-party guide. That source hierarchy supports factual descriptions of what Steam and the team announced, but not unobserved outcomes from a particular repair. If an article claims a guaranteed result, exact route, or optimal profit method, the claim needs release-build evidence that is Pending confirmation here.
Keep pre-release claims separate from confirmed play
The official August 11 news item adds a fuller list of activities, including electrical work, furniture assembly, and fitting windows and doors, but it was published before the scheduled release. It supports a statement about planned full-game content, not a claim that every activity was already accessible, identical in the demo, or finished in a particular way. Completion conditions, tool unlocks, contract payouts, penalties, and the final campaign sequence are Pending confirmation.
The publication time shown by the official feed is useful context because it locates this promise in the pre-launch period. It does not make the announcement false, but it means readers should distinguish planned content from a verified post-launch inventory. A later patch, omitted activity, or changed interaction cannot be inferred from the source snapshot and is Pending confirmation.
Start with the version you can identify
The official demo page is the clearest place to try a verified public build because Valve marks it as a free demo and identifies its app ID. Its description deliberately limits the scope to selected jobs and basic renovation, cleaning, and improvisation, while pointing to additional tasks and tools in the full version. That boundary matters when reading guides: a statement about a demo job should not be presented as a universal solution for the full game, and a full-game feature should not be promised in the demo.
The demo and full game also have separate Steam metadata, including different storage figures and different cloud-feature listings. This makes version labels necessary when reporting a bug, a save observation, or hardware behavior. Whether content, saves, or settings pass from demo to full is Pending confirmation because neither record publishes that policy.
A fact-bound checklist before following a guide
First, verify whether the page or video names the demo or full-game app, because those are distinct Steam records with different stated scope and storage requirements. Next, check whether a claimed mechanic comes from Steam's own description or news rather than from an unlabelled player anecdote, especially when it concerns progression, profitability, or a workaround. Finally, recheck the official store page after launch for build-specific information; controls, exact objectives, and validated job solutions are Pending confirmation in the pre-release record used here.
This approach leaves room for later hands-on documentation without treating speculation as a fact. It also makes it possible to correct a guide when the live page changes, rather than silently carrying forward a pre-release statement. The current store build, current patch notes, and player-tested walkthrough details are Pending confirmation until independently checked.