Concourse & Jira Cloud Portal
Put Simply:
If a user provides a valid Salesforce ID when starting the scoping process, we can use the linked product codes to directly identify the corresponding offerings that should be in scope. This allows us to bypass manual offering navigation and jump straight into confirming and refining the scope.
Why It Matters:
Accelerates scoping: Reduces manual steps by pulling offerings directly from Salesforce sales data.
Improves alignment with sales: Ensures scope matches what was sold, minimizing downstream discrepancies.
Reduces cognitive load: Guides users through a streamlined, pre-filtered path that feels personalized and accurate.
Supports scalable scoping: Ideal for enterprise sales processes where product codes are already standardized and mapped to offerings.
Enables smarter automation: This foundation supports automated scoping and future contract integration (e.g., Icertis).
What’s Needed:
Ability to accept and validate a Salesforce ID at the beginning of the scoping flow
Fetch associated product codes and engagement metadata
Friendly, confidence-building UX that shows users how offerings were selected
Allow users to override or manually add/remove offerings if needed
Not in Scope:
Mappings between Offerings and Product Codes are managed outside of the Concourse team.
