Home › Services › Make.com automation
// service
Make.com automation, built to run without you
I design and build Make.com scenarios for small businesses — the glue between the form, the CRM, the calendar and the messenger you already pay for. Four of the scenarios on this site are real captures from my Make.com editor, not mock-ups.
What I build in Make.com
- Lead routing — form or ad lead → lookup in the CRM → new vs. returning → deal created or updated → the right person notified in Telegram, Slack or email.
- CRM and marketing sync — Pipedrive, HubSpot, ActiveCampaign, Airtable and Google Sheets kept consistent without a human copying rows.
- Booking flows — Cal.com / Calendly events creating, moving and recovering deals; reminders; no-show follow-ups.
- AI steps inside a scenario — Whisper transcription, GPT or Claude classification and drafting, with a human review step where it matters.
- Content and reporting pipelines — Telegram or Drive in, formatted posts or weekly reports out.
What you get
- A scenario map you approve before the build — every module, every branch.
- Error handlers and retries on every external call; an alert to you when something needs a human.
- Scenarios in your Make.com organisation, connections under your accounts.
- A walkthrough video and documentation your team can follow to change a filter or a field.
- 30 days of support after handoff; small fixed-price tasks after that.
How a project runs
- Discovery call (free, 30 min). You walk me through the process; I ask about volumes, tools and who maintains the result.
- Written scope. Every step mapped, tools named, what "done" looks like, timeline and a fixed price. Nothing starts before you approve it.
- Build with test data. Error handling, retries and alerts are part of the build, not an extra.
- Review. You test against the scope checklist; fixes to anything off-scope are included.
- Handoff. Walkthrough video, step-by-step documentation, credentials in your accounts. Then 30 days of support.
Make.com or something else?
Make.com is my default recommendation when the team will maintain the automation themselves and the volume fits a standard plan. If you need self-hosting, custom code in the middle of a flow, or a lower per-run cost at high volume, read the n8n page. Coming from Zapier? See Zapier → Make.com migration.
Related work
Lead Qualification Router
Qualification form → phone-match router → Pipedrive deal → Google Sheets log → "Qualified" / "Not Qualified" tag in ActiveCampaign, before a rep opens the inbox.
Read the case →
Ebook Opt-in Funnel
ClickFunnels opt-in → Pipedrive lookup by email (phone fallback) → new vs. returning routing → person + deal → Sheets → ActiveCampaign tag.
Read the case →
Booking Cancellation Recovery
Cancelled Cal.com call → Pipedrive lookup → cancellation logged → "Call Discovery Cancel" tag → deal moved back a stage so the lead gets a real follow-up.
Read the case →
AI Content Machine
Telegram message (photo, text or voice) → Whisper transcript → GPT-4o post copy → DALL·E image → Google Drive + Sheets → finished post back in Telegram.
Read the case →Questions
Make.com or n8n — which should we choose?
Who owns the automation afterwards?
What happens when something breaks or our tools change? Are we stuck waiting on you every time?
How long does a project actually take?
Describe your process
Which tools are involved, what is done by hand today, how often. I reply within 24 hours with a fit/no-fit answer and, if it fits, a fixed quote.