My Networking Runs Itself: The LinkedIn Pipeline That Grew My Reach While I Slept
Networking is a numbers game played with hours you don't have. Writing a good LinkedIn post takes an evening; doing it consistently takes a discipline that competes with actually building things. So I treated my own visibility as an engineering problem and shipped a product for it: an autonomous pipeline that turns my real work into scheduled LinkedIn content, publishes it, and tracks its own state — entirely on free infrastructure. My network started growing while I slept.
The architecture of showing up
The system is deliberately boring, which is the point. A GitHub Actions workflow wakes on a cron schedule. It reads a content queue, generates the post draft from the queued topic, publishes to LinkedIn, and then — the part most automation skips — commits its own state back to the repository in a published.json ledger. The Git history is the database. There is no server to babysit, no dashboard subscription, no runtime cost. If it ever misfires, the ledger is a diff I can read and revert like any other commit.
Automation with a quality gate
The word "bot" earns its bad reputation from systems that publish without judgment. Mine has a human trust boundary in the same place all my products do: the queue. Nothing enters it that I haven't decided is worth saying — the pipeline automates the showing up, not the thinking. It is the same propose/confirm split that governs my finance agent: the machine handles cadence and delivery, the human owns the content decisions that carry my name.
Consistency is a systems property, not a personality trait. If showing up matters and humans are bad at it, that is not a self-improvement problem — that is a pipeline waiting to be built.
What it changed
The pipeline did what consistency always does: compounded. Posts went out on schedule through weeks when I was heads-down shipping Sable and streamerOS — precisely the weeks I would previously have gone silent. Profile visits, connection requests, and recruiter conversations arrived on the pipeline's schedule instead of my energy level's. The product's full architecture breakdown lives on its product page.
The transferable lesson for companies
Every company has a version of this problem: work that is valuable, repetitive, and chronically skipped because it competes with "real" work — release notes, changelogs, status updates, onboarding emails, documentation refreshes. The pattern that fixed my networking fixes those too: a queue a human curates, a scheduled worker that executes, state committed somewhere auditable, and zero new infrastructure to own. I've now built that pattern three times (content, outreach, and blog publishing) — it takes days, not quarters, and it never calls in sick.