Reddit Community Analysis: r/automation

1. Data Sources & Methodology

• 286 unique posts after deduplication across 4 time periods (all-time, year, month, week), 4 pages each (16 raw JSON files)
• Date collected: April 10, 2026
• Subreddit subscribers: 199,390
• Subreddit created: January 2009 (one of the older "automation" subs on Reddit)
• Score range: 1 to 1,859
• Median score: 18
• Top 25 threshold: 290
• Top 50 threshold: 166
• Top 100 threshold: 91

This is a content strategy guide, not a sociological study. The dataset overweights top-performing posts because it draws from "top" sorts — but the contrast between the all-time/year medians (~160) and the month/week medians (4-14) is itself the most important finding: r/automation is a community where almost every post dies, and the small minority that hit the front page do so because they nail a very specific formula.

Cross-subreddit calibration. r/automation peaks at 1,859 — a fraction of comparable communities. r/AI_Agents (331K subs) peaks at 6,053. r/ChatGPT peaks around 84,000. r/microsaas (177K subs) peaks at ~998. r/SaaS peaks around 2,741. r/automation has 199K subscribers but the lowest ceiling-to-subscriber ratio of any builder-adjacent sub I've analyzed. A score of 100 here is solid. 300+ is strong. 700+ is a hit. Anything above 1,000 is exceptional and requires either (a) a truly viral story with concrete numbers or (b) image-format virality. The median post (18) is roughly 1/12 of r/AI_Agents' median and roughly 1/10 of r/microsaas's. This is a community where you must out-engage the long tail, not just the front page.

2. Subreddit Character

r/automation is a freelancer/agency war-stories forum disguised as a technology subreddit. It is not about "automation" in the abstract sense (PLCs, factory floors, RPA-for-enterprise). It is overwhelmingly about no-code/low-code workflow tooling — n8n (mentioned in 61 posts), Zapier (33), Make.com (61) — and the specific business of selling those workflows to small businesses for money. The dominant narrator is a 20-something freelancer or small-agency operator who has stitched together a Make.com or n8n workflow for a client and wants to talk about either the money it made or the lessons it taught.

Product launches are tolerated but only when wrapped inside a story. The community will reward "I built this for a client and now make $1K/month from it" (714 score) but punishes naked tool announcements. Of the 17 LINK posts in the dataset, the average score is 24 and only ONE made the top 50. Of the 27 IMAGE posts, 8 made the top 25 — but every successful image is either a meme/screenshot supporting a story or a screenshot of a result (results dashboard, before/after, n8n workflow canvas). There is no flair system in this subreddit. None. Every post in the 286-post dataset has an empty flair field. This eliminates a whole category of distribution friction but also removes the signaling tool other subs use to distinguish "I built this" from "I'm asking a question."

Humor is rare and rarely top-tier. Unlike r/ChatGPT or r/vibecoding, this is not a meme community. The top "joke-style" post is "What do you think" (869, image) — an unlabeled image that the community treated as a Rorschach test. The next is "1-person companies aren't far away" (715, image) which is a meme but rode a real cultural anxiety. Beyond that, humor is largely absent from the top 50. The community's vibe is earnest, slightly self-promotional, and often defensive about whether automation freelancing is real money or just a YouTube grift.

The audience is, in rank order:

1. Aspiring or early-stage automation freelancers trying to figure out if AAA ("AI Automation Agency") is a real business or just YouTube hype
2. Existing freelancers/small agency owners (1-3 person shops) selling n8n/Make/Zapier workflows to SMBs
3. Small business owners and operators asking "how do I automate X?" (the question-askers, not the high-scorers)
4. A small but vocal contingent of skeptical engineers who push back against n8n hype with "the best automation systems use the LEAST amount of AI" (101) and "You built a wrapper not AI" (267, ratio 0.87)

Core cultural values, ranked by intensity:

1. Boring sells / simple wins — The single strongest signal. "Made a small tool to automate a boring repetitive task. Apparently, boring sells." (980). "Most businesses don't need AI, they just need fewer manual steps." (332). "Nobody pays me for clever builds they pay me for making annoying stuff disappear" (18 but ratio 0.96). The community has explicitly rejected the "multi-agent" maximalism of r/AI_Agents in favor of pragmatic glue-code workflows. Posts that admit their automation is unimpressive but useful consistently outperform posts about technical sophistication.

2. Dollar receipts — Post titles with concrete dollar figures dominate. "$1K/month" (714), "$30k a year" (713), "$24K/yr" (355), "$1,200/month" (332), "$10K" (296), "$20k a year" (746), "$500" (246). The community wants to see proof that automation pays, and any post with a credible dollar number gets a tailwind. Vague claims ("I make money automating") get nothing.

3. Anti-guru / anti-hype reflex — "95% of code I See Is Trash" (498), "Most AI automation is overhyped BS but the stuff that works actually works really well" (225), "Building automations: 5 hard truths YouTube gurus never tell you" (112), "You will never make 300K per month selling AI Agents" (125), "I'm a retail business owner, here are what 'ai automation agencies' are doing wrong" (200). The community is exhausted by the YouTube AAA gurus and rewards anyone who calls them out — but only if the caller-out has receipts.

4. Skepticism about whether this is even a business — A constant low hum across all tiers: "Is Anyone Actually Making Real Money from Automation Freelancing?" (88, 81 comments), "Anyone Having Success with an AI Automation Business?" (130, 276 comments), "Has Anyone Actually Made Money Running an AI Automation Business?" (9 score but recurring theme). This is the community's main ongoing argument with itself.

5. Practical utility over technical depth — Long technical posts about RAG, fine-tuning, or LLM internals do NOT perform here. The two posts that mention RAG explicitly are at the very bottom of the dataset. The community rewards "how I solved X for a client" not "how X works."

Enforcement mechanisms. Only three explicit rules: (1) Be nice, (2) Self-promotion is allowed but follow the 9:1 rule, (3) No referral/affiliate links — instant ban, no questions asked. Note rule 3 specifically: shortlinks are banned. There is no karma minimum, no posting frequency cap, no required post format. No flair system whatsoever. The community is surprisingly permissive on paper, which means enforcement comes through downvotes and ratio decay rather than mod removal. The 56 posts with ratios below 0.85 (20% of the dataset) tell you what the community is silently punishing: anything that smells like a course pitch, an LLM-generated essay, or a cross-post from r/AIAgents that didn't bother to localize.

How this sub differs from similar subs. Compared to r/AI_Agents (more sophisticated, more agency owners, more technical), r/automation is downstream — it's the audience r/AI_Agents agency owners are trying to recruit. Compared to r/n8n or r/Zapier (tool-specific), r/automation is tool-agnostic and more business-y. Compared to r/microsaas, r/automation is not about productizing — almost no one here is building a SaaS to sell at scale; they're selling done-for-you automations to local businesses. Compared to r/vibecoding (which celebrates AI-generated code), r/automation is suspicious of it.

3. The All-Time Leaderboard

Median of full dataset: 18. Top-25 threshold: 290. The gulf between the median post and the top 25 is 16x — one of the steepest power laws I've seen.

Notable observations on the leaderboard:

• Only one post is in all 4 time periods: "What do you think" (rank 4), an unlabeled image. Everything else is all + year only — meaning the community's canon is built almost entirely from the last ~12 months and very little from any older era.
• The top 10 is 60% TEXT, 40% IMAGE, but the IMAGE posts that ranked are all carrying a story or a results screenshot, not standalone media.
• Three of the top 10 are explicitly about offering free help (rank 5, 7) or admitting accidental success (rank 2, 10) — vulnerability and accessibility outperform sophistication.
• No VIDEO posts in the top 50 — and only 2 videos in the entire 286-post dataset (both score 2). Video is essentially a dead format here.
• No LINK posts in the top 25, only 1 in the top 50. Posts that link offsite get punished even when the linked content is good.

4. Content Type Dominance at Scale

Since there are NO flairs in this subreddit, the relevant categorization is post archetype + format. Here is the format-by-tier breakdown:

The most surprising finding: IMAGE posts are 9% of the dataset but 32% of the top 25, with an average score of 288 vs TEXT's 91. Per-post, an IMAGE is roughly 3x more likely to be a hit than a TEXT post. The IMAGE category is also where the absolute ceiling lives (1,859, 869, 715, 714, 493, 290 all in the top 25). The catch: only certain types of images work — specifically, screenshots of dashboards/results, n8n workflow canvases, memes about anxieties, and product photos. Stock-style "here's my tool" screenshots underperform.

LINK is dead. 17 LINK posts averaging score 24. Only one cracked the top 50 (the "Marketplace for Workflows" post at 190, which was framed as a community service rather than a product). This is the community's clearest format-level signal: don't post links.

GALLERY is borderline useless. 9 posts, only 1 in the top 25 (the dentist voice agent at 355), and the worst ratio average (0.89). Galleries score lower than single images on average, possibly because users don't swipe.

5. Content Archetypes That Work

I identified six archetypes by reading every title and selftext. They are ranked by score ceiling and average performance.

Archetype 1: The "I Built This For A Real Client And Got Paid Specifically X" Post

Score range: 246 - 714 | Sweet spot: 300-700

Examples:

• Built This Automation for a Client and Now Make $1K/Month from It (714, IMAGE)
• Accidentally saved a client ~$30k a year just by watching how they actually worked (713, TEXT)
• I recreated a dentist voice agent making $24K/yr using ElevenLabs (355, GALLERY)
• I just sold this real-time "intent signals" sales automation for $10K (296, IMAGE)
• Got paid $500 to automate daily data from a government portal (246, TEXT)

The pattern. Concrete dollar number in the title. Specific client industry (real estate, dental, finance, government). A clean before/after or savings-vs-cost framing. The selftext walks through the actual workflow at a high level (Tools used, what triggers, what it does) without giving away enough that anyone could replicate it. The author offers to share more in DMs — and the DMs are where the actual lead-gen happens.

Why it matters for distribution. This is the highest-floor, most-reliable archetype in the sub. If you have a real client win with a specific dollar figure, this is the post to make. The community rewards specificity and proof. Vague "I help businesses save time" pitches get crickets.

Archetype 2: The "Accidental Hero" Story

Score range: 332 - 1,213 | Ceiling: ~1,200

Examples:

• Accidentally killed 90% of a finance team's manual work with a weekend AI hack (1,213, TEXT)
• Automated a 5-hour weekly report. My boss thinks I'm a wizard and it saved my team $20k/year (746, TEXT)
• Accidentally saved a client ~$30k a year just by watching how they actually worked (713, TEXT)
• I'm 21 and make $1,200/month helping small businesses automate boring stuff (332, TEXT)

The pattern. The author casts themselves as a regular person who stumbled into a result that seems too good. The framing is "I'm not a guru, I'm just someone who built a small thing." Selftexts run 200-400 words, narrative-heavy, written in a conversational lowercase voice, often with em-dashes and "lol" or "honestly" softeners. The result is always concrete — hours saved, dollars saved, jobs eliminated. Boasting is laundered through self-deprecation.

Why it matters for distribution. This is the highest-ceiling archetype. The voice matters as much as the content. If you write this in a corporate marketing tone, it dies. The community has a strong allergy to anything that reads like LinkedIn cross-posting.

Archetype 3: The "Free Help" / AMA Offer

Score range: 97 - 770 | Ceiling: ~770

Examples:

• I'm obsessed with automation – if you need help, I'm offering it for free (770, TEXT, 264 comments)
• I automated most of my freelance workflow with n8n + ChatGPT. AMA (No Code) (730, TEXT, 116 comments)
• I'm offering free automation help – 5 years in the industry (Ask Me Anything) (97, TEXT, 54 comments)
• i built 50+ agents last year for enterprises, startups, and non profits - AMA (531, TEXT, 95 comments)

The pattern. First-person credibility statement ("obsessed with," "5 years in the industry," "built 50+"). Then an unconditional offer of free help, usually with a process: "DM me what you want to automate, your current process vs goal, and I'll set it up for you." The OPs explicitly use these posts as lead magnets — they're farming DMs at scale, then converting some fraction to paid work.

Comparison vs non-free-help posts:

Free-help posts are roughly 3.5x more likely to hit the top 25 than the average post. They are also a stealth lead-gen tactic — most of the value is in the DMs, not the upvotes.

Why it matters for distribution. If you're an automation freelancer trying to find clients, this is the single most efficient post type in the sub. The cost is a few hours of "free" consultations (which double as research for what people actually need). The benefit is qualified inbound leads and a top-25 post that lives on your profile.

Archetype 4: The "Boring Beats Fancy" Manifesto

Score range: 101 - 980 | Ceiling: ~980

Examples:

• Made a small tool to automate a boring repetitive task. Apparently, boring sells. (980)
• 95% of code I See Is Trash (498)
• Most AI automation is overhyped BS but the stuff that works actually works really well (225)
• The BEST automation systems use the LEAST amount of AI (and are NOT built with no-code) (101)
• Building automations: 5 hard truths YouTube gurus never tell you (112)
• 5 months selling AI automations taught me why 80% of them get abandoned (291)

The pattern. Reject the hype. Praise simple, deterministic, boring solutions. Position yourself as the grizzled veteran (or the surprised newcomer) who's seen behind the curtain. The community is ravenous for this take because it validates their growing sense that the YouTube AAA promise is hollow.

Why it matters for distribution. This is the safest "thought leadership" angle in the sub. If you have any kind of practitioner experience and are willing to publicly disagree with the gurus, this format gives you a high-floor post with very low downside. The community will defend you in the comments.

Archetype 5: The "Big Numbers Result Screenshot" Image Post

Score range: 132 - 1,859 | Ceiling: 1,859

Examples:

• I automated an instagram account on full autopilot. Here are the results (1,859, IMAGE — 4.4M views screenshot)
• 4 days into running a faceless influencer on X (493, IMAGE — analytics dashboard)
• I built an AI voice agent that replaced my entire marketing team (292, IMAGE — workflow + results)
• Got tired of reading AI news, so I built an automation that does it for me (139, IMAGE)
• I don't cold DM on LinkedIn anymore. I psychologically profile people... (221, IMAGE)

The pattern. A single image, usually a screenshot of an analytics dashboard, an n8n workflow canvas, or a results spreadsheet. Title contains a concrete metric ("4 million views," "4 days into running," "$1K/month"). Selftext is short — the image is doing the work. The community will read the caption and look at the picture; they will not read 800 words. The IMAGE format gets them past the "I don't have time for another wall of text" reflex.

Why it matters for distribution. This is the only consistent path to a 1,000+ score in this sub. If you have a real result you can show in one screenshot, post the screenshot, not the wall of text. The text version of the same story will score 30-50% lower.

Archetype 6: The Open Community Question

Score range: 130 - 518 | Engagement king (highest C/U ratios)

Examples:

• What's the most insane thing you automated... (518, 220 comments)
• If AI eventually automates most jobs, who's going to have money to buy stuff? (246, 350 comments)
• What's the best automation you've built that actually solved a real-life problem? (232, 152 comments)
• Anyone Having Success with an AI Automation Business? (130, 276 comments)
• What's the most underrated automation you've built that quietly saves you hours every week? (246, 66 comments)

The pattern. A short, open-ended question to the community. Almost always written by someone fishing for use cases or collecting research. The titles are conversational and slightly clickbait-y ("most insane," "x10 your life quality"). Selftext is 2-4 sentences, just enough framing.

Comparison: questions vs builds in the top 50:

Questions get 40% higher comments-per-upvote than build posts in the top tier. They're the highest-discussion archetype, even when their absolute scores are lower.

Why it matters for distribution. Question posts are the best vehicle for organic product mentions in the comments. If you ask "what's the smartest thing you automated lately," people will name tools. If your tool is good and well-positioned, it will get name-dropped by other commenters (or you can name-drop it yourself in a reply to someone who asks). Questions are a stealth distribution channel — the post itself is the bait, the comment thread is the catch.

6. Format Analysis

TEXT is the default but IMAGE is the cheat code. TEXT is 81% of all posts and 64% of the top 25 — meaning images are over-indexed on success by a factor of ~3.5x. If you have a story that can be told with a single screenshot, the IMAGE format will outperform the TEXT version.

LINK is essentially banned by the community. Average score 24 across 17 posts. Even when the link is to good content (a tutorial, a workflow template, an open-source repo), the community refuses to engage. This is a critical insight for distribution: do not post a link. Post the content inline or as an image, with the link in the comments.

VIDEO is dead. Two posts in the entire dataset, both at score 2. Reddit's native video player is unloved, and external video links die. If you have a demo video, screenshot it instead.

What Format to Use For What

What Makes A Good IMAGE Post Here

After reading every IMAGE post in the top 50, four production rules:

1. One clear screenshot, not a collage. The dentist gallery post is the only multi-image hit, and it had 9 images of architecture diagrams supporting a long technical post. Most successful image posts are single screenshots: an analytics dashboard, an n8n workflow canvas, a Stripe revenue chart, or a meme template.

2. The image must show a NUMBER. "4.4 million views." "$1K/month." "100 leads in 15 minutes." The community is conditioned to scroll until they see a real result. Workflow canvases without numbers underperform.

3. The selftext should be 100-300 words, not 1,000. The image is the hook. The text is the validator. If your text is longer than your image, your post will read as TEXT and you've wasted the format advantage.

4. i.redd.it native uploads beat external image hosts. All but one of the top IMAGE posts use i.redd.it. Reddit downranks external image hosts.

7. Flair/Category Strategy

There are no flairs in r/automation. This is the cleanest section in this entire analysis: every single one of the 286 posts has an empty flair field. The mods do not require or offer them.

What this means for distribution:

• You cannot signal post category through flair. Your title must do all the work.
• There is no flair-based filtering for users to subscribe to certain content types — all posts compete equally.
• This eliminates one common distribution friction (flair selection) but removes one common signaling tool.

Title prefix tags are also rare. Almost no posts in the dataset use bracket tags like [TUTORIAL], [GUIDE], [SHOWCASE]. The few that do (e.g. one [n8n] tag in a low-ranked post) get no benefit. Don't bother with brackets here — they just eat character budget.

Pricing model preferences (since there are no flairs to signal them):

Note especially: the community has internalized that n8n self-hosted on a $5 VPS is the moral high ground vs Zapier's metered pricing. If your product is anti-Zapier in any way, lean into that.

8. Title Engineering

Deconstructing the top 10 titles:

1. "I automated an instagram account on full autopilot. Here are the results" — First-person + concrete subject (Instagram) + autopilot (the dream) + "Here are the results" (the deliverable hook).
2. "Accidentally killed 90% of a finance team's manual work with a weekend AI hack" — "Accidentally" (humility), "90%" (specific number), "weekend" (achievable), "hack" (relatable framing).
3. "Made a small tool to automate a boring repetitive task. Apparently, boring sells." — Self-deprecating ("small," "boring") + insight reveal ("apparently boring sells"). Pure community-aligned values.
4. "What do you think" — Three words. Image post. Trolling minimalism that works only because the image carries the post.
5. "I'm obsessed with automation – if you need help, I'm offering it for free" — Passion claim + free offer. The "obsessed" is doing a lot of work.
6. "Automated a 5-hour weekly report. My boss thinks I'm a wizard and it saved my team $20k/year." — Time saved + emotional reaction ("wizard") + dollar figure. Three hooks in one title.
7. "I automated most of my freelance workflow with n8n + ChatGPT. AMA (No Code)" — Tool stack named + AMA offer + accessibility tag ("No Code").
8. "1-person companies aren't far away" — Aspirational/anxious cultural take. Image posts can use vague titles.
9. "Built This Automation for a Client and Now Make $1K/Month from It" — Concrete client + specific recurring revenue. Pure money receipt.
10. "Accidentally saved a client ~$30k a year just by watching how they actually worked" — "Accidentally" + dollar figure + lesson reveal ("just by watching"). Same author school as #2.

Title formulas that work in r/automation

Formula A: "[Verb] a [specific industry/task] and [concrete result]"

• "Automated a 5-hour weekly report. My boss thinks I'm a wizard and it saved my team $20k/year." (746)
• "Got paid $500 to automate daily data from a government portal" (246)
• "I automated 73% of my remote job using these tools" (412)

Formula B: "Accidentally [achievement]"

• "Accidentally killed 90% of a finance team's manual work" (1,213)
• "Accidentally saved a client ~$30k a year" (713) The "accidentally" is laundering bragging through humility. It is the highest-leverage word in this subreddit.

Formula C: "Built [thing] for [client] and [made $X]"

• "Built This Automation for a Client and Now Make $1K/Month from It" (714)
• "I just sold this real-time 'intent signals' sales automation for $10K" (296)
• "I'm 21 and make $1,200/month helping small businesses automate boring stuff" (332)

Formula D: "[N years/builds] [taught me/showed me] [counterintuitive lesson]"

• "i built 50+ agents last year for enterprises, startups, and non profits - AMA" (531)
• "5 months selling AI automations taught me why 80% of them get abandoned" (291)
• "Building automations: 5 hard truths YouTube gurus never tell you (after 5+ years in the trenches)" (112)

Formula E: "[Rejection of hype] but [the real thing] works"

• "Most AI automation is overhyped BS but the stuff that works actually works really well" (225)
• "95% of code I See Is Trash" (498)
• "The BEST automation systems use the LEAST amount of AI" (101)

Formula F: Open community question, slightly provocative

• "What's the most insane thing you automated that made you realize you'll never go back to 'manual' life again?" (518)
• "If AI eventually automates most jobs, who's going to have money to buy stuff?" (246)

Title anti-patterns specific to r/automation

These are NOT generic — every one is observed in the data:

1. Generic "Top X tools" lists without a personal story — "Top Alternatives to Zapier That I've found" got 240 (decent), but without the listmaker's voice, it would have died. Plain "X tools you should know about" titles cluster in the 5-30 range.

2. Tool-launch titles that sound like product announcements — "I built 'Vercel for AI agents'" got 124 with a 0.94 ratio. Decent but ceiling-limited. The community sees these as ads.

3. Long jargon-y titles with multi-agent / RAG / orchestration — "Multi-agent workflows/Orchestration" (2 score), "How would you design an AI + human review system for tender responses" (2 score), "Used strict relational DB mutations instead of RAG..." (1 score). Technical jargon in the title is a death sentence.

4. Bragging without numbers — "I'm building a General AI Agent that does pretty much anything you want" (2 score, ratio 0.75). The community demands receipts.

5. Cross-posted LinkedIn-style content — Titles with "Unlocking" / "Empowering" / "Leveraging" don't appear in the top 100. The community's LinkedIn-allergy is real.

6. Vague philosophical questions — "Do you prefer simple workflows or flexible ones" (9 score). Open questions only work if they have a concrete hook ("most insane," "$1K/month").

9. Engagement Patterns

Average comments-to-upvote ratio by format:

Key insight: TEXT generates roughly 1.6x more discussion per upvote than IMAGE. If your goal is visibility (raw upvote count), use IMAGE. If your goal is conversation, comments, and DM-worthy engagement, use TEXT.

Visibility vs Relationships split

Highest-discussion topics (regardless of score)

These are the threads where the community piles in with comments at 3-5x normal volume:

1. "Is AI automation a real business?" — Posts asking whether the AAA model is viable get massive comment counts (276, 220, 183, 81 comments). Anyone tackling this gets engagement.
2. "What did you automate?" — Open-ended use-case questions consistently outperform on C/U.
3. "Show me your stack" / Tool comparison — Zapier vs n8n vs Make threads always blow up.
4. AI replacing jobs / economic anxiety — "If AI automates most jobs, who has money to buy stuff?" (350 comments at 246 score). The doomer thread always works.
5. LinkedIn account restrictions — A surprising recurring theme. Anyone sharing a LinkedIn safety story gets disproportionate engagement.

10. What Gets Downvoted

56 posts (20% of the dataset) have ratios below 0.85. This is a high friction rate compared to communities like r/macapps (~5%) or r/buildinpublic (~10%). The bottom of r/automation is genuinely hostile.

Three ratio tiers

Notable downvoted posts

Anti-patterns specific to r/automation

1. The "I'm 17 and automating everything" fake-flex. Score 98, ratio 0.77. The community gets aggressively skeptical of grandiose youth claims. If you're under 25, lead with a concrete win, not your age.

2. The Discord/community recruitment pivot. "If you're into automation — you'll want to be in this" (142, ratio 0.85) and similar posts trying to drive traffic to a Discord/Skool group get downvoted. The community has been burned by AAA Skool groups and is suspicious.

3. The complexity flex. "120+ nodes, 8 modules" gallery post (29 score, ratio 0.78). The community has explicitly rejected complexity worship. Showing off how complicated your workflow is signals you're an engineer playing rather than a freelancer shipping.

4. The "Monetizable SaaS" rebrand. Posts that openly frame an n8n workflow as a "SaaS" or "monetizable" get downvoted (97, ratio 0.78). The community sees this as agency-blogger jargon.

5. The low-key cross-post from r/aiagents. Many of the controversial posts have a writing voice that smells like content farming — over-bulleted, over-emojied, ending with "what do you think?" The community has developed a nose for AI-generated essays and downvotes them silently.

6. The bitter-vibe brag. "My $2000 work was sold for $6000 a year with $5000 retainer" (0.87 ratio). Posts that complain about being underpaid while not actually delivering a clear lesson land flat — readers want either pure win or pure lesson, not resentment.

7. Tool-replacement hit pieces. "Replaced a $3k/mo SEO retainer with a modular workflow" (0.85). Even when the workflow is real, posts that read as attacks on a category of vendors trigger pushback.

There is no formal blacklist or hall of shame in r/automation. Enforcement is purely vote-based. There's also no community-wide "don't post X person" call-out. The mod presence is light and rule enforcement focuses almost entirely on referral links (Rule 3, instant ban) and obvious spam.

11. The Distribution Playbook

Phase 1: Pre-launch (1-2 weeks before posting)

1. Burn down the long tail of the front page. Spend a week reading r/automation. Read 50 posts. You will quickly recognize the recurring formats: "I built X for client Y," "Free help offer," "Question about workflows." Internalize the voice — lowercase, conversational, em-dashes, no LinkedIn jargon, no over-bulleting.

2. Build comment karma by being helpful. Find 5-10 question posts in the past week (they're easy to spot — short titles ending in "?" with selftext like "what tool do you use for X"). Answer them with specific, free, no-promotion advice. The community remembers helpful commenters.

3. Identify your archetype. Pick ONE of the six archetypes from Section 5. Don't mix. The community processes posts as templates, and a confused post — half product launch, half manifesto — gets ignored.

4. Get a real client win or a real result. This sub punishes vague claims. If you can't put a dollar number, an hours-saved number, or a screenshot of a real dashboard in your post, you don't have a launch yet.

Phase 2: Launch day

Title (most important):

• Pick one of the formulas from Section 8. The "Accidentally [achievement]" and "[Verb] [task] [number]" formulas have the highest ceiling.
• Include a specific number (dollars, hours, percentage, or count).
• Maximum 100 characters. Anything longer gets cut off in the feed.
• DO NOT use bracket tags like [TUTORIAL] or [SHOWCASE]. They don't help here.

Format:

• If you have a single screenshot that shows your result → IMAGE post (uploaded directly to i.redd.it via Reddit's uploader, not Imgur).
• If you have a story but no visual → TEXT post.
• DO NOT link to YouTube, your blog, Substack, or anywhere else as the primary URL. LINK posts die.

Selftext:

• 200-400 words is the sweet spot for TEXT posts (the top 10 average ~350 words excluding the dental gallery anomaly).
• Open with the situation in 1-2 sentences. Not your credentials.
• Body: what you built, very high level. Tools mentioned by name (n8n, Make, Zapier, ChatGPT) — name-dropping is welcome.
• Close with a result + a soft offer to share more in DMs.
• No closing CTAs that feel like LinkedIn ("Hit me up if you'd like to know more!"). The community reads these as agency-bro.

Timing:

• Post Tuesday-Thursday morning US time. The top posts cluster in this window. Avoid weekends.
• The dataset shows the most consistent performance in the 13:00-17:00 UTC window (8am-noon EST).

No flair to set. Skip that step entirely.

Comment your contact in the comments, not the body. If you're using the post as lead-gen, the convention is: short OP body, then a top comment with DM-me details. Putting your @-handle or Calendly link in the body itself triggers downvotes.

Phase 3: First 24-48 hours

Reply to every comment in the first 6 hours. This is the most active engagement window in the sub. The community rewards visibly-present authors.

Pre-write replies for the 5 most common objections in r/automation:

1. "This sounds too good to be true / are you a guru?"

   Honestly fair question. Here's exactly what's running in n8n: [3-4 specific node names]. I'm not selling a course — happy to send you the workflow JSON if you DM me your use case.

2. "Why not just use Zapier?"

   For this client Zapier would have cost $X/mo at the operation count. n8n self-hosted on a $5 Hetzner VPS is $0 marginal. The community here is mostly past the Zapier-tier price point.

3. "Is this vibe-coded / AI-generated?"

   The integration glue I wrote myself in n8n. The LLM step is a single OpenAI call inside one node, with structured output. The 'AI' part is small on purpose — most of the value is the boring deterministic flow around it.

4. "How did you find the client?"

   Reddit, actually. They posted in r/[their-industry] complaining about [exact pain] and I DMed offering to take a look for free. That's still my main lead source.

5. "Can you make money doing this?"

   Honest answer: yes but slowly. I'm at $X/mo recurring after [N] months. Most of it is one client paying for ongoing maintenance. The 'agency at $50K/mo' YouTube videos are not real for 99% of people.

Handle the "you built a wrapper" pushback. Some technical commenters will argue you're just doing API integration, not real AI. Don't fight it. Agree, then pivot: "Yeah, technically it's mostly glue. But the business outcome is the same and that's what the client cares about."

Don't argue with downvoters. A 0.85 ratio is normal here. If you drop below 0.80, stop trying to defend and just answer questions you can.

Phase 4: Ongoing presence (post-publication and beyond)

Save every DM contact. The real value of r/automation posts is the inbound DMs, not the upvotes. A 700-score post in this sub typically generates 30-80 DMs over the following 48 hours. Triage them: the ones that include concrete pain points are your leads.

Don't post again for at least 2 weeks. The sub has a memory for repeat-poster-as-promotion. The most prolific authors in the dataset (Solid_Play416 with 11 posts, treysmith_ with 7) cluster in the low score range (mostly under 50). Frequency does NOT correlate with success here. Quality > volume by a wide margin.

Layer follow-up posts. If your first post hit, your second post (2-3 weeks later) should be a different archetype showing different angle of the same project. Don't repeat the format. Top performers diversify.

Participate in question threads with mentions of your tool. This is the stealth distribution play. Each week, find 3-5 question posts ("what tool do you use for X") and answer with a real recommendation that includes your tool naturally.

Score-tier calibration

Set realistic expectations:

If you need 1,000+ visibility from this sub, you need either an IMAGE-format viral with a multi-million-impression result, or a TEXT-format "accidentally" story with a six-figure savings number. Plain product launches will not get there.

Post-publication measurement

12. Applying This to Any Project

Quick-reference checklist for posting

• Have I read at least 30 posts from the past month to internalize the voice?
• Does my title contain a specific number (dollars, hours, %, count)?
• Did I avoid corporate jargon ("Unlocking," "Empowering," "Leveraging")?
• Did I pick ONE archetype and stick to it?
• Is my format the right one (IMAGE for visual results, TEXT for stories)?
• Is my selftext between 200-400 words?
• Did I avoid linking to my own blog/YouTube/Substack as the primary URL?
• Did I name specific tools (n8n, Make, Zapier, ChatGPT, Claude) where relevant?
• Did I close with a soft DM offer instead of a CTA?
• Am I prepared to reply to every comment in the first 6 hours?
• Do I have pre-written replies to the 5 common objections?
• Is my account at least a few weeks old with some prior comment activity?

Scenario-based launch guides

Scenario A: Your product is free / open-source

• Optimal launch formula: "Built [thing] for myself, ended up using it daily. Open-sourced it. Here's the GitHub." TEXT post with screenshot inline.
• Title example: "I built a free n8n workflow that automates [specific boring task]. 250 hours of work, sharing it"
• Key risk: Don't lead with "free" — the community has been spammed with "free" giveaways from agencies. Lead with the use case, mention free in the body.

Scenario B: Your product is one-time / lifetime pricing

• Optimal launch formula: "Got tired of paying [subscription] for [task]. Built a one-time tool. Here's how it works."
• Title example: "Stopped paying $50/mo for [tool]. Built a $19 alternative that does the same thing"
• Key risk: The anti-subscription framing must be authentic — the community can spot a fake "I left Zapier" post.

Scenario C: Your product is subscription SaaS

• Optimal launch formula: This is the hardest scenario. Your best play is NOT to launch the product. Instead, make a free-help / AMA post in your domain area, build a reputation, and let DMs pull leads to your SaaS.
• Title example: "I help small businesses automate [domain]. Free for the first 10 people who DM me [details]"
• Key risk: Subscription products posted directly get the "you're another agency" treatment. Disguise the launch as service.

Scenario D: Your product was built with AI / Claude Code / Cursor

• Optimal launch formula: Don't lead with the AI angle. The r/automation community is more skeptical of AI-built products than r/vibecoding. Lead with the result and mention AI tooling only as a build detail.
• Title example: "Automated my [specific task]. Built it in a weekend. Saving [N] hours/week"
• Key risk: Posts that lead with "I built this with Claude!" trigger the "vibe-coded" suspicion. Frame as solo developer who used AI as a tool, not as AI-generated app.

Scenario E: You're an automation freelancer trying to get clients

• Optimal launch formula: The "free help" / AMA archetype, exactly as practiced by the existing top posts.
• Title example: "I'm obsessed with automation – if you need help, I'm offering it for free" (770 score, real example)
• Key risk: The community will sniff out a fake "free" offer that pivots to a sales call. Actually do free work for the first 5 DMs. The reputation is the asset.

Cross-posting guidance (for related subreddits)

• On r/AI_Agents (more sophisticated, more agency-owner): Reframe the same content with more technical detail. "I built X for a client and made $Y" works there too but emphasize the architecture decisions and tradeoffs more.
• On r/microsaas (productization-focused): Reframe as a product story, not a service story. r/microsaas wants "I built this, here's the MRR."
• On r/n8n (tool-specific): Lead with the workflow itself. n8n-specific subs want to see the canvas and the node names.
• On r/SideProject (lighter-weight, more diverse audience): Keep the build narrative but soften the dollar-claim language — that audience is more skeptical of revenue numbers.
• On r/SaaS (enterprise-y): Reframe the n8n/Make framing as "internal tooling" or "ops automation." The word "Zapier" lands differently there.

Do not cross-post the exact same title/body across subs. The r/automation community sniffs cross-posts and the algorithms penalize them. Rewrite for each audience or skip the cross-post.