Manual coordination
Copying data between inboxes, calendars and spreadsheets. Every hand-off is a place where something gets lost.
Netta Ops · Sant Cugat del Vallès, Barcelona
We bring order to operations that have grown without a plan.
We connect the tools you already use into a single flow, with an approval queue for anything that should not go out unseen. The person who analyses your operation is the person who writes the code.
We work in Spanish, Catalan and English
The problem
When every tool runs on its own, your team is what has to hold it together.
Every part of the work lives in a different tool, and whatever fits none of them ends up in a spreadsheet. Nobody designed it that way: it grew. And the real cost is not the licence fees, it is the hours that go each day into copying data from one screen to another.
Invisible state
Nobody knows which option is on hold, who owes a reply, or what was promised to the customer last Tuesday.
Risk at the critical edge
A price, a confirmation or an invoice goes out with nobody having looked at it. Nearly always, nothing comes of it. The day something does, it is expensive.
What we build
The layer that joins the tools you already have.
We do not replace your stack. We add the part it is missing: a layer that knows what state each case is in and whose move it is.
Operational routing
Email, messaging and forms arrive in a single work thread, bound to the customer or case they belong to.
State and capacity
Options, holds, shifts or queues with an owner and an expiry. If two things compete for the same slot, the system says so before the customer finds out.
Approvals with a brake
The routine is automated. Commitments, prices and financial documents wait for somebody to press the button.
Documents and collection
Contacts, proformas and invoices linked to the same case, without rewriting the story in another tool.
Operational knowledge
Policies, capacities, extras and instructions in one place your team edits, not us.
Audit and trail
Who approved what, when, and with which data.
Case work
Three of the operations we have rebuilt.
A sample, no names. The sector, the starting point and what is running today are real.
Charter boat operator
Several dates in play, one real capacity
Agencies would ask about three or four dates at once, and all of them had to be held while the agency spoke to its own customer. Availability lived in a calendar, the conversations in two separate channels and the financial documents in a third.
A single inbox for email and messaging, bound to each agency's opportunity. Real reservation state per boat and time slot, with ownership, expiry and conflict detection. And an approval queue for anything that commits availability, price or money.
Operational prototype delivered in the first week. Go-live is proceeding in phases: each external integration is validated before it is switched on, and until it is, the system does not claim to do something it cannot yet do.
Nautical retailer
Over 600 product lines and a warehouse run by hand
There was no online shop. Stock was adjusted by eye, and incoming goods were reconciled against the books several days after arriving, once nobody remembered the details.
Their own public storefront. A goods-in flow where accepting a delivery note posts the stock movement straight into the accounting system. And the carrier's delivery notification closes the order with nobody touching it.
In production and in daily use.
Regulatory consultancy
Technical documentation rebuilt by hand for every submission
Each dossier was assembled from spreadsheets, PDFs and email threads, with somebody checking by hand which data was missing and where each figure came from.
Web tools that assemble the documentation from a single validated dataset and flag the gaps before submission rather than after.
In production, with real submissions closed.
How we work
Four phases, and something usable at the end of each.
No six months of silence followed by one final delivery. Every phase leaves you something you can open and try.
Operational map
We sit down with the people who do the work every day, not only the people who run it, and write down the tools, the exceptions and the places the flow breaks. The boundaries and where we start come out of that.
Operational prototype
A first system usable on real work, with whichever integrations are actually available. Whatever cannot be connected yet is left explicitly out, not simulated.
Hardening
Conflict prevention, controlled recovery and visible failures.
Go-live
Training, written acceptance criteria and monthly support.
Limits
Where the automation stops.
Every system we build assumes people decide the critical path. These five limits are not negotiable, not even when a client asks us to drop them.
Human on the critical path
Availability, prices, booking changes, complaints and financial documents do not go out without somebody approving them.
Tools you already use
We start from your real stack. If your team already knows a tool, the value is in connecting it, not replacing it.
Explicit state
If something fails, it shows. If something is approved, it is recorded with who, when, and with which data.
Honest promises
If an integration is not validated yet, neither the system nor we will say that it is. You read it above, in the first engagement.
The system is yours
The code and the documentation are in your hands from day one. If you ever want to carry on alone or with another team, there is a written handover and nothing to unlock.
Who does the work
There is no sales team behind this page.
The person who analyses your operation, the person who writes the code and the person who answers when something breaks on a Friday afternoon are the same person.
What you describe on the first call is what ends up running in the system, with nobody in between reinterpreting your operation along the way.
Next step
Tell us where your operation stalls.
A paragraph is enough. We read every enquiry and reply directly.
Form information is used only to handle your enquiry.