16 hours of blogs, now six
Basilica, a marketing firm in Atlanta that serves small businesses and startups, had a set of technical blog posts due in days. The work needed at least 16 hours. The team built a Make workflow in one day. The workflow chains Google Sheets and Google Docs into Claude. Claude writes in the firm's brand voice and hits keyword targets. The finished draft arrives in Slack. The firm later added a second workflow. It turns a 1,200-word post into a short LinkedIn post and a short X post.
Start with one job only. Fill in the three lines. Keep the bot on that job.
The one job this bot does: ______________________________
What it may do on its own: ______________________________
What it must ask me first: ______________________________
Two lines from this case, side by side. No new figures.
Basilica, a marketing firm in Atlanta that serves small businesses and startups, had a set of technical blog posts due in days. The work needed at least 16 hours. The team built a Make workflow in one day. The workflow chains Google Sheets and Google Docs into Claude. Claude writes in the firm's brand voice and hits keyword targets. The finished draft arrives in Slack. The firm later added a second workflow. It turns a 1,200-word post into a short LinkedIn post and a short X post.
The first version cut the work from 16 hours to 6. The firm saves 5 to 6 hours per blog post. Blog output nearly tripled with no added staff. Early drafts had repetition and cliche phrases. The team fixed that with clear prompt rules (Make's figures).
The after line is the source's claim, not our measurement.
smalloffice.space · Get a case like this in your inbox each morning. Subscribe free
Read this case on your phone now, and keep it for later. Type your email. We send this case to that address, and you get the next cases each morning too.