A full mailbox cost us eight days of email. Here is the fix we are building.

A bounced email is invisible to the person who owns the inbox. That is what makes storage the most expensive boring problem in a small business.

This is a true story from inside Insert Fuel, and what Insert Fuel does about it now.

The scene every owner has lived

You see "storage almost full." You click away. Two weeks later a customer says they emailed you and got an error. In our case it was the founder's own inbox: 886 GB sitting in a 300 GB plan, and mail to him stopped for eight days in June 2026. It had happened once already in November 2025.

The cause was not complicated. Photos, video and attachments live in several accounts, under several owners, with no one watching the limit across all of them.

What it cost us

From our own records:

• More than 39 months of recurring warnings, 44 of them from Google in ten months.
• 8 cleanup tasks, about 92 hours of builder time.
• One freelancer ($82.63) who delivered a guide, not a migration.
• Roughly $2,300 in storage, recovery and help, and $40.64 a month for plans that did not solve it.
• About 40 hours of founder time, which is the expensive part.

Every one of those fixes worked for a few months and then expired, because each fix was a project, and the problem was a process.

What Insert Fuel does about it

We stopped treating storage as a cleanup task and gave it a home inside Insert Fuel. This is the plan we are building now, not a finished product:

• One archive we control. A Hetzner Storage Box as the primary copy, plus a cold copy at a second provider. Two copies, two companies.
• Servers do the moving. Our workers on a Hetzner server in Finland pull data straight from Google Takeout to storage, so no one's laptop fills up and a failed transfer resumes.
• Albums and dates kept, because the export carries them.
• Fingerprints. Every file gets a hash, so duplicates across accounts are stored once.
• AI search inside Insert Fuel, so finding a file is a question, not a hunt.
• Quota watch (next). Read storage per account and raise a task before a mailbox fills, not after it bounces.

The stack

Next.js on Vercel for the app. Supabase Postgres and storage for the records. Claude behind Fuela for search and answers. Hetzner for the heavy work. Nothing here is exotic, which is the point: any business can run this shape.

What to take from it

Count your accounts. Find the ones holding the most data, and ask who owns the limit. If the answer is "someone, probably," you have our June 2026.

If you want to see how we run this, come to the free Thursday class and I will walk through it live.