> @CaseyBuildsIt

I build tools. Then I put the build on YouTube.

SEO tools. Web apps. Focused utilities I choose to ship — not a repair queue. Watch the work happen, then use what makes it out alive.

See what’s shipping

> ls ./tools

What I’m building

A short list of tools I choose to make — then document in public.

Sites, admin panels, and product UIs I design and ship end to end — Flask, App Engine, Firestore, and a UI that doesn’t look like a default template.

Index checkers, Search Console workflows, bulk utilities — tools I’d want in my own stack. Built for operators, not course funnels.

Every tool gets a public trail: what I’m making, why it exists, and how it works. Subscribe for the builds — use the tools when they ship.

> stack --list

> ./pipeline.sh

01
Pick the tool
Something worth building — a clear job for SEO or the web, not a feature salad.
02
Build in public
Design, code, and ship decisions on camera so you can follow the real process — not a highlight reel.
03
Publish the product
Live URL, docs in The Files, and a YouTube episode you can actually learn from.

Read the build notes, watch the videos as they go up, or suggest a tool you’d like to see built.

Read The Files