You quote $3,500 for the build. Same discovery call, same scope document, same $3,500 — whether the workflows end up in Zapier or in Make. Six months later, the Zapier client has eaten forty unbilled hours of "quick fixes" and three awkward conversations about task overages, while the Make build that was supposed to take thirty hours took sixty because the scenario kept sprouting new branches and edge cases. Same fee, two different losses. The platforms did not cause either one. Pricing them identically did.
This post is for automation consultants and small agencies selling Zapier and Make builds. It explains why the two platforms carry opposite risks, how to match your pricing model to the risk instead of the logo, and what to track in your books so each project prices the next one better.
The platform bill hiding behind your quote
Zapier and Make charge for the same idea — one automated step running once — in ways that diverge fast. Zapier bills per task, and nearly every step in a Zap counts: the trigger, each action, formatter and filter steps. Make bills per operation, with far more generous volume baked into each tier. The sticker prices look close until you multiply by steps and volume.
Measured head-to-head on identical workloads at 2026 list prices, the spread between the two is roughly five to eight times at every volume tier. One benchmark running the same workflow basket 1,000 times a month priced it at $73.50 on Zapier against $9 on Make. A six-step AI workflow processing 1,000 leads a month lands around $150 to $300 on Zapier and under $50 on Make. At 10,000 monthly runs, Make's Core tier covers the volume for about $9 to $11 a month, while the equivalent Zapier task count sits on a plan costing several times more.
None of that is your client's problem on build day. It becomes your problem the month their volume doubles. A Zapier client who outgrows their task tier gets an overage notice with your agency's fingerprints on it — you chose the platform, you designed the step count, and now their automation costs more every month. A Make client with the same growth usually absorbs it inside the plan they already have. If your flat fee assumed "the build is the whole job," the Zapier version of that assumption expires first.
Two platforms, two opposite ways to lose money
The loss on a Zapier build usually arrives after launch. Multi-step Zaps are quick to assemble, so the build itself often comes in under budget — which feels like a win until the maintenance phase starts. Every new step you add to fix an edge case raises the client's monthly task burn. Every volume spike becomes a support ticket. Because the client's platform bill is visible and growing, they negotiate your maintenance fee downward at exactly the moment the workload grows. You quoted the build; you are now donating the operations.
The loss on a Make build usually arrives before launch. Make scenarios are cheaper to run but slower to design well. Routers, iterators, error-handling routes, and data-store lookups reward careful architecture and punish rushing. A scope document written from Zapier-shaped assumptions — one trigger, a few linear steps, done — quietly understates a Make build by half. Agencies that time-track honestly often find the Make version of "the same" project takes 50 to 100 percent longer to build, test, and document. You quoted the build too; you just underpriced a different half of it.
This is the core argument for platform-aware pricing: Zapier concentrates your risk after handover, in volume-driven support and overage friction. Make concentrates your risk before handover, in build complexity. One flat fee cannot cover both shapes. It will be too generous on the platform where you are fast and too thin where you are slow — and you will not notice for months, because each loss hides in unbilled hours rather than in an invoice.
Fixed price vs retainer: match the model to the risk
Fixed-price and retainer engagements are not two flavors of the same thing. A fixed-price engagement is a project with agreed deliverables, a defined timeline, and a locked cost: the client gets budget certainty, and you absorb the cost risk for everything inside the scope document. A retainer is pre-purchased monthly capacity — a set number of hours or a defined service level — applied to new builds, fixes, monitoring, and improvements as needs arise. The client gets continuity; you get predictable revenue.
The decision rule is simple: fixed price fits stable, well-defined builds, and retainers fit everything that keeps changing. A one-time lead-routing Zap with a frozen spec is a fixed-price project. An automation program where the client discovers a new workflow every month is a retainer client wearing a project quote. Most agency losses come from selling the first shape when the engagement is really the second — quoting a build when the client is buying an ongoing capability.
On Zapier work specifically, lean toward pairing every fixed-price build with a care plan from day one. The platform's economics guarantee post-launch conversations about tasks, volume, and plan tiers; a retainer turns those from free support into the service the client already bought. On Make work, protect the build phase instead: quote fixed fees from timed Make estimates, not from Zapier-shaped guesses, and put a tighter change-request boundary around scenario redesigns, which are where Make hours actually go.
The numbers that should set your rates
Real 2026 rate data from working automation operators puts complete client builds — lead capture into CRM with notifications, the bread-and-butter project — at roughly $1,800 to $4,500 flat fee, with monthly retainers between $1,200 and $3,800 for maintenance plus new workflow builds. Hourly rates span $95 to $235, and established agencies quote $3,000 to $15,000 per project with retainers from $500 to $5,000 a month. If your flat fee sits below that build range while your delivery hours match everyone else's, the market is not underpaying you. Your quote is.
The margin math favors retainers once you are past the first build. Industry benchmarks put retainer gross margins around 50 to 70 percent versus 40 to 60 percent for fixed projects, and retainer clients are typically worth three to five times more over their lifetime. But retainers leak: about 52 percent of projects experience scope creep, nearly four in five agencies rarely or only sometimes bill out-of-scope work, and a retainer priced at a healthy margin can lose around five margin points a year to unbilled scope growth. The agencies that keep retainer margins are not the ones that avoid scope creep. They are the ones that measure it and reprice it.
Two benchmarks are worth pinning above your desk. First, your effective rate per project — actual revenue divided by actual hours worked — should clear your cost rate by a wide multiple, with enough headroom that scope creep and write-offs cannot eat it; when it lands near cost, the difference went to unbilled hours. Second, track that number separately for Zapier builds and Make builds. Blended averages are how the cross-subsidy stays invisible: the platform you price correctly hides the one you do not.
What your books should capture
Your accounting setup either reveals these leaks or buries them. Four habits make the difference.
First, separate build revenue from retainer revenue in your chart of accounts. A single "client income" account blends one-time project fees with recurring care plans, so you cannot see which model earns its keep. Two income accounts — projects and retainers — turn every month-end into a readout of your business mix.
Second, never bundle the client's platform subscription into your fee. The client should pay Zapier or Make directly, on their own account, even if you set it up for them. The moment platform costs flow through your books as revenue and expense, your top line inflates, your margins distort, and every plan upgrade becomes a renegotiation of your price. If you must front a subscription, book it as a reimbursable pass-through in its own account, never as revenue.
Third, log hours against projects even when the project is fixed-price. Unbilled hours are the currency both platform risks trade in — post-launch Zapier support, pre-launch Make overruns — and hours you do not record are losses you cannot price into the next quote. Your time tracker is a pricing instrument first and a payroll record second.
Fourth, review profitability per client every quarter, not just overall profit. Agencies that do this typically find 10 to 20 percent of clients are unprofitable once true delivery cost is counted — usually the fixed-price clients still receiving free support months after launch. That review is the single most valuable financial habit most small agencies never build. Each unprofitable client is either a repricing conversation or a resignation letter; the books tell you which ones, and the longer you wait, the more expensive the answer.
Here is what the month looks like in a plain-text ledger for a consultant who keeps these habits — a $3,500 fixed-fee build, a $1,200 monthly care plan, contractor help on the build, and a small Make subscription fronted for the client:
2026-01-01 open Assets:Cash:Operating USD
2026-01-01 open Assets:Receivable USD
2026-01-01 open Income:Projects USD
2026-01-01 open Income:Retainers USD
2026-01-01 open Expenses:Contractors USD
2026-01-01 open Expenses:Software USD
2026-10-01 * "Harbor Dental" "Lead-routing build, fixed fee"
Assets:Receivable 3500.00 USD
Income:Projects -3500.00 USD
2026-10-05 * "Harbor Dental" "Build invoice paid"
Assets:Cash:Operating 3500.00 USD
Assets:Receivable -3500.00 USD
2026-10-05 * "Contract developer" "Scenario build help, 12 hours"
Expenses:Contractors 1080.00 USD
Assets:Cash:Operating -1080.00 USD
2026-11-01 * "Harbor Dental" "November care plan"
Assets:Receivable 1200.00 USD
Income:Retainers -1200.00 USD
2026-11-01 * "Make" "Client scenario operations, October"
Expenses:Software 29.00 USD
Assets:Cash:Operating -29.00 USDWith build and retainer income in separate accounts, one query shows the mix shifting month by month. Pair it with your time log — build hours against the $3,500, support hours against the $1,200 — and the effective rate per engagement is simple arithmetic instead of a feeling.
A pricing playbook for your next two quotes
Put this into practice the next time a prospect asks for "a simple automation":
- Quote Make builds from timed Make estimates. If you have never tracked a Make build honestly, add 50 percent to your Zapier-shaped guess and time the project to calibrate the one after.
- Attach a care plan to every Zapier build at signing, priced from expected monthly task volume plus a support allowance — not as an afterthought when the first overage notice lands.
- Put the client on their own platform account, on their own card, before you build anything. No pass-through subscriptions in your pricing.
- Define one change-request boundary in writing: new apps, new triggers, and scenario redesigns are new quotes, not tweaks. Most unbilled scope enters through vocabulary, not malice.
- Review effective rate per project and profit per client quarterly. Reprice the bottom 20 percent or release them.
The agencies losing money on automation work are rarely underpaid on paper. Their quotes look fine because the losses never appear on an invoice — they appear as unbilled Tuesday afternoons, free overage triage, and builds that took twice the hours nobody logged. Price the platform you are actually selling, sell the retainer the engagement actually is, and let your books grade every quote. The $3,500 fee was never the problem. Charging it identically twice was.
