Skip to content
StriqTech Logo
Back to blog
Strategy10 min read

Chatbot and automation: one-time payment or monthly subscription? The 24-month math

One-time payment if the workflow only touches systems you control. Subscription if it depends on Meta, marketplaces or AI. Here is the 24-month math, with numbers.

If your automation depends on APIs you do not control —Meta Cloud API, Mercado Libre, Google Calendar, an AI model— the monthly subscription ends up being the sensible option even if the number on the proposal says otherwise, because those platforms change on their own and someone has to fix it when they do. If the workflow only touches your own systems (your database, your spreadsheet, your mail server) and there is someone inside who knows how to read a log, one-time payment is correct and the subscription is money thrown away. With the assumptions of the case below, which you should replace with your own quote: a one-time project of USD 2,800 ends up costing between USD 4,744 and 5,464 over two years once you add the real maintenance; a subscription of USD 225 per month adds up to USD 7,048 in the same period. The difference is not the software. It is who answers the phone the day it breaks.

The 24-month math, with a case worked end to end

Take a modeled case, not a quote: a three-chair dental practice, around 600 WhatsApp conversations per month. Third-party costs are typical market ranges; the provider's prices are assumptions you should replace with the ones in your proposal. The workflow answers frequent questions with RAG over the list of treatments and the accepted health insurance plans, books the appointment in Google Calendar, sends the reminder 24 hours in advance with a utility template, and creates the patient in the CRM.

One-time payment option (custom project):

Monthly subscription option (a provider's pre-designed solution):

The number that matters is not which of the two is cheaper, it is how much separates one from the other: between USD 1,584 and 2,304 over two years, that is, between USD 66 and 96 per month. That is the figure you have to evaluate, not the USD 225 of the monthly fee. The right question is not whether you can pay USD 225 per month; it is whether you would rather pay around USD 80 per month on average so that you are not the one doing the diagnosis at 10 pm on a Friday.

What you are really paying for in a monthly fee

A monthly subscription breaks down like this, and every line has a market price if you buy it separately:

  1. Hosting and database. A 4 GB VPS costs USD 8-15 per month; a managed Postgres like Supabase Pro, USD 25. It is the cheapest part and the one everybody uses to argue that the subscription is expensive.
  2. Monitoring with someone behind it. The tool is free: self-hosted Uptime Kuma costs zero. What costs money is having someone look at the alert on a Sunday at 9 pm and know what to do with it.
  3. Updates when a third party changes. Meta versions the Graph API and retires old versions every couple of years. AI providers announce the retirement of a model with 3 to 12 months of notice. n8n publishes releases every week and some nodes change shape between versions. All three announce it through changelogs and developer newsletters, not to the inbox of whoever hired the bot.
  4. Support with an SLA. The difference between a response in under 4 business hours and whenever I can is not a clause, it is the number of appointments you lose.
  5. Content iteration. You changed the price of the first consultation, added a health insurance plan, closed on Saturdays. If nobody updates the RAG knowledge base, the bot does not fail: it confidently quotes a price that no longer exists. That is worse than being down.

The risk of one-time payment is not that it goes down: it is that it fails silently

Let us follow the same dental practice. The mechanism is the one we have seen repeated most often; the numbers are still those of the case modeled above.

Month 8. Meta recategorizes the reminder template: the text had a promotional phrase at the end and moved from utility to marketing; quality drops and the template ends up paused. The n8n send node has Continue On Fail enabled —almost everybody enables it so that one invalid number does not cut off the morning batch— so the daily execution keeps showing up green. Zero messages sent, zero alerts.

Nobody finds out for three weeks. What you see from the other side is the absenteeism: out of 60 weekly appointments, the no-show rate goes from 8% to 18%. That is 6 appointments lost per week at an average ticket of USD 45: USD 270 per week, USD 810 over the three weeks. Add 4 hours of a developer to find the cause at USD 60, and the incident cost USD 1,050. Next to the USD 66-96 per month that separated the two models, that single event ate up almost eleven months of the difference.

The expensive failure is never the one that brings the system down. It is the one that returns success.

What breaks an automation without anyone touching it

None of these causes is triggered by a change of yours. They all come from outside or from the simple passing of time, and that is why one-time payment does not cover them:

When one-time payment is the right option and the subscription is money thrown away

Five situations where charging you a monthly fee would mean selling you something you do not need:

The rule we use: if the workflow depends on more than two third-party APIs you do not control, one-time payment has an expiry date. It is not that it is wrong; it is that it is better to know that date before signing, not to discover it in month 8.

The middle ground: one-time payment plus maintenance, without hosting

There is a third option that almost nobody quotes and that makes the most sense when the client has their own team: a one-time project, infrastructure in the client account, and reduced maintenance covering monitoring, updates for third-party changes and support, without hosting. Assuming USD 79-129 per month, over 24 months that is USD 1,896-3,096 on top of the setup: between a third and just over half of what the subscription fees in the case add up to, and the server is yours.

The variant for low volume is a block of 10 hours per year, used when something breaks and not lost if nothing happens.

What does not work is the fourth option, the one that shows up on its own when nothing gets decided: one-time payment and then I will call whoever built it. In practice that call takes between 3 and 15 days to turn into work, because the person is already on another project, and it starts with two hours of remembering how this thing was put together.

Ownership breaks differently in each model

Both require the same baseline —workflows exported as JSON in your Drive, credentials in your own accounts, the notice period in writing— but they fail in opposite places and it is worth knowing which one to watch.

With one-time payment the typical hole is the infrastructure: they hand you the workflows, but the VPS and the domain ended up contracted with the provider card and email because nobody defined whose name they were bought under. A year later you need to get into the server and you depend on someone answering. Ask for the transfer of those accounts on delivery day, not when you need it.

With the subscription the infrastructure belongs to the provider by design, so what has to be agreed is the exit: which version of the workflow you take with you the day you cancel —the last one in production or the one that existed when you signed— and with how many days of notice. It is the clause almost nobody reads and the only one that matters when you want to leave. We break it down in full in if you hire an agency, are the workflows yours?.

How we resolve it in the first conversation

Four questions with thresholds, in this order:

  1. How many third-party APIs does the workflow touch? Zero or one, one-time payment. Three or more, subscription.
  2. How much revenue goes through it? If the process touches more than USD 3,000 of monthly revenue, do not leave it without monitoring, whichever model you choose.
  3. Who goes in to look at a log? If the answer is whoever built it, you already have a subscription; only without a price, without a term and without an SLA.
  4. How much does 48 hours of downtime cost you? If that number exceeds six months of the monthly fee, the discussion is over.

If you want the numbers for your case —real volume, which systems it touches, how much the process weighs in your revenue— tell us which process you want to solve: write to us at info@striqtech.com. If that first conversation shows that your workflow does not justify a monthly fee, we tell you right there and the proposal goes as a one-time project, with scope, stages and timelines. To put together the full project budget it helps to first read how much an AI WhatsApp chatbot costs and the 90-day roadmap.

Frequently asked questions

What happens to my automation if I stop paying the monthly subscription?

It depends on what you signed, and that is why you have to ask beforehand. In a well-designed subscription you keep the workflows exported as JSON, the credentials that were already in your own accounts (your WhatsApp Business Account, your AI model API key, your VPS) and the documentation. What you lose is the managed hosting, the monitoring and the support: the workflow still exists, but it now depends on you. If cancelling leaves you with nothing, you did not hire a service.

How much does it cost to maintain an automation on my own after paying for it once?

Under a reference assumption, between USD 960 and 1,680 over 24 months for a WhatsApp workflow with 2 or 3 integrations. The math comes from 4 to 7 interventions in that period, of around 4 hours each (in practice they range from 2 to 6), at USD 60 an hour, within the USD 45-70 band for a senior freelance developer in LATAM; replace the hours and the rate with those of whoever will maintain it for you. It does not include the cost of the days the workflow was broken before anyone noticed, which is usually higher.

How often does a WhatsApp automation that nobody touches break?

In typical ranges, something cuts it off between 2 and 4 times a year when it depends on external platforms. The most frequent concrete causes: Meta recategorizes or pauses a template, the refresh token of Mercado Libre (the dominant marketplace in LATAM) expires after 6 months and is single-use, a Google Cloud project left in Testing mode invalidates the refresh token every 7 days, the VPS disk fills up with the n8n execution history, and the AI provider retires the model you were using.

Is one-time payment a good idea if I have a developer in the company?

Yes, if that person has real access to the server and assigned time, not just the job title. The concrete test is simple: ask them whether they know where to look at a failed n8n execution and how long it takes them to look at it on a Saturday. If the automation touches revenue and the answer is Monday, one-time payment costs you more than the subscription even if the number on the proposal says otherwise.

Can I start with a subscription and switch to one-time payment later?

Yes, and it is the path we recommend most when there are doubts. You start with the subscription model during the first 6 to 12 months, which is when the workflow changes the most and content and rule adjustments show up. Once it is stable, the infrastructure is migrated to your account and you move to reduced maintenance or to an annual block of hours, with scope and response times detailed in the proposal. The important part is agreeing on the handover at the start, not when you already want to leave.

Want to apply this in your company?

Tell us which process you want to sort out and which systems you use today. We review your inquiry and coordinate the next step.

Let's talk on WhatsApp

You may also like