August 16, 2026 · the build log
Build log #1: the week we became our own ad agency
I got tired of the idea of paying for ads before I ever paid for one.
We’re a homeschool family. For the past couple of years I’ve been building the software that runs our house — the app that turns our textbooks into worksheets, the one that tracks what we cook, the chore system, the road-trip planner. Seven apps, one family, used every single day. This year I formed Family Flow LLC to take the best of them public.
Which meant marketing. Which meant either an ad budget or a better idea.
The better idea
Everything we already do is content. When we cook, that’s a video. When I make a beat on the MPC, that’s a video and the soundtrack for every other video. When a textbook chapter becomes a worksheet in front of a kid, that’s the product demo. When I fix a bug, that’s a story.
So instead of an ad budget, I spent the last 48 hours building a content engine into our own app:
- An idea bank — any of us says “that’d make a good video” and it’s captured, by voice if I want.
- Shoot days — planned sessions with shot lists, so the boring-but- necessary shots (the wide, the B-roll, the behind-the-scenes) never get forgotten. One session gets multiplied into posts for every platform.
- An approval queue — this is the part I care about most. My kids appear in some of this content. So the system is built so that nothing posts anywhere without me explicitly approving it on my phone. Not “usually.” Structurally. The publish code refuses unapproved posts, and there’s a test suite that fails if anyone ever changes that.
- A render farm — my PC takes raw clips and spits out vertical cuts with burned-in captions (it transcribes the audio itself), watermarks them, and picks thumbnail candidates. The tedious 80% of editing, automated.
Receipts
This isn’t a plan, it’s running. The first three posts — on X, Facebook, and Instagram — each went through the queue: drafted, pushed to my phone, approved, posted. The Instagram post is a screenshot of the queue posting itself, which felt right.
The launch wasn’t clean, either, and that’s kind of the point of a build log: the very first Approve tap looked like it did nothing. The write worked, but the screen watching it had died quietly (a missing database index — the query gave one cached answer and then went silent). Found it from the screenshot, fixed it two ways, wrote a test so it can’t come back. If you build software, you know: the bug five minutes after launch is tradition.
What’s next
Monday is beat day — the first instrumental gets made on camera and becomes our soundtrack. The render farm is waiting for the footage. After that, the queue stops handing me copy-paste packs and starts posting by itself the moment I tap Approve.
If you homeschool and any of this sounds useful, the app that started it all — curriculum in, worksheets and grading help and transcripts out — is opening up soon. The waitlist is on the front page. And the daily version of this log lives at Rndm Life Things.
— Tristan, Family Flow LLC