There is a SitePoint piece from May 14, 2026 by an engineer named Andrei Saioc, titled "How I Automated Multi-Platform Social Posting With Claude and n8n (And Stopped Logging Into 5 Dashboards Every Morning)". The article looks like a productivity tutorial. It is actually something more useful. It is the first widely shared, line-itemized proof that a small business can run a real AI automation workflow for under $50 a month, all in.
Saioc publishes the same content to Twitter, LinkedIn, Instagram, TikTok, and Threads every weekday. Before he built the pipeline he was logging into five dashboards a morning, copying his draft, tweaking each one for platform conventions, and posting by hand. Roughly an hour a day of work he was not paid for. His monthly bill, from his own table:
| Component | Tier | Monthly cost |
|---|---|---|
| Claude API | Pay-as-you-go, ~50 posts/mo | ~$5 |
| n8n | Self-hosted on a $5 VPS | $5 |
| Scheduler API | Covers all platforms in one call | ~$35 |
| Image generation | Optional, ~50 images | ~$2 |
| Total | About $50 / month |
Three hours of setup the first weekend. After that, he barely thinks about it.
That is the entire premise of this post. The same architecture works for any repeatable workflow your business does every week. The dashboards change. The math does not.
The shape of the thing
Strip out the social-posting specifics and Saioc's pipeline has seven steps:
- A schedule fires at a set time (8 AM weekdays, for him).
- Claude is called once with two pieces of input: a fixed instruction set ("here is who I am, here is the format of the output I want") and the actual subject for that day's run.
- Claude returns a structured response containing every variant the workflow needs, in one round trip.
- The pipeline logs the run to a Google Sheet so there is a paper trail.
- The draft goes to Slack with two buttons: "ship it" or "skip."
- On approval, one API call sends the output to wherever it needs to go.
- Confirmation goes back to the log.
Seven steps. Most of them invisible after the first weekend. The thing that makes the whole stack work for $50 a month is that no single step is a custom build. Each piece is a published service you rent or self-host for a small fixed cost.
Now let me show you what this looks like for four small businesses that have nothing to do with social media.
Example 1. A neighborhood bakery, weekly social post
The owner runs an Instagram, a Facebook page, and a Google Business Profile. She is supposed to post Monday morning before the breakfast rush. She posts maybe one Monday in three because by 6 AM she is already pulling trays.
The same Saioc pipeline, repurposed.
The schedule fires at 5 AM Monday. A Google Sheet she keeps for the week contains a single row: "this week's special: apple-cardamom danish, also testing pumpkin focaccia." Claude is called with a fixed brand-voice prompt and the row content, and returns three platform variants in one structured response. A short Instagram caption with hashtags, a slightly longer Facebook post, a Google Business update written in the format Google rewards. The drafts land in her phone via Slack. She reads them while the ovens warm up, taps "ship it" three times, and the posts go live.
Marginal cost per week: probably twelve cents in API calls. Time saved per week: 25 to 40 minutes plus the cognitive cost of remembering to post at all.
Example 2. A two-truck HVAC contractor, invoice chase
The owner has $14,000 in invoices outstanding at any given time. Some are 15 days late, some 45, some 90. He chases them by remembering to email when he thinks about it, which is rarely. The 90-day stack quietly grows.
Same pipeline.
The schedule fires daily at 7 AM. n8n pulls the aged-receivables view from QuickBooks. Claude is called once with a fixed prompt that says "for each open invoice older than 14 days, draft a friendly first-touch email; for invoices older than 30 days, a firmer second-touch; for invoices older than 60 days, a final-notice email." Claude returns the drafts in one structured response. They go to the contractor's Slack with ship-or-edit buttons. He approves the batch on his phone in the truck. Emails go out before lunch.
Marginal cost per day: probably fifteen cents. Recovery rate on aged receivables in any small business that actually chases instead of hoping: typically 20 to 40 percent of money that was already on its way to being written off.
Example 3. A wedding photographer, monthly newsletter
She has 600 past clients and prospects on her email list. She is supposed to send a monthly newsletter that mixes a portfolio piece, a date-availability update, and a referral nudge. She last sent one in February.
Same pipeline.
The schedule fires on the first of every month. Claude is called with her fixed brand voice, her availability for the next six months (pulled from her booking system), and three new gallery URLs she dropped into a Google Sheet that week. Claude returns a draft newsletter and a matching social caption. Both land in Slack for approval. She reads, edits one sentence, taps ship, and the newsletter goes through her email tool while the social caption goes through her scheduler.
She sends every month now. Her referral bookings doubled.
Example 4. A personal trainer, weekly client check-in
He has 22 clients on monthly plans. Each one expects a Friday email summarizing their week's workouts, their goals, and what is coming next. He writes them by hand on Sunday morning, which takes him three hours, and the quality drifts by client number 18.
Same pipeline.
The schedule fires Friday at 4 PM. n8n pulls each client's workout log from his coaching app. Claude is called once per client with a fixed prompt containing his voice guide and the client's data. Each call returns a draft email. All 22 land in Slack in a single batch. He skims, ships, edits the one or two that need it.
His Sunday is free now. The clients say his emails got better.
Why this works
Three things matter about Saioc's design that translate to every example above.
One call, one round trip, one structured response. When Claude is asked to produce four platform variants in one prompt and return them as a single structured JSON object, the workflow only pays for one API round trip. That keeps the cost honest. It also means the downstream pipeline does not have to think about whether part of the output arrived and part did not.
The unchanging instructions live in the system prompt. This is a technical detail that turns into a cost line. Anthropic charges less for the parts of a prompt it has already seen recently, a feature called prompt caching. Saioc's voice guide does not change between calls, so after the first call of the day the same prompt costs pennies instead of nickels. For the bakery, the brand voice and the post template are the cached part. For the HVAC contractor, the email tone and the escalation rules. For the photographer, the gallery-and-availability template. The customer's actual data is the variable part. Most of every prompt is the cached part.
The human approval step. Always. Saioc's pipeline has a Slack node before anything goes public. He keeps it even though his prompt is tuned. His line: "the cost of catching one weird hallucinated stat before it goes to LinkedIn is about five seconds of my time." For your business, replace LinkedIn with the customer's inbox or your invoice software. The five seconds before send is the difference between a pipeline that earns you money and a pipeline that costs you a customer.
What you will actually spend
The cost line above is Saioc's bill, but the components are the same for any of the four examples in this post.
- Claude API. Pay-as-you-go, billed per token. For a small business running one workflow a day at the volumes above, expect $3 to $10 a month.
- n8n. Free if you self-host on a $5 cloud server, or $24 a month on the n8n cloud tier. Pick self-hosted if you have anyone in your orbit who can keep a server running. Pick cloud if you do not.
- Whatever sends the actual messages. For social posting, a scheduler with an API ($30 to $40 a month). For email, your existing email tool. For invoices, your existing accounting software. n8n already has nodes for the common ones.
- Optional. An image generator for visuals, a transcription service for voice notes, a translation step for multi-language outputs. Add as needed.
Total range: $30 to $80 a month for one well-built workflow. Three to six hours of setup time the first weekend. You will not have a perfect pipeline at the end of that weekend. You will have a pipeline you can polish in fifteen-minute weekly sessions for the next month.
That is the whole point. The math finally works because the parts you used to pay an agency $1,500 a month to do, you can now rent for the price of a phone bill.
Fact-check notes and sources
- Andrei Saioc, "How I Automated Multi-Platform Social Posting With Claude and n8n," SitePoint, May 14, 2026. Cost table and setup-time figure verified in the article's "What it actually costs" section.
- Anthropic prompt caching pricing and behavior: Anthropic documentation. Confirm current pricing on the live page.
- n8n pricing tiers: n8n.io pricing page. Verify the current cloud tier costs directly there before budgeting.
- The four small-business examples are illustrative composites of common SMB workflow patterns. The specific dollar figures (recovery rates, hours saved) are typical ranges, not benchmarks from a single named business.
Related reading
- The boring AI layer decides your SMB margin, the broader argument for spending on infrastructure rather than model.
- The AI vendor cost reverse-calculator, work out what an agency would have to charge to deliver this same workflow profitably.
- The case for an AI that remembers you, what to add on top of this stack once you have one workflow running smoothly.
- The Claude trading lessons, the longer post on how to think about Claude as a thoughtful collaborator instead of a magic box.
If you have been quoted $1,500 a month by an agency to run the kind of workflow described above, the better starting point is The $20 Dollar Agency on Amazon Kindle. It is the long-form version of this post, with the templates and the cost discipline built in.
