Work / NEXO at La Nuestra
First small workflows. Then bigger ones. Then NEXO.
I have worked for La Nuestra, a food producer in Lima, Peru, since March 2024. From home, as their AI specialist. I started with small workflows in n8n. Then came bigger ones, then apps, and in the end one system that holds all of it. This page is that story, with the films I posted on LinkedIn.
Small: one trigger, one check, one message.
The first things I automated were small. An alert when a product hits zero stock. A notification when a new worker is added. A daily list of products that are about to expire. A reminder before a deadline.
None of them is impressive. Each one takes away something that a person had to remember. That is how you earn the room to build the bigger things.
45 workflows built for La Nuestra. Counted in n8n on 13 Nov 2026, without test copies and backups.
Others of this size
Bigger: agents, channels and a knowledge base.
Then the workflows grew. A recruitment screening bot on Messenger reached 137 nodes. It worked, until I had to change something in it. I rebuilt it as 16 core nodes plus subflows.
The biggest is the AI customer service. One gateway, built for WhatsApp, Messenger and Instagram, puts every message in the same format. A router agent decides whether it is a consumer or a business. Each has its own agent, and the business agent also collects a lead. The answers come from a knowledge base in Postgres with pgvector, synced from a shared drive.
137 nodes, rebuilt as 16 core nodes plus subflows.
A rebuilt screen with sample data. The real ones hold a client's numbers.
One system: NEXO.
After the workflows came the apps. A delivery system in April 2026, and apps for attendance, stock, meeting minutes and applicant screening, among others. Each one solved a real problem. Each one also had its own login.
From June 2026 I merged nine of those apps into one: NEXO. One login, one permission system, one database. 320 pages, 594 API routes and 226 database migrations, in Spanish, Dutch and English. 75 people clock in on it.
n8n did not go away. It still runs around NEXO, for the chat channels and the notifications.
9 apps became 9 modules behind one login.
Eight films of the real thing.
I posted these on LinkedIn, one module at a time. The first is the main menu. The other seven each open one module for about a minute. A minute is not enough for a whole module, so each film shows a small part.
The screens are the real NEXO. Every name and amount in the films is made up. The films have music: the sound starts when you press play.
The front door
97 sThe main menu. Nine modules behind one login, and everyone sees only the parts their job needs. One click switches the whole screen between Spanish, Dutch and English.
Configuration
55 sEvery role is built from 355 permissions: the 202 screens it may open and the 153 actions it may do there. One click grants a permission, one click takes it away. La Nuestra sets this up without me.
Logistics
62 sEvery morning the routes go out per zone, each with a truck, a driver and a co-driver. The driver confirms each stop on a phone: what was delivered, what was paid and how. At the end of the route the counted cash sits next to what every stop says was paid.
Production
59 sThe team records who worked on which machine, for how long, and how much came out. NEXO checks that against the target of the machine. Planning runs the other way: type the units you need and it works out the mixes, the machines and the raw material.
Sales
73 sA sale is a customer, a product and a quantity, with the stock and the total on the same screen. Price lists have volume scales. Leads come in from Facebook, Instagram, WhatsApp, the web and the B2B chat, each with an origin, an owner and a status.
HR
73 sOne staff list for the whole company. People clock in on tablets linked to NEXO, and one click shows only the late arrivals and the absences. Vacation days are counted for you. Payroll is worked out per half month.
Finance
77 sEvery cash box and bank account shows its balance. Payments collected in the street stay red until finance confirms them. One payment can be split over several methods. When the trucks come back, each route is settled on one screen.
Inventory
64 sStock per warehouse, with every product under its minimum in red. The stock ledger follows one product through purchases, sales, transfers and adjustments. Ask for 40 boxes from a warehouse that holds 25, and NEXO says no.
Nine modules. A company takes the ones it needs.
NEXO is not one block. It is nine modules behind one login. At La Nuestra no old system was switched off before its NEXO module could fully take over. Until then the old one kept running, and the work went on.
That is also how it fits another company. If you only need stock and sales, you start with those two. Your own admin decides which role sees which screen. What your trade needs and NEXO does not have yet, I build as a module next to the rest.
La Nuestra's NEXO is the big example. The public demo is the small one: a made-up company where sales, inventory, purchasing, finance and HR work. The real one has nine modules and 320 pages.
- Sales
- Sales, price lists with volume scales, leads per channel.
- HR
- Staff, attendance clock, vacation, payroll per half month.
- Logistics
- Routes per zone, delivery on the driver's phone, cash settlement.
- Production
- Output per machine against target, formulations, planning.
- Finance
- Cash boxes and banks, confirmed payments, route settlement, reports.
- Inventory
- Stock per warehouse, stock ledger, transfers, adjustments.
- Marketing
- Not in the films.
- Admin
- Not in the films.
- Configuration
- Roles and permissions, delivery zones, vehicles, chat channels.
| n8n workflows built for La Nuestra | 45 | measured, 13 Nov 2026, without test copies and backups |
|---|---|---|
| Separate apps merged into NEXO | 9 | measured, project plan |
| Modules | 9 | measured, Nov 2026 |
| Pages | 320 | measured, Nov 2026 |
| API routes | 594 | measured, Nov 2026 |
| Database migrations | 226 | measured, Nov 2026 |
| Permissions a role is built from | 355 | measured, 202 screens and 153 actions |
| Languages | 3 | measured, Spanish, Dutch, English |
| Staff on the attendance clock | 75 | measured, Sept 2026 |
Tell me what goes wrong on a normal Tuesday.
Thirty minutes, video or phone. You describe one process that costs you time. I ask questions and tell you honestly whether I would automate it, fix it first, or leave it alone. No slides.
Lima time, UTC-5. I reply within one working day, in English, Dutch or Spanish.
Open to remote roles and to projects.