Key takeaways
- Every morning, a scheduled task pulls three unused phone clips from my iCloud library into a working folder, no editing, no captions, just the raw pull.
- This pipeline used to do more than that. It used to caption and stage three posts a day on its own.
- We retired that second half on purpose, once a bigger system took over staging for every content lane at once, so the two pipelines wouldn't quietly compete with each other.
- What's left is a small, honest tool that does one job: keep a folder full of ready-to-use clips so a bigger system never runs dry.
- The lesson wasn't about the code. It was about noticing when a tool you built has been quietly duplicated by a better one, and having the discipline to cut the redundant half instead of running both forever.
Consistency is the hardest part of content, not creativity. Anyone can post something good once. Posting something every single day, on a schedule, without it turning into a chore that gets skipped the first busy week, is the actual problem most people never solve. The slice-of-life pipeline started as an attempt to solve exactly that, using nothing more dramatic than phone clips I was already taking.
What it does now
Every morning at 10:30, a scheduled task looks at my iCloud Photos library, finds videos I haven't used yet, checks that they're actually readable, and pulls three of them into a working folder. That's it. No editing, no captions, no posting. Just a reliable morning delivery of raw material that's already been screened for quality, so there's never a morning where the honest answer to "what should I post today" is a blank page.
It sounds almost too simple to be worth writing about, and that's kind of the point. The job this tool does is small on purpose. It solves exactly one problem, running dry, and nothing else.
It used to do a lot more
Early on, this same task didn't stop at pulling clips. It also wrote captions in my voice for each platform and staged three draft posts a day, on its own, every morning. For a while that worked fine, since it was the only system doing that kind of staging.
Then a bigger system got built to run the whole social calendar across every content lane at once, reels, carousels, stories, static posts, pulling from a shared cadence and a shared approval inbox. And that system could pull from the exact same folder of unused clips this smaller pipeline was already filling every morning. Once that existed, the slice-of-life task's own captioning and staging step wasn't adding anything. It was quietly duplicating work the bigger system already did, just through a separate, unreviewed path.
The honest fix was cutting half the tool, not adding to it
The obvious instinct when you notice two systems doing the same job is to make them talk to each other, add some coordination logic, build a check so they don't step on each other's toes. We looked at that and decided it was the wrong fix. The simpler move was retiring the half of this task that had become redundant, and keeping only the part nothing else did: the daily pull that keeps the folder stocked. Now the smaller task does one job well, and the bigger system does the staging, captioning, and approval routing for everything, this lane included, in one place instead of two.
Why this matters for Bay Area and San Jose businesses
Most small businesses build their content process the same accidental way this pipeline started: a tool gets added to solve one problem, then grows extra features over time because it's easier to bolt something on than to step back and ask whether a newer system already covers it. That's how a business ends up with three different places tracking the same customer, or two different tools both trying to post to the same social account. The fix is rarely "build one more system to reconcile them." It's usually going back and cutting the part that's been quietly duplicated, even when the tool that started it all still technically works fine.
Practical steps
- Notice when a new, bigger system starts covering ground an older tool already handles. Overlap is easy to miss because both pieces still technically work.
- Resist the instinct to add coordination logic between two overlapping systems. Ask first whether one of them should just do less.
- Keep the smaller tool if it still does one job well, and cut only the part that's been duplicated, not the whole thing.
- Build daily raw-material pulls, whatever your version of unused phone clips is, so a bigger content system never runs dry on any given morning.
- Revisit this every few months. Systems that made sense to run in parallel six months ago might not make sense today.
We build systems like this at On Point Tech Solutions in Los Gatos, serving San Jose and the whole Bay Area. Every one, you own outright, done for you or taught with a full SOP. If your own tools have quietly started duplicating each other's work, that's a fixable gap. Start at optechsol.llc.