Software the team stops having to think about.

Operations Automation — Replace Spreadsheets, Paper and Manual Workflows

The spreadsheet works. The WhatsApp group works. The clipboard works. Until the day the company doubles in size and the same tools start losing invoices, dropping stock counts and hiding the balance sheet. That is when automation stops being a nice-to-have and becomes the only way to keep growing. I replace those workflows with software the team stops having to think about.

Why it matters

Every hour spent on manual re-typing is an hour not spent selling, serving, or building. More dangerously, every manual step is a place where the operation can fail silently. Automation is not about removing people from the loop — it is about removing the fragile steps between them.

What you get

  • →ERP layer over the POS you already own (Distrialma has a live SQL Server sync running under a Next.js dashboard).
  • →AFIP electronic invoicing (RG 5616) with Comprobantes A, B, C, Notas de Crédito, per-day cierre de caja.
  • →Google Sheets ↔ database sync — the team keeps editing the spreadsheet they know, the app just reads / writes.
  • →MercadoLibre v1, TiendaNube v1, Facebook, Instagram, WhatsApp — all unified into one inbox with 5-role RBAC.
  • →Bulk stock and price Excel operations that used to take 3 hours now run in 30 seconds.
  • →Live Cuadro de Cuentas Mayores balance sheet computed from the same POS the store already runs.
  • →Automated PDF / receipt generation with per-branch branding.
  • →Cron-scheduled backups to Google Drive via rclone, plus daily sanity-check emails.

Stack

  • Next.js 14/15
  • NestJS
  • Node.js
  • PostgreSQL
  • SQL Server
  • MySQL
  • AFIP SOAP
  • MercadoPago
  • MercadoLibre API
  • TiendaNube API
  • WhatsApp Cloud API
  • rclone
  • Docker

Delivered projects using this stack

Frequently asked questions

What is the shape of an operations-automation project?+

The first week is a walk-through of what is being done manually today, followed by a written map of every touchpoint. The MVP replaces one workflow (the one that hurts most) in weeks 2–4. From there each new automation is a 3–7 day increment. Nothing is built without a business consequence attached.

Do you build on Zapier, Make, n8n, Power Automate?+

No. Those tools are excellent for hobbyist personal automation. In a business context, every new step becomes a per-execution charge and every debug becomes a black-box adventure. I write it in Node / Python / TypeScript directly, hosted on the client's own infrastructure, with proper logging and error handling. It costs less to run and much less to maintain.

Can you integrate with our existing accounting system (Contabilium, Xubio, Bejerman, Tango)?+

Yes. Every one of those exposes either a REST API, a database export, or a CSV drop. Integration is usually a 3–5 day job. AFIP electronic invoicing directly to the taxpayer with their own certificate is also standard.

What happens to the spreadsheet the team already uses?+

It stays. A Google Sheets sync layer keeps the spreadsheet as an editable front-end where that fits (e.g. bulk price updates), while the database is the source of truth. Nobody is forced to abandon a tool that works.

Ready to start?

Send a written brief with the business problem to solve. I come back with a concrete plan against that document, in the client's language.

Contact →

Other services