Proof of Performance
RULE UPDATES
Days to Minutes
Implementing business rule updates went from days of developer time to minutes in DecisionRules
COST SAVINGS
$2,000+/mo
Estimated monthly savings by eliminating developer involvement in routine rule management
ONBOARDING
Non-Technical Users
Operations team members manage rules independently without coding skills
About DRUO
DRUO is an international direct debit payment method headquartered in Miami, Florida. Founded in 2021, the company provides businesses with a fundamentally different way to accept payments: directly from bank accounts, bypassing traditional card networks entirely.
The result? Merchants save more than 90% on payment processing fees compared to traditional card payments. Fraud rates drop dramatically, running at roughly 25 times lower than the industry average. And because DRUO works with any bank account, it reaches three times more potential customers than card-based systems.
DRUO's proprietary network connects to over 10,000 financial institutions and more than 1 billion bank accounts around the world. The company processes hundreds of millions of dollars a year in transaction volume, growing 2-3x % year over year.
The Challenge: Code-Based Rules That Couldn't Keep Up
From the start, DRUO needed business rules to manage the complexity of payment processing including fraud detection and complex user decsioningacross multiple countries and financial institutions.
Initially, this logic was hard-coded into the core platform. Within about a month of operations, the team realized this approach was unsustainable. As Alejandro Pinzon, CEO of DRUO, put it:
Taking a massive script to do many checks and output many things, especially when you seek layering and nested decisions... it's just very difficult to do via code, very difficult to manage.
Alejandro Pinzon
CEO of DRUO
The team explored a business rules engine early on and initially adopted a vendor, but that solution soon hit its own limits. Scale became a problem, both from a cost and a product perspective. The platform could only process rules sequentially, which forced DRUO to think linearly about logic that was inherently complex and interconnected.
DRUO needed something better. Something that would let a fast-growing fintech iterate on risk and payment logic without burning developer hours, and that could handle the kind of nested, multi-layered decisions that payment processing demands.
| Problem | Impact |
|---|---|
| Hard-coded logic | Any rule change required developer involvement, taking days to implement even simple updates. |
| Limited scalability | The previous vendor's sequential processing and pricing model couldn't keep up with DRUO's growth across new markets. |
| Non-technical teams locked out | Only developers could read or modify the rules, creating bottlenecks and slowing the operations team. |
| No testing capability | There was no built-in way to test rule changes before pushing them to production. |
Why DRUO Chose DecisionRules
Alejandro Pinzon led the evaluation, researching multiple vendors online, scheduling meetings, and assessing each platform's track record, robustness, and pricing. The selection criteria came down to a few things that mattered for a fast-moving startup processing real money.
Low Friction to Get Started
DRUO could sign up, pick a plan, and start building a proof of concept within minutes. No lengthy sales cycles, no multi-week account provisioning, no locked-in contracts.
The fact that we could just sign up and pay something cheap, and get started with no commitment meant very little friction for us to test it out. And once the system proved it could work, we started implementing it more.
Alejandro Pinzon
CEO of DRUO
Technical Capabilities That Stood Out
Several features caught the team's attention during evaluation:
- Decision Flows with nested rule sets: The ability to tie multiple rule sets together in a flow, nesting them into larger decision processes, was something Alejandro described as unique among the vendors they evaluated.
- External service calls within flows: DRUO could invoke external services during rule execution.
- Test Bench: Built-in testing gave the team confidence to validate rules before going live. Their previous tool had no equivalent.
- JSON export and Management API: The ability to export entire rule sets as JSON, and the Management API for programmatic rule creation and management, provided the technical flexibility DRUO needed.
Fair, Transparent Pricing
Pricing was spot on for DRUO's scale. No long-term commitments, month-to-month billing, and the freedom to walk away at any time without negotiating an exit from a multi-year agreement.
No commitment and month to month payments eliminated the friction to make such an important decision. We couldn’t be happier about selecting DecisionRules as our rules engine.
Alejandro Pinzon
CEO of DRUO
Implementation and Migration
DRUO built their own proof of concept, starting with a simple rule set and sending their first successful API request within minutes.
We signed up and we tested our first request. And in the first couple of minutes, we had a successful request coming back without the need to have three, five, six calls, training, or reading a manual.
Alejandro Pinzon
CEO of DRUO
The full migration from their previous vendor took approximately three to four months. Nicolás Navas, who leads operations at DRUO and is a daily power user of DecisionRules, managed the migration process. The team started with simpler rule sets and progressively migrated more complex domains.
Because the two platforms had fundamentally different architectures, the migration was not a simple copy-paste exercise. The previous tool processed rules sequentially. DecisionRules offered Decision Flows that allowed parallel and nested execution. Nicolás and the team used this as an opportunity to rethink and optimize their rule structures.
If you want to get the best out of the platform, it's probably better to understand how both platforms work and determine rule by rule how it should be implemented.
Alejandro Pinzon
CEO of DRUO
he DecisionRules AI Assistant helped during migration. Nicolás used it to understand which rule types would be most appropriate for each use case, whether a Decision Table or a Decision Tree would be the better fit for a particular piece of logic.
Support That Showed Up When It Mattered
For a company that moves money across borders, downtime is not an option. DRUO found DecisionRules' support to be one of the best they have experienced.
Sometimes I request things with a critical level, and they are critical. I have somebody on a Saturday or Sunday just sending me a link to chat. I think it's one of the best support experiences I've had.
Alejandro Pinzon
CEO of DRUO
Nicolás added that the combination of strong documentation and the AI Assistant reduced his team's need for direct support. When the documentation and AI Assistant provided answers, they did not need to open a ticket at all.
Key Use Cases
- Risk Scoring and Fraud Detection: DRUO's core use of DecisionRules centers on evaluating transactions in real time. The platform processes payment requests through layered rule sets that assess risk signals, flag suspicious activity, and route transactions accordingly. With millions of records flowing through the system, accuracy and speed are non-negotiable.
- Multi-Country Payment Processing: As DRUO expands across the Americas, business rules must adapt to different regulatory environments, banking systems, and market conditions. DecisionRules allows the team to manage country-specific logic within a unified platform, keeping the core system clean while accommodating regional variation.
- Customer Support Automation: More recently, DRUO has extended DecisionRules into support-related use cases. The operations team now uses business rules to automate support workflows, routing and categorizing issues based on structured criteria rather than manual triage.
Measurable Outcomes and Benefits
- From Days to Minutes: Before DecisionRules, implementing a rule change through code required days of developer time. Now, the operations team makes updates in minutes, tests them with the built-in Test Bench, and pushes them to production without waiting for a development cycle.
- $2,000+ Monthly Cost Savings: By removing the need for developer involvement in routine rule management, DRUO estimates savings of over $2,000 per month. That figure accounts only for direct labor savings and does not include the broader value of faster iteration and reduced opportunity cost.
- Non-Technical Teams in Control: Six team members across operations and product now use DecisionRules. Four are active daily users. The visual interface means that collaborators without a development background can be onboarded and productive quickly.
We can onboard any collaborator without that technical background. That's a good challenge solved by DecisionRules.
Nicolás Navas
Operations, DRUO
- Built-In Testing and Confidence: The Test Bench was a significant upgrade from the previous tool, which had no built-in testing capability. Nicolás highlighted this as one of the most valuable day-to-day features: the ability to capture inputs, run a test, and see exactly which rows and conditions were triggered.
What's Next for DRUO and DecisionRules
- Global Expansion: DRUO is opening new markets, and DecisionRules will continue managing business rules, risk scoring, and compliance logic as the company scales into new countries and regulatory environments.
- Deeper Automation with the Management API: Nicolás sees the Management API as an underexplored opportunity. The ability to create and manage rules programmatically, potentially combined with tools like Claude Code, opens the door to automated rule generation and management at scale.
- AI Agent Integration: The DecisionRules AI Agent is a new feature that adds a probabilistic decision node directly into Decision Flows. For a payments company dealing with complex fraud patterns and risk signals, this represents a powerful new capability that DRUO plans to explore.
Conclusion
DRUO needed a rules engine that could keep pace with a fast-growing global payments company. DecisionRules delivered: low-friction onboarding, flexible pricing, and a technical platform that lets non-technical teams manage complex, nested business rules across multiple countries.
The migration from their previous vendor was an investment, but it paid off. Rule updates that took days now take minutes. Operations team members who previously depended on developers now manage rules independently. And as DRUO scales into new markets, DecisionRules provides the foundation for consistent, reliable decision-making.
DecisionRules enables us to centralize, adapt, and execute complex decision logic in real time. We just get a bunch of data, process it, make decisions on it, and get a result. And we can change and iterate with it easily, without the need for code.
Alejandro Pinzon
CEO of DRUO
Erik Lehocky
Head of Solution Consulting