Pricing
No tiers here.
A number on the first call.
You are billed by the turn (one question asked and answered) against a ceiling you set. There is no price on this page, which is normal for this category and not very useful; the shape is, so you can work out roughly where you would land before you talk to anybody.
The shape
Priced on what you ask, capped by what you set
Usage-based pricing has one real problem and it is not the rate: it is not knowing the ceiling. So the ceiling is the part we make you set.
The meter is a turn
A turn is one question answered: the reasoning, the queries it compiled, and the answer that came back. Opening a saved dashboard or paging a report is not a turn, because no model runs: a stored view holds a compiled query, so re-reading it is database work and an SAP read.
You set the ceiling, not us
Budgets are enforced before a run starts rather than reconciled after it. A team cannot spend past the cap you set them, which makes the worst case a number you chose rather than a number you discover.
Cost per turn is visible to you
The admin surface shows what turns actually cost, not just how many there were. You should be able to audit your own bill from inside the product rather than reconstructing it from an invoice.
The meter
The shorter list is the one you pay for
A saved view holds a compiled query rather than a prompt, so re-opening it is a database read and an SAP read. That is why the right-hand column is longer, and why it stays longer as a team settles into the thing.
Moves the bill
A turn is one question answered: the reasoning, the queries it compiled, the answer
- Asking a new question
- A follow-up that needs fresh reasoning
- Building a dashboard or report for the first time
Does not move the bill
No model runs, so there is nothing to meter
- Opening a saved dashboard
- Paging or sorting a report
- Re-running a stored view tomorrow, or next quarter
- Reading an answer somebody else already asked for
- Adding a viewer who only reads
What a first engagement looks like
Priced in time before it is priced in money
-
1. Thirty minutes
A session against a system we provide. No access to yours, no environment setup, no data from you. You bring one question your reporting cannot answer.
No cost
-
2. A scoped pilot
In your own landscape, against your own SAP, with your security team involved. This is where the real evaluation happens and where the number gets specific.
Quoted once scoped
-
3. Production
Priced on usage against a cap you set, per the shape above.
Quoted
Straight answers
What we are not going to pretend
A pricing page that only lists advantages is one you should read twice.
-
Usage-based means usage moves the bill. We would rather write that plainly than bury it: a heavy month of asking costs more than a quiet one, and any vendor telling you otherwise is averaging it into a number you cannot see.
-
It runs on your infrastructure, so there is a cost we do not quote and cannot. That is the trade for your SAP data never leaving your landscape.
-
There is no self-serve tier and no credit card path. A deployment inside your landscape involves your security team whether we would like it to or not.
-
We do not publish a rate card. Not because the number is embarrassing, but because scope genuinely varies by how many systems and modules are involved, and quoting before we know that produces a figure you would have to renegotiate.
What people ask about cost
Why not just publish the number?
Four honest reasons. Scope varies by how many SAP systems and modules are in play. It deploys inside your landscape, so a meaningful share of the cost is infrastructure we do not supply and should not pretend to price. Approval-workflow configuration differs per organisation. And we would rather quote something true than a headline you have to renegotiate. What we will not do is make you sit through three meetings to get a figure; you get one on the first call.
What stops the bill running away?
A cap you set, enforced before a run starts rather than after it. The honest caveat is that a run which begins inside its limits can still overshoot them, so the ceiling is close rather than absolute; that gap is stated rather than hidden.
Does opening a dashboard cost anything?
No model call, so nothing is metered for reasoning. A saved view stores a compiled query rather than a prompt, which is why re-opening it is a database read plus an SAP read, and also why the figure does not drift between the board pre-read and the board meeting. The two properties come from the same design.
How does this compare to SAP AI Units?
Factually: SAP meters premium AI scenarios and agent executions against AI Units, a prepaid consumption currency, and does not publish a consolidated rate card. Reported overage rates run well above contracted per-unit rates. We are not going to editorialise on that beyond noting it is the comparison most people are actually making, and that a cap you set is a different instrument from a pool you exhaust.
What does a first engagement cost?
Thirty minutes, and nothing else. A first session runs against a system we provide: no access, no environment setup, no data from you. If it continues, a pilot in your own landscape is a scoped piece of work with your security team involved, and we price that once we know the scope rather than before.
Ask for the number on the first call
Bring the question your team has been waiting on a report for, and we will tell you what it would cost to answer it every day.