Request types in scope
Each request type, such as Reg E disputes or fee waivers, brings its own rules, data and escalation paths.
Every engagement starts with a two-week, fixed-scope diagnostic on one request type. You see your own policy in the Rulebook and a sealed decision record before you commit, and production is priced on the scope you have already proven.

Developed by Sphere, named a Top Chatbot Company and a Top AI Company in the US by Clutch
Request type and owner agreed. Fee waivers on chat and voice.
Your thresholds written as Rulebook rules.
Sample requests run through your rules. Sealed records ready for compliance.
Systems: core and CRM. Deployment: co-managed. Next step: production proposal.
Palladium does not publish a price list. Each engagement is priced on three things: the request types you automate, the channels and systems involved, and where the platform runs.
Every engagement starts with a two-week readiness diagnostic at a fixed scope, with the fee agreed before kickoff. You know what you are buying before you buy it.
Conversational AI and AI agent vendors price in a handful of ways. Each one moves risk differently between you and the vendor. Here is how to read them as a bank.
| Model | How it works | What to watch for in a bank |
|---|---|---|
| Per seat | A monthly fee for each employee who uses the tool. Fits internal assistants. | Says nothing about customer volume, so it rarely fits customer-facing AI. |
| Per conversation | A fee for each conversation the AI handles, resolved or not. | You pay for conversations that end in a handoff. Ask how a conversation is counted across channels. |
| Per resolution | A fee only when the AI resolves the request without a person. | Ties cost to outcomes. Check who defines “resolved” and whether escalations are excluded. |
| Usage-based | A platform fee plus model usage, often per token or per call. | Hard to forecast. Model price changes and long conversations go straight to your budget. |
| Scoped engagement | A fixed-scope pilot, then production priced on the request types and channels in scope. | Easier to budget and to defend in procurement. This is how Palladium is priced. |
Each request type, such as Reg E disputes or fee waivers, brings its own rules, data and escalation paths.
Voice, chat and in-app, SMS and WhatsApp, and email each need their own setup and testing.
Core banking, CRM, ticketing, payment rails and identity providers the agents read from and act on.
How many requests each workflow handles, and how they peak during fraud waves or seasonal spikes.
Hosted by Sphere, co-managed, or fully private in your VPC with private model options.
Sphere manages policy and operations, or your team writes the rules and Sphere operates the platform.
The two-week diagnostic covers one request type. At the end you have evidence your compliance team can review and a scoped proposal you can take to procurement.
We walk the request type with its owner, map your policy thresholds to Rulebook rules, and review the channels and systems involved.
We run your rules on sample requests and produce a sealed decision record your compliance team can retrace step by step.
If you continue, the diagnosed workflow goes into production on one or more channels, with Coach / QA review from day one.
Add request types, channels and teams on the same Rulebook and audit trail, or move to a private deployment.
What changes is who runs the platform and where it runs. The rules, agents and Ledger are the same in every option.
Sphere runs the platform. You bring the policies and systems of record.
Your team owns policy authoring. Sphere owns platform operations and audit.
Fully private in your VPC, with private model options and your own operating team.
| Managed by Sphere | Co-managed rollout | Private deployment | |
|---|---|---|---|
| Who writes the rules | Sphere, from your policies | Your team | Your team |
| Who operates the platform | Sphere | Sphere | Your operating team |
| Where it runs | Hosted by Sphere, strict data isolation | Hosted by Sphere | Your VPC: AWS, Azure or Google Cloud |
| Models | Model-agnostic | Model-agnostic | Private model options, bring your own |
| Audit trail and guardrails | Included | Included | Included |
Agree these measures before the diagnostic starts: autonomous resolution rate, escalation rate, time to compliance sign-off, and handle time on the request type in scope.
Every engagement, at every size, ships with the controls your compliance and vendor-risk teams ask for first.
Every decision sealed in the Ledger and exportable for examiners as a digitally signed PDF.
Dollar and risk thresholds live in the Rulebook, never in the model.
Prompt-injection screening and PII redaction on every message, in both directions.
Every interaction reviewed, with root causes and policy improvements surfaced.
Independently audited controls. No training on your customer data, by default and by contract.
The answers your vendor-risk team will ask for, ready before the first call. Open the kit
Palladium is priced per engagement, based on the request types in scope, the channels and systems involved, and the deployment model. Every engagement starts with a two-week readiness diagnostic at a fixed scope, with the fee agreed before kickoff.
Two banks automating the same request type can have very different volumes, channels and core systems. The diagnostic puts your scope in writing, so the production proposal is priced on your actual situation, not a generic tier.
The policy for one request type, an owner who can answer questions about it, and a contact in compliance who will review the sealed decision record at the end.
The diagnostic takes two weeks. A first production workflow typically ships in weeks after that. A $2B regional bank had its audit trail signed off by compliance in 9 days.
Yes. The architecture is the same in every option, so rules and records carry over when you move from a managed or co-managed setup to a private deployment in your VPC.
Pricing follows scope, not institution type. A community bank or credit union starting with one request type on one channel scopes a smaller engagement than a regional bank automating several request types across voice and chat. Palladium for banks and credit unions.
Palladium is a Sphere product. The engineers who design, run and support it are the same team Clutch ranks among the top AI and chatbot companies in the United States, and the team behind production systems for more than 300 clients over 21 years.
That is why Palladium ships with what regulated teams ask for first: rules in code, a record of every step, and people on every exception.








In a 30-minute discovery call we load one of your thresholds into the Rulebook and show you the sealed record it produces. Then we scope your diagnostic.