How Much to Charge for a Make.com Automation (Method)

Duncan RogoffDuncan Rogoff November 17, 2026 8 min read
An intricate brass gear train with interlocking cogs mounted on a walnut workbench, a short stack of copper coins and a leather notebook beside it in warm late-afternoon light
Original image, Claude Code Club

How much to charge for a Make.com automation

How much to charge for a Make.com automation comes down to a floor and a ceiling you can calculate. The floor is your estimated hours times your rate. The ceiling is the yearly value of the manual work the automation removes, plus any tools it replaces. Your quote sits between the two. The typical job is a business moving data by hand between apps they already pay for: form responses into a CRM, orders into a spreadsheet, invoices into accounting, new leads into an email list.

I am not giving you a market dollar figure. A two-step scenario that copies a form into a sheet and a set of linked scenarios with routers, error handling and a webhook from a custom app are different jobs. One number would be noise. Your rate and the client's numbers will get you a real one.

Make is visual, and that is the pricing trap. The client sees a few circles joined by lines and assumes it took an afternoon. They are actually paying for the process map behind it and for what happens on the day a run fails. Where Claude Code earns its place is the work around the scenario: cleanup logic for messy data, webhook handlers and small services for apps with no ready-made module, and test data that proves every path works before the client switches it on.

Calculate your floor and ceiling

Run this before you name a price. Every input is yours or the client's, so you can show the working in the proposal.

The Make.com automation calculation

NumberHow to get itWho supplies it
FloorYour estimated hours for each line in the quote, plus a buffer you choose for edge cases and revisions, times your hourly rateYou
Time value per yearHours per week spent copying, re-keying and checking data between the apps, times 52, times what an hour of that person's time costsClient
Spend replacedWhat they pay per year for tools or contractors the automation takes over, if anyClient
Cost of a missOnly if they can point to real examples: a lead nobody followed up, an order keyed in twice, an invoice that never went outClient's own history, your judgment
CeilingTime value plus spend replaced, plus the miss line only if it is documented, minus the yearly cost of the Make plan and extra credits the automation addsCalculated

Watch the last line. If the floor plus a year of the client's Make plan is above the ceiling, the automation will not pay for itself. Say so and offer a smaller version, such as automating only the step that eats the most hours.

Size the credits before you quote

Make bills in credits. Each action a scenario performs consumes credits, and most actions consume 1 credit, while some features that use Make's AI Provider consume more. Reading a record, searching, creating, updating or deleting data, transforming data with the built-in tools, and aggregating or iterating rows all count. Router modules and the error handler modules (Rollback, Break, Resume, Commit, Ignore) do not.

The multiplier is bundles. A trigger runs once per check, however many records it returns. Every module after it runs once per record. A scenario that watches a form, then creates, downloads and emails a document for each response, uses 31 operations in a run that returns 10 responses: 1 for the trigger and 10 for each of the three modules after it. One busy scenario can run from two credits to thousands in a single run.

Credit facts to put in front of the client

What happensWhat it means for your design
Credits run outScenarios stop until credits are added. Incoming webhooks queue up to the plan's queue allowance, and polling triggers pick up from their last successful run when scenarios resume
Credits left at the end of the termThey expire. Extra credits expire after one month on monthly billing, or at the end of the year on annual Pro and Teams plans
Running short mid-monthUpgrade, buy extra credits in bundles of 1,000 or 10,000, or turn on auto-purchase of 10,000 credits on Core, Pro and Teams
Webhook queue667 queued webhooks per 10,000 licensed credits, up to 10,000
Free plan1,000 credits per month, which is a test bed, not a production plan for most client work
DowngradingActive scenarios that use features of the higher plan are stopped

Estimate monthly credits from the client's real volume: records per month times the modules each record passes through, plus one per trigger check. Put that number and the plan it needs in the proposal. Design changes are also price changes. Filtering out records before the expensive modules, or watching for only the records that matter, cuts credits every month for as long as the scenario runs.

The CCC Scenario Quote

Six parts of a Make.com automation quote

PartWhat it pricesQuestion to ask the client
Process mapEvery step, every app, every decision, written up and signed off by the owner before the buildWalk me through one record from the moment it arrives to the moment nobody touches it again
ScenariosThe triggers, modules, routers and filters, built and named so someone else can read themWhich apps does this touch, and who owns the login for each?
Data cleanup and custom stepsFormatting, deduplication, webhooks and any small service for an app with no ready-made moduleShow me the messiest record you got last month
Error handlingWhat each scenario does when an app is down or a record is bad, and who gets toldIf this stops for a day, who notices first, and how?
Credits and planThe monthly credit estimate and the plan it needs, as a running cost next to your priceHow many of these come in on a normal month, and on your busiest?
Handover and tuning windowA walkthrough, notes on each scenario, and adjustments after the first month of real volumeWho will own this once it is live?

Error handling is your anchor line. It is the part the client cannot see and the part that decides whether they trust the automation in three months. A scenario with no error route fails quietly, and the client finds out when a customer complains. Price it as its own line and show them what happens when something breaks.

Agree who owns the Make account

Put ownership in the proposal. The Make organization, every connected app and any API keys stay in the client's name, and the subscription goes on their card. If you build in your own organization and the client leaves, their operations stop with your account. Ask to be invited to their organization and agree the date your access ends.

Then put responsibility in writing. The owner signs off the process map. If they later add an app or a new path, that is a change request, not a bug. Define done: which scenarios, which error routes, and which test records went through every path.

Always quote the tuning window

A Make scenario meets reality in its first month of real volume. An app returns a field in a format nobody expected, a busy week uses more credits than the estimate, or a filter lets through records the owner wanted skipped. If you have not quoted for that, you fix it for free while the client wonders why they paid.

Put a fixed tuning window in the first proposal, next to the build price. Say what it covers: fixing broken paths, adjusting filters, and a check of actual credits used against your estimate after the first full month. Say what it does not cover: new apps, new scenarios and new processes. For ongoing work, offer a retainer. How to price a maintenance retainer covers the structure.

How to present the Make.com automation quote

  • Lead with the outcome in the owner's words. One line on what changes, such as every new lead in the CRM and the welcome email sent without anyone touching it, then the price.
  • Offer three options. A starter that automates the single busiest path, a standard that adds error handling and the full process, and a full version that covers the related processes with a longer tuning window. Make the middle one the clear best value.
  • Show your calculation. Put their own hours and tool spend in the proposal, and show the monthly credit estimate and plan as its own line so the value is net of it.
  • Itemize it. Process map, scenarios, cleanup and custom steps, error handling, credits and plan, then handover and the tuning window. That gives the client a line to trim instead of a reason to say no.
  • Take a deposit and tie the rest to milestones, with the signed process map and a full test run as two of them. How much deposit to charge covers the schedule.

Skip hourly on the invoice, even though hours set your floor. Why I stopped charging hourly for AI builds explains why. If you are not sure what the client actually needs, sell paid discovery first. Client discovery questions before you quote has the questions.

Free Claude Code drops, straight to your inbox

Short, practical drops on skills, MCP, agents, prompts, and more. No spam, unsubscribe anytime.

Frequently asked questions

How much should I charge for a Make.com automation?

Work out a floor from your estimated hours times your rate, and a ceiling from the manual hours it removes per year plus any tools it replaces, minus the yearly Make plan and credit cost. Quote between the two and itemize each part.

Should I charge per scenario or per module?

Neither. Charge a fixed price for the project, itemized by part, then a monthly retainer if the client wants ongoing changes. Per-module pricing rewards bloated scenarios, which also use more credits every month.

How do Make.com credits work?

Each action a module performs uses credits, usually 1, with some AI Provider features using more. A trigger uses one per check, every later module runs once per record, and routers and error handler modules use none.

What happens when a client runs out of Make credits?

Their scenarios stop until credits are added. Incoming webhooks queue up to the plan's queue allowance, and polling triggers pick up from their last successful run when the scenarios resume.

Who pays for the Make subscription?

The client. The Make organization and the subscription stay in their name and on their card, and your access ends on an agreed date. Show the plan and monthly credit estimate in your proposal.

Can Claude Code help build a Make.com automation?

Claude Code can write data cleanup logic, webhook handlers and small services for apps with no ready-made module, plus test data for every path. You still own the process map, the client conversations and the sign-off on how errors are handled.

Last reviewed by Duncan Rogoff on November 17, 2026

Duncan Rogoff

Written by

Duncan Rogoff

Apple · PlayStation · Charles Schwab

Keep reading

MonetizationAgency

How Much to Charge for a Google Sheets Automation (Method)

How much to charge for a Google Sheets automation depends on the manual work it removes, not on how many lines of Apps Script it takes. Price it from a floor and a ceiling you can calculate, itemize the process map, the scripts, triggers and error handling, and check the client's Google account limits before you quote, because a busy trigger can hit its daily runtime cap.

Duncan Rogoff 8 min
Read article
MonetizationAgency

How Much to Charge for an Airtable Build (Method)

How much to charge for an Airtable build depends on what the base replaces and how many people will run their day in it, not on how many tables it has. Price it with a floor from your hours and a ceiling from the client's numbers, itemize the data model, the migration, the interfaces, the automations and the handover, and show the plan the client will need as a running cost. Here is the calculation, plus the plan limits to check before you quote.

Duncan Rogoff 8 min
Read article

Ready to build it yourself?

Join Claude Code Club, the #1 community for learning claude code, for $9/month.

← Back to the blog