AI automation workflows for sales and marketing teams
There's a difference between automating and stacking tools. Many teams already have n8n, Make, or a Clay subscription lying around, but none of it is actually wired into their real processes. The result: tools they pay for, underused, and the same tasks still done by hand every week.
I build workflows that plug into your existing processes, not demo automations running in a closed loop that never touch the team's actual work.
Who it's for
I work with B2B SMBs and scale-ups facing one of these situations:
- A team enriching leads manually, one by one, when the process could run on its own
- A founder who wants automatic alerts on important sales signals (a new hot lead, a customer status change, churn risk) instead of finding out everything in a weekly meeting
- A team losing significant time each week manually building reports from multiple data sources
What I actually do
I build automations with tools suited to your volume and budget, mainly n8n, Make, and Clay for orchestration, and Claude for tasks that require reasoning (writing, qualification, synthesis) rather than plain mechanics:
- Auto-enrichment: as soon as a lead enters your CRM or prospecting tool, it gets enriched automatically (company data, context, contact details) with no manual work
- Scoring: rules that automatically prioritize leads or opportunities based on criteria you define together, so the sales team focuses on what matters
- Alerts: automatic notifications on important sales events, sent wherever your team already works (Slack, email, CRM)
- Automated reports: regular reports generated from your real data, without someone having to compile them by hand every week
I remain opposed to 100% automation with zero human involvement. The goal is to give you back time on mechanical tasks, not to remove human judgment where it actually matters.
How it works
Sprint Quick Wins method applied to automation:
- Audit: I map your current processes to identify the high-volume repetitive tasks worth automating first, and the ones that aren't
- Quick wins: I first build one or two automations with fast, visible impact, to validate the approach on a small scope
- Systems: once validated, I roll out the full set of workflows (enrichment, scoring, alerts, reports) connected together, not in isolated silos
- Handover: documentation of each workflow and team training so they can adjust the rules themselves without depending on me for every change
What changes
On similar engagements: up to -40% admin time on the tasks concerned, 100% of leads processed automatically where some used to slip through the cracks, and sales team productivity tripled when automation touches the core of the prospecting process directly.
Frequently asked questions
No. I favor no-code or low-code tools (n8n, Make, Clay) precisely so your team can adjust the workflows without deep technical skills. I document every automation in a readable way.
That's exactly why I keep human involvement on the decisions that matter. The automations handle volume and mechanics, not the high-stakes decisions, which stay in your team's hands.
It depends on the number of workflows and their complexity. An initial audit lets us scope it precisely before quoting.
Where to start: 30 minutes on what you cannot see.
Describe your stack or your AI need by email. Within 7 days: a numbers-based diagnosis and a ROI-ranked action list. No strings attached.
Book my 30 min call Or even simpler: a 30-minute call, no slides.