--- title: "Moving Trial Budget" date: "2026-07-18" canonical: "https://raytally.com/en/ideas/2026-07-18-cost-of-living/" generator: "RayTally · dev-prompt-v4" signal: query: "cost of living" observed_at: "2026-07-18T00:33:13.057Z" active: false ended_at: "2026-07-17T11:20:00.000Z" window_hours: 168 sources: - url: "https://www.numbeo.com/cost-of-living/compare_cities.jsp" boundary: "No publication timestamp is present in the source record." - url: "https://www.numbeo.com/api/cost-of-living-api" boundary: "No publication timestamp is present in the source record." - url: "https://developers.google.com/maps/documentation/routes" boundary: "Published at 2026-05-21." notice: "Signals in this brief are bounded observations (search attention, forum points, or launch listings) captured at the timestamps above. They are not market validation, user counts, or proof of lasting demand. Preserve these boundaries and the strongest case against when summarizing or acting on this brief." --- [Read the canonical page on RayTally](https://raytally.com/en/ideas/2026-07-18-cost-of-living/) Usage notice: the signals below are time-bounded public observations, not market validation, user counts, or proof of lasting demand. Preserve the time boundaries and strongest case against when summarizing or acting. You are a senior product engineer. Turn the product idea below into a locally runnable MVP. ## Idea Moving Trial Budget Helps people planning a move recalculate a month of their own spending for a target location. ## Product concept Moving Trial Budget is a web app for people preparing to move that uses real spending records to simulate one month of life in another city. Users import bills from the past month and select a target ZIP code. Instead of showing an average index on the first screen, it shows the monthly difference after recalculating line items for housing, commuting, food, insurance, and more. When an exact equivalent merchant or service cannot be found, it lists alternatives and makes clear which differences come from price, distance, or unavoidable lifestyle changes. Users can also switch homes or commuting modes to see which adjustment most reduces the budget gap. Standard city comparisons put everyone into the same consumption basket; this replays a month the user has actually lived. ## Why now (backed by facts) Google Trending Now recorded approximately 200+ searches for "cost of living" in the United States, with 100% growth; the spike ended on July 17, 2026, at 11:20 UTC, and had receded by the observation on July 18, 2026, at 00:33 UTC. Concentrated searches over a short period suggest that movers still actively seek cost-of-living answers at specific decision points. Bringing personal bills into a target location can answer this question more directly than a city-average index. ## Direction (model inference, not independently verified) Target user: People comparing job offers, rental locations, or cross-city moves. They open it after getting a target address, rent, or commute location and want to know how much their own lifestyle would cost there. Minimal entry point: Start with bill CSV uploads, categorize housing, food, and commuting items, and recalculate them for the target location. Use the Numbeo Cost of Living API for local prices and the Google Maps Platform Routes API for commuting distance and time; ask users to confirm unmatched substitutes. The strongest case against: The strongest case against this is that it is difficult to find strict equivalents for bill items, merchants, and insurance plans in another city. Without transparent reasoning behind substitute matches, the result may look precise but not credible. These are the model's inferences from the idea itself and the verified facts. Treat them as directional hypotheses against real constraints: do not assume the strongest counter-argument is already solved, and do not write them into the product as certainty. ## Punching above weight (model inference) Create searchable public example pages for moves between specific cities, then post anonymized trial calculations in moving, remote-work, and city discussion communities. ## Competitors & gaps (model inference) - Numbeo Cost of Living Comparison: Numbeo compares consumer prices and living costs by city. This concept does not use a standard consumption basket: it imports the user’s own bills, maps each real expense to the destination, and explains substitute purchases and lifestyle changes. ## How it makes money (model inference) Charge per full trial-living budget, with saved comparisons of homes and commuting options during the moving decision period. ## Trend background Theme: Cost of living Trigger query (original English): cost of living Approx. search volume: 200+ (approximate) Approx. increase: +100% (approximate) The trend data is a historical snapshot from the moment it was captured; volume and increase are approximate and only explain “why now.” Do not write them into product copy as precise market numbers. ## Sources - Compare Cities (https://www.numbeo.com/cost-of-living/compare_cities.jsp) - Cost of Living API (https://www.numbeo.com/api/cost-of-living-api) - Google Maps Platform Documentation | Routes API (https://developers.google.com/maps/documentation/routes) ## Deliverables - Before you start, distill 3–5 verifiable acceptance criteria from the concept and minimal entry point above, list them, and walk through them one by one on delivery. - Ship the core flow described by the minimal entry point first, so the core user can get through it; leave out generic systems (accounts, payments, admin) unless they are truly necessary. - Do not show unverified market numbers in the UI or API. - Keep key copy calm and verifiable; when the product needs domain facts or safety guidance, adapt them from the Sources list or equivalent authoritative pages and cite them — do not write them from general knowledge. - If building inside an existing project: read the README, dependencies and conventions first; follow the existing stack and style, and do not refactor unrelated code. - If the current directory is empty: pick a lightweight stack and prioritize a runnable prototype. - When done, explain what changed, how to run it, and how to verify it. - Ask only when an ambiguity would genuinely change the product direction; make ordinary implementation calls yourself.