For sales & enablement teams
Sell with answers, not folklore
Packaging, pricing, and the question the prospect always asks: when reps pull these from an AI that guesses, you lose the deal or the margin. Give every rep's assistant the approved version instead.
- Approved packaging and pricing answers
- Reviewed before a rep can quote it
- Reps and assistants see the same answer
- Free tier to start
- Bring in existing battlecards in bulk
Asked
Which plan includes SSO?
The approved answer
SSO is not available yet. OIDC sign-on is in development for Enterprise, with SAML and SCIM planned to follow. Enterprise customers can contact us about timing.
Asked
Can we offer net-60 payment terms?
The approved answer
Standard terms are net-30. Net-60 is available on annual contracts above $50k with finance approval.
Asked
How do we respond when a prospect says a competitor is cheaper?
The approved answer
Lead with total cost of ownership, not list price. Approved response: emphasize included support tiers and implementation time saved. Do not discount below the approved floor to match a competitor's headline number.
One source for what's sold, and for how much
Plans, packaging rules, and pricing guidance become approved pages a sales assistant quotes from at answer time.
Nothing quotable until it's signed off
A pricing change is a draft until its owner approves it, so an assistant never quotes a number nobody signed off.
On message under pressure
Approved positioning and objection responses, in your team's words, retrieved when the rep asks instead of reconstructed from memory.
Fits the tools reps already use
Connect the copilot or assistant already in your stack over MCP or REST with a scoped key. No new tool for reps to learn.
Questions
- Does this replace our CRM or CPQ?
- No. It is the knowledge source behind your sales assistant, not a quoting or pipeline system.
- How do we keep pricing from going stale?
- Changes are drafts until a reviewer approves them, so assistants always answer from the current approved version, not a cached deck.
- Can reps read the same answers the assistant uses?
- Yes. Approved pages are readable in the same workspace your team edits and reviews in, so reps and assistants stay on one answer.
- Is our pricing isolated from other companies?
- Yes. Every workspace is its own tenant, and access keys are scoped to one organization.
- We already have a sales enablement platform for our decks and battlecards.
- Good, keep it. That platform is built for a rep browsing content. Curated Data is the layer an AI assistant calls at answer time, so whatever it retrieves is the approved revision, not an old export or a cached copy. The two run side by side.
- Can this plug directly into our CRM or Slack bot?
- Not as a built-in connector today. What is shipped is the hosted MCP server and the REST API, and a CRM-embedded assistant or Slack bot your team already runs can call either directly to get the approved answer.
- Can reps' assistants see our internal battle notes?
- Only if you scope them to. A token is limited to the classifications it should read, so a customer-facing assistant reads packaging and pricing while internal-only competitive notes stay with the tools cleared for them.
- If a rep's assistant gives a wrong answer, can we tell what version it used?
- Yes. Every approved revision keeps its author, reviewer, and approval time, so you can trace an answer back to exactly which version was live when it was given.
Standardizing answers across sales and enablement?
Tell us about your stack and the trigger for this rollout, whether it's a new hire class, a repricing, or a competitive push, and we will help you plan it.
Put the approved answer behind every rep
Start free, load your packaging and pricing pages, and connect the assistant your reps already use.
