AI workflow automation
Connect the steps across your apps with n8n. Route information, apply your rules and move routine work forward.
n8n · Workflow orchestrationIndependent AI & automation practice
Less busywork.
More momentum.
Connect your tools. Simplify the handoffs.
Put practical AI to work in your business.
I build workflows, AI agents and integrations around the way your team actually works.
Work directly with Moe. Start with one clear use case.
A clearer way to work01 → 04
ILLUSTRATIVE WORKFLOWConnected. Considered. Useful.
Built around your stack
n8nPythonAPIs & webhooksAI modelsYour CRM
01 / What I build
Make the work
between tools disappear.
For agencies and B2B teams dealing with repetitive tasks, scattered information and manual follow-ups. Begin with the process that gets in your way.
Practical AI agents
Give AI a defined job: find information, summarize context or prepare a next step—with clear limits and human review.
AI models · Tool connectionsSupport & email automation
Sort incoming requests, draft relevant replies and route exceptions to the right person before they fall through the cracks.
Inbox triage · Reply draftingLead follow-up
Turn new enquiries into an organized follow-up process, with useful context, reminders and agreed sending rules.
Lead routing · Follow-up logicCRM integration
Keep contacts, deal details and activity connected across your tools. Map your fields and handle duplicate or missing data.
Data mapping · Record updatesPython & API integrations
Connect tools that do not fit neatly together. Use custom scripts, webhooks and APIs for the parts that need a closer fit.
Custom logic · API connections02 / In practice
One process.
A better way through it.
A useful automation starts with a specific task. Explore a few examples of what that could look like.
EXAMPLE / LEAD ENQUIRIESFrom new enquiry
From new enquiry
to a useful next step.
Give a person the context to follow up, without asking them to copy information between tools.
- 01Capture the enquiry
A form or inbox receives a new lead.
- 02Organize the context
AI drafts a summary and suggests a route.
- 03Review & follow up
A person checks the details before the agreed CRM update or reply.
EXAMPLE / SUPPORT INBOXA quieter inbox.
A quieter inbox.
A clearer queue.
Separate routine questions from exceptions and put a useful draft in front of the person replying.
- 01Receive the request
A customer email enters the support inbox.
- 02Find the right context
Use approved reference material to classify the request and draft a reply.
- 03Check & route
A person reviews the draft; uncertain or sensitive cases are escalated.
EXAMPLE / CRM HANDOFFSKeep the context.
Keep the context.
Skip the retyping.
Move the right information between systems with field mapping and a clear path for exceptions.
- 01Notice a change
A source tool sends a webhook or a scheduled check finds an update.
- 02Validate & match
Check required fields and match the existing record to reduce duplicates.
- 03Update or flag
Apply the agreed changes and send missing or conflicting data for review.
Illustrative examples, not client case studies. The actual scope depends on your tools, permissions and requirements.
03 / How we'll work
Clear scope.
Thoughtful delivery.
Start small, check the details and build something your team can understand and use.
Map the process
Walk through the task, your tools and the awkward handoffs. Agree on what should happen—and what should stay with a person.
A clear scope & agreed milestones
Build & test
Create the workflow and test typical inputs, exceptions and failure paths. Review the behavior together before enabling live actions.
A working flow to review
Launch & hand over
Enable the agreed workflow, document how it works and explain how to manage it. Set any ongoing support scope before launch.
Documentation & a practical handover
04 / Good questions
Before we
get started.
Practical answers for a practical project.
What is a good first project?
A repetitive task with a clear input and a clear next step: routing enquiries, preparing support replies or moving data into your CRM. We can start with one workflow and agree on how to check that it works.
Can you work with the tools I already use?
Often, yes. I check the available APIs, n8n connections, account permissions and platform limits before confirming the scope. If a tool cannot support the workflow reliably, I'll say so.
Will AI send messages or make changes on its own?
Only if we explicitly agree to that behavior. Workflows can prepare drafts, request approval and route uncertain cases to a person. We define which actions need review before anything goes live.
How are price and timing decided?
After a short review of the process, I propose a scope, milestones, fee and timeline. Tool subscriptions, hosting and AI usage costs are discussed separately so you know what is included.
How will access and business data be handled?
We agree on access, data flows and any third-party services before building. Share only what is needed and use limited permissions where possible. Don't send passwords, API keys or sensitive customer data in the initial brief.
What happens after the handover?
The project includes the agreed documentation and handover. Ongoing monitoring, maintenance and changes can be scoped separately. Ownership and access to accounts, workflows and custom code are agreed before work begins.
Start with one workflow
What keeps
getting done
by hand?
Tell me about the process. I'll assess what could be automated and suggest a sensible starting point.
Email me about your workflow
If you found me through Upwork, keep project discussions and payments on Upwork.
YOUR STARTING POINT
Make a quick project brief.
A little context makes a better conversation. Copy your brief, then send it when you are ready.