799 files in Drive root. 13 years of output. 2 hours to sort. 3 hours to automate.

Found 799 files sitting in my Google Drive root last week. Thirteen years of daily output with no filing system.

Rough breakdown by type: professional/consulting work (~200 files), book-related drafts and outlines (~180 files), app builds and tech docs (~120 files), personal daily writing (~200 files), miscellaneous invoices and cover letters (~99 files). Date range: 2013 to 2026.

What I did

Manual sort took 2 hours. Created a folder structure that matched how I actually work now. Then built a classification script (Python, about 120 lines) that reads file names and dates, infers content type, and routes to the right folder. Added a weekly cron job to catch anything new landing in root. Logs every move to a Supabase table.

Build time: 3 hours. Runs indefinitely.

Why I'm sharing this

The pile is proof of output, not evidence of disorganization. It accumulated because I was creating.

17 published books. 6 apps under the ARL umbrella, 4 live in the iOS App Store. A content engine publishing to 40+ accounts from a single Supabase pipeline. Senior enablement role at a public company held simultaneously through most of this.

The pile built up because the creating was the job.

If your file structure is chaos, I'd argue that's a sign of the right priority. The cleanup can wait. The building can't. Build the capture system before you need it, though. The routing layer should exist on day one, not after 13 years.

Happy to share ARL MRR and conversion rates in the comments if that's useful context.

What does your file structure look like? Is this a solo founder thing, or do we all eventually hit 799?