We built the tooling we needed, because it didn't exist.
We started in 2014 doing Oracle EBS work the way everyone did: manual installs, DBA bottlenecks, no version control. Ten years later we run EBS R12.2 and Fusion Cloud for enterprise clients across the Americas, and we built Katrina — our own CI/CD platform — because the tooling we needed didn't exist. Today we're applying the same discipline to AI: agents that work inside EBS and Fusion, with the guardrails an ERP demands.
EBS consulting out of Buenos Aires and Dover, DE. Financials and SCM, the hard way — like everyone else back then.
git, automated installers, approval gates for EBS. Now in production — 3,800+ packages shipped, 67 daily users at our largest client.
MCP servers that connect Claude to EBS and Fusion — used daily by our own consultants before we ever sell them.
In a boutique, you hire the people — not the logo.
Information Systems Engineer and software developer. Leads the Oracle EBS practice and the engagements that shaped how we work: financials and SCM on R12.2, delivered the disciplined way we now build tooling around.
Specializes in AWS, distributed systems, and security. The engineering behind Katrina and the MCP servers that connect Claude to EBS and Fusion — the tooling our own consultants run every day.
The case against hiring a big SI for this.
ET and ART overlap your whole workday. Your 9 AM standup is our 9–10 AM — not someone's midnight.
The engineer on the call is the engineer in your environment. No account-manager relay, no bait-and-switch staffing.
Senior Argentina-based engineering at rates a big SI charges for juniors — with a US entity to contract with.
Schedule with a founder.
Not a discovery-call script — an engineer who has run your stack, on your timezone, with an opinion you can push back on.