Make.com cost calculator

A form, a booking or a payment fires a webhook. Make is idle until then, so these cost nothing in a quiet month.

• Lead comes in → logged → alert. No hands.

  3 modules → 3 credits per event · blueprint

  How many form leads a month?
• New client → welcome email → onboarding checklist → alert

  4 modules → 4 credits per event · blueprint

• Returning lead → recognised → "second contact", not "new lead"

  4 modules → 4 credits per event · blueprint

• Form arrives incomplete → an email asking for exactly what is missing

  3 modules → 3 credits per event · blueprint

• Payment received → invoice marked "paid" → a thank-you to the client

  4 modules → 4 credits per event · blueprint

• Tally form → lead log → Telegram alert. The free version of the lead alert

  3 modules → 3 credits per event · blueprint

• Booking form → meetings sheet → confirmation email. Feeds the no-show reminder

  4 modules → 4 credits per event · blueprint

• Feedback score → the same thank-you and review link for everyone; a low score also alerts you

  4 modules → 4 credits per event · blueprint

• Booked on Cal.com → logged in the meetings sheet → you know in seconds

  3 modules → 3 credits per event · blueprint

• A Make scenario fails → a row in the error log and a Telegram alert in seconds

  3 modules → 3 credits per event · blueprint

Make checks Gmail on a schedule. Every check costs one credit, even when there is no new email.

• Labelled email → task in the log → reminder

  2,976 checks a month at 1 credit, plus 2 credits per email · blueprint

• "Remove me" email → marked → confirmation, within a minute

  2,976 checks a month at 1 credit, plus 3 credits per email · blueprint

Make reads a sheet at a fixed time. Each run costs a credit for the search, then more for each row it acts on.

• Invoice past due → an automatic, polite reminder

  Runs every day: 1 credit per run, plus 2 per row · blueprint

  How many overdue invoices reminded a month?
• Weekly report → Telegram, every Sunday at eight

  Runs once a week: 5 credits per run, whatever the volume · blueprint

• Quote unanswered for 3 days → one follow-up, automatic

  Runs every day: 1 credit per run, plus 3 per row · blueprint

• Project closed → 7 days → a Google review request

  Runs every day: 1 credit per run, plus 2 per row · blueprint

• Every morning: what is due today → one message

  Runs every day: 3 credits per run, whatever the volume · blueprint

• Every Thursday: project status → an email to the client, without writing it

  Runs once a week: 1 credit per run, plus 2 per row · blueprint

• A task overdue by 3 days → an alert to the consultant, not the client

  Runs every day: 3 credits per run, whatever the volume · blueprint

• On the 1st: the month's summary → an email to the client, without opening a sheet

  Runs once a month: 5 credits per run, whatever the volume · blueprint

• A meeting tomorrow → a reminder 24 hours ahead, with a "can't make it" link

  Runs every day: 1 credit per run, plus 2 per row · blueprint

• Every Sunday: leads by source → one message with the change from last week

  Runs once a week: 5 credits per run, whatever the volume · blueprint

• A lead untouched for 7 days → an alert to the salesperson, not the client

  Runs every day: 3 credits per run, whatever the volume · blueprint

• Invoice 30 days late → a firmer second notice, and a nudge to call

  Runs every day: 1 credit per run, plus 3 per row · blueprint

• Quote still unanswered on day 10 → one last "should I close this?" email

  Runs every day: 1 credit per run, plus 3 per row · blueprint

• Quote marked "won" → kickoff email → onboarding task → alert

  Runs every day: 1 credit per run, plus 4 per row · blueprint

• Contract ends in 30 days → renewal email to the client → alert to you

  Runs every day: 1 credit per run, plus 3 per row · blueprint