Real environments, real numbers, real names.
Every case here follows the same format: the technical context, the problem in one sentence, what we actually did — with the real tools — and the result against a baseline. If a number is on this page, we can defend it on a call.
Argentina's largest water utility — 7M+ users — runs EBS R12.2 with Katrina as its release pipeline.
Manual installs and DBA bottlenecks across DEV/TEST/UAT/PROD — no version control over hundreds of customizations.
Put every customization — FNDLOAD, PL/SQL, forms, BI Publisher — in git and deployed Katrina as the release pipeline, with approval gates and ticket-locked PROD.
An EBS R12 database cut from 6.2 TB to 2.9 TB — without losing a row the business needed.
A decade of transactional history was inflating storage costs, backup windows, and clone times for every non-production refresh.
Designed and ran a module-by-module purge and archiving program using Oracle's standard purge concurrent programs plus custom PL/SQL for the gaps — validated against finance sign-off at every step.
FAH journal batch processing time cut by 95%.
Journal batches were taking hours to process, pushing accounting close past its window night after night.
Re-architected the batching and parallelization strategy for journal import — profiling the bottleneck first, then restructuring batch sizes and worker distribution around it.
Companies we've worked with directly
verifiable engagements onlyLogos shown with written permission. Ask us for references in your industry.
Want to talk to one of these clients?
We'll connect you with a reference running the same stack you do — EBS, Fusion, or both.