A team that gets into the process, not just the system
Huapix Solutions builds administrative automation and integrations for companies. We don't sell a platform: we analyze how the process works, identify the rules that govern it and build the solution on top of the systems the company already has.
How it started
Huapix Solutions was founded in 2022 by Cristian Miguens, in Argentina. It grew out of something seen again and again on systems projects: the bottleneck is almost never in the ERP, but in everything happening around it.
Documents that arrive by email, spreadsheets someone consolidates by hand, portals that offer no integration, and business rules that live in the experience of the administrative team.
That space was going unsolved: too specific for a standard product and too operational for an ERP implementation project. It's the one we decided to take on. Since then we've worked with processes at companies in seven countries across the region.
What sets us apart
Most automation tools handle the visible part of the work: open a screen, fill in fields, click OK. A real administrative process is something else: a document that arrives in a different format than last month, a material called one thing on the order and another in master data, a price that doesn't match and a decision about what to do next.
That's why our starting point isn't the tool but the process. We automate the whole process: documents, validations, business rules, system integration and exception handling. It's more work up front, and it's the reason our solutions keep working afterward.
How we work with clients
We're a small, senior team, and our working model is built around that. The person who maps the process is the person who develops it: there's no sales layer translating between the business and the code, and no account team between the client and the people who know the solution.
One point of contact, start to finish
The same person who sits down to map the process builds it and answers for it afterward. There are no internal handoffs, and no re-explaining the process at each new project stage.
Focused scope, project by project
We take on projects we can give the depth they require. If a scope goes beyond what we can sustain with quality, we say so in the first meeting rather than finding out halfway through.
Nothing depends on one person
Every solution is delivered documented: business rules, design decisions and how to run it. The client can audit it, maintain it or transfer it to another provider without depending on us.
Areas of expertise
These are the capabilities the team combines on every project. There's no one area per person: whoever maps the process also takes part in developing and running it.
Automation and development
Python, RPA, APIs and databases, choosing the technique based on the process.
SAP integrations
ECC, S/4HANA and Business One through BAPI, Service Layer, DI API or GUI Scripting.
Document AI and data
Reading variable documents, OCR and consolidating information for reporting.
Process analysis
Mapping the real process, its business rules and its exceptions.
Operations and support
Supporting what's already in production and running it under BPO.
How we support clients
Every project has an assigned lead who knows the process end to end. There's no ticket desk between the client and whoever built the automation: you talk directly to the team that developed it.
Support doesn't end at go-live. Documents change format, systems get updated and business rules get adjusted. We stay available for those changes and, when a client would rather not handle day-to-day operations, we take them on under the BPO model.
Where we work
We have processes in production in seven Latin American countries. This isn't a list of markets where we'd like to work: these are automations up and running, each with its own country's regulations, documents and systems.
A foreign trade process in Chile looks nothing like one in Mexico, and a bank reconciliation depends on the format each bank provides. Having solved those differences seven times is not the same as having read about them.
What we work with
How we work
Stage 1Process discovery
We walk through the process with whoever runs it today, including the cases that go wrong. That's where the real rules come from, and they're almost never written down.
Stage 2Scope and rules
We document what gets automated, what stays out and what the solution does with each exception. It's agreed before any code is written.
Stage 3Development
We build and test with the client's documents and data, not with samples. We adjust on real cases.
Stage 4Go-live
We launch alongside the client's team, reviewing results run by run until the process stabilizes.
Stage 5Operation and improvement
We stay available: adjustments for changes in documents, systems or rules, and improvements based on what the operation shows.
Let's talk about which processes we can automate at your company
You don't need a fully defined project. Once we understand how the process works today, we can tell you whether it can be automated and where to start.
Or email us at [email protected]