Trust
Your data, your rules.
These policies are written for you to read, audit and put into the contract. A specific, verifiable commitment is worth more than a badge on a wall: this is exactly what we bind ourselves to with your data.
Your data never trains models.
Your operation's data is used only to answer for your operation. Never to train models — ours or anyone else's.
Minimal, revocable access.
Read-only credentials wherever possible, separate accounts per client, and every access revoked when the contract ends.
Full reversibility.
If you leave, you take the code, the data and the documentation with you. No hostages, no exit fees.
Human in the loop.
Everything your customer sees passes human review before shipping, and sensitive cases always escalate to a person.
FAQ
The questions that kill contracts.
Answered in writing, before the first call.
Am I locked in with you?+
No. Code and configuration live in repositories under your name or transferable to you, and documentation is part of the deliverable: if you leave, you leave with a system that works. What doesn't carry itself is the work of keeping it true — your catalog changes, your rules change, and the models shift underneath. That's what the monthly fee pays for, not ransom.
Who owns the IP and the data?+
You do. Software built for your project is yours once paid, and your data never stops being yours: we don't use it to train models or for other clients.
How do I measure that it actually works?+
Metrics are defined before we build — response times, leads served, case coverage — and you review them in reports a manager can read, not just an engineer.
What if the AI tells my customer something false?+
That's what Grounding is for: if a fact isn't in your base, the agent won't state it — it asks or escalates to a person. And every system passes a suite of real scenarios before touching customers — a suite that keeps growing with each month's real conversations.
What if I want to leave tomorrow?+
Thirty days' notice, an orderly handover of access, data and documentation, and the system remains yours. What stops that day is the upkeep: nobody re-syncs the catalog, adjusts the rules when your operation changes, or answers when the agent gets something wrong in front of a customer. It's all in the contract from day one.
How do you charge?+
One-time implementation + a monthly operation fee. The implementation builds the system; the monthly keeps it true — the catalog stays in sync, rules get adjusted when your business changes, the test scenarios grow with real conversations, and someone is accountable when the agent gets it wrong in front of a customer. A system without that doesn't break all at once: it starts lying slowly. That's why a "$0/month" plan doesn't exist. Ranges are published on the pricing page.
When it has to work, start with Betancore.
A 15-minute audit of your real case — not a canned demo. You leave with an honest read on what to automate first, and what not to.