Skip to main content

Get started with RevOps Intelligence

Start with a revenue question your team already needs to answer. Connect the systems that hold the evidence, inspect the result, and make the review repeatable. You do not need to understand the underlying data model to get a useful first answer.

Your first revenue review​

  1. Connect a revenue system: start with Salesforce or HubSpot, then add the systems that contain relevant evidence.
  2. Ask your first question: begin with a concrete question such as “Which renewals in the next 30 days have an open escalation?”
  3. Inspect the evidence: see the systems, records, and freshness behind the answer before you act on it.
  4. Make it repeatable: use the same revenue review in your next forecast or operating meeting, with the latest available evidence.

For the fuller RevOps workflow, see RevOps Intelligence.

Set up your team​

Once you know the first review you want to run, create the workspace where your team will work, connect its systems, and decide who should have access.

  • Connect the sources your review needs: begin with the CRM and add evidence sources deliberately.
  • Decide who should participate: give the forecast and revenue-review owners access to the information they need.

Before you start​

  • A SixDegree account. If you don't have one yet, book a working session.
  • At least one system you can connect, with credentials or OAuth access. Salesforce, Zendesk, HubSpot, GitHub, and AWS are common starting points.

What discovery gives you​

Once an integration runs, you can ask questions that span the systems you just connected:

Revenue operations Which accounts renew in the next 30 days and have an open support escalation?

Support Which PagerDuty incident has tickets from more than one customer, and what renewals do they touch?

Operations Which vendors are we paying for that no team has used this quarter?

Engineering What services depend on the payments database, and who owns them?

You’re querying current information from your systems of record, not a stale export.

Every answer carries its receipts: which systems it read, how many records, and how fresh they were. That line is built from what the query actually did, so it can't be invented. When a number surprises you, ask "where did that come from?" and follow it back to the source record.

See Trust and control for what the receipts show and how to trace a single value.

Where to go next​

Once you've been through the path above:

Next steps​

Start with your first revenue question →.

When that question is useful, use RevOps Intelligence to extend it into your forecast workflow.