Small Business Automation:
Stop Doing the Computer's Job
If someone on your team opens an email, reads an attachment, and types what it says into another system — that's the computer's job, being done by a person. Most small businesses have three or four of these jobs hiding in plain sight.
I'm Andrew Judd. I've been running my development business since 2014, and automating exactly this kind of work is most of what I do — remotely, for businesses anywhere, and in person around the GTA when it helps.
The test: is a person re-keying anything?
The simplest way to find automation candidates isn't a process audit — it's one question: does information that already exists in digital form get retyped by a human? If yes, that step can almost always be removed. Orders, invoices, timesheets, customer records, intake forms — anything that arrives by email or upload and ends up in a database, spreadsheet, or accounting system by way of someone's keyboard.
If your team re-keys anything, that job belongs to a computer. The question is just what it costs to move it there — and whether that math works for your volume.
What I've automated (with receipts)
I write up my automation work in detail — real architectures, real failure modes, real costs — so you can judge the work before you ever talk to me.
Email to database, no human in the middle
At one company I worked with, invoices and purchase orders arrived by email and were retyped into the system. I built the pipeline that ingests them automatically — here's exactly how it works, from the mail server to the structured database row.
Documents that read themselves
Scanned paperwork, handwriting, photos of forms — I've built production OCR pipelines that turn them into structured data, and the modern approach costs less than a penny per document. That's not a vendor's pricing page talking; those are my actual numbers from processing thousands of documents.
Infrastructure that minds itself
Automation you can't trust is worse than none. I run my own backup system that verifies its restores and monitoring that catches failures before users do — and I've documented every bug I hit making it reliable.
Where AI fits (and where it doesn't)
The useful version of AI for a small business is boring: reading documents, extracting fields, classifying messages, drafting the first version of repetitive text. It's cheap, it works today, and it slots into pipelines like the ones above.
The not-useful version is anything pitched as "AI will run your business." I use AI where it beats the alternative on cost and accuracy, and I'll show you the math either way.
The practical test: if a task is high-volume, low-judgment, and currently done by a person reading something and typing it somewhere else — AI is probably cheaper and faster than the person. If it requires real judgment, domain expertise, or trust decisions, AI is a draft assistant, not a replacement.
What automation actually costs
Less than you'd guess to run — the email-to-database pipeline above sits on infrastructure that costs a few dollars a month. The build is the real cost, and it depends on how many systems are involved and how messy the current process is.
I won't guess at a number on a first call; there are usually too many unknowns hiding in the details. What a 60-minute working session gives you: a map of the process, what's automatable, where the unknowns are, and what it takes to scope a real quote.
~$5/mo
Typical running cost for a simple pipeline
<¢1
Per document with modern vision models
2–4 wks
Typical time to ship a first pipeline
How an engagement works
Tell me about the problem
Book a 60-minute working session ($100 USD) — we'll map the manual process, what's automatable, and what scoping it properly looks like. Not sure a session is the right fit yet? The contact form works for anything else. A few sentences about your process is enough.
A small first project
Something shippable in 2–4 weeks — one pipeline, one integration — so you can judge the work before committing to more.
Ongoing only if it earns it
Some clients need a retainer; many just need the thing built, documented, and handed over. Everything I build is on boring, maintainable technology (Laravel, PHP, MySQL) that any developer can take over after me. The how to hire a developer guide covers the full range of engagement models.
Frequently asked questions
What's the most common first automation for a small business?
Document intake — invoices, orders, or forms that arrive by email and get retyped. It's high-volume, low-judgment work, which is exactly what automates well. It's also the example I've written about in most detail.
Do you work remotely?
Yes — remote is my default mode and most of my clients are remote. I'm based in the GTA, so local businesses get in-person options too.
Will automation break when our process changes?
Only if it's built brittle. I design pipelines to fail loudly — alerts and fallbacks to human review — rather than silently. A lesson I learned the hard way running my own systems.
Do we need to replace our existing software?
Almost never. Most automation lives in the gaps between systems you already use — taking output from one and putting it into another without a human bridge.
What if our volume is small — is it still worth it?
Sometimes no, and I'll say so. The math is hours saved per month × what those hours cost, against the build. A 60-minute session is usually enough to tell whether that math is even close — and to surface the unknowns that decide it.
Have a process that eats an hour a day?
Tell me about it. A few sentences about what your team does repeatedly is enough to start the conversation.
Working session: $100 USD · 30-min mentoring session: $60 USD