What to Automate First: A Practical 30-Day Roadmap for Chicago Small Businesses

"We should automate more" is one of those ideas that sounds great — until you sit down and try to pick what to automate.

Most Chicago-area small businesses we talk to aren't short on ideas. They have too many ideas:

- "Can we auto-route leads?"
- "Can AI write our proposals?"
- "Can we automate invoicing?"
- "Can we stop chasing signatures?"
- "Can we get our team to stop re-entering the same info into three systems?"

The mistake is trying to automate the biggest, flashiest thing first. That's how automation turns into a stalled project that everyone resents.

A better approach is boring (and it works): automate the workflows that are frequent, repeatable, and low-risk — then build toward the complicated stuff once your foundation is stable.

Below is a practical 30-day roadmap you can run in a typical SMB environment — Microsoft 365 or Google Workspace, QuickBooks, a CRM (or at least a shared inbox), and a few line-of-business tools. No hype. Just a plan that produces measurable time savings and fewer dropped balls.

Before you automate anything: pick the right targets

Not every process should be automated. In the early days, you want automation to reduce busywork, not introduce new failure modes.

Here's a quick decision filter we use:

Good automation candidates (do these first):
- Happen at least weekly (daily is even better)
- Follow a predictable "if X then Y" pattern
- Have clear inputs/outputs (a form submission, an email, a new invoice, a new employee)
- Are painful but not mission-critical (if it fails once, you don't lose a major client)

Bad early candidates (save these for later):
- Rare edge cases ("we do this once a quarter")
- Highly variable work that relies on judgment (heavy exceptions, negotiation, custom pricing)
- Anything that touches compliance or money without guardrails (payments, payroll changes, tax filings)

The 30-day automation roadmap (week by week)

Week 1: Stabilize your inputs (so automation has something reliable to run on)

Most automation fails because the business doesn't have consistent entry points. Leads come in through five channels. Requests come in via text messages. Tasks live in people's heads. If you automate on top of chaos, you get automated chaos.

Week 1 is about picking one standard for each major input.

Day 1–2: Define your "single front door" for each workflow

Pick one primary intake method for each:

- Sales leads: website form + shared inbox (leads@…)
- Customer support/internal requests: shared inbox (support@… or help@…) or a simple ticketing tool
- New hires: a short onboarding form or checklist with an owner
- Vendor invoices: AP@ inbox or a single upload location

Don't over-engineer this. The goal is not "perfect." The goal is "consistent."

Day 3–4: Inventory your systems and owners

Create a simple list:

System → What it's used for → Owner → Admin access
Examples: Microsoft 365, Google Workspace, QuickBooks, HubSpot, your scheduling tool, your phone system.

Automation almost always needs admin-level access (API keys, permissions, shared mailboxes). If no one owns a system, automation becomes a political problem instead of a technical one.

Day 5: Choose your automation "hub" (don't use five tools)

For many SMBs, the simplest choice is to start with what you already have:

- If you're on Microsoft 365: Power Automate + Outlook + SharePoint/OneDrive can go surprisingly far.
- If you're on Google Workspace: Google Forms + Apps Script (light) or a connector tool can cover common flows.
- If you're tool-agnostic: Zapier or Make are common for SMB-friendly integrations.

Pick one hub for the first month. You can always expand later, but switching tools midstream creates half-built automations everywhere.

Week 2: Automate notifications + task creation (the safest, highest-ROI wins)

If you only automate one category first, do this: whenever something important happens, create a trackable item and notify the right person. This reduces missed follow-ups, delays, and "I thought you had it."

Day 6–7: Lead intake → create a record + alert

Minimum viable automation:

- Website form submission → create a CRM contact/deal or add a row to a "Leads" sheet/table
- Send an alert to a shared channel (Teams/Slack) and/or assign a task to a person

Guardrail: alerts should go to a shared place, not just one individual. People get sick, go to court, go on vacation, get stuck on a job site. Your pipeline should not depend on one inbox.

Day 8–9: "Request received" auto-reply with expectations

When someone fills out a form or emails support@, send a branded auto-reply that:

- Confirms receipt
- Sets a response window ("We respond within 1 business day")
- Provides an urgent fallback ("If this is urgent, call …")
- Offers scheduling if appropriate

This is simple, but it reduces anxiety and improves conversion because prospects feel taken care of immediately.

Day 10: Internal requests → ticket/task

Common SMB pain: requests arrive via email/text/drive-by conversations and then disappear.

Automation target:

- Email to help@ → create a ticket/task in your system (Help Scout/Freshdesk/Planner/Asana/etc.)
- Auto-tag by keywords ("password reset," "new user," "invoice question") and route to the right queue

Even if you don't have a helpdesk, you can create a lightweight queue in a shared task list. The point is: requests become trackable.

Week 3: Automate document routing (files, signatures, and "where did that PDF go?")

After leads and tasks, the next best automation targets are documents. Chicago SMBs often lose hours to manual file naming, hunting down the latest version, and chasing signatures.

Day 11–13: Standardize file storage locations (so automation knows where to put things)

Pick one primary home for internal documents:

- Microsoft: SharePoint/OneDrive (with clear team sites and permissions)
- Google: Shared Drives (not personal My Drive)

Then create a simple convention:

- /Clients/ClientName/
- /Vendors/VendorName/
- /HR/EmployeeName/
- /Finance/Invoices/

Day 14–15: Form submission → create a folder + save attachments

This is a surprisingly high-impact automation for service businesses.

Example: "New client intake form" includes uploads (photos, PDFs, IDs, W-9s).

Automation flow:

- Form submitted → create folder "Client - [Name] - [Date]"
- Save uploaded files into that folder
- Post a link to the folder in the CRM record or the project/task

Guardrail: keep permissions tight. Intake uploads often contain sensitive data. Make sure folders inherit the right access controls.

Day 16–17: E-signature routing + status reminders

You don't need "AI" to improve signatures. You need a consistent flow.

Automation ideas:

- When a proposal/contract is sent → create a follow-up task due in 2 business days
- If not signed in 3 days → send a polite reminder email template
- When signed → save PDF to the right folder and notify the internal owner

This alone can improve cash flow and reduce the "we forgot to send the agreement" problem.

Week 4: Automate handoffs (onboarding, offboarding, and recurring admin)

Week 4 is where you start saving time across departments. These automations touch more systems, so you do them after you've proven your basics.

Day 18–20: New hire onboarding checklist automation

For many SMBs, onboarding is a repeatable workflow with a lot of manual coordination:

- Accounts (email, line-of-business apps)
- Hardware (laptop, phone, accessories)
- Access (shared drives, password manager, tools)
- Training (policies, SOPs)

Automation target:

- New hire form submission → create a standard onboarding project with tasks assigned to IT, HR, and manager
- Set due dates relative to start date (T-3 days, Day 1, Week 1)

This doesn't have to provision accounts automatically on day one. Even just creating the task pack prevents last-minute chaos.

Day 21–23: Offboarding "must not miss" automation

Offboarding is risk management. Missed steps become security incidents.

Automation target:

- Termination/exit form → generate an offboarding checklist (disable accounts, revoke access, retrieve hardware, transfer files)
- Notify the right people (manager + IT) immediately

Guardrail: offboarding is one area where automation should create tasks and alerts, but humans should confirm completion. Don't auto-delete accounts without a review step.

Day 27–30: Measure impact and harden what you built

By the end of the month, you should have 3–6 working automations that your team actually uses.

Spend the last few days doing what most teams skip:

- Document the owner of each automation ("If this breaks, who fixes it?")
- Add error alerts (if a run fails, someone gets notified)
- Reduce noise (too many notifications = everyone ignores them)
- Create a simple change log (what was modified and when)

Automation that nobody trusts is worse than no automation. The hardening step is what turns experiments into infrastructure.

Two simple examples (SMB-realistic)

Example 1: A Chicago-area home services company (lead response automation).
Their leads came from a website form and a Google Business Profile message inbox. The owner assumed "someone sees them." In reality, responses were inconsistent — and speed-to-lead was often 6–24 hours.

We implemented a simple week-2 flow:

- New web form or GBP message → create a lead entry in a shared tracker/CRM
- Instant Teams/Slack alert to a shared "New Leads" channel
- Auto-task assigned to the on-call coordinator with a 30-minute due time

No AI, no big rebuild. The result is predictable follow-up and fewer lost jobs — because the business responds while the customer still has urgency.

Common mistakes (and how to avoid them)

Mistake #1: Automating a broken process.
If your lead intake is unclear, automating it just makes the confusion faster. Fix the workflow first (even a simple SOP), then automate it.

Mistake #2: Too many notifications.
If every automation pings everyone, people start ignoring alerts. Route notifications to the smallest responsible group.

Mistake #3: No naming conventions.
Automations that create files/folders without a standard format produce a bigger mess. Pick naming rules once and stick to them.

Mistake #4: No owner, no maintenance plan.
Automations aren't "set it and forget it." Apps update, permissions change, and workflows evolve. Assign an owner and schedule a quarterly review.

If you're not sure where to start, start here

If you want one "default" place to begin, pick one workflow and implement this three-step pattern:

1) A consistent intake point (form or shared inbox)
2) Automatic record creation (CRM/ticket/task)
3) Automatic notification to the right person (with a due time)

That pattern solves more SMB operational pain than most "AI initiatives." And once it's working, you'll have the confidence (and the foundation) to tackle more advanced automation later.

Want a 30-minute plan for your specific stack?

Every Chicago-area business has its own mix of tools and constraints — Microsoft 365 vs Google, QuickBooks vs other accounting, a CRM vs spreadsheets, different compliance needs, and different team habits.

If you want help deciding what to automate first (and what to avoid), book a 30-minute tech stack audit call. We'll map your current workflows, identify the highest-ROI automations for the next 30 days, and outline a realistic path that your team can actually maintain.