Case study · Pipeline
From a blog post to LinkedIn — in one button.
Writing a post twice is a tax on shipping. So I built a pipeline into the site admin that does the second copy for me, while keeping the original voice intact.
- Role
- Builder · Designer
- Stack
- Lovable · Supabase · Buffer API
- Status
- Running in production
- Year
- 2026
The problem
Every post on simeonherbert.com deserved a LinkedIn version — but doing it by hand meant copy, paste, reformat, fight with line breaks, pick an image, and then inevitably ship the post a week late. The friction was killing the cadence.
The pipeline
The blog admin — built in Lovable, backed by Supabase — has a character counter built in that tracks against LinkedIn's 3,000 character limit as you write. When you're ready, you hit Schedule via Buffer and it calls a Supabase Edge Function that hands the post off to Buffer, which queues it for LinkedIn at the right time. If the post is too long for LinkedIn, the editor prompts for a shorter version and appends the canonical link automatically.
One source of truth. The blog stays canonical. LinkedIn becomes the megaphone.
What I'd change next
The short-version prompt is currently manual — I want an AI step that drafts the LinkedIn teaser for me given the full post, so I'm editing rather than writing from scratch. The failure path when Buffer throttles also needs a friendlier retry than a toast notification that disappears.
Outcome
Posting cadence held for a full quarter without a Sunday-night panic. The LinkedIn versions out-perform the ones I used to write manually — probably because they actually ship.