AI & Automation · Business Strategy
✍️ Bea Lejano · 📅 June 2026 · ⏱ 6 min read
A client recently asked me whether we should add AI to read handwritten sales order forms from their field team. My answer was no — and I want to explain why, because that conversation gets to something I think a lot of businesses are getting wrong about AI right now.
We’re in a moment where AI feels like the answer to everything. New tool? Add AI. Slow process? AI will fix it. Messy data? AI can handle it. But that reflex — reaching for AI first — skips a more important question: does this actually need AI, or can an automation do it better?
Most of the time, it’s the automation.
Questions to ask before adding AI to any workflow
Acceptable error rate for revenue-critical workflows
What automations run on. It doesn’t change its mind.
The Handwritten Order Form Problem
The specific request was this: field sales agents submit handwritten purchase orders. Could AI read those forms, extract the order details, and route them automatically into the system?
In theory, yes. AI can read handwriting. Computer vision has gotten remarkably good. But here’s the problem: handwriting varies. Ink smudges. Forms get photographed at odd angles. A number 7 looks like a 1. A product code gets cut off at the edge of the frame. And when AI makes a mistake reading a sales order — it misreads a quantity, gets a product SKU wrong, or misses a line item entirely — that mistake flows directly into revenue.
Sales orders aren’t social media posts. There’s no margin for “mostly right.”
💬 The answer wasn’t “AI can’t do this.” The answer was “when AI makes a mistake here, the cost is too high to accept — and a human validator still needs to be in the loop anyway. So we didn’t gain much by adding AI in the first place.”
Automations Don’t Hallucinate. AI Does.
This is the core distinction that gets lost in the AI hype: a well-built automation runs on logic. If a form is submitted, a record is created. If an expense exceeds a threshold, it routes to the right approver. If a customer is tagged as a distributor, they see distributor pricing. These outcomes are deterministic — the same input produces the same output, every time, without exception.
AI doesn’t work that way. AI interprets. It infers. It makes probabilistic judgments based on patterns. That’s genuinely powerful — but it means AI can be confidently wrong. It can misread context. It can fill in gaps with assumptions. The same input can produce a different output on a different day.
For many use cases, that uncertainty is acceptable — even desirable. For others, it’s a dealbreaker.
The 3 Questions to Ask Before Adding AI to Any Workflow
Before reaching for AI, run through these three questions. They’ll tell you quickly whether AI is actually the right tool — or whether automation will get you there more reliably.
Can an automation handle this instead?
If the process follows a clear rule — if X happens, do Y — then automation is almost always the better choice. Structured data, defined logic, predictable inputs. Automations handle this without interpretation errors, without hallucinations, without variability.
Reserve AI for situations where the logic genuinely cannot be pre-defined — where the input is ambiguous, unstructured, or requires contextual judgment that a rule can’t capture.
What happens when it’s wrong?
This is the impact assessment question — and it’s the one most people skip. For the handwritten sales order scenario: a mistake means a wrong quantity shipped, a revenue discrepancy, a client dispute. The downstream cost is significant.
Compare that to social media content analysis. If AI misclassifies a post’s engagement tone, the marketing team reviews the weekly report and adjusts. The cost of a wrong answer is low. That changes the calculus entirely.
Is the input something AI reads reliably?
AI performs best on clean, structured inputs — well-formatted text, JSON data, clear digital copy, consistent language. It performs less reliably on ambiguous inputs: handwriting, inconsistent formatting, images with variable quality, intent that depends heavily on context.
This doesn’t mean AI can’t handle ambiguous inputs — it can, and it often does impressive work. But the error rate goes up, and you need to factor that into whether AI belongs in that specific workflow.
When AI Is Exactly Right: A Real Example
AI isn’t the wrong tool — it’s the wrong tool when applied without asking these questions. I want to be clear about that, because I’ve built AI-powered systems that work precisely because they were designed for the right use case. One of them is a multi-layered social media intelligence agent I built for a B2B brand — you can read the full case study here.
For a Philippine herbal brand, I built a multi-layered AI agent system that scrapes their Facebook posts weekly, analyzes each post for engagement performance and ICP alignment, and delivers a strategic content briefing to the marketing team every Monday morning — automatically, with no manual work required.
That system uses AI to read images and text from social media posts and evaluate them against the brand’s ideal customer profile. It’s analyzing sentiment, visual content, messaging alignment — exactly the kind of contextual, interpretive work that automation cannot do.
Run it through the three questions:
All three questions clear. AI is the right tool. And the system works exactly as designed — delivering weekly intelligence the team actually uses, without anyone having to compile it manually.
AI Has Its Place. But Automation Should Always Come First.
The most robust operational systems I’ve built are primarily automation-driven, with AI layered in only where it genuinely earns its place. Automation handles the structured, high-volume, rules-based work — form submissions, data routing, approval chains, notifications, file organization. AI steps in for the interpretation layer — classifying open-ended email inquiries, analyzing content performance, generating summaries from unstructured input.
When you flip that relationship — when you reach for AI first and ask it to do the work that a structured automation could handle more reliably — you introduce variability into processes that don’t need it. You add cost. You add a validation layer that didn’t exist before. And you create a system that looks impressive until the day it quietly gets something wrong.
💬 The question isn’t “can AI do this?” — the answer to that is almost always yes. The question is “should AI do this, given what happens when it gets it wrong?” Start with automation. Add AI where interpretation genuinely adds value and where imperfect answers are acceptable. That’s how you build systems that actually hold up.
Not Sure Whether Your Workflow Needs AI or Automation?
That’s exactly the kind of question I work through with businesses before any build begins. Let’s map out what your operations actually need — and what tool deserves to be in each part of the process.
Or send a message at [email protected] to start with a few questions first.
About Bea Lejano
Bea is the founder of Digital Freedom with Bea, an AI and automation systems consultancy based in Metro Manila. With 10+ years of corporate operations experience, she builds custom automation systems for Philippine SMEs, trading companies, and field-driven operations using Airtable, Zapier, Fillout, OpenAI, and the Microsoft 365 stack. www.digitalfreedomwithbea.com
Leave a Reply