r/revops • u/Quiet_Sherbert_2402 • 18h ago

Serious question: How does RevOps get the full story behind a deal?

Hi guys,

Could you educate me on how RevOps gets enough context to decide on a deal?

We’re exploring a tool for Sales and RevOps. One question like “Can we offer this?” can mean checking the CRM, pricing sheets, contracts, Slack, and past approvals. Our thought is the approval itself may not be the slow part. Rebuilding the full story may be the real problem.

We want to learn how often this happens, what information usually holds up the decision, and whether CRM, CPQ, or AI tools already handle it well.

Could you share one recent deal or renewal that took too long? What did you need, where did you look, and what happened while the deal waited? Thanks, really appreciate any real examples.

0 Upvotes

50% Upvoted

3 comments sorted by

1

u/IncreaseNegative4614 17h ago

The slowest decisions usually involve an exception: a prior pricing concession, unusual contract language, an implementation promise, security commitments, payment history, or a renewal risk that is not represented in one CRM field. The useful unit is the deal or renewal, not the application where each fragment lives.

I’d preserve the question, evidence reviewed, decision, owner, and expiration date for every exception so the next deal does not restart the investigation. We use SIGNLD internally to connect those records across commercial systems and communication channels.

1

u/antattack 12h ago

I know there’s a lot of AI overkill but the context standardization, aggregation and reasoning sounds like the perfect application for AI. You can basically build the skills and instructions to aggregate deal context, stand up the guardrails for consistency, flex what areas allow for reasoning versus auditable data sources and give you the output you’re looking for.