Sellers and partners describe the deal in Slack, Teams, or the CRM. Across returns a configuration and a draft quote that follow your rules.
Request a demodeal-desk
Renew Northwind for a year, add 500 Analytics seats, via Summit Partners.
Found the contract (ends Mar 31) and the partner (Summit, Gold).
Start the new seats now, prorated, or at renewal?
Draft quote · Northwind
Total $184,140
Standard partner discount. No approval needed.
Submitted to your CPQ as a draft.
Draft quote · Northwind
Total $161,040
Standard partner discount. No approval needed.
Submitted to your CPQ as a draft.
Today, a seller’s request passes through configuration, contracts, pricing, and approvals by hand. Each handoff can delay the quote or send the wrong price to the customer.
Seller in Slack
Renew Northwind and add 500 seats, through our partner.
Quote sent Days later
Rework
Across checks the product, contract, partner price, and approval rules, asks for missing details, then drafts the quote.
Action
Reasoning
Context
Sources
Many quoting rules live with your deal desk, not in the CPQ. The Architect reads your pricing policies and past quotes, then asks your deal desk about the gaps.
Pricing policies, approval rules, past quotes, and your deal desk’s answers.
The Architect drafts it in plain language. Your deal desk reviews it.
A versioned graph of small agents, each with one job.
The Operator catches rule changes. Your approved quotes re-run before a person signs off.
Targets we agree with you before the build, scored on quotes your deal desk already approved.
Drafts that build in your CPQ with the right SKUs, quantities, prices, and dates.
Average time from the seller’s first message to a confirmed draft.
The right discount and approval path for each scenario.
Apply real rule changes, then re-run every past scenario with no regressions.
Why it matters: Most quoting rules live with product managers, SEs, and the deal desk.
Across: The graph is built from all of it, not just the catalog.
Why it matters: Sellers stop using tools that make them repeat what the CRM already knows.
Across: It checks the CRM and contracts first, then asks one question.
Why it matters: The same request can’t produce two different prices.
Across: Pricing, discounts, and co-terms run as rules, in code.
Why it matters: Rules change every quarter. Each change can’t become an engineering ticket.
Across: Describe it in plain language. It’s tested on past quotes and approved first.
Why it matters: The deal desk and finance need to see why each number is there.
Across: Every price, discount, and approval links to its rule and source.
A three-week pilot on your own data, scoped to one product family or region.
Connect your CPQ, CRM, and Slack or Teams for a first group of sellers.
Across sits between the conversation and your CPQ. It reads under each user’s permissions and writes only after a person confirms.