Role description
Business Analyst – Salesforce Revenue Cloud (ARM / RCA)
Cloudely, IncRole: Business Analyst – Salesforce Revenue Cloud (ARM / RCA)
Contract: 12+ Months
Location: Sunnyvale CA or Cleve Land, OH
Engagement Type: Discovery (6–8 weeks) with continuity into Implementation Delivery Model: Onsite‑led (US) with offshore engineering teams Platform: Salesforce Revenue Cloud / Agentforce RCA (ARM)
Role Objective
The Business Analyst will function as a Revenue Cloud functional architect–grade BA, responsible for converting complex, Excel‑driven pricing and quoting logic into Salesforce ARM / Revenue Cloud–ready functional specifications.
This role requires deep technical understanding of Revenue Cloud data models, pricing engines, guided selling, and decision logic, and the ability to translate real‑world commercial complexity into configurable Salesforce constructs, minimizing custom code.
Core Responsibilities (Technical)
- Revenue Cloud Functional Decomposition
Decompose end‑to‑end Quote‑to‑Cash (Q2C) flows into Revenue Cloud components:
Product Catalog & Price Books
Attribute‑based Product Configuration
Guided Selling Flows
Pricing Rules, Calculation Sequences, and Decision Tables
Contract, Amendment, Renewal, and Multi‑Year Structures
Define Revenue Cloud object‑level mappings, including:
Product, Price Dimension, Attribute, Rate Plan
Quote, Quote Line, Charge, Contract Line
Usage / Volume‑based constructs (where applicable)
- Complex Pricing & Calculation Logic Translation
Analyze and reverse‑engineer Excel pricing calculators, including:
Nested formulas and macros
Multi‑dimensional pricing drivers (volume, weight, capacity, geography)
Tiered, stepped, and threshold‑based pricing
Convert spreadsheet logic into:
ARM pricing rules
Decision tables / matrices
Calculation sequences with dependency ordering
Explicitly document calculation precedence, fallbacks, and exception handling.
- Guided Selling & Attribute Modeling
Define attribute taxonomy (technical, commercial, operational attributes).
Design guided selling flows that:
Dynamically drive attribute capture
Control product eligibility
Influence pricing and charge generation
Specify validation rules and constraints to prevent invalid configurations.
- Fit‑Gap Analysis at Feature Level
Conduct feature‑level fit‑gap analysis against ARM / Revenue Cloud capabilities:
Identify pure configuration vs extension vs custom logic
Clearly flag non‑standard requirements with impact assessment
Produce fit‑gap traceability from business requirement → Revenue Cloud feature → configuration artifact.
- Discovery Deliverables (Technical)
The BA is accountable for producing implementation‑ready artifacts, including:
Functional Architecture Diagrams (Q2C‑focused)
ARM / Revenue Cloud Configuration Blueprint
Pricing Logic Specification (rule‑by‑rule)
Attribute & Guided Selling Design
Functional Assumptions & Constraints Register
Risks tied to pricing complexity, data quality, and integration dependencies
- POC & Differentiation Support
Define POC scope limited to 1–2 high‑complexity use cases, not generic demos.
Specify exactly:
Which products
Which attributes
Which pricing rules
Which calculation outcomes
Ensure POC demonstrates non‑trivial pricing logic, not out‑of‑the‑box flows.
- Integration Awareness (Functional)
Identify functional integration touchpoints, including:
Upstream: CRM master data, product, customer
Downstream: Order Management, Billing, Fulfillment systems
Define functional integration assumptions, payload expectations, and sequencing (without owning technical design).
- Estimation & Implementation Enablement
Support ROM and WBS creation by:
Breaking down configuration vs extension effort
Highlighting pricing logic complexity drivers
Identifying test data and scenario explosion risks
Ensure discovery outputs allow engineering teams to start configuration immediately with minimal re‑interpretation.
Required Technical Skills (Non‑Negotiable)
Proven hands‑on experience with Salesforce CPQ / Revenue Cloud / ARM
Deep understanding of:
Attribute‑based pricing
Guided selling design
Decision tables and pricing rules
Ability to translate Excel macros and pricing sheets into system logic
Strong knowledge of Q2C domain models, not just CRM
Experience working alongside Solution Architects and Lead Developers in delivery programs
Strongly Preferred
Experience with services‑based or usage‑based pricing, not only product CPQ
Prior work in regulated or operations‑heavy domains
Experience supporting discovery‑to‑implementation continuity
Familiarity with multi‑year contracts, renewals, and amendments
What This Role Is NOT
Not a requirements note‑taker
Not a user‑story‑only BA
Not a generic CRM BA
Not a UI‑only or reporting‑focused role
Success Indicators
Pricing logic can be configured without repeated clarification cycles
Engineering teams can start ARM configuration directly from BA artifacts
Stakeholders trust the BA on what can and cannot be done out‑of‑the‑box
Discovery outputs materially reduce implementation risk and rework