← Back to home

Process Automation Consultant

Stop burning hours on tasks a script could handle in seconds.

The problem

Your team spends half the day copy-pasting data between tools. Exporting a CSV here, reformatting it there, sending the same follow-up email for the third time this week. Someone built a spreadsheet that "kind of" tracks everything, but it breaks every Monday and nobody remembers how it works.

You know this could be automated. You've seen the tools, read the blog posts, maybe even started a Zapier account that's been sitting unused for six months. But between figuring out what to automate first, choosing the right tool, and actually building the thing, nothing moves. Meanwhile the manual work piles up, people get frustrated, and the best employees start spending their energy on tasks that a script could handle in seconds.

Not a motivation problem. A priority problem. You need someone who looks at your operations, spots the time sinks, and builds the fix.

What I do

Process audit and time recovery mapping

I start by watching how your team actually works. Not the process diagram from 2019. The real one, with the workarounds, the manual steps nobody documented, the "we've always done it this way" routines. I map every manual task, estimate how many hours it eats per week, and rank them by automation ROI. Some tasks save 30 minutes a week. Others save 10 hours. We start with the ones that hurt most.

Workflow design and implementation

This is where the hours come back. I connect your tools together so data flows without anyone touching it. CRM to invoicing. Form submissions to database. Report generation that used to take a full morning, now runs on its own before you get your coffee. At Google (through Teleperformance), I automated SQL-based reporting workflows that saved 10 hours of manual work per week. I use n8n, Google Apps Script, or Python depending on what fits your stack. No over-engineering. Just the simplest solution that works.

Monitoring and maintenance

Automations aren't "set and forget." APIs change. Data formats shift. A field gets renamed and the whole chain breaks at 2 AM. I set up monitoring and alerts so you know the moment something fails. Every workflow comes with clear documentation so your team understands what runs, why, and how to fix basic issues themselves. The goal is your autonomy, not a permanent dependency on me.

How it works

1. Discovery call
30 minutes, free, no commitment. You walk me through the processes that frustrate you most. I ask questions, identify quick wins, and tell you honestly whether automation will actually solve the problem or just move it somewhere else.
2. Manual process audit
I dig into the workflows you flagged. I document every step, every tool involved, every manual handoff. You get a clear report: here's what can be automated, here's the estimated time saved, here's what to tackle first. No jargon, no 80-page deliverable. A prioritized action plan.
3. Iterative implementation
I build the first automation, you test it with real data. We adjust, improve, move to the next one. No big-bang deployment where everything changes overnight. Each workflow goes live when it's solid, and your team validates it before we proceed.
4. Documentation and autonomy
Every automation is documented: what it does, how it triggers, what to check if something looks off. I walk your team through it. When the project ends, you own everything. You can modify it, extend it, or hand it to someone else. No lock-in.

Tech stack

n8nGoogle Apps ScriptPythonREST APIsSQLBigQueryZapier

Frequently asked questions

What's the difference between automation and AI?

Automation follows rules you define. If this happens, do that. It's predictable, reliable, and perfect for repetitive tasks with clear logic. AI makes decisions based on patterns. It reads unstructured text, classifies data, generates content. They complement each other well. Most process automation projects start with rule-based workflows. When you need the intelligence layer on top, I also work on AI integration projects.

How long does it take?

It depends on the complexity. A simple workflow connecting two tools takes a few days. A full process overhaul with multiple integrations can take a few weeks. The discovery call is free precisely for this reason: I need to see what you're dealing with before giving you a timeline. And if the project isn't worth the investment, I'll tell you upfront.

What if my tools aren't compatible?

Most modern tools have APIs, even if they don't advertise it loudly. n8n connects to hundreds of services out of the box, and custom API integrations cover nearly everything else. If a tool genuinely can't be connected, I'll tell you before we start. Sometimes the honest answer is "replace this one tool first, then automate."

Your team's time is worth more than copy-paste

Every hour your team spends on manual data entry is an hour they're not spending on work that actually moves the business forward. If you suspect there's a better way, there probably is. 30 minutes is all it takes to find out.