The Bills Must Be Paid skill tree offers multiple paths, so the useful question is not “which node is strongest?” but “what is ending this run?” The official Steam listing names grip strength, caffeine, gym, wrist and luck, alongside abilities such as rock rain and an electrified hammer. Those names are reliable categories; their current costs, scaling and unlock requirements must be read from the active build.
Match a branch to a problem
Grip strength is the first branch to inspect when the hammer feels weak or a target takes too many contacts. Caffeine and gym are useful labels for stamina or physical-output experiments, but do not assume their exact effect without reading the current node text. Wrist can matter when speed or repeated swings are limiting your income. Luck is a riskier choice when the run depends on random loot: it can address variance, but it cannot guarantee a specific piggy drop.
Active abilities are route tools
Rock rain and an electrified hammer are named by the official description as examples of abilities deeper in the tree. Treat them as answers to field pressure. A clearing ability can be valuable when targets cluster or when a bill is close, while an elemental or special hammer effect may be more useful when ordinary damage is the problem. Test the ability in the situation that caused you to buy it; a showcase activation in a quiet field says little about its practical value.
Spend with a checkpoint
Before buying, note your stamina, current bill state, remaining cash and selected hammer. After buying, test only the node’s intended effect for one run. If the run improves, keep the observation; if it fails, record why. A route that looks slower can still be better if it reduces missed swings or keeps enough stamina to pay the next bill.
Avoid inherited certainty
Do not import unrelated code lists, unit tiers, rarity tables or old demo math into this game. Do not label an upgrade “best” from a single lucky loot roll. Use a dated screenshot or the current in-game wording when you report a numeric effect. For weapon trade-offs, read Hammer Comparison; for post-bankruptcy systems, read Prestige, Rings and Bracelets.
Sources
Branch and ability names come from the [official Steam listing](https://store.steampowered.com/app/4421010/Bills_Must_Be_Paid/ “Official Steam listing” rel=“nofollow ugc”). Exact node effects and prices are live-check information.
Three experiments that stay useful
For a stamina experiment, keep the hammer and target route stable and compare how far the run gets before the hand is tired. For an accuracy experiment, test a stationary target and then a moving one while keeping bill state similar. For a loot experiment, observe several piggies rather than one lucky result. These experiments isolate the kind of problem each branch may solve without claiming a universal numerical effect.
Perk timing matters
A perk offered after payment can change the value of a skill-tree purchase. Read the perk before spending, and ask whether it solves the current bill, next target or future run. If it is temporary, do not describe it as permanent. If it persists through bankruptcy, confirm that in the current post-run screen. A build log should contain the exact wording, date and product scope.
When to change branches
Change branches when the original hypothesis is disproved or the build changes. Do not switch because one run had unusually good or bad loot. If the game adds a node, place it in the update tracker first and wait for enough current evidence before assigning it a recommended route.
Keep a branch hypothesis
State the problem before selecting a branch: exhaustion, missed contact, slow clearing or unstable loot. Test the smallest relevant change, then compare the same route and bill state. If the outcome is mixed, report the uncertainty instead of turning one run into a best-build claim. Keep exact costs and node effects tied to the current screen. Note whether the effect lasts through bankruptcy before calling it permanent.