What AI Automation Costs a Small Business: The Three Bills, Not One

AI automation costs a small business three separate things: a platform subscription that meters by volume, per-message and registration fees the platform never quotes, and the labor to repair and build the process being automated. The subscription is the smallest of the three, and it is the only one most guides price.

So this guide prices all three - the platform tiers from the vendors' own published pages as of September 2026, the messaging and consent costs from Twilio's fee documentation and the FCC's rules, and the part no page can quote. The one Mirastart number in it is the published floor: ongoing engagements start at $3,000 a month.

What the platform subscription actually costs

Automation platforms are the cheapest bill and the easiest to underestimate, because all of them meter. As of September 2026, Zapier's free plan includes 100 tasks a month and its Professional plan starts at $19.99 a month for 750 tasks; Make's Core plan starts at $9 a month for 10,000 credits. Both discount annual prepay.

The trap is the meter, not the sticker. Zapier's own documentation says that at the task limit you are switched to pay-as-you-go unless you turn it off or move up a tier - so the bill tracks your busy season, which is exactly when nobody is watching it. And since June 15, 2026, Zapier prices AI steps by model tier: Standard one task per run, Advanced three, Premium five, with new steps defaulting to Advanced. A workflow priced at one task a run can quietly be costing three.

The fees the pricing page does not show

Any system that texts customers carries a second bill the automation platform never quotes: the carrier layer. Twilio's published US rate starts at $0.0083 per outbound long-code message as of September 2026, and its help documentation states that carrier fees, where they apply, are charged per message segment and passed through to the customer.

Before a single message sends, US business texting also has to be registered under A2P 10DLC. Twilio's published fee schedule, as of September 2026, lists a one-time $4.50 brand registration with The Campaign Registry, a $15 campaign vetting fee charged at vetting, and monthly campaign fees of $2 to $10 by use case, with sole-proprietor brands at $2. Individually trivial; the point is that they recur, they arrive on a different invoice, and no automation quote includes them.

Consent is a line item, not a checkbox

Consent handling is engineering work with a legal deadline attached, and it is the cost most vendors leave out entirely. The FCC's rules at 47 CFR § 64.1200 require prior express consent before an autodialed or artificial-voice call to a wireless number, and prior express written consent when the message is telemarketing.

The FCC's own consumer guide, last reviewed February 2026, is blunter about the voice side: "AI-generated voice calls are illegal unless the consumer has agreed to receive them or the caller is exempt." That sentence is a budget item. Somebody has to capture consent, store it, and be able to produce it later.

The exit costs money too. The rule treats a reply of "stop", "quit", "end", "revoke", "opt out", "cancel" or "unsubscribe" as a reasonable revocation on its face, and requires any revocation made by a reasonable method to be honored within ten business days. Opt-out plumbing therefore has to exist across every channel the system touches, and be tested rather than assumed. This is a general explanation of published rules, not legal advice.

Build versus subscribe: where the line sits

Subscribing wins while the workflows are few, the volume is low and the logic is standard. Building wins when the metered bill grows with your busy season rather than your margin, when the workflow encodes something specific to how you actually operate, or when the data has to live somewhere you control.

• Count the meter, not the plan: real monthly volume times the tasks or credits each run consumes, including the AI-step multiplier.
• Ask what happens at 3x volume. A subscription that is cheap today and painful at triple it is a build decision deferred, not avoided.
• Ask who owns the accounts. The messaging number, the registered brand, the automation account and the data should be in your name.
• Ask what happens when it fails at 2am. A built system can be inspected; a stack of subscriptions fails inside whichever vendor you cannot see into.
• Ask what was deliberately left manual. Anyone who cannot name something they chose not to automate has thought about their tooling, not your process.

The cost nobody prices: fixing the process first

The largest line in most automation projects is not software at all - it is deciding what the process actually is. Automating a process nobody has written down means paying to encode the version in one person's head, then paying again when it turns out three people were doing it differently.

That work is where the money goes: what counts as a qualified lead, who owns a reply after hours, what the system says when it does not know, when a human takes over, what happens to the customer who says stop. A vendor who quotes an automation without asking those questions is quoting the demo, and the difference arrives later as change orders rather than as a lower price.

How to price your own first year

Price it as three columns rather than one number, because only two of the three can be quoted from a page. Column one is the metered platform bill at your real volume. Column two is the messaging layer: registration fees, monthly campaign fees, per-message rates and carrier pass-throughs. Column three is labor.

1. 1Take the monthly volume of whatever you want automated - inquiries, missed calls, quotes, reminders - from the last 90 days, not from memory.
2. 2Multiply it by the platform's unit (tasks or credits) and by the AI-step multiplier where a workflow uses one, then check that against the tier you were quoted.
3. 3Add the messaging layer at that volume: registration and monthly campaign fees, per-message rates, carrier fees passed through.
4. 4Add the labor to write the process down and build it, treating the first three months as partly discovery.
5. 5Compare the total against what the leak costs today - the inquiries unanswered overnight, the quotes nobody chases. If it cannot beat that number, the honest answer is not yet.

What this looks like when it runs

A built system replaces the three-column estimate with one visible operation: an inquiry answered immediately, a missed call texted back, a quote followed up on a schedule, a review requested at a fixed milestone, and one dashboard showing what each of those produced. The meter is still there; the difference is that somebody is watching it and the accounts are in your name.

Mirastart builds and runs those systems for Charlotte businesses - the online booking and repair-status system built for Quick Auto NC is the shape of it - and the third column is why our ongoing floor sits at $3,000 a month. The process work, the consent plumbing and the reporting cannot all be done properly below it.