Hiring someone to automate or outsourcing: the real 12-month math

For an SMB of 5 to 50 people, outsourcing automation costs between USD 7,000 and USD 9,000 in the first year. Hiring someone in-house starts at USD 32,000-35,000 in Argentina and at EUR 34,000-45,000 of total employer cost in Spain. Hiring only starts to make financial sense when your operation generates more than 55 to 60 hours of automation work per month, sustained for more than a year, and an SMB of that size usually generates between 10 and 25. Below is the full calculation: the real loaded cost, the four employee expenses that never show up on the payroll sheet, what a partner overcharges you for, and the five cases where hiring is clearly the right decision. All figures are market ranges, not audited results from a specific company.

The salary is roughly 60% of what the employee costs

A semi-senior operations and automation profile in Argentina, on the payroll, with a gross salary of USD 1,700 a month at the official exchange rate (the market band runs from USD 1,200 for a junior to USD 2,400 for someone who has already built ERP integrations):

• Thirteen salaries, counting the statutory extra month: USD 22,100.
• Employer contributions, between 24% and 27% depending on the regime: USD 5,525.
• Workers' compensation insurance, mandatory life insurance and private health coverage if you offer it: USD 900.
• Severance provision, one salary per year worked: USD 1,700.
• Payroll subtotal: USD 30,225 a year.

On top of that come the one-off expenses almost nobody budgets for: recruiting and selection between USD 800 (posting the ad yourself plus 25 to 40 of your own hours reading CVs and interviewing) and USD 3,400 if you use a recruiter charging 12% to 18% of the annual salary; laptop, monitor and desktop licenses for around USD 1,300; and infrastructure the employee needs just as much as a provider does, between a VPS for n8n, monitoring, a Make account for specific connectors and model API consumption, around USD 1,400 a year.

First-year total: close to USD 34,700. From the second year on, around USD 32,000 with the salary adjustment included. If you pay in pesos, that dollar figure moves with every collective bargaining round and with the exchange rate: recalculate it every six months instead of treating it as fixed.

Outside Argentina the bands change but the logic does not. In Spain, a junior or mid operations and automation profile is priced between EUR 26,000 and EUR 34,000 gross per year, and the employer's social security share adds roughly 31%: a total employer cost of EUR 34,000 to 45,000, not counting severance (20 days per year for objective dismissal, 33 for unfair dismissal). In Italy, a RAL of EUR 28,000 to 35,000 turns into a company cost of EUR 40,000 to 54,000 with a factor of 1.45 to 1.55, plus the TFR that accrues at nearly 7.4% of compensation. In Mexico the loading factor over gross salary is around 1.25-1.35 and in Colombia 1.45-1.55. Verify your case with your accountant or payroll advisor before budgeting: these bands are for deciding, not for signing.

The four employee costs that never appear on the payroll

1. The ramp-up. Between 60 and 90 days until they produce without supervision. If they have never automated in your vertical, they will rebuild the first two or three workflows once. That does not show up on the pay slip, but it is three months of output at 40%.
2. The weeks with no coverage. Fourteen days of vacation in Argentina up to five years of seniority, some 19 public holidays and the usual leave add up to roughly seven weeks a year with nobody there. The concrete question: if the WhatsApp bot stops replying on January 3rd, who brings it back up?
3. Bus factor one. A single person building, with nobody reviewing their work, produces workflows written the way they understand them. Nobody else in the company can touch them, and you have no way to know whether they are sound until they break.
4. The exit. Severance plus notice period, 45 to 60 days of vacancy while you look for a replacement, and one more month until the new person understands what was there. If nothing was documented, in practice the replacement rewrites between 30% and 50% instead of inheriting it.

What a partner overcharges you for, and what they will not give you

Outsourcing has four concrete costs:

• Latency. A four-business-hour SLA is not someone sitting in your office. A two-line change to a message may only get picked up the next day. If your commercial rules change every fortnight because you decide so, that friction is paid on every iteration.
• Scope. Whatever is not in the contract gets quoted. A "just add this" that costs nothing with an employee becomes a work order with a provider, even if it is two hours.
• Business knowledge. The partner knows n8n and Meta's Cloud API. You know why the customer in Rosario pays at 45 days and the one in Córdoba does not. The first 30 days are discovery and you will have to explain your operation patiently.
• Dependency. If the Business Manager, the VPS and the workflows stay on the provider's side, switching partners stops costing a month of coordination and starts costing the full setup all over again: in the scenario below, USD 1,500 plus the time to explain eleven processes again. It is the right fear and it is solved by contract, not by trust: the specific clauses are at the end.

A 12-month scenario: a wholesale distributor with 22 people

A scenario built from list prices and market ranges, not a specific client's file. It sells through WhatsApp, Tiendanube and Mercado Libre (respectively the leading e-commerce platform and the dominant marketplace in LATAM), invoices with Xubio and tracks its pipeline in Pipedrive. The year's backlog, eleven automations plus a chatbot:

stock synchronization between Tiendanube and Mercado Libre every ten minutes; order creation in the system and notification to the warehouse; a WhatsApp chatbot with RAG over the price list and stock, with handoff to a salesperson; payment reminders at 7, 15 and 30 days past the invoice due date; routing of after-sales complaints to Chatwoot with an SLA per type; a daily sales report by channel in Looker Studio; creation of leads from the web form in Pipedrive; stock-out alerts per SKU; automatic sending of the PDF delivery note on dispatch; reconciliation of Mercado Pago (Mercado Libre's payment arm) settlements against issued invoices; a satisfaction survey 48 hours after delivery.

Outsourced path: setup of the two pre-designed solutions USD 1,500, a USD 299 monthly subscription with hosting, monitoring, support and minor changes USD 3,588, one custom project during the year for the stock integration USD 1,800, and Meta conversations plus AI tokens at around USD 45 a month, USD 540. Total: USD 7,428.

In-house path: the USD 34,700 calculated above.

First-year difference: USD 27,272 in favor of outsourcing. And that comparison is generous to the employee, because we have not yet counted that during their first 90 days half of those automations would not have existed.

That entire backlog represents between 140 and 170 hours of real work, around 13 hours a month. A full-time employee has about 1,150 effective hours in their first year, once you subtract vacation, holidays, meetings and ramp-up. That leaves 87% of the calendar unused.

The valid objection is that the employee will fill that time with other things: internal support, user provisioning, ad hoc reports, supplier follow-up. That is true, and there lies the real question: are those other tasks worth USD 27,000 a year? If the answer is yes, you are not hiring an automation specialist, you are hiring an IT manager, and the honest comparison is no longer against an automation partner.

The number that decides it: how many automation hours per month your company generates

A partner billed on a subscription costs between USD 45 and USD 55 per effective hour of work delivered. A loaded employee costs between USD 24 and USD 30 per productive hour. The employee is cheaper per hour, always. The trap is that you pay for them whether or not you fill their calendar.

That gives you the break-even point: USD 33,000 of annual fixed cost divided by USD 48 an hour gives around 690 hours a year, that is 55 to 60 hours a month. Above that, hiring is cheaper in cash. Below it, you are buying idle time.

To estimate your number without guessing: list the processes by name that you want to touch in the next 12 months, multiply each one by 10 to 15 hours of build time, and add 20% for maintenance. The distributor in the example came out at 155 hours. If your calculation does not exceed 600 hours a year, the decision is already made. If you want to organize that backlog before calculating it, the 90-day roadmap helps put processes in order of impact.

When hiring in-house does make sense

1. When the backlog exceeds 55 hours a month on a sustained basis. This usually happens above 50 employees, with several branches, or when there is a proprietary ERP that demands continuous integration.
2. When the data cannot leave the company. Medical records, files under professional privilege, card data under PCI. It can be outsourced with a contract and restricted access, but if your compliance framework requires your own staff, no economic argument holds.
3. When you already have the person inside. That administration lead who builds macros and understands why invoicing works the way it does. Formalizing the role costs a salary adjustment, not a search, and the expensive part of the learning curve (knowing the business) is already paid for.
4. When automation is part of what you sell, not of your back office. If your end customer receives the workflow, that is product and it belongs in-house.
5. When you have someone to supervise it. A junior alone, with nobody reviewing their work, is bus factor one with a salary. If there is no technical or operations lead who can read what they built, hiring adds risk instead of removing it.

Who outsourcing is the worst option for

• If what you need is someone on site. Setting up the fiscal printer, provisioning users, training the counter staff, helping whoever forgot their password. That is not an automation partner, that is an IT employee. We do not do it and no remote provider will do it well.
• If your rules change every two weeks and you cannot stand tickets. The coordination cost will hurt more than the price difference.
• If three automations closed everything. From the fourth month on you would be paying a monthly fee to monitor something that barely changes. In that case a one-time project plus a bucket of 10 to 15 hours a year for adjustments is better, and we say so before signing, not after.
• If your total annual budget for this is under USD 1,500. Neither option works. Organize the processes by hand first.

The model that works best between 5 and 50 people

Neither an employee nor a detached provider: a partner that builds and operates, plus an internal owner of the topic. Someone already working with you (the operations lead, the head of administration) with 3 to 5 hours a week formally assigned to prioritize the backlog, validate the flows before they go to production and flag when a commercial rule has changed. Zero new headcount, and dependency stops being a serious problem: there is always someone inside who knows what is automated, why, and on which account it runs.

The clauses that make the decision reversible

This applies equally whether you outsource or hire, and it is what turns dependency into a one-month problem instead of a reimplementation:

• Ownership. Meta Business Manager, the WhatsApp number, the Google Cloud project, the VPS, the Postgres database and the API keys under your company's name. You invite the provider, never the other way around.
• Exportables. The n8n workflows exported as JSON to a repository of yours every time they change, and the assistant's prompts in a document you can read.
• One sheet per automation. What triggers it, which systems it touches, what happens if it fails and who it notifies. Half a page is enough.
• Exit clause. Thirty days of handover support and delivery of credentials at the end of the contract, written down before you start.

If you are comparing quotes, the breakdown of the cost layers (Meta, AI, software, support) is detailed in how much an AI WhatsApp chatbot costs.

The decision in one line

Count the real automation hours your company will generate over the next twelve months. If it is under 600, outsource; hiring is buying idle time at the price of a loaded salary. If it is over 700 and sustained, hire, but hire with supervision and with mandatory documentation from the very first workflow.

If you do not know which number you fall under, that is literally the calculation we run in the free 15-minute audit: we look at your processes, estimate the hours and tell you what is worth automating and what is not. Write to us at info@striqtech.com.