I had one source library, separate platform documents, and no trustworthy answer to the simplest question.
I made separate Instagram and YouTube upload documents for the same videos intended to promote my app. At the time, I was promoting a note-taking app I had built after work, and keeping each platform’s copy, links, media notes and upload details in its own file felt sensible.
They were supposed to stay in sync, which is the sort of sentence that sounds completely reasonable until two files have had a few months to develop independent lives.
When I opened them again, they no longer described the same library. Instagram listed videos YouTube did not. One Instagram entry still carried a YouTube tracking link. The calendar offered a third version of the week, although a row could mean planned, drafted, scheduled, attempted or genuinely public depending on when I had last touched it.

None of this came from one dramatic failure. I had simply been sloppy about keeping every copy updated, and the files had drifted far enough apart that I could no longer trust any of them.
One source library. Two upload documents. Several answers to what existed.
At first, I treated it as a bookkeeping problem. Then I tried to follow one post backwards from its public URL to the idea that had started it. That trail led through the upload documents, the calendar, the exported media and, eventually, the research system where the content had begun.
The system started with a sensible idea
I did not want to invent random posts and hope somebody cared. I started with questions people were already asking about iPad notes, Apple Pencil workflows, lecture notes, handwriting, organisation, summaries and exports. I searched for them manually on the platforms where those questions came up.
Those questions became the source material for the content. I kept the supporting notes in an LLM-backed knowledge base so a popular search phrase could not turn straight into a confident answer I could not support.
The goal was not to produce as many ideas as possible. It was to separate topics I could answer responsibly from topics that needed better evidence, fell outside the app or simply were not useful enough.
That distinction mattered around claims. A query containing “best” needed a real comparison. Prices had to be checked again before publishing. Statements about another app needed an official source, and recognition accuracy needed testing rather than optimism.
From there, the strongest answers could become short educational carousels or videos. The source would remain the same, but the presentation would later have to change for Instagram, TikTok, YouTube and anywhere else I wanted to publish it.
For a topic to move forward, its registry entry needed enough supporting material to survive that process. This gave me a useful difference between something people searched for, something I could answer and something I was genuinely ready to produce.
The research system worked. It could even reject an idea.
Research kept growing because it felt like progress
It also gave me an endless supply of tidy work. I could refine another query, check another claim or clean another row and finish the evening with a better-organised registry.
“Ready” still meant I had permission to begin.
The topic needed a script, visuals, real product screens, layout, exports and a separate version for each destination. Even a short five-slide carousel could absorb an evening before I had prepared a single upload.
When I compared the registry with the published feed, the imbalance became obvious. I had a growing bank of defensible topics and only a few finished carousels at the other end.

Deciding what deserved to exist was no longer holding me back. Moving one decision all the way to a public post was.
The difficult work began after approval
Once a topic cleared the research stage, it entered a different system.
The same underlying idea might become a carousel, a short video, an X post, an Instagram caption and a YouTube title and description. The useful observation stayed the same. Almost everything surrounding it changed.
I kept scripts, media, exports and upload instructions in separate places because each place made sense on its own. The separation became a problem as soon as I revised anything.
Updating the source did not update the Instagram copy. Fixing the title in the YouTube document did not change the calendar. Scheduling a post did not confirm that the provider had accepted it, and acceptance still did not prove that somebody else could see it.
The calendar could not repair those gaps. Putting an item on Tuesday made the week look organised, but Tuesday could mean planned, ready, scheduled, attempted or public.
Those states had gradually collapsed into one another. That was why the documents at the beginning of this story disagreed: none of them represented the complete journey.
I was saving outputs instead of their source
I had treated the final caption as the thing worth reusing. It should have been the real source underneath it.
That source might be a feature I had built, a question from the research registry, a result from a previous post or something I had learned while fixing a bug. The event and its evidence should remain stable while the presentation changes for each destination.
On X, I can spend more time on the reasoning. On TikTok, the useful visual has to arrive almost immediately. Instagram may begin with similar material but still needs its own framing. YouTube needs another title, description, thumbnail and link setup.
Copying one finished caption into every box was fast. It also produced a version that fitted nowhere particularly well.
The workflow I needed was simple enough to explain:
one real source
→ native platform versions
→ human review
→ schedule
→ provider result
→ confirmed public post
I was still the only thing keeping those steps connected. Once I wrote the process down like that, the mismatched documents stopped looking like a filing mistake. They were separate files trying to remember one shared process.
That missing connection became Sendezeit
Sendezeit grew out of that missing connection.
It starts with something that actually happened, then keeps the destination versions, media, edits, approvals, calendar entries and provider results attached to the same source.

The software can help adapt the material, but it does not decide what is worth saying or approve the final version for me. Those decisions remain mine.
It solves one specific problem
Sendezeit does not tell me whether the post was good, whether the audience cared or whether the product converted. Those questions still belong in the content, the product and the analytics.
What it can tell me is whether the right version reached the right destination, what the provider returned and where the public result lives.
You can build the same workflow in a spreadsheet: keep one source, write the platform versions beside it, review each one, add the schedule and record the final public URL. I had pieces of that system already. I built Sendezeit because maintaining the connections between them had become another job.
That brings me back to the upload documents. Their real problem was not that one contained more rows or information than the other. I had asked two separate files to remember a single moving workflow, then acted surprised when they represented it differently.
The question that started all of this was not “What should I post next?”
It was “What actually made it live?”
That sounds less exciting. It was also the question I needed the system to answer.
Thanks for reading.