For deal desk & RevOps teams
Current terms on every quote
The discount matrix changes, the approval chain changes, and someone always quotes the old version. A wrong number here does not just cause confusion, it costs margin or an unapprovable quote. Keep the current approved rules in one place and let every assistant answer from them.
- The current discount matrix, every time
- Approval rules assistants can cite
- Every change tracked to its approver
- Free tier to start
Asked
What's the max discount on a 2-year agreement?
The approved answer
Up to 15% without approval. 16 to 25% needs deal desk sign-off. Above 25% goes to the CRO.
Asked
Who approves a non-standard MSA clause?
The approved answer
Legal owns all MSA redlines. Anything touching liability or data terms needs Legal sign-off before it goes to the customer.
Asked
Can we do a 3-year ramp deal?
The approved answer
Yes. Ramps up to 3 years are standard with a year-1 minimum of 60% of run rate. Longer ramps need CFO approval.
One discount matrix, always current
Thresholds, floors, and regional exceptions live on approved pages. Update the matrix once and every assistant quotes the new rules, so the same question stops landing back in your queue.
Approval chains, written down
Who signs off at which discount level stops living in someone's head. The assistant cites the rule instead of guessing at it.
Defensible when a deal is questioned
Every answer traces to a version with an author, reviewer, and approval time, so you can show which rules were in force when the quote went out.
Beside your CPQ, not replacing it
Your quoting stack stays. This is the source the AI in the middle answers from, connected over MCP or REST with a scoped key. Import your existing discount matrix and terms sheets to start, instead of writing the rules over from scratch.
Questions
- Does this replace our CPQ or approval workflow?
- No. Quotes and approvals keep flowing through your existing tools. This is where the current rules live, so assistants answer from them.
- What happens when the discount matrix changes?
- The edit is a draft until its owner approves it. From the next question on, every connected assistant answers with the new matrix, and the old version stays in the history, so the version everyone quotes at quarter-end is the one that was actually signed off.
- Can different teams see different rules?
- Yes. Access is scoped per connection, so a partner-facing assistant can read standard terms while internal exceptions stay internal. Finance-confidential exceptions stay internal, too. No specific compliance certification is claimed here; your security team can review the access scopes and approval trail directly.
- How fast can we start?
- Start free, write down the discount matrix and payment terms, and connect an assistant. The workflow is a shared doc with an approve button.
- What does this cost for a deal desk team?
- Free to start: 60 requests a minute, 5,000 a day, up to 200 documents and 5 members, enough to prove the workflow on one policy area. The Team plan is $99 a month with higher limits, sized for a full rollout across discount, approval, and payment-term policy.
- We already have a search tool over our policy folder. Isn't this the same thing?
- A search tool retrieves whatever text matches best, including a discount policy that was superseded last quarter. This serves only the current approved revision, so a search can't surface a version nobody signed off on.
- Doesn't this just become another wiki that goes stale?
- The difference is the publish rule. A wiki page can be edited by anyone with no review step, and an assistant reading it cannot tell whether the edit was reviewed. Here, an edit is a draft until an owner approves it, so a stale approved version is visible, with its own approver and date, instead of drifting silently.
Standardizing deal rules across regions or teams?
Tell us how your desk runs today, and we will help you plan the rollout.
Retire the out-of-date discount PDF
Start free and make the current rules the ones every assistant quotes.
