Product
Write approval rules in English.
Not decision trees.
A rule like "VP approves marketing spend over $25K, except recurring vendors with 12+ months history" is stored verbatim and evaluated by AI at runtime. No code. No deployment. No consultant.
Same policy change.
Two different realities.
The scenario: It's September 28. The CFO needs Q4 close tightening — stricter approvals, vendor exceptions, delegation rules, and a time-bound policy that auto-expires December 31.
Legacy ERP
Draft requirements document
Controller + Finance Manager write functional spec for 4 rule changes, map approval matrix, document edge cases
Submit IT change request
Finance Manager → IT Service Desk. Ticket sits in queue behind 23 other requests. Priority: Medium.
IT analysis & development
Business Analyst translates spec → ERP Developer builds 4 workflow branches, 6 condition nodes, calendar integration, delegation chain. Cannot implement "pre-approved vendor" exception — requires custom dev.
Sandbox testing & UAT
QA Team runs 40+ test scenarios. Finance Manager validates in sandbox. 3 bugs found — sent back to dev.
Change Approval Board
IT Director, Finance Director, Compliance Officer review. Board meets Thursdays. Just missed this week's meeting.
Production deployment
IT Ops schedules deployment window. Notify affected users. Pray nothing breaks.
Total turnaround
6 people across 3 departments
14–27 days
$8K–$15K
Q4 starts Oct 1. Policy requested Sept 28. Best case: policy goes live Oct 12 — 12 days of Q4 without proper controls.
Uno360
Effective October 1 through December 31:
- All consulting invoices over $10,000 require my approval, regardless of department.
- Exception: vendors on the approved Q4 budget plan can be auto-approved up to their budgeted amount.
- Any related-party transaction requires Audit Committee review, regardless of amount.
- If I'm unavailable, route to VP Finance as backup approver.
This policy auto-expires December 31. Simulate against last 90 days of transactions and show me what would have changed before activating.
• 4 rules created with auto-expiry Dec 31
• Simulation complete: 23 of 847 transactions would have been rerouted
• Backup routing configured for VP Finance
• Awaiting your confirmation to activate
Total turnaround
1 person. 1 email.
30 seconds
$0
Policy active before Q4 starts. Simulated against real data. Auto-expires when Q4 ends. Every edge case handled.
Six reasons this changes everything.
Agility
CFO reads vendor is under investigation. Legacy: 5–10 business days to freeze payments. Uno360: One email, 30 seconds, done.
Setup Time
New entity workflow setup: Legacy 165+ hours ($25–50K). Uno360: 2–4 hours of rule writing.
Change Management
The rule IS the documentation. No drift. No "the docs say X but the system does Y."
Cost Reduction
Eliminate $155–385K/year in workflow tooling, consultants, change requests, and testing.
Edge Cases
LLM reasons from policies naturally. First-time scenarios don't fail — they route to humans with confidence scores.
Email Integration
CFO sends email at 11:47 PM to freeze vendor payments. ERP processes 4 actions in seconds. Responds with confirmation.
The one-email policy change.
Incoming Email
Immediate — freeze all DataFlow Systems payments
I just learned DataFlow Systems is under investigation for billing irregularities. Effective immediately, freeze all pending and scheduled payments to DataFlow Systems. Any new invoices from them should be held for my personal review. Set a reminder to revisit this in 30 days.
ERP Response
uno360
Processed in 4 seconds
Payment hold placed on 3 pending payments ($47,200 total)
Approval rule created: "All DataFlow Systems invoices require CFO approval"
Report generated: DataFlow Systems — 12-month payment history
Reminder set: Review DataFlow freeze in 30 days
Confirmation email sent to cfo@company.com
Slack notification sent to #accounts-payable
Legacy ERP: 5–10 business days. During that time, payments continue flowing.
"Our financial controls adapt as fast as our business does. The policy IS the configuration."
Your policies should read like policies.
Not flowcharts.
30 minutes. No pitch deck. Just demo & discussion!