Quick start for revenue operations

Business Summary: RevOps teams use Nimbus to connect CRM and pipeline data to governed AI analysis — pipeline health, forecast reviews, and account research — with approvals before anything updates your system of record.

This guide is for RevOps, sales operations, and revenue leaders who own CRM hygiene, forecasting, and GTM analytics.

What Nimbus means for revenue

Your first week — daily playbooks

Day 1 — Connect CRM

1. Open Connectors → search Salesforce or HubSpot.
2. Toggle on → Continue → complete OAuth with your GTM admin account.
3. Confirm Connected.

Deep guide: Connecting a connector

Day 2 — Intelligence vs Action

1. Open your CRM connector card — note Intelligence (read) capabilities.
2. If using Slack or CRM write-back, review Action connector requirements.
3. Document which writes require HITL before enabling Action connectors.

Deep guide: Intelligence vs Action connectors

Day 3 — Browse Revenue agents

1. Open Workstreams → filter Revenue domain.
2. Compare two agents' connector requirements and governance tabs.
3. Shortlist one for pipeline or forecast work.

Deep guide:

Day 4 — Scope forecast workstream

1. New workstream → name your forecast cycle (for example Q4 commit review).
2. Bind CRM Intelligence connector and Revenue agent.
3. Add sales leadership as approvers.

Deep guide: Creating a workstream

Day 5 — Run pipeline review

1. Plan mode → ask for pipeline health and coverage gaps.
2. Confirm & run → approve at Soft checkpoint for draft.
3. Hard checkpoint before any CRM write via Action mode.

Deep guide:

RevOps use cases to try first

• Pipeline health weekly — CRM connector + Revenue agent flags stale deals and coverage gaps
• Forecast call prep — Workstream scoped to quarter/region; outputs feed leadership review
• Account research brief — Analyze mode for quick intelligence before customer meetings

How this fits in Nimbus

RevOps sits between CRM data, forecast process, and leadership review. Connectors read CRM; workstreams scope each cycle; approvals gate any write-back.

flowchart LR
  CRM[CRM]
  Intel[Intelligence connector]
  Agent[Revenue agent]
  WS[Workstream]
  Approve[RevOps approval]
  Action[Action connector]

  CRM --> Intel --> Agent --> WS --> Approve --> Action --> CRM

Connector strategy for RevOps

flowchart TB
  P1[Phase 1 Intelligence]
  P2[Phase 2 Action]

  P1 --> Read[CRM read]
  P1 --> Analyze[Agent analysis]
  P1 --> Review[Human review]
  P2 --> Write[Approved CRM write]

Start with Intelligence connectors until your team is comfortable with approval flows. See Intelligence vs Action connectors.

Example scenario

RevOps scopes Q4 commit review, connects Salesforce, runs the Revenue agent in Plan mode, and routes forecast adjustments through a Hard checkpoint. Approved narrative lands in Outputs; CRM stage updates wait until Action connectors are enabled and a second approver signs off.

Governance tips for revenue data

• Treat pipeline and forecast workstreams as Hard checkpoint minimum before external sharing
• Restrict Action connector access to RevOps admins
• Use Connector and export rules to block unapproved CRM writes

FAQs {#faqs}

Q: Will Nimbus overwrite CRM fields automatically? A: Only via Action connectors after human approval. Intelligence connectors are read-only.

Q: Can we run analysis without consuming many NTUs? A: Use Analyze mode for lighter chart/summary work; Plan mode for multi-step governed runs with full quotes.

Q: How do we align with sales leadership on approvals? A: Add VPs to the workstream team and set approval count in Checkpoints and approvals.

Q: Which Revenue agents exist today? A: Browse the Workstreams filtered by Revenue — pipeline health and forecast accuracy are common entry points.

Q: Can marketing and sales share one workstream? A: Yes, when both teams need the same goal and approvers. Separate workstreams when objectives or data scope differ.