Hundreds of posts, and no memory of them
Since late 2024, I’ve posted on LinkedIn every single day. But once I posted something, it almost always evaporated from my mind, given the sheer volume of topics I was covering. I couldn’t answer basic questions: Have I already written about this? Which topics actually travel? What did I pin under that carousel?
Scheduling tools are built for posting, not for archiving. I wanted an archive I could search and analyze.
Three decisions behind it
Library and data before scheduling
LinkedWin’s first job is looking back, not posting forward. Import scripts pull content, including links to individual posts, from LinkedIn’s analytics exports and Favikon’s CSVs into one record, tagged by topic and hashtag and refreshed every four hours.
A composer built around my habits
LinkedIn’s own composer is built for everyone. Mine is built for how I actually write. It has a palette of the special characters I use, saved footer templates, @mentions, and a staging area for the pinned first comment that goes out with almost every post. The pinned comment used to live in a notes app and get pasted in after publishing. Now it gets drafted alongside the post.
Built, but not wired, for automation
I wired the app to schedule and even publish posts through a third-party scheduling API, but I haven’t switched it on, for a simple reason: my LinkedIn account is a professional asset, and automated activity is one of the fastest ways to get an account restricted or banned. Since I can write and schedule right in LinkedWin, publishing by hand costs seconds of my day. Losing the account would cost me my audience.
Results
With 557 deduplicated posts in one place, I could finally audit my own feed, and the audit changed what I post. I identified three topic lanes that performed well for me and started optimizing for saves and dwell time instead of reactions.
| 557 posts | 3 topic lanes | Every 4 hours |
|---|---|---|
| Deduplicated into one searchable archive | Found in the audit, and now the core of what I post | The archive refreshes from my exports |
Next steps
I’d like to run the publishing pipeline on a sandbox account, so I can test it before it gets anywhere near my real one.