Make Your Team Faster

Most companies have work that a person does every week because nobody ever sat down and automated it. Pulling the same report. Checking the same list. Copying data between two systems that were never introduced. Chasing a shared inbox. It is not the hard part of the business, and it quietly costs more than anything on the invoice.

This is the second of three things I do. Where documentation work makes the process visible, this side makes it run with fewer hands on it, and puts real checks around it so it stays trustworthy.

Find Where the Time Actually Goes

The first job is not automation. It is finding out where the hours go, and being honest about which of them should be automated at all. Some tasks look repetitive and carry a judgment call in the middle. Those are the ones that go wrong quietly when you hand them to a machine.

I shadow the team and map the process as it really runs, then sort the work into three piles: automate it, leave it alone, and change the process so the work stops existing. The third pile is usually bigger than people expect.

• Process mapping across the systems you already pay for
• A ranked list of time sinks with hours saved per fix, so you choose by payoff
• Honest scoping of what automation saves and what it costs to maintain

Connect the Tools That Do Not Talk

At one organization I replaced dozens of manual weekly tasks with scripts: user provisioning from a form, a standup report assembled from three systems, alert triage, access reviews, health checks. Each one was small. Together they gave a one-person IT department the capacity of three.

• Integration between Microsoft 365, Google Workspace, your line-of-business apps, and spreadsheets
• Scheduled jobs that run without anyone remembering to start them
• Reporting that arrives on its own instead of being assembled on Friday afternoon
• Onboarding and offboarding that takes minutes instead of a checklist and a day
• Shared-inbox work turned into a tracked queue with an owner and a status

Put AI Where It Earns Its Keep

AI is very good at drafting, summarizing, classifying, and extracting, the work that is tedious rather than difficult. It is unreliable in exactly one way that matters: it will produce a confident, well-formatted answer that is wrong, and nothing about the output looks different when that happens.

So the automation is only half the job. The other half is the check. A safety net that verifies the format is correct will pass a false answer every time. The check has to test whether the claim holds up against the underlying data. I build that check first, and I prove it can fail before I trust it to pass.

• Identifying which tasks AI is actually suited to, and which it is not
• Drafting, summarizing, and classification built into existing workflows
• Verification steps that test the answer, not the formatting
• A human approval point wherever the cost of being wrong is high
• Spend limits and usage alerts, so a metered service cannot surprise you

Write-Ups From This Work

These are the decisions and the mistakes behind the list above, written out in full.

See everything on the blog →

How This Usually Starts

With a one-week process audit. I shadow the team, and you get the ranked list of time sinks with an estimate for each. Fixed price. Almost always we then automate the one process everybody complains about, end to end with the checks in place, and you have something working before we discuss anything larger. If it does not pay for itself, that is a cheap thing to find out. When the fix needs more than glue, it becomes custom software.