06 — Distribution

Social

Multi-brand content generation and scheduled distribution to LinkedIn, X, Facebook and Instagram — fed by the same RSS the blog publishes. The loop HubSpot used to close, on infrastructure a vendor cannot switch off.

Marketing · Multi-brand social.maplesage.com
Request a live walkthrough Book a call

The product

Captured from the running system
Product screen
One scheduling calendar across brands and platforms
Product screen
Platform-specific copy generated per post
Product screen
RSS in, scheduled distribution out — the loop closed
How it's built

New posts publish from the Astro build to /rss.xml. Social ingests that feed on its existing RSS pipeline, drafts platform-specific copy, and schedules distribution across LinkedIn, X, Facebook and Instagram.

It is multi-brand: each brand has its own tokens, voice and schedule. Generation runs on Azure OpenAI with Gemini as a second model. A HubSpot API client keeps CRM in the loop where it still matters.

It runs on Azure App Service with Azure Blob for posts, blogs and tokens — deployed by GitHub Actions, with a second workflow driving the scheduled-publish cron. It is the one system on this list that is both live and revenue-shaped today.

Next.js 16React 19Azure App ServiceAzure BlobAzure OpenAIGeminiHubSpot API
On request, not on a schedule

The cluster behind Social comes up when someone asks to see it. Ask.

Request a live walkthrough See the rest of the work