
An Agent That Watches Our Blog and Drafts the Social Posts
Spadoom
SAP CX Partner & Consultancy
Publishing a blog post is the easy half. The other half is telling people about it: a LinkedIn post, something shorter for X, an Instagram caption, and if you run country pages, the Italian variants on top. That work is small, repetitive and endlessly postponable, which is why it reliably did not happen.
So in August we taught our own product a new trick. Engage Social, our social publishing tool for SAP Sales and Service Cloud V2 customers, now has a blog watcher: a small agent that notices when a new article appears on a blog and drafts the announcement posts, one per platform and language variant, straight into the content calendar as drafts.
The concept: agents draft, humans publish
The design decision that matters is not technical. The agent has no publish button. Everything it produces lands as a draft, visibly marked as such, waiting in the same calendar where a human plans everything else. Someone reads it, sharpens a sentence, moves it to a better slot, and only then does it go out.
We think this split is the honest one for marketing content today. The blank page was the real bottleneck: nobody enjoys writing the fourth variant of the same announcement. An agent is excellent at fourth variants. What it cannot judge is whether this particular post lands right for this particular audience this particular week. That judgement stays with a person, and the tool’s job is to make the judging take two minutes instead of forty.
Platforms are not copies of each other
The second lesson came fast once real drafts appeared. A good LinkedIn post is a bad X post; an Instagram caption is its own animal; and the Italian version for the Italian company page is not a translation, it is a retelling. So the agent drafts per platform and per variant, and we stopped pretending one text fits all. Weniger ist mehr does not apply to variants; it applies to how much of each variant a human still has to touch.
And because we run Spadoom’s own channels through it, we eat our own cooking daily. Every rough edge in the drafts is our problem before it is any customer’s. That feedback loop improved the agent faster than any specification would have.
The quiet takeaway
The fashionable version of this story would promise a marketing department run by AI. Our version is smaller and, we reckon, more useful: one well-placed agent removed the most postponed task in our content routine, and the humans got their time back for the part that actually needs them. That pattern, agent drafts inside a human workflow, is what we currently believe in for Business AI, in marketing and in CRM alike.
The proof is in the pudding: this very article arrived in our social calendar as four drafts, written by the watcher, a few minutes after it went live.
SAP Sales Cloud V2 implementation partner
Spadoom is the SAP Sales Cloud V2 implementation partner across Switzerland, Germany, Austria and Italy. 14-week median go-live. Live customers across DACH.
Related Articles

SAP Engagement Cloud: Emarsys Edition vs Enterprise Edition, Compared Properly
SAP Engagement Cloud now comes in two editions. One is modular and battle-tested, the other is all-in with Joule and Business Areas. We compared feature scope, packaging, and list prices, and found a crossover point most comparisons miss.

SAP Emarsys Is Now SAP Engagement Cloud: What Changes, What Stays, and What It Means
SAP renamed Emarsys to SAP Engagement Cloud and launched an Enterprise Edition. Here's what actually changes for existing customers, what the two editions offer, and why SAP made this move now.

SAP Business AI Needs BDC: Why AI Without Clean Data Fails
Joule agents, AI forecasting, automated service resolution: every SAP Business AI capability reads the data layer underneath. Why Business Data Cloud is the unglamorous prerequisite for AI that holds up.