Otomat: What People Mean When They Search That Word (And What I Actually Do)

Last Tuesday I was watching someone at a small logistics company manually copy order details from an email into a spreadsheet. Copy, paste, reformat the date, check the customer code, paste again. They did this maybe forty times before lunch. I asked how long they'd been doing it this way. 'Since we started,' they said, without looking up.

That scene lives in my head rent-free. Not because it's rare, but because it's completely ordinary. And it's exactly the kind of thing that sends people searching for words like 'otomat' when they half-remember reading about automation somewhere.

What 'Otomat' Actually Is (And Isn't)

Let me clear this up before we go further. 'Otomat' is not a product, a company, or a category. It's a common misspelling of 'automat' or 'automate' -- the kind of thing that happens when you're typing fast on a phone and your brain is already three words ahead.

People land on my site via searches like 'otomat business', 'otomat workflow', 'otomat repetitive tasks'. What they're looking for is exactly what I write about: taking the tedious, human-error-prone, copy-paste-and-pray parts of running a business and making them happen automatically.

The typo is actually kind of endearing. It suggests someone urgently interested in the concept, not yet sure what to call it.

The Real Problem Behind the Misspelling

Here's what I've noticed after years of building automation tools: people don't search for 'workflow automation platform'. They search for the pain. 'How to stop copying emails into spreadsheets.' 'Automatic invoice reminder.' 'Get quotes faster without calling everyone.'

The word 'otomat' fits that pattern. It's someone who knows there's a solution, doesn't quite have the vocabulary for it yet, and is reaching for the concept with whatever spelling comes out.

This matters because the vocabulary gap is itself a problem. A lot of businesses that would benefit hugely from automation never pursue it because they don't know the right words to search for, or they search and land on enterprise software pages that quote them per-seat annual contracts before showing them a screenshot.

According to McKinsey's research on automation, roughly 60% of all occupations have at least 30% of activities that could be automated with current technology. That number has been cited in various forms for years, but what strikes me is the flip side: the majority of those activities still aren't automated. Not because the technology is missing. Because the knowledge gap is.

The copy-paste economy

I have a working theory that a significant chunk of office time in small businesses is what I call 'copy-paste work'. Moving data from one place to another. Reformatting it so it fits the next system. Sending the same email with slightly different names in it. Checking whether a thing happened and then updating a spreadsheet to say it happened.

None of this requires a human. Humans are expensive, error-prone, and get tired. The copy-paste economy is a tax on every business that participates in it, and most businesses don't even notice they're paying it because the cost is spread across dozens of tasks that each feel 'quick'.

I've written more about why small businesses keep doing repetitive work by hand -- the short version is that most of it comes down to habit and the low visibility of the cumulative cost.

What Automation Actually Means for a Small Business

I want to be specific here because the word 'automation' covers a lot of ground. At one end you have industrial robots welding car frames. At the other you have a script that sends a text message when a form is filled out. For most small businesses, the useful stuff is much closer to the second end.

The Zapier State of Business Automation report has consistently found that small businesses using automation report saving meaningful time on tasks like data entry, customer follow-up, and internal notifications. The specific numbers shift year to year, but the direction is consistent: people who automate routine tasks get that time back for work that actually requires a human.

What does that look like in practice?

Quotes and inquiries

I built Grease Trap Quotes because I watched a restaurant owner spend an afternoon calling grease trap cleaning companies, leaving voicemails, and waiting. The whole thing -- getting three competitive quotes -- took days. I made something that delivers three quotes by SMS in sixty seconds. That's not magic. It's just connecting the right data to the right people without a human in the middle.

Inbound calls

Trades businesses bleed leads from missed calls. A plumber is under a sink, an electrician is in a switchboard -- nobody's answering the phone. CallCrewHQ is an AI front desk that handles those calls, captures the details, and follows up. The human still does the actual work. They just stop losing the jobs they never knew they were called about.

Both of those are 'otomat' in the spirit the searcher intended: take a thing that required repeated human effort and make it happen on its own. If you want a concrete sense of what this kind of AI phone handling looks like in practice, that post gets into the specifics.

How to Think About What's Worth Automating

Not everything should be automated. I want to be clear about that. Some things require judgment, relationship, or genuine human touch. The question isn't 'can this be automated' but 'does a human need to be the one doing this specific step'.

A useful filter: if someone could do the task while watching TV without making errors, it's probably automatable. If it requires real-time judgment calls or emotional intelligence, it's probably not.

The Harvard Business Review has written about the distinction between automating tasks that are routine and structured versus those that require improvisation. The practical upshot for small businesses is: start with the stuff that's structured and repetitive, because that's where the easy wins are and where you're most likely to get a clean result.

Signals that something is worth automating

You know a task is a candidate when: you or someone on your team does it more than a few times a week, it follows the same steps each time, the information is already digital (or could be), and the cost of a mistake is low-to-medium. If all four of those are true, you're probably leaving money on the table.

If any of those are false -- the task is highly variable, the data is messy, or an error would be serious -- automation needs more thought, not less. Start simple. I've gone into more detail on how to pick your first automation project if you want a more structured way to think it through.

Getting Started Without Losing Your Mind

The number one mistake I see people make when they decide to automate something is picking a complex, tangled process as their first project. They want to automate the thing that annoys them most. That's understandable. It's also how you end up three weeks deep in a half-finished workflow that breaks in new ways every day.

Pick something small. Something where you can see the whole process in one sitting, where the inputs are clean and the output is clear. Get one thing working. Then use that confidence to tackle the next.

The MIT Sloan Management Review makes a version of this point about AI and automation adoption: organizations that start with focused, bounded use cases build the internal knowledge and trust needed to scale. The ones that try to boil the ocean first tend to get burned.

Start with the copy-paste task. Fix the thing that has someone copying forty order lines before lunch. That's the 'otomat' the searcher was looking for. And if you're not sure where the copy-paste tax is hiding in your business, I've written about spotting the hidden manual work that drains your week -- it's usually in the gaps between your tools.

If You Want a Hand With This

If any of this sounds familiar -- you're doing repetitive work that feels like it should be someone else's problem, or you've tried to figure out automation before and got lost in the options -- feel free to reach out. I like talking through this stuff, and I'm usually pretty quick to say if something isn't worth automating. No pitch, no form with seventeen fields. Just drop me a message.

Related reading: Utome, Utomat, and the Typo That Keeps Finding Me.