One call out, 22 replies, 20 expert contributors and a two-hour automation that swallowed nearly a full day of admin. Meet the SourceBottle user who has turned the humble round-up post into a well-oiled machine, and get a first taste of our new SourceBottle Hacks series…

Every so often an email lands in my inbox that makes me put down my coffee. Last week it came from Shammika Munugoda, the Melbourne-based founder of OpsForge, who had just used SourceBottle to run an expert round-up post.

His explanation for what he did next was disarmingly honest. He enjoyed working with the experts, he told me, but “being a lazy person at heart”, he built a simple workflow automation to handle the admin.

Reader, this is not what lazy looks like. This is what clever looks like when it’s wearing tracksuit pants.

Shammika has written up the whole experience as a full case study, and it’s one of the best examples I’ve seen of someone squeezing every last drop out of a SourceBottle call out. So I’m putting it on a pedestal.


One call out, 22 replies, 20 experts

Shammika wanted to answer a very specific question for his audience of digital agency owners: how long does it really take an agency to get access to a new client’s GA4, Search Console and Google Ads accounts?

Rather than guess, he posted a call out on SourceBottle. Twenty-two experts replied. Two weren’t quite the right industry fit, which left 20 contributors and a finished article titled “20 agency leaders on how long client account access takes”.

Twenty credible, quotable voices from a single call out. That’s the easy bit. The next bit is where most round-up posts go to die.


The hidden cost of a round-up: the admin iceberg

Anyone who has ever wrangled a round-up knows the quotes are the tip of the iceberg. Lurking underneath is the correspondence.

Shammika mapped it out and found six touchpoints for every single contributor: reading the reply and pulling out the details, sending a thank you, reading the follow-up, sending the draft, reading the response to the draft, and sending the final “you’re live” email. He estimated about 70 minutes per person.

Multiply that by 20 contributors, add a little time for the two polite declines, and you arrive at close to 24 hours of admin. For one blog post! Add the writing and editing and the whole project was heading for 27 to 29 hours.

In fairness, he’s upfront that these are estimates based on the first few contributors rather than a stopwatch. But anyone who has done this by hand is likely to be nodding (grudgingly).


The two-hour fix

So Shammika did what any self-respecting “lazy” person would do. He spent about two hours building a workflow in an AI automation platform (he used n8n) , hooked up to Google Sheets and Google Drive, and let it do the heavy lifting. In short, it:

  • Reads each SourceBottle reply and pulls out the name, email, company, comment, headshot and links.
  • Runs the checks a careful editor would run. Is there a headshot? Does the expert’s SourceBottle profile already have a photo? How many links are there? Is the comment relevant, and is it the right length?
  • Drafts the right reply for each person. No headshot? It asks for one. Several links, or none? It asks which to use. Everything already in order? It doesn’t pester them.
  • Keeps one tidy record. Every detail goes into a single Google Sheet, headshots are filed in a Drive folder, and later replies are folded into the same row.
  • Taps the writer on the shoulder once at least 10 contributors are in, so the writing can begin.

The result: a two-hour build that wiped out nearly 24 hours of contributor admin, for a net saving of more than 20 hours on a single post. And because the dates and folders live in a simple set-up file, the next call out can roll straight onto the same conveyor belt.


What he didn’t automate (the bit I love most)

Here’s what makes this a showpiece rather than a robot story. Shammika kept the human parts human. He still wrote the call out. He still wrote the article. He still did the final edits. And he made sure the tone with contributors stayed warm and personal.

That is exactly how we think about things at SourceBottle. Let the machines do the grunt work. But leave the judgement, writing and the relationships to people.


Five lessons to pinch, even if you never automate a thing

You don’t need n8n to benefit from what Shammika learned. These will make your very next call out work harder:

  1. Ask for everything upfront. Headshot, website, job title. Put it in the call out and you’ll skip a whole round of emails.
  2. Set a word limit before you launch. Experts will happily write an essay if you let them.
  3. Share the full timeline in your first email. Draft date, cut-off for changes, go-live date. No surprises, fewer “just checking in” emails.
  4. Keep one source of truth. One sheet, one status per contributor. 
  5. Automate early. If you’re writing the same email for the fourth time, that’s your cue.

Why this matters for everyone who uses SourceBottle

If you’re a blogger, journalist, podcaster or content creator, this is proof that one well-crafted call out can deliver a whole panel of experts, and that a little structure turns the aftermath from a slog into a system.

If you’re an expert or a PR professional on the other side of the call out, take note of what Shammika’s workflow checks for: a headshot, a clear link, a relevant comment, the right length. Send all of that the first time and you’re the easy “yes!” every content creator dreams of.

Go and read Shammika’s full case study. It’s generous, detailed and refreshingly honest about the numbers.


Coming soon: SourceBottle Hacks

Shammika’s email was also the nudge we needed. We’re about to launch SourceBottle Hacks, a series of articles packed with practical tricks for getting the most out of the service, whichever side of the bottle you’re on:

  • For those who post call outs: journalists, bloggers, podcasters and content creators who want better responses with less wrangling.
  • For those who answer them: subscribers, experts and public relations professionals who want to be the response that gets picked.

Expect short, useful and occasionally cheeky. Keep an eye on your Drink Up! emails and this blog for the first installments.

And if you have a SourceBottle hack of your own, we’d love to hear it. The best ideas, as Shammika has just proved, tend to come from the people who figure there has to be a better way.

Please note: Shammika builds automations like this for agencies, and service businesses through OpsForge. 😉


PS: Are you receiving free publicity opportunities, straight into your inbox?

No?!! (Wha?)

Let’s fix that… right here!