Request demo

Know where every deal stands, and why.

A seller asks in Slack. Across reads the calls, email, and CRM, checks your playbook, and answers with the signals and a next step.

Request a demo

renewals

  1. Jordan Lee

    Is the Northwind renewal at risk?

  2. Across

    I checked 11 calls, email, and the CRM since June.

    Yes. Three signals put it at risk.

  3. Sample renewal brief · Northwind

    At risk
    • Champion left Elena Cole, VP Operations · Oct 3 No sponsor
    • Buyer gone quiet No meeting with the CFO since Jun 12 126 days
    • Promise overdue SSO integration, due Sep 30 16 days late

    Next step: meet Marco Ortiz, the new VP Operations.

    Draft saved for your review. Nothing sent.

    1. S-04 Champion leaves within 6 months of renewal: flag at risk Renewal playbook, p. 3
    2. S-07 No meeting with the economic buyer in 90 days: flag at risk Sales methodology
    3. S-09 Commitment overdue before renewal: tell the account manager Account manager interview

Where renewal risk hides today.

Calls, email, and calendar show renewal risks, but those signals never update the CRM stage. By the time someone reviews the deal, five weeks remain and the sponsor has left.

days to renewal

Five weeks out, with no sponsor left to call.

CRM stageCommitUnchanged since Jun 12
  1. 292 days to renewal. Jun 12 · Calendar · Last meeting with the CFO. No one books the next.
  2. 229 days to renewal. Aug 14 · Call · SSO promised for Sep 30. It slips.
  3. 179 days to renewal. Oct 3 · Email · The champion’s email bounces. She has left.
  4. 35 days to renewal. Feb 24 · Renewal call · The risk is found.

How Across spots renewal risk.

Across checks each buyer’s recent contact and open commitments against your renewal playbook, then flags gaps and drafts the next step.

Buying group for the sample Northwind renewal
SeatPersonLast contactCoverage
Champion Elena ColeVP Operationsleft Oct 3 Last contactLeft Oct 3 Coverage
New championMarco OrtizVP Operations, newLast contactNot metCoverageNone
S-04Left Oct 3, 179 days before renewal.Email · people data
Economic buyer Ana RuizCFO Last contactJun 12 CoverageCold
S-07No meeting in 126 days. Your playbook flags 90.Calendar
Technical buyer Nina ParkIT Director Last contactOct 9 CoverageActive
S-09SSO was due Sep 30. Asked about it twice.Aug 14 call · email

At risk. Across drafts an intro to Marco Ortiz from the last three calls. Jordan reviews it and sends it.

Built from how you sell.

Much of your renewal judgment lives with your best reps, not in the CRM. The Architect reads your playbooks and past deals, then asks your best reps about the gaps.

  1. Methodology, renewal playbook, recorded calls, past deals, and your best reps’ answers.

    • Sales methodology
    • Renewal playbook
    • Recorded calls
    • Won and lost deals
    • Architect asks:A commitment is overdue before renewal. Who should know? Account manager answers:Tell me, every time.

  2. The Architect drafts the risk and next-step rules. Sales ops reviews them.

    • S-04 Renewal playbook, p. 3 Champion leaves within 6 months of renewal: flag at risk
    • S-07 Sales methodology No meeting with the economic buyer in 90 days: flag at risk
    • S-09 Account manager interview Commitment overdue before renewal: tell the account manager
    • S-12 Sales manager interview Two risk signals within 6 months of renewal: brief the sales manager

  3. A versioned graph that links each signal to a next step and the person who acts on it.

    • Read Calls and email · CRM and calendar · People changes
    • Check Renewal playbook · Methodology gaps · Open commitments
    • Act Renewal brief · Next step · Draft follow-up

  4. The Operator catches rule changes. Past renewals re-run before your team approves the change.

    • Renewal lost after a reorg Flagged at risk
    • Renewal won with two sponsors Healthy
    • Customer asks about more seats Growth brief
    • Buyer quiet: flag at was 90 days, now 60 days Past renewals re-run ·Awaiting sales ops approval

How we’ll measure the pilot.

Targets we agree with you before the build, scored on renewals you already know the outcome of.

Every signal in a brief links to the call, email, or record behind it.

Change a real risk rule and re-run past renewals without engineering work.

A global software company, three months in.

+36%

average monthly bookings, with the same team and the same lead volume.

Questions to askCheck the answer against your own cases

Questions to ask any deal intelligence AI.

  1. Does it know your playbook, or only your CRM?

    Why it matters: Risk lives in your methodology, your playbooks, and your best reps’ habits.

    Across: The rulebook is built from all of it. Sales ops reviews it.

  2. Does it show why a deal is at risk?

    Why it matters: A score with no reason doesn’t change what a rep does next.

    Across: Every signal links to the call, email, or record behind it.

  3. Why it matters: Thresholds and stages change every year. Each change can’t become an engineering ticket.

    Across: Describe it in plain language. It’s tested on past deals and approved first.

    • Buyer quiet: flag at 90 days to 60 days
    • Northwind: flagged Aug 11, not Sep 10
    • Past renewals re-run , awaiting approval

  4. Does it work where reps already work?

    Why it matters: Reps skip another dashboard.

    Across: Reps ask and get briefs in the chat tool they already use. CRM updates follow the rules you set.

  5. Is the risk call the same every time?

    Why it matters: The same deal can’t be at risk in the morning and healthy by lunch.

    Across: Thresholds are set by your rules, and the same signals give the same call.

Start with your hardest renewals.

A three-week pilot on your past deals, scoped to one sales team.

  1. Week 1
    • Methodology and renewal playbook
    • Last year’s won and lost deals, with calls
    • Recorded interviews with top reps
  2. Week 2
    • Writes the risk and next-step rules
    • Sales ops reviews them
    • Runs past deals through the graph
  3. Week 3
    • Tested on held-out renewals with known outcomes
    • Reps try it in a sandbox channel
    • Results against the agreed targets
  4. Your decision

    Use the results to decide whether to connect your CRM, call recorder, and chat for a first team.

What we need to start.

  • Sales methodology Stages, exit criteria, and required fields
  • Renewal playbook Risk signals and who acts on each
  • Past deals Last year’s won and lost, with outcomes
  • Call recordings For the pilot team’s open deals
  • CRM export Accounts, contacts, and opportunity history
  • Recorded interviews With your best account managers
How it connectsPermissions, approvals, and your systems of record

Your CRM stays the record.

Across reads calls, email, and the CRM under each user’s permissions. You choose which fields it updates on its own.

Across
  1. Permissions Reads only what each user can see
  2. Confirmation Sends nothing without a rep’s yes
  3. Logged Every CRM update is recorded
  1. Ask in Slack
  2. Read, under the user’s permissions Calls, email, calendar, CRM
  3. Brief the seller with the signals
  4. Send the draft after a yes, and log every CRM update
  1. ITCleared
  2. InfoSecCleared
  3. RiskCleared
  4. SOC 2Type II
  • Cleared by IT, InfoSec, and risk teams at a Fortune 100 technology company.
  • Single sign-on through Okta, Entra ID, Google, or Duo.
  • Runs on the models you approve and does not train on your data.
across / new run start here

Let us help you get work done.

Request a demo See customer stories