All posts

Planning

This free site got billed a hundred and four thousand dollars

Two real cloud bills, and the prompt that shows what a change could cost before any code is written.

What to do

  1. Ask for a plan that shows what a change could cost

    Before your AI changes anything, ask it for a plan that lists the outside costs the change adds or removes[1]. A free static site on Netlify was billed $104,500 after an attack flooded it in 2024[2][3].

  2. Ask for every file it touches

    A good plan also lists the new structure and every file the change touches[1].

  3. Ask what could break downstream

    A good plan flags anything downstream that could break[1].

  4. Allow no code until you approve

    Tell your AI not to write code until you approve the plan[4].

  5. Do not count on a budget to stop the spend

    One founder had set a $7 billing budget and still ran up about $72,000 on Google Cloud[5][6][5]. Read the costs in the plan before you approve it.

The prompt

Paste this into your coding agent before it writes any code.

The plan prompt
Plan this change first. Do not write any code until I approve the plan.

In the plan, list:
1. Every file this change touches.
2. Any outside cost this change adds or removes, such as a paid service or cloud usage.
3. Anything downstream that could break.

Then stop and wait for my approval.

Use it before any change you are unsure about, and read the costs before you approve, because a cloud budget alone does not cap what you spend[5].

Did not fit in the video

The Netlify site was on the free plan, and the bill came from a DDoS attack in February 2024[2][3]. Netlify bills extra bandwidth at $55 per 100 GB, which is how a static site reached $104,500[2][3]. That was a bill, not money paid. After the story went viral, Netlify's CEO said the user was not getting charged[3].

The $72,000 case is from 2020. A startup founder tested Cloud Run with Firebase for a few hours, and the bill arrived overnight[5][6]. Google's own docs say a billing budget does not automatically cap usage or spending[5]. A budget tells you about the spend. It does not stop it.

By the founder's own account, his test missed that crawled pages can link back to each other, which caused infinite recursion[5]. That is the kind of downstream effect the third line of the prompt asks the agent to look for.

The cost line is a planning habit, not a tool rule[1]. A plan lists costs only when your prompt asks for them. One way to make a plan easier to check is to ask, for each phase, what done looks like and how it will be tested[4].

Sources

  1. joinfndrs - The $120/Month AI Stack That Ships a 5M-User App (PDF, September 2026) - planner handoff prompt

    joinfndrs.com

  2. GIGAZINE - A record that a request of 15 million yen was suddenly received from a cloud computing company due to a DDoS attack (Feb 28, 2024)

    gigazine.net

  3. Netlify Support Forums - Netlify billing horror story (Feb 27, 2024)

    answers.netlify.com

  4. Murphmaxxing - 1,000 hours of vibecoding: everything I learned, start to finish (plan prompt)

    murphmaxxing.com

  5. The Register - Google Cloud (over)Run: How a free trial experiment ended with a $72,000 bill overnight (Dec 10, 2020)

    theregister.com

  6. Milkie Way blog (founder's own account, Wayback Machine copy) - We Burnt $72K testing Firebase + Cloud Run and almost went Bankrupt [Part 1]

    web.archive.org

Want the rest? Every post, by month and topic.

See all posts