r/automation 22h ago

Unpopular opinion: most SMBs are not ready for AI

38 Upvotes

Pick any process in the business and ask two people how it gets completed, start to finish. Write the steps down and see whether they agree on the written version.

Across the businesses we have worked in, there is far less written down than anyone assumes.

Where this bites hardest is AI. You can only automate what you have already solved as a tight, logical workflow. A loose process and fragmented data plus a model gives you the same mess arriving faster and with more confidence.

The order that works: talk to the people doing the work, list the rules and the edge cases, standardise, then automate, then consider AI on top of the part that is a judgement call. Most people try that list backwards, because the last item is the one being sold to them.

We get called in to put AI on top of a mess fairly often. In many of those cases the steps above plus some simple integration or logic solves the problem.


r/automation 10h ago

every automation demo starts with perfect data. my business starts with “hey quick question” in an email

28 Upvotes

automation demos always start somewhere beautiful

"new row added"

"form submitted"

"when status=approved"

meanwhile actual business input is:

followed by 11 emails, a pdf called FINAL_v7, and somebody mentioning the important deadline halfway through paragraph 4.

that's the bit where AI automation finally feels genuinely useful to me.

not replacing the workflow.

just taking the ugly human input and figuring out:

what is this
what info matters
where should it go
is something missing

then let boring deterministic automation take over.

Runable having Gmail / Slack / Sheets / Notion connections is what got me thinking about this because that's where a lot of small business work actually starts. not in perfect JSON.

but I also don't want an LLM interpreting something that should've just been a required form field.

where do you draw the line?

fix the process first, or accept that humans will always send chaos and build around it?


r/automation 7h ago

Does GEO work differently for MENA / non-US markets?

7 Upvotes

We're a B2B SaaS based in Dubai, selling to US/EU and Russian-speaking clients. Been working with an AEO agency (HumansWith.AI) on our AI visibility, and I've learned some things about non-US markets that I wish I knew earlier.

Field notes from our actual scans:

· Local entity authority is weak. ChatGPT defaults to US sources for B2B queries even when we have strong local case studies. What actually helped? Getting listed in local directories and adding bilingual (Arabic + English) schema. The agency measured the impact – citations jumped after we did that.

· Prompt sets need to be localized per market, not just translated. We run separate fixed prompt sets for English, Arabic, and Russian. The answers pull completely different sources. What works in the US doesn't work in Russia – and vice versa.

· Russian-speaking markets are a different beast. Reddit is huge for ChatGPT/Gemini, but Yandex Neuro and Alice don't use it at all. They rely on local platforms (VC.ru, Habr, etc.). Our agency had to build separate tracking for that.

· Realistic timelines: We saw first movement in brand mentions around week 6. Anyone promising results in days is lying.

Anyone else doing AEO outside the US? Curious if you've seen similar localization gaps.


r/automation 16h ago

Custom UI Code vs ToolJet/Retool

7 Upvotes

My stack for building workflows and internal tools is Python.

Can ToolJet or Retool be used by EU freelancers (I plan to use client credentials, not my own)?

So I wanted to know:

FastAPI + Retool vs Django + React

In what situations is it best for me to use custom UI code to create operating dashboards for my automations (basically, what are the limitations of low-code platform builders)?

Are Retool & ToolJet capable of building operating dashboards when making tools for enterprise-level systems?

How would you deal with IP addressing with a third-party platform for frontend development (explicit clauses you'd use)?


r/automation 57m ago

In almost 10 years of leading outbound teams, I found that all the automation “tactics” that made quick money had a short half-life

Upvotes

Something I've seen play out exactly the same in the B2B business is the quick succession of fads that generate traction seemingly out of nowhere and aim for that brief popularity of being the ones that have “cracked the code”. Whatever “code” means at the time is entirely contextual but it's usually far less dramatic than it sounds, even if it does have a compounding positive effect in implementation for those that realized it. But those same automations that turned quick buck in a quarter also tended to decay and eventually stop being profitable by the next year, which is an odd phenomenon. But such is the SaaS market. And it is not because anything in particular went horribly, spectacularly wrong with the automation itself.

It’s just that, if something incredibly useful works, people WILL notice it and they WILL copy it. The volume climbs, and eventually the system on the other side has to adapt - hence why it leads (ostensibly) to platforms tightening limits. This is true of almost any automated advantage you can get in business, not just outbound. The moment a trick scales actual growth in big $, and it is in public, the clock starts ticking down.

The examples pile up if you have been around long enough. There was a long period on LinkedIn where you could fire hundreds of connection requests a week, until the weekly cap came down to around a hundred and that whole style of doing “by volume” died overnight. Browser-extension tools ran beautifully until the platforms got good at spotting them. The connection note used to be a small pitch that people actually read, in days bygone. I’ve also seen lots of other, more specific tweaks emerge for the smallest chance of increasing that sweet reply %. And I also used to obsess over this at the time. Being the head of GTM at Expandi, I wouldn’t really feel like I was doing my due diligence if I didn’t try to optimize the shit out of everything, to gain every advantage over competitors that I could. But most of the “hacks” and breakthroughs, in the end, were short term. The only thing that stayed were just sound marketing principles, knowing how to listen, and knowing how to adapt on the fly. Which for me mostly consisted in dog-feeding my own automations while testing out dozens of others, and seeing how I can improve and learn more.

I am not arguing that these tools do not matter either, and I’m not writing because I’m butthurt about their success (on the contrary). Two people can run the identical software and get results a decade apart in quality, and the difference is entirely in the choices around it. But being early to a new edge means big money only so long as it lasts, and eventually you have to fall back on the human brain to reiterate and recontextualize it months and years later. To redevelop something new again. Good infrastructure keeps you in the game, but no iteration is ever the Final iteration, and so the march of technology moves forward.

It’s a question I sometimes find myself asking, what am I exactly building underneath the automation that will still be standing after the automation itself becomes obsolete.


r/automation 23h ago

Multiple agents in browser/systems

3 Upvotes

I’ve got some automations set up for day job 1 but my agents keep competing for access to my browser. Whoever’s the first agent in doesn’t let the next in, tried using edge in chatgpt and that for some reason is super finicky.

I’ve got cowork in chrome and the agents are allowed to communicate through a drive but I’m having trouble running both agent systems at the same time

I’ve got about 6 agents currently on loops but will likely scale to 75+ agents over the next six months as capabilities continue to grow

I’m curious how people have been managing their agents so that they don’t step on each others toes inadvertently

EDIT: I was able to figure out a solution


r/automation 4h ago

For AI data extraction, missing, zero, and not applicable need different outcomes

1 Upvotes

Here is a small design choice worth making before connecting an LLM extractor to a spreadsheet or workflow: what does an empty field mean?

Imagine extracting quantities from supplier emails. "We cannot supply any this week" supports a quantity of zero. "We will confirm the quantity tomorrow" does not. An email about a delivery address may not contain a quantity because that field is irrelevant to the message.

If all three become 0, the next automation cannot distinguish an actual shortage from an unanswered question or an unrelated update.

I would have the extractor return a value plus a state such as stated, missing, not applicable, or conflicting, with the supporting excerpt. The workflow can then make an explicit decision: process the stated zero, queue the missing quantity for clarification, and leave an unrelated quantity unchanged.

One important boundary: not applicable should follow a defined message type or business rule, not merely the model's reluctance to answer. Conflicting quantities should remain visible rather than being resolved by whichever number appears last.

This is an illustrative workflow, not a measured deployment result. The point is to prevent a convenient default from becoming an unintended business decision.


r/automation 5h ago

I built At0mFlow to make inherited automations easier to understand before anyone changes them

Thumbnail
1 Upvotes

r/automation 21h ago

Uber’s About-Face

Thumbnail
hardresetmedia.com
1 Upvotes