Zapier's pricing page lists 100 tasks a month on its free plan, and that one number explains a lot about the AI automation agency Zapier templates problem. A package assembled from copied templates can run on a plan that costs the agency very little, while the invoice you receive is priced like custom engineering. Here are the checks you can run yourself before you sign anything.
Key Takeaways
- A resold template workflow connects generic apps, while custom automation encodes your own rules for service areas, emergencies, approvals and failures.
- Zapier is a legitimate tool, so the real test of an agency is whether it designed a workflow around your business or only configured a copy.
- Before signing, ask for a diagram of your process, a failure plan, and proof that the accounts will be registered in your company's name.
- Zapier's help center says a task is counted for each successful action step, so an agency should be able to estimate your monthly task volume.
- A fair proposal separates agency fees from tool subscriptions and lists every workflow in writing.
How an AI automation agency resells Zapier templates
Zapier publishes a library of ready-made workflows, called templates, that anyone can switch on in a few clicks. Nothing is wrong with that. The trouble starts when an agency picks a template, connects your accounts, adds its own logo to the report, and sells the result as a bespoke AI system.
You can often spot it in the proposal. The deliverables list names apps, such as a form feeding a spreadsheet or a Gmail message posting to Slack, but never names a single rule from your business. The scope reads the same for a roofer, a dentist and a boutique. The kickoff call covers which accounts to connect, not how a customer request moves through your company.
The pricing logic gives it away too. Zapier's help center says a task is counted for each successful action step, while triggers, filters and paths do not use tasks. A three-step template is cheap to run, so the money in a resale sits in the markup, not in the engineering. That is fine when the price is honest. It is not fine when the proposal says “custom AI development.”
A quick test: ask which part of the build is not on a public template list. A real builder can answer in one sentence. A reseller will talk about integrations instead.
Is Zapier the problem, or the way agencies sell it?
No. Zapier is a legitimate tool, and for many small jobs a template is the right answer. If new form submissions only need to land in a spreadsheet, you do not need a custom build, and an honest agency will tell you so.
The problem is the packaging. A template solves a generic case: when X happens, do Y. A trades company rarely has a generic case. Your jobs have service areas, after-hours rules, a dispatcher who overrides the schedule, and customers who text instead of filling out a form. A template knows none of that.
Honest agencies pick Zapier, Make, n8n or plain code depending on the job, and we compared two of those platforms in our n8n vs Make guide. The platform is a detail. You are paying for the design: which steps exist, what happens when one fails, and who gets told.
Six tells you can check before you sign
Each of these takes one email or one call to check. None needs technical knowledge.
They cannot draw your process
Ask for a simple map of how a customer request moves through your company today, with boxes and arrows, before any building starts. If the first deliverable is a login to a tool, nobody has designed anything yet.
Every answer starts with a tool name
Ask what the system should accomplish and listen to the first words. A designer starts with your jobs, your customers and your bottlenecks. A reseller starts with “we'll use Zapier to connect...”
No plan for failure
Ask what happens when a phone number is missing or your CRM is down for an hour. Zapier's own help center describes error handler paths, so planning for failure is a normal part of the work. A template answer is “it should just retry,” or silence.
The demo is identical for every industry
If the sales demo is the same for plumbing, cleaning and roofing, the demo is the product. Ask to see a workflow that includes a rule specific to a trade, such as an emergency call or a service area check.
The accounts belong to the agency
When the automation runs inside the agency's own account, you rent it. Stop paying and the workflow stops, and you cannot see how it works.
Reports count activity, not outcomes
A screenshot of run history proves that something ran. It does not prove that more quotes got an answer. Ask which business result the workflow is meant to change, and how you will see it.
What genuine custom automation looks like in a trades company
Take a plumbing company as a hypothetical example, not a client. A request arrives by phone, web form or text message. A custom workflow checks the address against the service area, separates an emergency from a quote request, creates the customer record, assigns an owner, and sends a confirmation message. If nobody replies to the quote, a follow-up sequence starts and stops by itself when the customer answers.
Notice how many of those steps are decisions, not connections. Our CRM and customer follow-up service is built around that idea, and our guide to quote follow-up for contractors shows why the silent days after an estimate matter so much.
AI belongs in the messy parts: sorting free-text messages, summarizing a call, drafting a reply for a person to approve. It does not belong where a plain rule works. We list the automations most service businesses need in our overview of AI automations for service companies.
Intake usually starts on your website, so the form, the click-to-call button and the tracking have to be built to feed the workflow. That is where our web design and development service meets the automation work.
Questions to ask an AI automation agency about Zapier templates
Bring these to the first call and write down the answers:
- Which parts of this proposal are templates, and which are built for us?
- Can you show a similar project, with the client's permission?
- Whose name is on the Zapier or Make account, and who pays for it?
- What breaks first, and how will we find out?
- Who maintains it when an app changes its settings?
A good agency answers these without discomfort, and often volunteers that some pieces are templates. That honesty is a better sign than a pitch that claims everything is proprietary. The same logic applies when you compare an agency with a freelancer or a DIY build, which we covered in our website agency vs freelancer vs DIY comparison.
What you should own when an automation project ends
You should own the accounts, the documentation and the data. Accounts should be registered to your business email and billed to your company, with the agency added as a collaborator. Documentation should explain each workflow in plain English, including what triggers it and who is notified when it fails.
Ask for an export or a written copy of each workflow's settings at handover. If you ever switch providers, that file is the difference between a quick transition and rebuilding from scratch. When you review any AI automation workflows service, ours included, check for this first.
How to price automation work without overpaying
Ask for two numbers: the agency's fee for building and maintaining the workflows, and the monthly cost of the tools. Zapier's prices are public, and its pricing page shows plans that scale with the number of tasks, so you can check the tool half of the bill yourself.
A fair proposal lists every workflow, says what each one should change in your business, and states what is included after launch. A vague “automation package” with a single price cannot be compared with anything. If a quote has no scope, you are buying an assumption.
Apps change their settings, so ask who watches the workflows after launch and how a failure reaches you. Maintenance is a real cost, and an agency that quotes none is either absorbing it or ignoring it.
Have an automation proposal to check?
Send us the scope you were quoted, and we will tell you which parts look custom and which look like templates.
Automation agency questions owners ask
Ask for a diagram of your own process before any building starts, because an agency that only resells templates will describe apps and connections instead of your rules, exceptions and failure handling. Then ask which steps are not in a public template, and what happens when one of them fails. Vague answers are the clearest sign.
No, using Zapier is not wrong, because the tool is widely used and fine for many small jobs, and the real question is whether the agency designed the workflow around your business or copied a generic one. Zapier, Make and n8n are all reasonable choices, and the platform matters less than the design and the ownership of the accounts.
Zapier publishes its prices, so you can check them yourself: its pricing page lists a free plan with 100 tasks per month and paid plans that scale with the number of tasks you use. Zapier's help center says a task is counted for each successful action step, so workflows with many steps use more tasks per run. Ask any agency to estimate your monthly task volume.
The accounts should be registered to your business email and billed to your company, with the agency added as a collaborator, so you can remove access or move the work if the relationship ends. Ask for written documentation at handover as well, so someone else can read and maintain what was built.
A template is a prebuilt workflow that handles a generic trigger and action, while a custom workflow is designed around your own rules, such as service areas, emergency handling, approvals and what happens when a step fails. Ask an agency to show a rule in the workflow that exists only because of your trade.
Not always, because many useful automations are plain rules like confirming a request, creating a record and reminding a person, and AI earns its place only for messy inputs such as free-text messages or call summaries. Ask the agency to explain where AI is used in your workflow and where a plain rule does the job.
Ask for a written scope that lists each workflow, the apps it touches, what happens when a step fails, who owns the accounts, and how the monthly cost splits between agency fees and tool subscriptions. A scope that cannot be written down usually cannot be delivered either.
