Money in the Rain98 Demo connects small jobs at home to living expenses, purchases, outings, and more time with Reina. The safest strategy is not to grind blindly. Identify the next visible goal, earn toward it through an available piecework activity, keep a reserve until the scene is clear, and trust the balance and result screens in your installed Demo.
No reliable public source establishes a permanent “best” job, exact universal payout, or required cash total for the whole Demo. Those values can vary between the October 16 public build and older event versions. Use this guide as a decision method rather than a price list.
Read the economy as a story loop
1. Find the need
Finish the conversation and identify whether the next step is food, an outing, a household expense, an activity, or an optional period object.
2. Choose available work
Open the piecework choice offered in the current apartment state. Learn one complete task cycle before trying to improve speed.
3. Confirm the result
Read the displayed earnings and compare the balance with what you recorded before the job. Do not import numbers from a preview.
4. Spend with a purpose
Fund the visible scene first. Preserve some money when the following request, shop inventory, or activity cost is not yet known.
The loop matters because cash is an enabler, not the Angel Passport itself. A work result can create a spending opportunity; a later shared experience may produce a sticker when the game explicitly presents one. Repeating paid work does not automatically create memories.
Earn through piecework without wasting attempts
Public hands-on reports describe home jobs such as filling gacha capsules and recreating a picture with beads. The capsule task involves preparing a capsule, placing an item inside, and moving the completed unit to its destination. The bead task asks the player to reproduce a shown pattern within the activity’s own limits.
Begin slowly. Identify the source area, assembly area, accepted destination, and result state. Complete a single unit from start to finish. Once it registers, shorten pointer travel and prepare the next unit. Starting several objects before you understand the accepted state can leave a screen full of partial work that earns nothing.
For pattern work, compare placement with the reference rather than filling the grid from memory. Use stable landmarks—corners, color groups, or a distinctive shape—to anchor the rest. If the result is imperfect, note what the game actually credits. A lower payout is evidence about that attempt, not proof of a fixed penalty table.
The Gacha Capsule guide and Bead Picture guide separate the two interaction styles.
Rank purchases by what they unlock now
Rain98 includes recognizable late-1990s toys and media. Their presence does not turn the Demo into a conventional collectible economy. Read the item’s displayed description and observe what the resulting scene does before assigning it a resale value or completion role.
Keep a tiny ledger, not a spreadsheet
Before a work choice, record only four facts: current balance, intended purchase, selected activity, and final balance. This is enough to catch a failed result, compare two activities in the same build, and recognize whether a purchase changed the story.
Do not compare your number with another player’s result unless the AppID, public date or version, platform, task outcome, and difficulty state all match. Event attendees often played shorter or earlier slices. A BuildID from a tracking site is also not a player-facing balance version.
If an activity has a score and a cash result, keep them as separate fields. A higher score may correlate with earnings in that task, but one observation does not prove the conversion formula. The displayed cash is the amount you can plan around.
Recover from an empty or low balance
First, finish any open conversation and return to the apartment state where jobs are offered. Look for an available piecework choice rather than restarting the story. If a task appears but pays nothing, repeat one clean unit and verify that the completed object reaches the submission area before time ends.
If the result screen showed money but the balance did not change, capture both screens, exit to a normal menu, and relaunch through Steam. Preserve the save. Do not edit files, install a trainer, or use an unofficial build to repair a Demo economy issue.
When a desired optional item remains unaffordable, move the story only if the current objective permits it. A later work opportunity may be more natural than repeating the same task. Public evidence does not establish that every activity remains infinitely farmable in every scene.
Avoid false economy shortcuts
There is no supported exchange from Steam Achievements to in-game money, no documented real-money store, and no evidence that Angel Passport stickers can be sold. Treat all three as different systems. Similarly, an object mentioned in a preview may be unavailable in your current chapter rather than secretly locked behind a cash threshold.
Save editing can break story flags that connect purchases to later dialogue. Even when a number can be changed, the game may not recognize the scene that should have produced it. The reliable route is to use the official activity, read its result, and spend through the presented interface.
For the public Demo, the useful money rule is simple: earn for the next named need, verify the result, and keep enough flexibility for the next scene. That supports the story without turning Reina’s daily life into an unsupported optimization problem.