Skip to main content
Guide

How much does AI automation cost for a small business?

By Francisco Salazar2026-06-308 min read

The cost of AI automation for a small business depends on the scope, not on the model: how many systems it touches, how clean the data is, how many human approvals it needs, the volume and the compliance rules. At ResonateOps every build is quoted as one fixed price after a free 15-minute call and agreed in writing before work starts, never by the hour. That holds for the three productized systems, the Lead Acquisition Engine, the AI Intake Agent with its knowledge base and the AI Operating System, and for custom scopes. Each productized system has an optional monthly operation that can be paused. On top of the build you pay vendors directly for running costs: model API usage, hosting, and channel fees such as WhatsApp. This guide explains what moves the number, what is included, how the pricing models compare, and when it is too early to pay for any of it.

How is the price of an AI automation build set?

A scoped AI automation build is paid once, as a fixed price agreed before the work starts. The number comes out of a free 15-minute call and a written system design that states the exact scope, timeline and price. Three productized systems have a defined scope and a delivery date; anything outside them is a custom scope, priced the same way.

Prices are not published here: the number depends on your stack, your data and your volume, so it is set in the written design, not on a web page. For the productized systems payment is 50% to start and 50% on delivery with the system running.

  • Lead Acquisition Engine: dedicated sending infrastructure, around 2,000 verified prospects and reply-focused email sequences. Live in about 30 days, with an optional monthly operation.
  • AI Intake Agent + knowledge base: a knowledge base trained on your business, plus an agent on WhatsApp or web with human handoff and calendar booking. Live in about 30 days, with an optional monthly operation.
  • AI Operating System: one knowledge base and three agents (intake, drafting, follow-up) connected to your CRM, email and calendar. Live in about 45 days, with an optional monthly operation.

What drives the price of an AI automation project?

Six things move the price of an AI automation project: how many systems it integrates, how clean the data is, how many human-approval steps it needs, the volume it must handle, compliance requirements, and where it is hosted. The language model is rarely the expensive part. The engineering around it is: integrations, error handling, testing and the handoff to your team.

Two projects that sound identical in one sentence can differ a lot in effort. Answering inquiries on WhatsApp is one scope when the answers live in a tidy price list, and a very different one when they live in three spreadsheets and the memory of one employee. This is why a quote given without a discovery call is a guess.

  • Systems integrated: each CRM, inbox, calendar or database is an API to connect, test and monitor
  • Data quality: scattered or outdated data has to be cleaned before an agent can answer from it
  • Human-approval steps: each review point before sending, invoicing or deleting needs its own interface and alerts
  • Volume: a few conversations a day is simpler than a load that needs queues, rate limits and cost controls
  • Compliance: personal, health, legal or financial data adds access rules, retention policies and audit logs
  • Hosting: running inside your existing cloud under your security rules takes more setup than a managed platform

What is included in a fixed-price AI automation build?

A fixed-price build from ResonateOps includes the working system, full ownership and a guarantee. You own 100% of the code, workflows, prompts and data. Everything runs in your own accounts: your cloud, your n8n, your API keys. Handoff includes documentation, exported code and workflows in your repository, and Loom walkthrough videos, so the system survives if I disappear.

Every build carries the same reliability work regardless of size: error handling and retries, logging, human approval before anything irreversible such as sending, invoicing or deleting, secrets management, backups, and versioned prompts and workflows.

After handoff there is a 60-day operational guarantee: if something I built breaks in that window, it is fixed at no cost. You work directly with the engineer who builds the system, and I bring in a second engineer for large scopes.

What running costs do you pay after the build?

After the build you pay usage-based running costs directly to the vendors, in your own accounts, with no markup from me because I do not resell tools. The main categories are model API usage, hosting, the workflow engine and channel fees such as WhatsApp. They are separate from the build price and from the optional monthly plan.

I am deliberately not quoting amounts here. Vendor rate cards change often and depend on your volume, so any figure in a blog post would be out of date or wrong for your case. Each vendor publishes its current pricing on its own site, and a reasonable request during scoping is an estimate of these costs at your expected volume.

  • Model API usage (Claude, OpenAI or Gemini): billed by the amount of text processed, so it grows with the number and length of conversations or documents
  • Hosting: a server or platform plan on a provider such as Railway, Vercel, GCP or AWS, plus a database such as Supabase or Postgres when the system keeps a knowledge base
  • Workflow engine: n8n, either as a cloud subscription or self-hosted on your own server, where the cost is the server and its upkeep
  • WhatsApp: Meta bills business messaging by its own rate card, which varies by message type and country, and a business solution provider adds its own fee if you use one
  • Existing tools: your CRM, email and calendar subscriptions stay as they are

Is the monthly plan required?

No. Monthly operation is optional on all three systems and can be activated or paused month to month. The system is yours after delivery, and you can run it in-house with the documentation and training included. The monthly fee buys ongoing operation work, not the right to keep using what you already paid for.

What it covers depends on the system. For the Lead Acquisition Engine it covers replies handled in under 24 hours, copy iteration and reporting. For the AI Intake Agent it keeps the knowledge base current, with monitoring and improvements. For the AI Operating System it covers the knowledge base, agent monitoring, a report and a review call. The monthly amount is quoted with the build, in the same written design.

Hourly, retainer, fixed price or in-house hire: which pricing model fits?

There are four common ways to pay for AI automation, and they differ mainly in who carries the risk of the work running long. Hourly billing puts that risk on you. A fixed price puts it on the builder. A retainer spreads it over time. An in-house hire turns it into a salary. None is wrong, and each fits a different situation.

My pricing follows the third model because most small businesses need one process fixed, not a permanent AI department. A fixed price only works when the scope is honest, which is why the discovery call comes first.

  • Hourly freelancer: flexible and easy to start, good for small fixes and exploration. The total is open-ended, you manage the scope yourself, and continuity depends on one person being available.
  • Agency retainer: a predictable monthly amount with a team behind it, good for continuous iteration across many processes. You pay in slow months too, and you should check who owns the workflows and in whose accounts they run.
  • Fixed-price productized build: one number for a defined outcome and date, the easiest to budget and approve. It requires a clear scope up front, and changes outside that scope typically need a new quote.
  • In-house hire: the deepest knowledge of your business and the right choice when AI work is continuous and core. It carries recruiting time, salary and management, and one hire rarely covers infrastructure, integrations and prompt work equally well.

When is AI automation not worth paying for yet?

AI automation is not worth paying for when the process is not stable yet, the volume is too low to matter, or a tool you already pay for can do the job. Automating a process that changes every month means paying to rebuild it every month. In those cases the better spend is zero, or a few hours of process cleanup.

I do not resell tools, so I have no reason to push a build. If the right answer is a 40-line script or a feature your CRM already has, I say so on the first call.

There is a limitation on my side too: I am one engineer. If you need a large on-site team or staffed support around the clock, a bigger firm is a better fit. I use n8n every day, but I am not an n8n certified partner.

  • The process lives in the head of one person and has never been written down: document it first
  • The task happens a handful of times a month: a checklist is cheaper than a system
  • Your CRM, help desk or calendar tool already has the feature and nobody has switched it on
  • Nobody on your team will own the system after handoff
  • You want outbound but the offer is not proven yet: the Lead Acquisition Engine is built for businesses with a proven offer

How do you get a fixed quote for a custom scope?

A custom quote starts with a free 15-minute call and ends with a written system design that states the exact scope, timeline and price. The price is agreed before any work starts. A scoped custom build runs as a 3-week sprint, or 3 to 5 weeks for larger ones.

To make the call useful, bring three things: the process you want fixed, described step by step, the tools it touches, and a rough idea of volume, such as inquiries per week or quotes per month. With that, the diagnosis is direct: which system fits, whether a custom scope makes more sense, or whether nothing fits yet.

Frequently asked questions

Is there a typical price range for small-business AI automation?

There is no honest single range: the same one-line request can be a small or a large scope depending on integrations, data and volume. At ResonateOps every build, productized or custom, is quoted as one fixed price after a free 15-minute call and written into the system design before work starts. I do not publish ranges for other providers either, because most of them do not publish theirs.

Why fixed price instead of hourly?

A fixed price puts the delivery risk on me, not on you. You know the number before the work starts, and if the build takes longer than I estimated, that is my problem. The trade-off is that the scope has to be defined up front, which is what the discovery call and the written system design are for.

Are model API and hosting costs included in the price?

No. The build price covers the engineering. Model API usage, hosting, n8n and WhatsApp fees are paid by you directly to each vendor, in accounts that you own, with no markup. They are usage-based, so they depend on your volume. Ask for an estimate at your expected volume during scoping, before you approve the design.

Do I have to sign up for a monthly plan?

No. Monthly operation is optional on all three systems and can be paused any month. The system, code, workflows and prompts are yours after delivery, and the handoff includes the documentation and training to run it in-house.

What happens if something breaks after handoff?

Every build carries a 60-day operational guarantee: if something I built breaks in that window, it is fixed at no cost. After those 60 days you can run the system with the documentation and Loom walkthroughs included in the handoff, or activate the optional monthly support.

Let's talk for 15 minutes about your operation.

A free call. I'll tell you straight which processes today's AI can solve and what your infrastructure needs for them to actually run. If it fits, we move forward. If not, I point you the right way, free.